On Monday 29 November 2010 12:17:22 pm Tom Jordahl wrote: > So if this is true, Macromedia (my and Glen Daniels employer at the time) > and now Adobe owns a copyright on Apache Axis code? We just didn't ask > the team to put this copyright in the code/NOTICE file? > > And Day (now Adobe) has copyrights on the JackRabbit code? > > And Sun (now Oracle) has copyrights on the tomcat code? > > But the license is all ASF.... > > Really?
Yes. Somewhat. With the CCLA and ICLA's, it's SLIGHTLY different. The patches on the JIRA are specifically granted to Apache under the terms of the Apache License which includes the "maintain NOTICES" clauses. (see Section 4, subsection b of the the Apache License: http://www.apache.org/licenses/LICENSE-2.0.txt) However, contributions directly from committers are under the terms of the ICLA: http://www.apache.org/licenses/icla.txt which is NOT the Apache License. It specifically says: 2. Grant of Copyright License. Subject to the terms and conditions of this Agreement, You hereby grant to the Foundation and to recipients of software distributed by the Foundation a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute Your Contributions and such derivative works. which makes no mention of maintaining or adding anything to the NOTICE files. Thus, even if Adobe or Sun/Oracle or whomever wanted stuff added to the NOTICE files about their copyrights, the above doesn't require that we maintain it. Apache can pretty much do whatever they want with code contributed via the ICLA, including completely relicensing it under a different license if they wanted to. Anyway, the important part is that it's a "Grant of Copyright License", not a "Grant of Copyright". The original author maintains the copyright. Dan > > Tom Jordahl > > > -----Original Message----- > From: Daniel Kulp [mailto:[email protected]] > Sent: Monday, November 29, 2010 12:09 PM > To: [email protected] > Cc: Tom Jordahl; Benson Margulies > Subject: Re: [VOTE] Release WSS4J 1.5.10 > > On Monday 29 November 2010 12:01:00 pm Tom Jordahl wrote: > > Arg! > > > > In order to submit a patch, isn't it a requirement that all rights of the > > patch be transferred over to the ASF? > > No. In fact, in almost no cases does code contributed to the ASF include > the copyright. When I make a commit to any code at the ASF, I (or my > employer if I'm doing it as a work for hire) maintain the copyright on the > code. HOWEVER, as part of my ICLA and my companies CCLA, the ASF is > granted a license to use the code. > > > I think we need to consult legal on this, because if the Innovation > > Center owns a copyright and/or license to the WSS4J code, that is not so > > good. > > This is no different. They maintain the copyright. However, when they > submitted it to the JIRA, they clicked on the tick box that says they > "Grant license to ASF for inclusion in ASF works (as per the Apache > License ยง5)". This is no different than the above. > > Dan > > > I would be -1 for accepting a patch that comes with copyrights. > > > > Tom Jordahl > > > > > > -----Original Message----- > > From: Daniel Kulp [mailto:[email protected]] > > Sent: Monday, November 29, 2010 10:51 AM > > To: [email protected] > > Cc: Benson Margulies > > Subject: Re: [VOTE] Release WSS4J 1.5.10 > > > > On Monday 29 November 2010 10:44:37 am Benson Margulies wrote: > > > Do we really have to credit patches? > > > > If they request it, yes. They hold the copyright on the material in > > that patch and, while they license it to us under the Apache License, > > the Apache License specifically states we need to keep notices intact > > that the copyright holders request/require. > > > > In this case, the submitter has asked that the copyright notice be in the > > NOTICE. Thus, we need to keep it there. > > > > Dan > > > > > On Mon, Nov 29, 2010 at 10:31 AM, Tom Jordahl <[email protected]> wrote: > > > > Conditional +1 (binding) > > > > > > > > I noticed that the NOTICE file has the following: > > > > > > > > "This product includes software Copyright University of Southampton > > > > IT Innovation Centre, 2006 (http://www.it-innovation.soton.ac.uk)." > > > > > > > > I couldn't figure out what software this was - if I am using > > > > wss4j-1.5.10.jar, do I have to worry about this? This should be > > > > removed or we should be clearer about what this means (i.e. what part > > > > do I need to exclude if I ship a product with wss4j in it). > > > > > > > > Also, the date in the NOTICE file is 2009, probably should be 2010. > > > > > > > > I only examined the binary zip, did not try to build the source. > > > > > > > > Tom Jordahl > > > > > > > > -----Original Message----- > > > > From: Colm O hEigeartaigh [mailto:[email protected]] > > > > Sent: Friday, November 26, 2010 12:17 PM > > > > To: [email protected] > > > > Subject: [VOTE] Release WSS4J 1.5.10 > > > > > > > > To the Apache Web Services Community, > > > > > > > > This is a call for votes for the wss4j-1.5.10 release. This release > > > > contains an upgrade to use XML Security 1.4.4, some important fixes > > > > for supporting chained certificates and processing SAML assertions, > > > > as well as a couple of other issues. > > > > > > > > The distribution was built from the following SVN tag; > > > > > > > > http://svn.apache.org/viewvc/webservices/wss4j/tags/1_5_10/ > > > > > > > > The distribution can be found at the following URL: > > > > > > > > http://people.apache.org/~coheigea/stage/wss4j/1.5.10/dist/ > > > > > > > > You can also point maven at the following URL to pull down the 1.5.10 > > > > release POM, source, and class JARs: > > > > > > > > http://people.apache.org/~coheigea/stage/wss4j/1.5.10/maven/ > > > > > > > > This vote will stay open for at least 72 hours. > > > > > > > > Here is my +1 (binding). > > > > > > > > Thanks, > > > > > > > > Colm. > > > > > > > > --------------------------------------------------------------------- > > > > To unsubscribe, e-mail: [email protected] > > > > For additional commands, e-mail: [email protected] > > > > > > > > > > > > --------------------------------------------------------------------- > > > > To unsubscribe, e-mail: [email protected] > > > > For additional commands, e-mail: [email protected] > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [email protected] > > > For additional commands, e-mail: [email protected] -- Daniel Kulp [email protected] http://dankulp.com/blog --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
