Re: LICENSE/NOTICE revisited (was Release Apache Marmotta 3.0.0-incubating (RC8))
Hi sebb, On 23/04/13 15:07, sebb wrote: On 23 April 2013 08:31, Sergio Fernández wrote: Right this would make the LICENCE files shorter. So, if I understood correctly, we should switch from licenses text to pointers No; it's not necessary to switch. Roy says that pointers are sufficient. He does not say they are necessary. From LEGAL-155: In any case, the intention is to allow use of whatever form seems most appropriate for the given distribution form, while still satisfying the legal requirements for each licensed work. Some projects will want to include all the text in one file. Others may not. Perfect, understood. Before properly reviewing the binary releases, in the PPMC we are discussing if such details we are discussing are something that MUST be fixed, or just something we SHOULD improve in upcoming releases. This is something I personally don't have clear now. Of course, we'll be wiling to fix whatever it is necessary; but at the same time we need to move on and continue working and improving the project. So... I would really appreciate any other vote, in one way or in the other, to know how we should proceed. Thanks! Cheers, -- Sergio Fernández Salzburg Research +43 662 2288 318 Jakob-Haringer Strasse 5/II A-5020 Salzburg (Austria) http://www.salzburgresearch.at - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: LICENSE/NOTICE revisited (was Release Apache Marmotta 3.0.0-incubating (RC8))
Not so fast about dispensing with Category B requirements for pointers to source code. In MPL 2.0, a common case, it is very clear that location of the source code is one of the requirements for distribution of the code in executable form or within a larger work (distributed in binary), that there must be identification of the origin of the code and where source code is available. It is insufficient to simply include the license (by reference or otherwise). MPL 2.0 has a handy Appendix (which I have never seen followed, but I don't get out much) that stipulates a suitable notice. The key is that it must be possible for a recipient of the executable to directly find the specific source code at a suitably archival location. This is also a requirement for distribution of most Category X works in binary form, and that applies in some cases where Category X licenses are bundled in binary distributions under sanitary conditions that satisfy ASF requirements. - Dennis PS: That these requirements are typically satisfied in the breach is not, it seems to me, something that is appropriate for the ASF to countenance. That there are projects out there that have never complied with such requirements is not justification. For me, it does not serve the public interest, nor does it demonstrate the care for the provenance of contributions (and dependencies) that should be the norm. Most of all, being careless about this undervalues the gift that such dependencies represent to projects that find reuse more convenient than not. PPS: There is also a forensic value to satisfying these license requirements. In these days of rapid disclosures of security flaws all over the landscape, it is important for a recipient of executable code to know whether or not vulnerability disclosures apply to dependencies in the distribution they are relying upon and whether mitigation is called for. (Although this is also of some benefit to adversaries, it must always be assumed that determined adversaries already know.) -Original Message- From: Sergio Fernández [mailto:sergio.fernan...@salzburgresearch.at] Sent: Tuesday, April 23, 2013 00:32 To: general@incubator.apache.org Cc: Marvin Humphrey Subject: Re: LICENSE/NOTICE revisited (was Release Apache Marmotta 3.0.0-incubating (RC8)) Hi Marvin, thanks for your time analysing our release. Please, find my reply inline. On 18/04/13 02:30, Marvin Humphrey wrote: On Wed, Apr 17, 2013 at 11:00 AM, Sebastian Schaffert wrote: [ ... ] - for dependencies of category B, [2] specifies that Although the source must not be included in Apache products, the NOTICE file, which is required to be included in each ASF distribution, must point to the source form of the included binary (more on that in the forthcoming Receiving and Releasing Contributions document)., a fact that is not mentioned in any of the other documents. This passage has somehow escaped my notice until now. Based on my understanding about the origins of the NOTICE file, it does not ring true. It seems to me that what works for category A should also work for category B: reference/quote the license in LICENSE and address mandatory attribution requirements in NOTICE. The goal is to satisfy the licensing requirements of the dependency, not to give credit -- so IMO linking only makes sense if that's a requirement of the dependency's license. So keep in NOTICE only those which require additional attribution requirements? Does anybody know any TLPs that are actually following the advice to link to source for category B dependencies in binary NOTICE files? [ ... ] - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept jclouds into the Apache Incubator
On Mon, Apr 22, 2013 at 3:39 PM, Rebecca Wood silky...@gmail.com wrote: Hello everyone, I am calling a VOTE for acceptance of jclouds into the Apache Incubator. The vote will close on Monday, April 29, 2013. [ ] +1 Accept jclouds into the Apache Incubator. [ ] +0 Don't care. [ ] -1 Don't accept jclouds into the Incubator because... +1 (binding) Thanks, Roman. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept jclouds into the Apache Incubator
+1 Accept jclouds into the Apache Incubator. On Tue, Apr 23, 2013 at 11:40 AM, Roman Shaposhnik r...@apache.org wrote: On Mon, Apr 22, 2013 at 3:39 PM, Rebecca Wood silky...@gmail.com wrote: Hello everyone, I am calling a VOTE for acceptance of jclouds into the Apache Incubator. The vote will close on Monday, April 29, 2013. [ ] +1 Accept jclouds into the Apache Incubator. [ ] +0 Don't care. [ ] -1 Don't accept jclouds into the Incubator because... +1 (binding) Thanks, Roman. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Davanum Srinivas :: http://davanum.wordpress.com
Re: Any podling need a non-mentor but recent graduate's help?
On Tue, Apr 23, 2013 at 03:36:08PM +0200, Christian Grobmeier wrote: Hello Chip, I think your help is highly appreciated. If I were you, I would look at the latest board reports and find out, which project report was not signed by a mentor. This might be an indicator that the project is in trouble. Do you know about the Shepherd model? Every reporting time folks are asked to make a crosscheck on various podling. This is also a good opportunity to find out who needs help. That said, the incubator misses a system to identify projects with lack of mentor support - you either need to ask or wait if somebody asks for help Cheers Christian OK, I'll check the board report. Good idea Christian. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: LICENSE/NOTICE revisited (was Release Apache Marmotta 3.0.0-incubating (RC8))
On Tue, Apr 23, 2013 at 8:39 AM, Dennis E. Hamilton orc...@apache.org wrote: Not so fast about dispensing with Category B requirements for pointers to source code. Thank you for the specific information about the MPL. What I said was this: The goal is to satisfy the licensing requirements of the dependency, not to give credit -- so IMO linking only makes sense if that's a requirement of the dependency's license. We must not treat linking as a requirement of ALL category B licenses because SOME of them require it. Marvin Humphrey - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: LICENSE/NOTICE revisited (was Release Apache Marmotta 3.0.0-incubating (RC8))
On 23 April 2013 18:05, Marvin Humphrey mar...@rectangular.com wrote: On Tue, Apr 23, 2013 at 8:39 AM, Dennis E. Hamilton orc...@apache.org wrote: Not so fast about dispensing with Category B requirements for pointers to source code. Thank you for the specific information about the MPL. What I said was this: The goal is to satisfy the licensing requirements of the dependency, not to give credit -- so IMO linking only makes sense if that's a requirement of the dependency's license. We must not treat linking as a requirement of ALL category B licenses because SOME of them require it. If the source code URL is required, then the question arises: does it *have* to go in the NOTICE file? Indeed is this one of the functions of the NOTICE file? Or should it be documented somewhere else? Marvin Humphrey
Re: [VOTE] Accept jclouds into the Apache Incubator
+1 -Brian On Mon, Apr 22, 2013 at 4:39 PM, Rebecca Wood silky...@gmail.com wrote: Hello everyone, I am calling a VOTE for acceptance of jclouds into the Apache Incubator. The vote will close on Monday, April 29, 2013. [ ] +1 Accept jclouds into the Apache Incubator. [ ] +0 Don't care. [ ] -1 Don't accept jclouds into the Incubator because... The full proposal is pasted below, and the corresponding wiki is http://wiki.apache.org/incubator/jcloudsProposal. Only VOTEs from Incubator PMC members are binding, but all are welcome to express their thoughts. Thanks, Becca Wood -- = jclouds Proposal for Apache Incubator = == Abstract == [[http://www.jclouds.org/|jclouds]] is an open source cloud agnostic library that enables developers to access a variety of supported cloud providers using one API. == Proposal == [[http://www.jclouds.org/|jclouds]] provides two portable API abstractions for cloud computing and cloud storage in the form of Java or Clojure libraries. By abstracting away vendor-specific details, jclouds supplies a solution for users to avoid lock-in to a specific cloud vendor. It also provisions hooks to make it easy to take advantage of specific features from those vendors. == Background == jclouds began in March of 2009 while Adrian Cole was working on the Amazon S3 plugin for Infinispan. He discovered that existing S3 libraries would not pass the concurrent test suite needed for write behind persistence. When it became clear that a new library was needed, jclouds formed as an independent project founded by Cole under the mentorship of Manik Surtani. The fledgling jclouds team soon encountered two portability issues: runtime portability with Google App Engine and compatibility with the similar cloud files service from Rackspace. The legacy of Google App Engine is still present within jclouds and is expressed by the 'driver' design which doesn't require threads. Supporting Rackspace started a legacy of cloud portability which would soon extend to provisioning. As jclouds supports newer and cutting edge cloud technologies, it is in a constant state of evolution. jclouds was founded in Shoreditch, London. The ensuing 4 months backpacking between European Java User Groups accounts for the initial population of European developers and users within the community. The initial contributors to jclouds included Adrian Cole, James Murty, Andrew Newdigate, and Andrew Phillips. Manik Surtani served as a mentor, and there were a number of other advisers as well. == Rationale == There are many providers that offer IaaS clouds, but few APIs that can bridge the gap between cloud providers. jclouds supplies an abstraction layer for both compute and storage resources that makes it easy to work with many different cloud APIs using a simple and singular API. jclouds provides this abstraction layer for the Java and Clojure communities. It is a unique niche within the cloud community. jclouds provides the write once, run anywhere concept when utilizing infrastructure cloud resources. == Initial Goals == * Build a more centralized community pulling together jclouds developers, jclouds integrators, and service providers who use jclouds. * Although jclouds has a fairly collaborative community, the committers wish to further bridge the gap between developers and community by encouraging more community involvement in development processes. * Break down from a monolithic release process into one that is more decentrilized. * Bring the jclouds core code base consisting of ComputeService and Blobstore into Apache. * jclouds will not move all existing provider code into Apache. The goal is to move the provider code for those clouds that have complete portability and are tried, tested, and true. This includes code for OpenStack, Amazon EC2, and Google Cloud. == Current Status == === Meritocracy === jclouds has an active community of contributors who are encouraged to become full-fledged jclouds committers. A jclouds committer understands the importance of seeking community feedback, actively listening to suggestions, and fostering relationships with community members who make contributions. The entirety of jclouds is built upon the relationships that have been built with community members. This camaraderie will continue to be promoted as jclouds is introduced into the Incubator and beyond. jclouds encourages involvement from its community members, and the issues are open and available to any developers who wish to contribute to the project. The jclouds team currently seeks help and asks for suggestions utilizing the jclouds and jclouds-dev Google groups and IRC on irc.freenode.net#jclouds. Any and all submissions for changes are reviewed and taken into consideration. === Community === jclouds has a highly active and growing community of users and developers. The community is currently fostered at
Re: [VOTE] Accept jclouds into the Apache Incubator
+1 (binding) Regards JB On 04/23/2013 10:40 AM, Andrei Savu wrote: +1 (non-binding) -- Andrei Savu On Tue, Apr 23, 2013 at 9:40 AM, Tomaz Muraus to...@apache.org wrote: +1 (binding) On Apr 22, 2013 3:39 PM, Rebecca Wood silky...@gmail.com wrote: Hello everyone, I am calling a VOTE for acceptance of jclouds into the Apache Incubator. The vote will close on Monday, April 29, 2013. [ ] +1 Accept jclouds into the Apache Incubator. [ ] +0 Don't care. [ ] -1 Don't accept jclouds into the Incubator because... The full proposal is pasted below, and the corresponding wiki is http://wiki.apache.org/incubator/jcloudsProposal. Only VOTEs from Incubator PMC members are binding, but all are welcome to express their thoughts. Thanks, Becca Wood -- = jclouds Proposal for Apache Incubator = == Abstract == [[http://www.jclouds.org/|jclouds]] is an open source cloud agnostic library that enables developers to access a variety of supported cloud providers using one API. == Proposal == [[http://www.jclouds.org/|jclouds]] provides two portable API abstractions for cloud computing and cloud storage in the form of Java or Clojure libraries. By abstracting away vendor-specific details, jclouds supplies a solution for users to avoid lock-in to a specific cloud vendor. It also provisions hooks to make it easy to take advantage of specific features from those vendors. == Background == jclouds began in March of 2009 while Adrian Cole was working on the Amazon S3 plugin for Infinispan. He discovered that existing S3 libraries would not pass the concurrent test suite needed for write behind persistence. When it became clear that a new library was needed, jclouds formed as an independent project founded by Cole under the mentorship of Manik Surtani. The fledgling jclouds team soon encountered two portability issues: runtime portability with Google App Engine and compatibility with the similar cloud files service from Rackspace. The legacy of Google App Engine is still present within jclouds and is expressed by the 'driver' design which doesn't require threads. Supporting Rackspace started a legacy of cloud portability which would soon extend to provisioning. As jclouds supports newer and cutting edge cloud technologies, it is in a constant state of evolution. jclouds was founded in Shoreditch, London. The ensuing 4 months backpacking between European Java User Groups accounts for the initial population of European developers and users within the community. The initial contributors to jclouds included Adrian Cole, James Murty, Andrew Newdigate, and Andrew Phillips. Manik Surtani served as a mentor, and there were a number of other advisers as well. == Rationale == There are many providers that offer IaaS clouds, but few APIs that can bridge the gap between cloud providers. jclouds supplies an abstraction layer for both compute and storage resources that makes it easy to work with many different cloud APIs using a simple and singular API. jclouds provides this abstraction layer for the Java and Clojure communities. It is a unique niche within the cloud community. jclouds provides the write once, run anywhere concept when utilizing infrastructure cloud resources. == Initial Goals == * Build a more centralized community pulling together jclouds developers, jclouds integrators, and service providers who use jclouds. * Although jclouds has a fairly collaborative community, the committers wish to further bridge the gap between developers and community by encouraging more community involvement in development processes. * Break down from a monolithic release process into one that is more decentrilized. * Bring the jclouds core code base consisting of ComputeService and Blobstore into Apache. * jclouds will not move all existing provider code into Apache. The goal is to move the provider code for those clouds that have complete portability and are tried, tested, and true. This includes code for OpenStack, Amazon EC2, and Google Cloud. == Current Status == === Meritocracy === jclouds has an active community of contributors who are encouraged to become full-fledged jclouds committers. A jclouds committer understands the importance of seeking community feedback, actively listening to suggestions, and fostering relationships with community members who make contributions. The entirety of jclouds is built upon the relationships that have been built with community members. This camaraderie will continue to be promoted as jclouds is introduced into the Incubator and beyond. jclouds encourages involvement from its community members, and the issues are open and available to any developers who wish to contribute to the project. The jclouds team currently seeks help and asks for suggestions utilizing the jclouds and jclouds-dev Google groups and IRC on irc.freenode.net#jclouds. Any and all submissions for changes are reviewed and taken into consideration. === Community === jclouds
Re: [VOTE] Accept jclouds into the Apache Incubator
+1 Tom On Mon, Apr 22, 2013 at 11:39 PM, Rebecca Wood silky...@gmail.com wrote: Hello everyone, I am calling a VOTE for acceptance of jclouds into the Apache Incubator. The vote will close on Monday, April 29, 2013. [ ] +1 Accept jclouds into the Apache Incubator. [ ] +0 Don't care. [ ] -1 Don't accept jclouds into the Incubator because... The full proposal is pasted below, and the corresponding wiki is http://wiki.apache.org/incubator/jcloudsProposal. Only VOTEs from Incubator PMC members are binding, but all are welcome to express their thoughts. Thanks, Becca Wood -- = jclouds Proposal for Apache Incubator = == Abstract == [[http://www.jclouds.org/|jclouds]] is an open source cloud agnostic library that enables developers to access a variety of supported cloud providers using one API. == Proposal == [[http://www.jclouds.org/|jclouds]] provides two portable API abstractions for cloud computing and cloud storage in the form of Java or Clojure libraries. By abstracting away vendor-specific details, jclouds supplies a solution for users to avoid lock-in to a specific cloud vendor. It also provisions hooks to make it easy to take advantage of specific features from those vendors. == Background == jclouds began in March of 2009 while Adrian Cole was working on the Amazon S3 plugin for Infinispan. He discovered that existing S3 libraries would not pass the concurrent test suite needed for write behind persistence. When it became clear that a new library was needed, jclouds formed as an independent project founded by Cole under the mentorship of Manik Surtani. The fledgling jclouds team soon encountered two portability issues: runtime portability with Google App Engine and compatibility with the similar cloud files service from Rackspace. The legacy of Google App Engine is still present within jclouds and is expressed by the 'driver' design which doesn't require threads. Supporting Rackspace started a legacy of cloud portability which would soon extend to provisioning. As jclouds supports newer and cutting edge cloud technologies, it is in a constant state of evolution. jclouds was founded in Shoreditch, London. The ensuing 4 months backpacking between European Java User Groups accounts for the initial population of European developers and users within the community. The initial contributors to jclouds included Adrian Cole, James Murty, Andrew Newdigate, and Andrew Phillips. Manik Surtani served as a mentor, and there were a number of other advisers as well. == Rationale == There are many providers that offer IaaS clouds, but few APIs that can bridge the gap between cloud providers. jclouds supplies an abstraction layer for both compute and storage resources that makes it easy to work with many different cloud APIs using a simple and singular API. jclouds provides this abstraction layer for the Java and Clojure communities. It is a unique niche within the cloud community. jclouds provides the write once, run anywhere concept when utilizing infrastructure cloud resources. == Initial Goals == * Build a more centralized community pulling together jclouds developers, jclouds integrators, and service providers who use jclouds. * Although jclouds has a fairly collaborative community, the committers wish to further bridge the gap between developers and community by encouraging more community involvement in development processes. * Break down from a monolithic release process into one that is more decentrilized. * Bring the jclouds core code base consisting of ComputeService and Blobstore into Apache. * jclouds will not move all existing provider code into Apache. The goal is to move the provider code for those clouds that have complete portability and are tried, tested, and true. This includes code for OpenStack, Amazon EC2, and Google Cloud. == Current Status == === Meritocracy === jclouds has an active community of contributors who are encouraged to become full-fledged jclouds committers. A jclouds committer understands the importance of seeking community feedback, actively listening to suggestions, and fostering relationships with community members who make contributions. The entirety of jclouds is built upon the relationships that have been built with community members. This camaraderie will continue to be promoted as jclouds is introduced into the Incubator and beyond. jclouds encourages involvement from its community members, and the issues are open and available to any developers who wish to contribute to the project. The jclouds team currently seeks help and asks for suggestions utilizing the jclouds and jclouds-dev Google groups and IRC on irc.freenode.net#jclouds. Any and all submissions for changes are reviewed and taken into consideration. === Community === jclouds has a highly active and growing community of users and developers. The community is currently fostered at
Karma request for IP clearance management
Hi, I'm the chair of the Apache Lucene PMC, and we've received an offer to donate software to the Lucene Core project. See https://issues.apache.org/jira/browse/LUCENE-4947. I'll be managing the IP clearance process. I've partially filled out the XML form to track the process, and added an entry to the index.xml page rendered at http://incubator.apache.org/ip-clearance/, and then committed both of these, so I apparently already have karma to commit under https://svn.apache.org/repos/asf/incubator/public/trunk/content/ip-clearance/. However, when I attempt to publish the website, by clicking the Submit button here: https://cms.apache.org/incubator/publish, I get: svnmucc: E175013: Access to '/repos/infra/!svn/txr/859641-ighy/websites/production/incubator/content' forbidden Can someone either publish the site for me, or grant me karma to do so myself? (Since I'll be recording activity in the clearance form incrementally, I'll want to publish the site proabably at least a couple more times.) Thanks for your help, Steve Rowe - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: LICENSE/NOTICE revisited (was Release Apache Marmotta 3.0.0-incubating (RC8))
I agree, I didn't mean to generalize about Category B notice requirements. With regard to there being a standard notice for MPL, I was careless. MPL 1.1 had a template notice. MPL 2.0 just has section 3.2(a): If You distribute Covered Software in Executable Form then: a. such Covered Software must also be made available in Source Code Form, as described in Section 3.1, and You must inform recipients of the Executable Form how they can obtain a copy of such Source Code Form by reasonable means in a timely manner, at a charge no more than the cost of distribution to the recipient; [...] The license is careful to discriminate between Source Code Form and Executable Form, and there is little detail on notifications associated with an Executable Form for MPL 2.0. I would think that providing the information in NOTICE satisfies the requirement. It would be much easier than coming up with another artifact beside LICENSE and NOTICE, which knowledgable folks already know to look for. I don't have any insight on dealing with the fact that the dependency is build-specific, however the information is provided. - Dennis -Original Message- From: sebb [mailto:seb...@gmail.com] Sent: Tuesday, April 23, 2013 10:43 To: Marvin Humphrey Cc: orc...@apache.org; Sergio Fernández; Roy T. Fielding; general@incubator.apache.org Subject: Re: LICENSE/NOTICE revisited (was Release Apache Marmotta 3.0.0-incubating (RC8)) On 23 April 2013 18:05, Marvin Humphrey mar...@rectangular.com wrote: On Tue, Apr 23, 2013 at 8:39 AM, Dennis E. Hamilton orc...@apache.org wrote: Not so fast about dispensing with Category B requirements for pointers to source code. Thank you for the specific information about the MPL. What I said was this: The goal is to satisfy the licensing requirements of the dependency, not to give credit -- so IMO linking only makes sense if that's a requirement of the dependency's license. We must not treat linking as a requirement of ALL category B licenses because SOME of them require it. If the source code URL is required, then the question arises: does it *have* to go in the NOTICE file? Indeed is this one of the functions of the NOTICE file? Or should it be documented somewhere else? Marvin Humphrey - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[CANCEL][VOTE] Apache Ambari (incubating) 1.2.1 Release Candidate RC0.
Closing out this vote for the votes monitor to catch. 1.2.1 RC1 was voted on and released quite some time back. -- Hitesh - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: LICENSE/NOTICE revisited (was Release Apache Marmotta 3.0.0-incubating (RC8))
On Tue, Apr 23, 2013 at 12:31 AM, Sergio Fernández sergio.fernan...@salzburgresearch.at wrote: Here's Roy Fielding, ASF Board member and author of the Apache License 2.0: http://s.apache.org/Hqj Pointers are sufficient. Roy elaborates here: http://s.apache.org/Iw6 By pointers, I mean a relative path reference to the license file within some subdirectory of the package being redistributed. Right this would make the LICENCE files shorter. So, if I understood correctly, we should switch from licenses text to pointers, something like: For the D3.js component, located at: path/to/foo/ Copyright (c) 2013 Foo Author, http://foo.net License at: path/to/foo/LICENSE Would be that fine? As sebb notes, it's fine either way. - for dependencies of category B, [2] specifies that Although the source must not be included in Apache products, the NOTICE file, which is required to be included in each ASF distribution, must point to the source form of the included binary (more on that in the forthcoming Receiving and Releasing Contributions document)., a fact that is not mentioned in any of the other documents. This passage has somehow escaped my notice until now. Based on my understanding about the origins of the NOTICE file, it does not ring true. It seems to me that what works for category A should also work for category B: reference/quote the license in LICENSE and address mandatory attribution requirements in NOTICE. The goal is to satisfy the licensing requirements of the dependency, not to give credit -- so IMO linking only makes sense if that's a requirement of the dependency's license. So keep in NOTICE only those which require additional attribution requirements? The answer as to whether a dependency requires something in NOTICE varies according on its license. There's no official definition anywhere as to what additional attribution requirements might mean, so I can't answer directly. What I can say is: * Don't put anything in NOTICE for the sake of an MIT-licensed dependency. * Don't put anything in NOTICE for the sake of a three-clause BSD dependency. * For an ALv2 dependency, follow the instructions in the licensing howto. * For all other licenses, either guess :( or ask. I say guess because that's what the ASF currently forces PMCs to do, not because it's a good idea. With the exception of MIT, three-clause BSD, and ALv2, we don't yet have documentation about what various licenses require as far as NOTICE. Assembling that information will take time. We'll probably need to open an individual LEGAL Jira issues for each license, e.g. Does bundling a dependency under the Python Software Foundation license require any additions to the ALv2 NOTICE file? http://opensource.org/licenses/PythonSoftFoundation.php Does anybody know any TLPs that are actually following the advice to link to source for category B dependencies in binary NOTICE files? Not sure if it is what you are looking, but we are doing it in a quite similar way that CouchDB, since they have a quite similar setup. See its NOTICE at: https://svn.apache.org/repos/asf/couchdb/trunk/NOTICE Thanks for that. At a glance, many of those dependencies seem to be available under MIT and three-clause BSD licenses, so inclusion in NOTICE at all is unnecessary. The CouchDB folks would be getting the same critique as Marmotta if their NOTICE came through here today. Third, if you get complaints about your RC, you can blame the howto. :) We blame ourselves ;-) Well, that stinks. :P The Marmotta community -- both core developers and Mentors -- worked really hard to get this right. The amount of effort you folks put in should have been enough. Perhaps I should go provide a patch to Solr. But I have a question -- if Solr's NOTICE had been empty, would you have kept looking at TLP NOTICE files until you found one that had the examples you were looking for? True :-) I don't relish the prospect of sweeping through TLP licensing, but if podlings continue to be misled by poor examples, that's what we'll need to do. Probably auditing a dozen of our highest profile projects would go a long way. Before properly reviewing the binary releases, in the PPMC we are discussing if such details we are discussing are something that MUST be fixed, or just something we SHOULD improve in upcoming releases. This is something I personally don't have clear now. The inclusion of unnecessary information in NOTICE is a licensing documentation bug. It makes life harder for downstream consumers of your product who are reading LICENSE and NOTICE and trying to ensure that they comply with our licensing requirements. Personally, I don't intend to vote -1 on this specific Marmotta release candidate because of the NOTICE file. You worked hard to follow the instructions as best you could. The Incubator had its *own* documentation bug, and
Re: [VOTE] Accept jclouds into the Apache Incubator
On Apr 22, 2013, at 3:39 PM, Rebecca Wood silky...@gmail.com wrote: Hello everyone, I am calling a VOTE for acceptance of jclouds into the Apache Incubator. The vote will close on Monday, April 29, 2013. [ ] +1 Accept jclouds into the Apache Incubator. [ ] +0 Don't care. [ ] -1 Don't accept jclouds into the Incubator because... The full proposal is pasted below, and the corresponding wiki is http://wiki.apache.org/incubator/jcloudsProposal. Only VOTEs from Incubator PMC members are binding, but all are welcome to express their thoughts. +1 binding Regards, Alan - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept jclouds into the Apache Incubator
+1 (not binding) Il giorno 23/apr/2013 07:41, Ashish paliwalash...@gmail.com ha scritto: +1 (non-binding) On Tue, Apr 23, 2013 at 4:09 AM, Rebecca Wood silky...@gmail.com wrote: Hello everyone, I am calling a VOTE for acceptance of jclouds into the Apache Incubator. The vote will close on Monday, April 29, 2013. [ ] +1 Accept jclouds into the Apache Incubator. [ ] +0 Don't care. [ ] -1 Don't accept jclouds into the Incubator because... The full proposal is pasted below, and the corresponding wiki is http://wiki.apache.org/incubator/jcloudsProposal. Only VOTEs from Incubator PMC members are binding, but all are welcome to express their thoughts. Thanks, Becca Wood -- = jclouds Proposal for Apache Incubator = == Abstract == [[http://www.jclouds.org/|jclouds]] is an open source cloud agnostic library that enables developers to access a variety of supported cloud providers using one API. == Proposal == [[http://www.jclouds.org/|jclouds]] provides two portable API abstractions for cloud computing and cloud storage in the form of Java or Clojure libraries. By abstracting away vendor-specific details, jclouds supplies a solution for users to avoid lock-in to a specific cloud vendor. It also provisions hooks to make it easy to take advantage of specific features from those vendors. == Background == jclouds began in March of 2009 while Adrian Cole was working on the Amazon S3 plugin for Infinispan. He discovered that existing S3 libraries would not pass the concurrent test suite needed for write behind persistence. When it became clear that a new library was needed, jclouds formed as an independent project founded by Cole under the mentorship of Manik Surtani. The fledgling jclouds team soon encountered two portability issues: runtime portability with Google App Engine and compatibility with the similar cloud files service from Rackspace. The legacy of Google App Engine is still present within jclouds and is expressed by the 'driver' design which doesn't require threads. Supporting Rackspace started a legacy of cloud portability which would soon extend to provisioning. As jclouds supports newer and cutting edge cloud technologies, it is in a constant state of evolution. jclouds was founded in Shoreditch, London. The ensuing 4 months backpacking between European Java User Groups accounts for the initial population of European developers and users within the community. The initial contributors to jclouds included Adrian Cole, James Murty, Andrew Newdigate, and Andrew Phillips. Manik Surtani served as a mentor, and there were a number of other advisers as well. == Rationale == There are many providers that offer IaaS clouds, but few APIs that can bridge the gap between cloud providers. jclouds supplies an abstraction layer for both compute and storage resources that makes it easy to work with many different cloud APIs using a simple and singular API. jclouds provides this abstraction layer for the Java and Clojure communities. It is a unique niche within the cloud community. jclouds provides the write once, run anywhere concept when utilizing infrastructure cloud resources. == Initial Goals == * Build a more centralized community pulling together jclouds developers, jclouds integrators, and service providers who use jclouds. * Although jclouds has a fairly collaborative community, the committers wish to further bridge the gap between developers and community by encouraging more community involvement in development processes. * Break down from a monolithic release process into one that is more decentrilized. * Bring the jclouds core code base consisting of ComputeService and Blobstore into Apache. * jclouds will not move all existing provider code into Apache. The goal is to move the provider code for those clouds that have complete portability and are tried, tested, and true. This includes code for OpenStack, Amazon EC2, and Google Cloud. == Current Status == === Meritocracy === jclouds has an active community of contributors who are encouraged to become full-fledged jclouds committers. A jclouds committer understands the importance of seeking community feedback, actively listening to suggestions, and fostering relationships with community members who make contributions. The entirety of jclouds is built upon the relationships that have been built with community members. This camaraderie will continue to be promoted as jclouds is introduced into the Incubator and beyond. jclouds encourages involvement from its community members, and the issues are open and available to any developers who wish to contribute to the project. The jclouds team currently seeks help and asks for suggestions utilizing the jclouds and jclouds-dev Google groups and IRC on irc.freenode.net#jclouds. Any
Re: [VOTE] Accept jclouds into the Apache Incubator
On Tue, Apr 23, 2013 at 12:39 AM, Rebecca Wood silky...@gmail.com wrote: Hello everyone, I am calling a VOTE for acceptance of jclouds into the Apache Incubator. +1 (binding) Best Regards, Nandana
Re: [VOTE] Accept jclouds into the Apache Incubator
+1 (binding) On Apr 22, 2013 3:39 PM, Rebecca Wood silky...@gmail.com wrote: Hello everyone, I am calling a VOTE for acceptance of jclouds into the Apache Incubator. The vote will close on Monday, April 29, 2013. [ ] +1 Accept jclouds into the Apache Incubator. [ ] +0 Don't care. [ ] -1 Don't accept jclouds into the Incubator because... The full proposal is pasted below, and the corresponding wiki is http://wiki.apache.org/incubator/jcloudsProposal. Only VOTEs from Incubator PMC members are binding, but all are welcome to express their thoughts. Thanks, Becca Wood -- = jclouds Proposal for Apache Incubator = == Abstract == [[http://www.jclouds.org/|jclouds]] is an open source cloud agnostic library that enables developers to access a variety of supported cloud providers using one API. == Proposal == [[http://www.jclouds.org/|jclouds]] provides two portable API abstractions for cloud computing and cloud storage in the form of Java or Clojure libraries. By abstracting away vendor-specific details, jclouds supplies a solution for users to avoid lock-in to a specific cloud vendor. It also provisions hooks to make it easy to take advantage of specific features from those vendors. == Background == jclouds began in March of 2009 while Adrian Cole was working on the Amazon S3 plugin for Infinispan. He discovered that existing S3 libraries would not pass the concurrent test suite needed for write behind persistence. When it became clear that a new library was needed, jclouds formed as an independent project founded by Cole under the mentorship of Manik Surtani. The fledgling jclouds team soon encountered two portability issues: runtime portability with Google App Engine and compatibility with the similar cloud files service from Rackspace. The legacy of Google App Engine is still present within jclouds and is expressed by the 'driver' design which doesn't require threads. Supporting Rackspace started a legacy of cloud portability which would soon extend to provisioning. As jclouds supports newer and cutting edge cloud technologies, it is in a constant state of evolution. jclouds was founded in Shoreditch, London. The ensuing 4 months backpacking between European Java User Groups accounts for the initial population of European developers and users within the community. The initial contributors to jclouds included Adrian Cole, James Murty, Andrew Newdigate, and Andrew Phillips. Manik Surtani served as a mentor, and there were a number of other advisers as well. == Rationale == There are many providers that offer IaaS clouds, but few APIs that can bridge the gap between cloud providers. jclouds supplies an abstraction layer for both compute and storage resources that makes it easy to work with many different cloud APIs using a simple and singular API. jclouds provides this abstraction layer for the Java and Clojure communities. It is a unique niche within the cloud community. jclouds provides the write once, run anywhere concept when utilizing infrastructure cloud resources. == Initial Goals == * Build a more centralized community pulling together jclouds developers, jclouds integrators, and service providers who use jclouds. * Although jclouds has a fairly collaborative community, the committers wish to further bridge the gap between developers and community by encouraging more community involvement in development processes. * Break down from a monolithic release process into one that is more decentrilized. * Bring the jclouds core code base consisting of ComputeService and Blobstore into Apache. * jclouds will not move all existing provider code into Apache. The goal is to move the provider code for those clouds that have complete portability and are tried, tested, and true. This includes code for OpenStack, Amazon EC2, and Google Cloud. == Current Status == === Meritocracy === jclouds has an active community of contributors who are encouraged to become full-fledged jclouds committers. A jclouds committer understands the importance of seeking community feedback, actively listening to suggestions, and fostering relationships with community members who make contributions. The entirety of jclouds is built upon the relationships that have been built with community members. This camaraderie will continue to be promoted as jclouds is introduced into the Incubator and beyond. jclouds encourages involvement from its community members, and the issues are open and available to any developers who wish to contribute to the project. The jclouds team currently seeks help and asks for suggestions utilizing the jclouds and jclouds-dev Google groups and IRC on irc.freenode.net#jclouds. Any and all submissions for changes are reviewed and taken into consideration. === Community === jclouds has a highly active and growing community of users and developers. The community is currently fostered at
Re: LICENSE/NOTICE revisited (was Release Apache Marmotta 3.0.0-incubating (RC8))
Hi Marvin, thanks for your time analysing our release. Please, find my reply inline. On 18/04/13 02:30, Marvin Humphrey wrote: On Wed, Apr 17, 2013 at 11:00 AM, Sebastian Schaffert wrote: - The section NOTICE file in [3] says that The NOTICE file may also include copyright notices moved from source files submitted to the ASF. The 3rd party Javascript files we include are submitted to the ASF, but they are often under MIT license and therefore category A in [2]. If I read the document correctly, category A only requires to include notices if a NOTICE file is contained in the product. According to [1], MIT and New BSD even can have a reduced entry in LICENSE. [4] says, however, that All the licenses on all the files to be included within a package should be included in the LICENSE document. Here's Roy Fielding, ASF Board member and author of the Apache License 2.0: http://s.apache.org/Hqj Pointers are sufficient. Roy elaborates here: http://s.apache.org/Iw6 By pointers, I mean a relative path reference to the license file within some subdirectory of the package being redistributed. Right this would make the LICENCE files shorter. So, if I understood correctly, we should switch from licenses text to pointers, something like: For the D3.js component, located at: path/to/foo/ Copyright (c) 2013 Foo Author, http://foo.net License at: path/to/foo/LICENSE Would be that fine? - for dependencies of category B, [2] specifies that Although the source must not be included in Apache products, the NOTICE file, which is required to be included in each ASF distribution, must point to the source form of the included binary (more on that in the forthcoming Receiving and Releasing Contributions document)., a fact that is not mentioned in any of the other documents. This passage has somehow escaped my notice until now. Based on my understanding about the origins of the NOTICE file, it does not ring true. It seems to me that what works for category A should also work for category B: reference/quote the license in LICENSE and address mandatory attribution requirements in NOTICE. The goal is to satisfy the licensing requirements of the dependency, not to give credit -- so IMO linking only makes sense if that's a requirement of the dependency's license. So keep in NOTICE only those which require additional attribution requirements? Does anybody know any TLPs that are actually following the advice to link to source for category B dependencies in binary NOTICE files? Not sure if it is what you are looking, but we are doing it in a quite similar way that CouchDB, since they have a quite similar setup. See its NOTICE at: https://svn.apache.org/repos/asf/couchdb/trunk/NOTICE I suspect we will want to bring this up on legal-discuss and see if we can't get that recommendation removed. - The labelling requirement source access in [2] requires that the NOTICE file contains pointers to the location of the source code for any 3rd party library that is bundled in a binary distribution (not only category B). [1] on the other hand does not mention this requirement and says that everything that is not legally necessary does not belong into NOTICE. Here's Roy again: http://s.apache.org/ZEA Hey, I'm all for people having opinions on development and credits and documentation. NOTICE and LICENSE are none of those. They are not open to anyone's opinions other than the copyright owners that require such notices, and they must not be added where they are not required. Each additional notice places a burden on the ASF and all downstream redistributors. Please, folks, I am not even a Sling committer. I am speaking as the author of the Apache License. Don't screw with what I have changed. I have way more experience in these matters than everyone else at the ASF combined. If you put stuff in NOTICE that is not legally required to be there, I will remove it as an officer of the ASF. If you add it back in, I will have to duplicate the effort of removing it again. That will not make me a happy camper. It seems that we might want to make the language in the licensing howto similarly scary in order to dissuade people from adding unnecessary copyright notices to NOTICE. ;) +1 First, if the Incubator can make this task formulaic, success will be more predictable and achievable for individual podlings. Actually now it is not, at least from my point of view. Too many subjective opinions open a huge window for potential errors. Second, there is not exactly one right way to handle licensing, but it is costly to debate the merits of legitimate alternatives. We'll all be better off if we can find one way that works and stick to it. We understand that. Every single project has concrete details that need to be addressed. But similar project should
Re: [VOTE] Accept jclouds into the Apache Incubator
+1 (non-binding) -- Andrei Savu On Tue, Apr 23, 2013 at 9:40 AM, Tomaz Muraus to...@apache.org wrote: +1 (binding) On Apr 22, 2013 3:39 PM, Rebecca Wood silky...@gmail.com wrote: Hello everyone, I am calling a VOTE for acceptance of jclouds into the Apache Incubator. The vote will close on Monday, April 29, 2013. [ ] +1 Accept jclouds into the Apache Incubator. [ ] +0 Don't care. [ ] -1 Don't accept jclouds into the Incubator because... The full proposal is pasted below, and the corresponding wiki is http://wiki.apache.org/incubator/jcloudsProposal. Only VOTEs from Incubator PMC members are binding, but all are welcome to express their thoughts. Thanks, Becca Wood -- = jclouds Proposal for Apache Incubator = == Abstract == [[http://www.jclouds.org/|jclouds]] is an open source cloud agnostic library that enables developers to access a variety of supported cloud providers using one API. == Proposal == [[http://www.jclouds.org/|jclouds]] provides two portable API abstractions for cloud computing and cloud storage in the form of Java or Clojure libraries. By abstracting away vendor-specific details, jclouds supplies a solution for users to avoid lock-in to a specific cloud vendor. It also provisions hooks to make it easy to take advantage of specific features from those vendors. == Background == jclouds began in March of 2009 while Adrian Cole was working on the Amazon S3 plugin for Infinispan. He discovered that existing S3 libraries would not pass the concurrent test suite needed for write behind persistence. When it became clear that a new library was needed, jclouds formed as an independent project founded by Cole under the mentorship of Manik Surtani. The fledgling jclouds team soon encountered two portability issues: runtime portability with Google App Engine and compatibility with the similar cloud files service from Rackspace. The legacy of Google App Engine is still present within jclouds and is expressed by the 'driver' design which doesn't require threads. Supporting Rackspace started a legacy of cloud portability which would soon extend to provisioning. As jclouds supports newer and cutting edge cloud technologies, it is in a constant state of evolution. jclouds was founded in Shoreditch, London. The ensuing 4 months backpacking between European Java User Groups accounts for the initial population of European developers and users within the community. The initial contributors to jclouds included Adrian Cole, James Murty, Andrew Newdigate, and Andrew Phillips. Manik Surtani served as a mentor, and there were a number of other advisers as well. == Rationale == There are many providers that offer IaaS clouds, but few APIs that can bridge the gap between cloud providers. jclouds supplies an abstraction layer for both compute and storage resources that makes it easy to work with many different cloud APIs using a simple and singular API. jclouds provides this abstraction layer for the Java and Clojure communities. It is a unique niche within the cloud community. jclouds provides the write once, run anywhere concept when utilizing infrastructure cloud resources. == Initial Goals == * Build a more centralized community pulling together jclouds developers, jclouds integrators, and service providers who use jclouds. * Although jclouds has a fairly collaborative community, the committers wish to further bridge the gap between developers and community by encouraging more community involvement in development processes. * Break down from a monolithic release process into one that is more decentrilized. * Bring the jclouds core code base consisting of ComputeService and Blobstore into Apache. * jclouds will not move all existing provider code into Apache. The goal is to move the provider code for those clouds that have complete portability and are tried, tested, and true. This includes code for OpenStack, Amazon EC2, and Google Cloud. == Current Status == === Meritocracy === jclouds has an active community of contributors who are encouraged to become full-fledged jclouds committers. A jclouds committer understands the importance of seeking community feedback, actively listening to suggestions, and fostering relationships with community members who make contributions. The entirety of jclouds is built upon the relationships that have been built with community members. This camaraderie will continue to be promoted as jclouds is introduced into the Incubator and beyond. jclouds encourages involvement from its community members, and the issues are open and available to any developers who wish to contribute to the project. The jclouds team currently seeks help and asks for suggestions utilizing the jclouds and jclouds-dev Google groups and IRC on irc.freenode.net#jclouds.
Re: [VOTE] Accept jclouds into the Apache Incubator
On Tue, Apr 23, 2013 at 12:39 AM, Rebecca Wood silky...@gmail.com wrote: ...I am calling a VOTE for acceptance of jclouds into the Apache Incubator +1 -Bertrand P.S. 10 mentors...I'll know where to look when other podlings need help ;-) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept jclouds into the Apache Incubator
+1 (binding) Olivier On Apr 23, 2013 8:39 AM, Rebecca Wood silky...@gmail.com wrote: Hello everyone, I am calling a VOTE for acceptance of jclouds into the Apache Incubator. The vote will close on Monday, April 29, 2013. [ ] +1 Accept jclouds into the Apache Incubator. [ ] +0 Don't care. [ ] -1 Don't accept jclouds into the Incubator because... The full proposal is pasted below, and the corresponding wiki is http://wiki.apache.org/incubator/jcloudsProposal. Only VOTEs from Incubator PMC members are binding, but all are welcome to express their thoughts. Thanks, Becca Wood -- = jclouds Proposal for Apache Incubator = == Abstract == [[http://www.jclouds.org/|jclouds]] is an open source cloud agnostic library that enables developers to access a variety of supported cloud providers using one API. == Proposal == [[http://www.jclouds.org/|jclouds]] provides two portable API abstractions for cloud computing and cloud storage in the form of Java or Clojure libraries. By abstracting away vendor-specific details, jclouds supplies a solution for users to avoid lock-in to a specific cloud vendor. It also provisions hooks to make it easy to take advantage of specific features from those vendors. == Background == jclouds began in March of 2009 while Adrian Cole was working on the Amazon S3 plugin for Infinispan. He discovered that existing S3 libraries would not pass the concurrent test suite needed for write behind persistence. When it became clear that a new library was needed, jclouds formed as an independent project founded by Cole under the mentorship of Manik Surtani. The fledgling jclouds team soon encountered two portability issues: runtime portability with Google App Engine and compatibility with the similar cloud files service from Rackspace. The legacy of Google App Engine is still present within jclouds and is expressed by the 'driver' design which doesn't require threads. Supporting Rackspace started a legacy of cloud portability which would soon extend to provisioning. As jclouds supports newer and cutting edge cloud technologies, it is in a constant state of evolution. jclouds was founded in Shoreditch, London. The ensuing 4 months backpacking between European Java User Groups accounts for the initial population of European developers and users within the community. The initial contributors to jclouds included Adrian Cole, James Murty, Andrew Newdigate, and Andrew Phillips. Manik Surtani served as a mentor, and there were a number of other advisers as well. == Rationale == There are many providers that offer IaaS clouds, but few APIs that can bridge the gap between cloud providers. jclouds supplies an abstraction layer for both compute and storage resources that makes it easy to work with many different cloud APIs using a simple and singular API. jclouds provides this abstraction layer for the Java and Clojure communities. It is a unique niche within the cloud community. jclouds provides the write once, run anywhere concept when utilizing infrastructure cloud resources. == Initial Goals == * Build a more centralized community pulling together jclouds developers, jclouds integrators, and service providers who use jclouds. * Although jclouds has a fairly collaborative community, the committers wish to further bridge the gap between developers and community by encouraging more community involvement in development processes. * Break down from a monolithic release process into one that is more decentrilized. * Bring the jclouds core code base consisting of ComputeService and Blobstore into Apache. * jclouds will not move all existing provider code into Apache. The goal is to move the provider code for those clouds that have complete portability and are tried, tested, and true. This includes code for OpenStack, Amazon EC2, and Google Cloud. == Current Status == === Meritocracy === jclouds has an active community of contributors who are encouraged to become full-fledged jclouds committers. A jclouds committer understands the importance of seeking community feedback, actively listening to suggestions, and fostering relationships with community members who make contributions. The entirety of jclouds is built upon the relationships that have been built with community members. This camaraderie will continue to be promoted as jclouds is introduced into the Incubator and beyond. jclouds encourages involvement from its community members, and the issues are open and available to any developers who wish to contribute to the project. The jclouds team currently seeks help and asks for suggestions utilizing the jclouds and jclouds-dev Google groups and IRC on irc.freenode.net#jclouds. Any and all submissions for changes are reviewed and taken into consideration. === Community === jclouds has a highly active and growing community of users and developers. The community is currently fostered at
AUTO: Richard Schwerdtfeger/Austin/IBM is out of the office until 04/29/2001. (returning 04/29/2013)
I am out of the office until 04/29/2013. I am traveling for work with limited access to email. Thanks, Rich Note: This is an automated response to your message Re: [VOTE] Accept jclouds into the Apache Incubator sent on 04/22/2013 11:41:05 PM. This is the only notification you will receive while this person is away.
Re: [VOTE] Accept jclouds into the Apache Incubator
+1 (binding) LieGrue, strub - Original Message - From: Rebecca Wood silky...@gmail.com To: general@incubator.apache.org Cc: Sent: Tuesday, 23 April 2013, 0:39 Subject: [VOTE] Accept jclouds into the Apache Incubator Hello everyone, I am calling a VOTE for acceptance of jclouds into the Apache Incubator. The vote will close on Monday, April 29, 2013. [ ] +1 Accept jclouds into the Apache Incubator. [ ] +0 Don't care. [ ] -1 Don't accept jclouds into the Incubator because... The full proposal is pasted below, and the corresponding wiki is http://wiki.apache.org/incubator/jcloudsProposal. Only VOTEs from Incubator PMC members are binding, but all are welcome to express their thoughts. Thanks, Becca Wood -- = jclouds Proposal for Apache Incubator = == Abstract == [[http://www.jclouds.org/|jclouds]] is an open source cloud agnostic library that enables developers to access a variety of supported cloud providers using one API. == Proposal == [[http://www.jclouds.org/|jclouds]] provides two portable API abstractions for cloud computing and cloud storage in the form of Java or Clojure libraries. By abstracting away vendor-specific details, jclouds supplies a solution for users to avoid lock-in to a specific cloud vendor. It also provisions hooks to make it easy to take advantage of specific features from those vendors. == Background == jclouds began in March of 2009 while Adrian Cole was working on the Amazon S3 plugin for Infinispan. He discovered that existing S3 libraries would not pass the concurrent test suite needed for write behind persistence. When it became clear that a new library was needed, jclouds formed as an independent project founded by Cole under the mentorship of Manik Surtani. The fledgling jclouds team soon encountered two portability issues: runtime portability with Google App Engine and compatibility with the similar cloud files service from Rackspace. The legacy of Google App Engine is still present within jclouds and is expressed by the 'driver' design which doesn't require threads. Supporting Rackspace started a legacy of cloud portability which would soon extend to provisioning. As jclouds supports newer and cutting edge cloud technologies, it is in a constant state of evolution. jclouds was founded in Shoreditch, London. The ensuing 4 months backpacking between European Java User Groups accounts for the initial population of European developers and users within the community. The initial contributors to jclouds included Adrian Cole, James Murty, Andrew Newdigate, and Andrew Phillips. Manik Surtani served as a mentor, and there were a number of other advisers as well. == Rationale == There are many providers that offer IaaS clouds, but few APIs that can bridge the gap between cloud providers. jclouds supplies an abstraction layer for both compute and storage resources that makes it easy to work with many different cloud APIs using a simple and singular API. jclouds provides this abstraction layer for the Java and Clojure communities. It is a unique niche within the cloud community. jclouds provides the write once, run anywhere concept when utilizing infrastructure cloud resources. == Initial Goals == * Build a more centralized community pulling together jclouds developers, jclouds integrators, and service providers who use jclouds. * Although jclouds has a fairly collaborative community, the committers wish to further bridge the gap between developers and community by encouraging more community involvement in development processes. * Break down from a monolithic release process into one that is more decentrilized. * Bring the jclouds core code base consisting of ComputeService and Blobstore into Apache. * jclouds will not move all existing provider code into Apache. The goal is to move the provider code for those clouds that have complete portability and are tried, tested, and true. This includes code for OpenStack, Amazon EC2, and Google Cloud. == Current Status == === Meritocracy === jclouds has an active community of contributors who are encouraged to become full-fledged jclouds committers. A jclouds committer understands the importance of seeking community feedback, actively listening to suggestions, and fostering relationships with community members who make contributions. The entirety of jclouds is built upon the relationships that have been built with community members. This camaraderie will continue to be promoted as jclouds is introduced into the Incubator and beyond. jclouds encourages involvement from its community members, and the issues are open and available to any developers who wish to contribute to the project. The jclouds team currently seeks help and asks for suggestions utilizing the jclouds and jclouds-dev Google
Re: [VOTE] Accept jclouds into the Apache Incubator
+1 (non binding) On Apr 22, 2013, at 3:39 PM, Rebecca Wood silky...@gmail.com wrote: Hello everyone, I am calling a VOTE for acceptance of jclouds into the Apache Incubator. The vote will close on Monday, April 29, 2013. [ ] +1 Accept jclouds into the Apache Incubator. [ ] +0 Don't care. [ ] -1 Don't accept jclouds into the Incubator because... The full proposal is pasted below, and the corresponding wiki is http://wiki.apache.org/incubator/jcloudsProposal. Only VOTEs from Incubator PMC members are binding, but all are welcome to express their thoughts. Thanks, Becca Wood -- = jclouds Proposal for Apache Incubator = == Abstract == [[http://www.jclouds.org/|jclouds]] is an open source cloud agnostic library that enables developers to access a variety of supported cloud providers using one API. == Proposal == [[http://www.jclouds.org/|jclouds]] provides two portable API abstractions for cloud computing and cloud storage in the form of Java or Clojure libraries. By abstracting away vendor-specific details, jclouds supplies a solution for users to avoid lock-in to a specific cloud vendor. It also provisions hooks to make it easy to take advantage of specific features from those vendors. == Background == jclouds began in March of 2009 while Adrian Cole was working on the Amazon S3 plugin for Infinispan. He discovered that existing S3 libraries would not pass the concurrent test suite needed for write behind persistence. When it became clear that a new library was needed, jclouds formed as an independent project founded by Cole under the mentorship of Manik Surtani. The fledgling jclouds team soon encountered two portability issues: runtime portability with Google App Engine and compatibility with the similar cloud files service from Rackspace. The legacy of Google App Engine is still present within jclouds and is expressed by the 'driver' design which doesn't require threads. Supporting Rackspace started a legacy of cloud portability which would soon extend to provisioning. As jclouds supports newer and cutting edge cloud technologies, it is in a constant state of evolution. jclouds was founded in Shoreditch, London. The ensuing 4 months backpacking between European Java User Groups accounts for the initial population of European developers and users within the community. The initial contributors to jclouds included Adrian Cole, James Murty, Andrew Newdigate, and Andrew Phillips. Manik Surtani served as a mentor, and there were a number of other advisers as well. == Rationale == There are many providers that offer IaaS clouds, but few APIs that can bridge the gap between cloud providers. jclouds supplies an abstraction layer for both compute and storage resources that makes it easy to work with many different cloud APIs using a simple and singular API. jclouds provides this abstraction layer for the Java and Clojure communities. It is a unique niche within the cloud community. jclouds provides the write once, run anywhere concept when utilizing infrastructure cloud resources. == Initial Goals == * Build a more centralized community pulling together jclouds developers, jclouds integrators, and service providers who use jclouds. * Although jclouds has a fairly collaborative community, the committers wish to further bridge the gap between developers and community by encouraging more community involvement in development processes. * Break down from a monolithic release process into one that is more decentrilized. * Bring the jclouds core code base consisting of ComputeService and Blobstore into Apache. * jclouds will not move all existing provider code into Apache. The goal is to move the provider code for those clouds that have complete portability and are tried, tested, and true. This includes code for OpenStack, Amazon EC2, and Google Cloud. == Current Status == === Meritocracy === jclouds has an active community of contributors who are encouraged to become full-fledged jclouds committers. A jclouds committer understands the importance of seeking community feedback, actively listening to suggestions, and fostering relationships with community members who make contributions. The entirety of jclouds is built upon the relationships that have been built with community members. This camaraderie will continue to be promoted as jclouds is introduced into the Incubator and beyond. jclouds encourages involvement from its community members, and the issues are open and available to any developers who wish to contribute to the project. The jclouds team currently seeks help and asks for suggestions utilizing the jclouds and jclouds-dev Google groups and IRC on irc.freenode.net#jclouds. Any and all submissions for changes are reviewed and taken into consideration. === Community === jclouds has a highly active and growing
Re: [VOTE] Accept jclouds into the Apache Incubator
+1 On Tue, Apr 23, 2013 at 12:39 AM, Rebecca Wood silky...@gmail.com wrote: Hello everyone, I am calling a VOTE for acceptance of jclouds into the Apache Incubator. The vote will close on Monday, April 29, 2013. [ ] +1 Accept jclouds into the Apache Incubator. [ ] +0 Don't care. [ ] -1 Don't accept jclouds into the Incubator because... The full proposal is pasted below, and the corresponding wiki is http://wiki.apache.org/incubator/jcloudsProposal. Only VOTEs from Incubator PMC members are binding, but all are welcome to express their thoughts. Thanks, Becca Wood -- = jclouds Proposal for Apache Incubator = == Abstract == [[http://www.jclouds.org/|jclouds]] is an open source cloud agnostic library that enables developers to access a variety of supported cloud providers using one API. == Proposal == [[http://www.jclouds.org/|jclouds]] provides two portable API abstractions for cloud computing and cloud storage in the form of Java or Clojure libraries. By abstracting away vendor-specific details, jclouds supplies a solution for users to avoid lock-in to a specific cloud vendor. It also provisions hooks to make it easy to take advantage of specific features from those vendors. == Background == jclouds began in March of 2009 while Adrian Cole was working on the Amazon S3 plugin for Infinispan. He discovered that existing S3 libraries would not pass the concurrent test suite needed for write behind persistence. When it became clear that a new library was needed, jclouds formed as an independent project founded by Cole under the mentorship of Manik Surtani. The fledgling jclouds team soon encountered two portability issues: runtime portability with Google App Engine and compatibility with the similar cloud files service from Rackspace. The legacy of Google App Engine is still present within jclouds and is expressed by the 'driver' design which doesn't require threads. Supporting Rackspace started a legacy of cloud portability which would soon extend to provisioning. As jclouds supports newer and cutting edge cloud technologies, it is in a constant state of evolution. jclouds was founded in Shoreditch, London. The ensuing 4 months backpacking between European Java User Groups accounts for the initial population of European developers and users within the community. The initial contributors to jclouds included Adrian Cole, James Murty, Andrew Newdigate, and Andrew Phillips. Manik Surtani served as a mentor, and there were a number of other advisers as well. == Rationale == There are many providers that offer IaaS clouds, but few APIs that can bridge the gap between cloud providers. jclouds supplies an abstraction layer for both compute and storage resources that makes it easy to work with many different cloud APIs using a simple and singular API. jclouds provides this abstraction layer for the Java and Clojure communities. It is a unique niche within the cloud community. jclouds provides the write once, run anywhere concept when utilizing infrastructure cloud resources. == Initial Goals == * Build a more centralized community pulling together jclouds developers, jclouds integrators, and service providers who use jclouds. * Although jclouds has a fairly collaborative community, the committers wish to further bridge the gap between developers and community by encouraging more community involvement in development processes. * Break down from a monolithic release process into one that is more decentrilized. * Bring the jclouds core code base consisting of ComputeService and Blobstore into Apache. * jclouds will not move all existing provider code into Apache. The goal is to move the provider code for those clouds that have complete portability and are tried, tested, and true. This includes code for OpenStack, Amazon EC2, and Google Cloud. == Current Status == === Meritocracy === jclouds has an active community of contributors who are encouraged to become full-fledged jclouds committers. A jclouds committer understands the importance of seeking community feedback, actively listening to suggestions, and fostering relationships with community members who make contributions. The entirety of jclouds is built upon the relationships that have been built with community members. This camaraderie will continue to be promoted as jclouds is introduced into the Incubator and beyond. jclouds encourages involvement from its community members, and the issues are open and available to any developers who wish to contribute to the project. The jclouds team currently seeks help and asks for suggestions utilizing the jclouds and jclouds-dev Google groups and IRC on irc.freenode.net#jclouds. Any and all submissions for changes are reviewed and taken into consideration. === Community === jclouds has a highly active and growing community of users and developers. The community is currently fostered at
Re: LICENSE/NOTICE revisited (was Release Apache Marmotta 3.0.0-incubating (RC8))
On 23 April 2013 08:31, Sergio Fernández sergio.fernan...@salzburgresearch.at wrote: Hi Marvin, thanks for your time analysing our release. Please, find my reply inline. On 18/04/13 02:30, Marvin Humphrey wrote: On Wed, Apr 17, 2013 at 11:00 AM, Sebastian Schaffert wrote: - The section NOTICE file in [3] says that The NOTICE file may also include copyright notices moved from source files submitted to the ASF. The 3rd party Javascript files we include are submitted to the ASF, but they are often under MIT license and therefore category A in [2]. If I read the document correctly, category A only requires to include notices if a NOTICE file is contained in the product. According to [1], MIT and New BSD even can have a reduced entry in LICENSE. [4] says, however, that All the licenses on all the files to be included within a package should be included in the LICENSE document. Here's Roy Fielding, ASF Board member and author of the Apache License 2.0: http://s.apache.org/Hqj Pointers are sufficient. Roy elaborates here: http://s.apache.org/Iw6 By pointers, I mean a relative path reference to the license file within some subdirectory of the package being redistributed. Right this would make the LICENCE files shorter. So, if I understood correctly, we should switch from licenses text to pointers, something like: No; it's not necessary to switch. Roy says that pointers are sufficient. He does not say they are necessary. From LEGAL-155: In any case, the intention is to allow use of whatever form seems most appropriate for the given distribution form, while still satisfying the legal requirements for each licensed work. Some projects will want to include all the text in one file. Others may not. For the D3.js component, located at: path/to/foo/ Copyright (c) 2013 Foo Author, http://foo.net License at: path/to/foo/LICENSE Would be that fine? - for dependencies of category B, [2] specifies that Although the source must not be included in Apache products, the NOTICE file, which is required to be included in each ASF distribution, must point to the source form of the included binary (more on that in the forthcoming Receiving and Releasing Contributions document)., a fact that is not mentioned in any of the other documents. This passage has somehow escaped my notice until now. Based on my understanding about the origins of the NOTICE file, it does not ring true. It seems to me that what works for category A should also work for category B: reference/quote the license in LICENSE and address mandatory attribution requirements in NOTICE. The goal is to satisfy the licensing requirements of the dependency, not to give credit -- so IMO linking only makes sense if that's a requirement of the dependency's license. So keep in NOTICE only those which require additional attribution requirements? Does anybody know any TLPs that are actually following the advice to link to source for category B dependencies in binary NOTICE files? Not sure if it is what you are looking, but we are doing it in a quite similar way that CouchDB, since they have a quite similar setup. See its NOTICE at: https://svn.apache.org/repos/**asf/couchdb/trunk/NOTICEhttps://svn.apache.org/repos/asf/couchdb/trunk/NOTICE I suspect we will want to bring this up on legal-discuss and see if we can't get that recommendation removed. - The labelling requirement source access in [2] requires that the NOTICE file contains pointers to the location of the source code for any 3rd party library that is bundled in a binary distribution (not only category B). [1] on the other hand does not mention this requirement and says that everything that is not legally necessary does not belong into NOTICE. Here's Roy again: http://s.apache.org/ZEA Hey, I'm all for people having opinions on development and credits and documentation. NOTICE and LICENSE are none of those. They are not open to anyone's opinions other than the copyright owners that require such notices, and they must not be added where they are not required. Each additional notice places a burden on the ASF and all downstream redistributors. Please, folks, I am not even a Sling committer. I am speaking as the author of the Apache License. Don't screw with what I have changed. I have way more experience in these matters than everyone else at the ASF combined. If you put stuff in NOTICE that is not legally required to be there, I will remove it as an officer of the ASF. If you add it back in, I will have to duplicate the effort of removing it again. That will not make me a happy camper. It seems that we might want to make the language in the licensing howto similarly scary in order to dissuade people from adding
Any podling need a non-mentor but recent graduate's help?
Hi podlings, I'm not an IPMC member, but I did do quite a bit of work around the Apache CloudStack project to get it through graduation. I'm willing to help answer questions and guide a podling that may need some additional eyes. I can't be an official mentor for you, but I figured it couldn't hurt to raise my hand to at least lurk on a list where help may be needed. IPMC members, if you have a suggested podling for me, that would be great too... Any takers? -chip - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Any podling need a non-mentor but recent graduate's help?
Hello Chip, I think your help is highly appreciated. If I were you, I would look at the latest board reports and find out, which project report was not signed by a mentor. This might be an indicator that the project is in trouble. Do you know about the Shepherd model? Every reporting time folks are asked to make a crosscheck on various podling. This is also a good opportunity to find out who needs help. That said, the incubator misses a system to identify projects with lack of mentor support - you either need to ask or wait if somebody asks for help Cheers Christian On Tue, Apr 23, 2013 at 3:22 PM, Chip Childers chip.child...@sungard.com wrote: Hi podlings, I'm not an IPMC member, but I did do quite a bit of work around the Apache CloudStack project to get it through graduation. I'm willing to help answer questions and guide a podling that may need some additional eyes. I can't be an official mentor for you, but I figured it couldn't hurt to raise my hand to at least lurk on a list where help may be needed. IPMC members, if you have a suggested podling for me, that would be great too... Any takers? -chip - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- http://www.grobmeier.de https://www.timeandbill.de - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept jclouds into the Apache Incubator
+1 (binding) On Tue, Apr 23, 2013 at 1:03 AM, Carlos Sanchez car...@apache.org wrote: +1 On Tue, Apr 23, 2013 at 12:39 AM, Rebecca Wood silky...@gmail.com wrote: Hello everyone, I am calling a VOTE for acceptance of jclouds into the Apache Incubator. The vote will close on Monday, April 29, 2013. [ ] +1 Accept jclouds into the Apache Incubator. [ ] +0 Don't care. [ ] -1 Don't accept jclouds into the Incubator because... The full proposal is pasted below, and the corresponding wiki is http://wiki.apache.org/incubator/jcloudsProposal. Only VOTEs from Incubator PMC members are binding, but all are welcome to express their thoughts. Thanks, Becca Wood -- = jclouds Proposal for Apache Incubator = == Abstract == [[http://www.jclouds.org/|jclouds]] is an open source cloud agnostic library that enables developers to access a variety of supported cloud providers using one API. == Proposal == [[http://www.jclouds.org/|jclouds]] provides two portable API abstractions for cloud computing and cloud storage in the form of Java or Clojure libraries. By abstracting away vendor-specific details, jclouds supplies a solution for users to avoid lock-in to a specific cloud vendor. It also provisions hooks to make it easy to take advantage of specific features from those vendors. == Background == jclouds began in March of 2009 while Adrian Cole was working on the Amazon S3 plugin for Infinispan. He discovered that existing S3 libraries would not pass the concurrent test suite needed for write behind persistence. When it became clear that a new library was needed, jclouds formed as an independent project founded by Cole under the mentorship of Manik Surtani. The fledgling jclouds team soon encountered two portability issues: runtime portability with Google App Engine and compatibility with the similar cloud files service from Rackspace. The legacy of Google App Engine is still present within jclouds and is expressed by the 'driver' design which doesn't require threads. Supporting Rackspace started a legacy of cloud portability which would soon extend to provisioning. As jclouds supports newer and cutting edge cloud technologies, it is in a constant state of evolution. jclouds was founded in Shoreditch, London. The ensuing 4 months backpacking between European Java User Groups accounts for the initial population of European developers and users within the community. The initial contributors to jclouds included Adrian Cole, James Murty, Andrew Newdigate, and Andrew Phillips. Manik Surtani served as a mentor, and there were a number of other advisers as well. == Rationale == There are many providers that offer IaaS clouds, but few APIs that can bridge the gap between cloud providers. jclouds supplies an abstraction layer for both compute and storage resources that makes it easy to work with many different cloud APIs using a simple and singular API. jclouds provides this abstraction layer for the Java and Clojure communities. It is a unique niche within the cloud community. jclouds provides the write once, run anywhere concept when utilizing infrastructure cloud resources. == Initial Goals == * Build a more centralized community pulling together jclouds developers, jclouds integrators, and service providers who use jclouds. * Although jclouds has a fairly collaborative community, the committers wish to further bridge the gap between developers and community by encouraging more community involvement in development processes. * Break down from a monolithic release process into one that is more decentrilized. * Bring the jclouds core code base consisting of ComputeService and Blobstore into Apache. * jclouds will not move all existing provider code into Apache. The goal is to move the provider code for those clouds that have complete portability and are tried, tested, and true. This includes code for OpenStack, Amazon EC2, and Google Cloud. == Current Status == === Meritocracy === jclouds has an active community of contributors who are encouraged to become full-fledged jclouds committers. A jclouds committer understands the importance of seeking community feedback, actively listening to suggestions, and fostering relationships with community members who make contributions. The entirety of jclouds is built upon the relationships that have been built with community members. This camaraderie will continue to be promoted as jclouds is introduced into the Incubator and beyond. jclouds encourages involvement from its community members, and the issues are open and available to any developers who wish to contribute to the project. The jclouds team currently seeks help and asks for suggestions utilizing the jclouds and jclouds-dev Google groups and IRC on irc.freenode.net#jclouds. Any and all
