We are about 3 weeks away from generating a release candidate which must conform to a new, murky policy. These options occur to me:

1) Generate a release which follows the old policy. I would imagine that the DB PMC would feel bound to reject such a release.

2) Wait for the policy to sort itself out lazily. Do we have reason to believe that this issue will move forward imminently after several months' stagnation?

3) Actively seek clarification from the appropriate authorities now.

My gut feeling is that option (3) has the least risk attached to it.

Regards,
-Rick

Jean T. Anderson wrote:

David Van Couvering wrote:
I have to say I don't understand where we stand at this point.  If
anybody can give me a recipe of what I should be doing I would
appreciate it...

I suggest you hold off doing anything yet, and give this time to sort out.

-jean

David

Daniel John Debrunner (JIRA) wrote:

   [
http://issues.apache.org/jira/browse/DERBY-1377?page=comments#action_12422783
]             Daniel John Debrunner commented on DERBY-1377:
----------------------------------------------

The ASF claims copyright on the distribution, the collection of many
contributions from many, so that is one case where
 Copyright [yyyy] The Apache Software Foundation
is correct (though I'm not a laywer).

It's interesting to read through the discussion in legal-disucss
archives, follow the first [1] link Jean gave. One reading could be
that notices of the form:

Copyright [yyyy] The Apache Software Foundation

are being removed from source files because they are legally
incorrect, no copyright assignment at ASF.

Since Derby is a somewhat  new project it has been following the newer
policy( that Andrew pointed out) and thus has legally correct notices:

Copyright 1997, 2004 The Apache Software Foundation or its licensors,
as applicable.
Removing these might require the permission of the actual copyright
holders, which might be a pain to track down as to who has copyright
on each file (allowing multiple holders per file). The new ASF policy
does allow copyright notices to be left in the header (but would
prefer not to).



Update copyright headers to comply with new ASF policy
------------------------------------------------------

               Key: DERBY-1377
               URL: http://issues.apache.org/jira/browse/DERBY-1377
           Project: Derby
        Issue Type: Bug
        Components: Documentation
  Affects Versions: 10.2.0.0
          Reporter: Jean T. Anderson
       Assigned To: David Van Couvering
          Priority: Blocker
           Fix For: 10.2.0.0


A new copyright header policy will take effect for distributions
released starting on Sep 1, 2006. Committers will receive
notification, but a heads up with details is in the legal-discuss
thread starting with
http://mail-archives.apache.org/mod_mbox/www-legal-discuss/200606.mbox/[EMAIL 
PROTECTED]

Date was 1-Aug-2006, is now 1-Sep-2006:
http://mail-archives.apache.org/mod_mbox/www-legal-discuss/200607.mbox/[EMAIL 
PROTECTED]



Reply via email to