Re: [VOTE] DeltaSpike to join the Incubator
+1 (binding) On Mon, Dec 5, 2011 at 8:52 AM, Francis De Brabandere franci...@gmail.com wrote: +1 (non-binding) On Mon, Dec 5, 2011 at 8:33 AM, Bart Kummel b...@kummelweb.nl wrote: +1 (non-binding) -- http://www.somatik.be Microsoft gives you windows, Linux gives you the whole house. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Any objections to git hosting for Incubator projects?
Hi Joe, On Sat, Dec 3, 2011 at 6:46 PM, Joe Schaefer joe_schae...@yahoo.com wrote: So earlier this week infrastructure put out an RFP regarding early adoption of git hosting at the ASF and 3 Incubator projects have responded: callback, s4, and deltaspike... Very cool. Unless there are formal objections to such submissions infrastructure will evaluate their proposals just as if they came from the IPMC itself I'm ok as long as you have evidence (via messages or votes on public mailing lists) that those podlings' mentors support those requests. -Bertrand - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] DeltaSpike to join the Incubator
+1 (binding) Good luck! On Sun, Dec 4, 2011 at 11:11 PM, Gerhard Petracek gpetra...@apache.org wrote: Hello, Please vote on the acceptance of DeltaSpike into the Apache Incubator. The proposal is available at [1] and its content is also included below for your convenience. Please vote: [ ] +1 Accept DeltaSpike for incubation [ ] +0 Don't care [ ] -1 Don't accept DeltaSpike for incubation because... The vote is open for 72 hours. Thanks, Gerhard [1] http://wiki.apache.org/incubator/DeltaSpikeProposal Apache DeltaSpike Proposal == Abstract Apache DeltaSpike is a collection of JSR-299 (CDI) Extensions for building applications on the Java SE and EE platforms. Proposal Apache DeltaSpike will consist of a number of portable CDI extensions that provide useful features for Java application developers. The goal of Apache DeltaSpike is to create a de-facto standard of extensions that is developed and maintained by the Java community, and to act as an incubator for features that may eventually become part of the various Java SE and EE-related specifications. Background One of the most exciting inclusions of the Java EE6 specification is JSR-299, Contexts and Dependency Injection (CDI) for Java. CDI builds on other Java EE specifications by defining a contextual component model and typesafe dependency injection framework for managed beans. It also defines a SPI that allows developers to write portable “extensions” that can be used to modify the behaviour of the Java EE platform, by offering additional features not provided by the platform by default. Apache DeltaSpike builds on this portable extensions SPI by providing baseline utilities and CDI Extensions which form the base of almost all CDI applications. Rationale There presently exists a number of open source projects that provide extensions for CDI, such as Apache MyFaces CODI, JBoss Seam3 and CDISource. Apache DeltaSpike seeks to unify these efforts by creating an “industry standard” set of extensions, combining the best core features of these projects. The project also aims to provide a rich, JBoss Arquillian based (license: ALv2), test environment to ensure that DeltaSpike portably runs in all important CDI environments. Initial Goals The initial goals of the Apache DeltaSpike project are to: * Setup the governance structure of the project * Receive code donations from contributing members * Ensure all donated code is appropriately licensed under the Apache License * Merge and rename code to reflect new project name * Merge code where feature overlap exists * Merge or produce documentation for all modules * Provide simple examples demonstrating feature usage * Produce release/s based on a schedule created by the PMC * Attract contributions from the greater Java EE community and other Java EE development groups Current Status The initial codebase for Apache DeltaSpike will be populated with mature code donations from project members, including JBoss Seam3, Apache MyFaces CODI and CDISource. Meritocracy All contributors have a well established history in the open source community and are well aware of the meritocracy principles of the Apache Software Foundation. Currently the Seam3 project is fortunate to receive the majority of its code contributions from its large community of users. Many of the modules that are contained in the Seam project are led by volunteers from the community, who have both direct commit access, and discretion over the direction of their modules. Apache MyFaces CODI is a subproject of Apache MyFaces and thus all contributors are already familiar with the meritocracy principles. The CDISource project has adopted the principles of meritocracy by the founding developers having control of different modules depending on their contribution to those modules. Community The JBoss Seam, Apache MyFaces CODI and CDISource projects already have well established communities, consisting of many active users and contributors. One of the primary goals of the Apache DeltaSpike project is to unify this community, and by creating a project that is a “single source of truth” for CDI Extensions. By doing this, we hope to make the whole greater than the sum of its parts, i.e. to attract a much stronger community than that which currently exists across the separate projects. To this end, it is a goal of this project to attract contributors from the Java EE community in addition to those from the three projects already mentioned. Core Developers * Shane Bryzak (Red Hat) * Jason Porter (Red Hat) * Stuart Douglas (Red Hat) * Jozef Hartinger (Red Hat) * Brian Leathem (Red Hat) * Ken Finnigan (Red Hat) *
Re: Any objections to git hosting for Incubator projects?
+1 for DeltaSpike I thinkthe other requests over at asf-infra also did come from Mentors (as far as I have seen). LieGrue, strub - Original Message - From: Bertrand Delacretaz bdelacre...@apache.org To: general@incubator.apache.org; Joe Schaefer joe_schae...@yahoo.com Cc: Sent: Monday, December 5, 2011 9:57 AM Subject: Re: Any objections to git hosting for Incubator projects? Hi Joe, On Sat, Dec 3, 2011 at 6:46 PM, Joe Schaefer joe_schae...@yahoo.com wrote: So earlier this week infrastructure put out an RFP regarding early adoption of git hosting at the ASF and 3 Incubator projects have responded: callback, s4, and deltaspike... Very cool. Unless there are formal objections to such submissions infrastructure will evaluate their proposals just as if they came from the IPMC itself I'm ok as long as you have evidence (via messages or votes on public mailing lists) that those podlings' mentors support those requests. -Bertrand - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Yan: [VOTE] DeltaSpike to join the Incubator
+1(binding) Gurkan Kimden: Gerhard Petracek gpetra...@apache.org Kime: general@incubator.apache.org Gönderildiği Tarih: 5 Aralık 2011 0:11 Pazartesi Konu: [VOTE] DeltaSpike to join the Incubator Hello, Please vote on the acceptance of DeltaSpike into the Apache Incubator. The proposal is available at [1] and its content is also included below for your convenience. Please vote: [ ] +1 Accept DeltaSpike for incubation [ ] +0 Don't care [ ] -1 Don't accept DeltaSpike for incubation because... The vote is open for 72 hours. Thanks, Gerhard [1] http://wiki.apache.org/incubator/DeltaSpikeProposal Apache DeltaSpike Proposal == Abstract Apache DeltaSpike is a collection of JSR-299 (CDI) Extensions for building applications on the Java SE and EE platforms. Proposal Apache DeltaSpike will consist of a number of portable CDI extensions that provide useful features for Java application developers. The goal of Apache DeltaSpike is to create a de-facto standard of extensions that is developed and maintained by the Java community, and to act as an incubator for features that may eventually become part of the various Java SE and EE-related specifications. Background One of the most exciting inclusions of the Java EE6 specification is JSR-299, Contexts and Dependency Injection (CDI) for Java. CDI builds on other Java EE specifications by defining a contextual component model and typesafe dependency injection framework for managed beans. It also defines a SPI that allows developers to write portable “extensions” that can be used to modify the behaviour of the Java EE platform, by offering additional features not provided by the platform by default. Apache DeltaSpike builds on this portable extensions SPI by providing baseline utilities and CDI Extensions which form the base of almost all CDI applications. Rationale There presently exists a number of open source projects that provide extensions for CDI, such as Apache MyFaces CODI, JBoss Seam3 and CDISource. Apache DeltaSpike seeks to unify these efforts by creating an “industry standard” set of extensions, combining the best core features of these projects. The project also aims to provide a rich, JBoss Arquillian based (license: ALv2), test environment to ensure that DeltaSpike portably runs in all important CDI environments. Initial Goals The initial goals of the Apache DeltaSpike project are to: * Setup the governance structure of the project * Receive code donations from contributing members * Ensure all donated code is appropriately licensed under the Apache License * Merge and rename code to reflect new project name * Merge code where feature overlap exists * Merge or produce documentation for all modules * Provide simple examples demonstrating feature usage * Produce release/s based on a schedule created by the PMC * Attract contributions from the greater Java EE community and other Java EE development groups Current Status The initial codebase for Apache DeltaSpike will be populated with mature code donations from project members, including JBoss Seam3, Apache MyFaces CODI and CDISource. Meritocracy All contributors have a well established history in the open source community and are well aware of the meritocracy principles of the Apache Software Foundation. Currently the Seam3 project is fortunate to receive the majority of its code contributions from its large community of users. Many of the modules that are contained in the Seam project are led by volunteers from the community, who have both direct commit access, and discretion over the direction of their modules. Apache MyFaces CODI is a subproject of Apache MyFaces and thus all contributors are already familiar with the meritocracy principles. The CDISource project has adopted the principles of meritocracy by the founding developers having control of different modules depending on their contribution to those modules. Community The JBoss Seam, Apache MyFaces CODI and CDISource projects already have well established communities, consisting of many active users and contributors. One of the primary goals of the Apache DeltaSpike project is to unify this community, and by creating a project that is a “single source of truth” for CDI Extensions. By doing this, we hope to make the whole greater than the sum of its parts, i.e. to attract a much stronger community than that which currently exists across the separate projects. To this end, it is a goal of this project to attract contributors from the Java EE community in addition to those from the three projects already mentioned. Core Developers * Shane Bryzak (Red Hat) * Jason Porter (Red Hat) * Stuart Douglas (Red Hat) * Jozef Hartinger (Red Hat) * Brian Leathem (Red Hat) *
Re: Any objections to git hosting for Incubator projects?
I would (hope to speak for the whole directmemory team) would be really willing to partecipate. Ciao, Raffaele Il giorno 03/dic/2011 17:47, Joe Schaefer joe_schae...@yahoo.com ha scritto: So earlier this week infrastructure put out an RFP regarding early adoption of git hosting at the ASF and 3 Incubator projects have responded: callback, s4, and deltaspike. Unless there are formal objections to such submissions infrastructure will evaluate their proposals just as if they came from the IPMC itself.
Re: Feedback on updated NOTICE and LICENSE files (was: [VOTE] Release Kafka 0.7.0-incubating)
There is a sample NOTICE file linked [1] from ASF Source Header and Copyright Notice Policy [2] [1] http://www.apache.org/legal/src-headers.html#faq-examplenotice [2] http://www.apache.org/legal/src-headers.html#notice As someone trying to generate these documents, I'm actually finding these to be poor examples when trying to see what should and should not be in NOTICE. On http://www.apache.org/legal/src-headers.html#notice, under NOTICE file, there is The remainder of the NOTICE file is to be used for required third-party notices. with a link to What Are Required Third-party Notices? However, this text doesn't talk about NOTICE, but LICENSE: Apache releases should contain a copy of each license, usually contained in the LICENSE document. And the httpd NOTICE doesn't provide many examples (there are only three non-Apache items listed). These don't answer questions such as: Do other Apache projects need to be listed in NOTICE as well (which was answered in the email exchange above, but as such won't of much use to the next Podling that comes along), or Do other Apache projects need to be noted in the LICENSE file (not answered here, that I can see), or How to include reference 3rd party jars in the LICENSE file that are also Apache 2.0 licensed? Casting about for an example more relevant, I come across Whirr's 0.4 release, which was +1'ed from Incubator and take a look at its NOTICE.txt (from http://people.apache.org/~asavu/whirr-0.4.0-incubating-candidate-2/): Apache Whirr Copyright 2010-2011 The Apache Software Foundation This product includes software developed at The Apache Software Foundation (http://www.apache.org/). And then the jars that are included in the source distribution: ./services/cassandra/lib/apache-cassandra-0.7.0.jar ./services/cassandra/lib/libthrift-0.5.jar ./services/hadoop/lib/hadoop-test-0.20.3-SNAPSHOT.jar ./services/voldemort/lib/linkedin-voldemort-0.90.RC3.jar Voldemort was not developed at the ASF and isn't listed in NOTICE. This candidate was +1ed and released. Was this in error? Regardless, I've made an honest attempt to build the NOTICE and LICENSE files necessary for a source release based on bringing most of the jars in via Maven at KAFKA-221 (https://issues.apache.org/jira/browse/KAFKA-221) and would very much appreciate a quick look at that to see if it's correct, before we call another vote. -Jakob - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Any objections to git hosting for Incubator projects?
Sent from my mobile device, please forgive errors and brevity. On Dec 5, 2011 10:21 AM, Mark Struberg strub...@yahoo.de wrote: +1 for DeltaSpike I thinkthe other requests over at asf-infra also did come from Mentors (as far as I have seen). Correct for Callback. My proposal links to the dev list thread in which all mentors agree to help. Ross LieGrue, strub - Original Message - From: Bertrand Delacretaz bdelacre...@apache.org To: general@incubator.apache.org; Joe Schaefer joe_schae...@yahoo.com Cc: Sent: Monday, December 5, 2011 9:57 AM Subject: Re: Any objections to git hosting for Incubator projects? Hi Joe, On Sat, Dec 3, 2011 at 6:46 PM, Joe Schaefer joe_schae...@yahoo.com wrote: So earlier this week infrastructure put out an RFP regarding early adoption of git hosting at the ASF and 3 Incubator projects have responded: callback, s4, and deltaspike... Very cool. Unless there are formal objections to such submissions infrastructure will evaluate their proposals just as if they came from the IPMC itself I'm ok as long as you have evidence (via messages or votes on public mailing lists) that those podlings' mentors support those requests. -Bertrand - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Feedback on updated NOTICE and LICENSE files (was: [VOTE] Release Kafka 0.7.0-incubating)
On Mon, Dec 5, 2011 at 1:56 PM, Jakob Homan jgho...@gmail.com wrote: There is a sample NOTICE file linked [1] from ASF Source Header and Copyright Notice Policy [2] [1] http://www.apache.org/legal/src-headers.html#faq-examplenotice [2] http://www.apache.org/legal/src-headers.html#notice As someone trying to generate these documents, I'm actually finding these to be poor examples when trying to see what should and should not be in NOTICE. On http://www.apache.org/legal/src-headers.html#notice, under NOTICE file, there is The remainder of the NOTICE file is to be used for required third-party notices. with a link to What Are Required Third-party Notices? However, this text doesn't talk about NOTICE, but LICENSE: Apache releases should contain a copy of each license, usually contained in the LICENSE document. And the httpd NOTICE doesn't provide many examples (there are only three non-Apache items listed). These don't answer questions such as: Do other Apache projects need to be listed in NOTICE as well (which was answered in the email exchange above, but as such won't of much use to the next Podling that comes along), or Do other Apache projects need to be noted in the LICENSE file (not answered here, that I can see), or How to include reference 3rd party jars in the LICENSE file that are also Apache 2.0 licensed? Casting about for an example more relevant, I come across Whirr's 0.4 release, which was +1'ed from Incubator and take a look at its NOTICE.txt (from http://people.apache.org/~asavu/whirr-0.4.0-incubating-candidate-2/): Apache Whirr Copyright 2010-2011 The Apache Software Foundation This product includes software developed at The Apache Software Foundation (http://www.apache.org/). And then the jars that are included in the source distribution: ./services/cassandra/lib/apache-cassandra-0.7.0.jar ./services/cassandra/lib/libthrift-0.5.jar ./services/hadoop/lib/hadoop-test-0.20.3-SNAPSHOT.jar ./services/voldemort/lib/linkedin-voldemort-0.90.RC3.jar Voldemort was not developed at the ASF and isn't listed in NOTICE. This candidate was +1ed and released. Was this in error? Personally I don't believe whirr is in error. Voldemort is under Apache 2.0 license, and as such falls under this: http://www.apache.org/legal/resolved.html#required-third-party-notices Patrick - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Apache Bloodhound
I don't know the proper answer to the licensing and patent questions. My understanding (standard caveats apply) is that the BSD is a Category A license, and as software distributed under it may be included in ASF software such as Bloodhound. I'm unsure what the concern about BSD notices in source file is, nor do I know if such concern is well-founded. -Hyrum On Fri, Dec 2, 2011 at 8:22 PM, Niclas Hedhman nic...@hedhman.org wrote: SO, IIUIC, the first step is to import TRAC, and we will have primarily a BSD codebase as the main body of code? Does this mean that all BSD notices in source files must live in ASF repository for all eternity, assuming that we are allowed to sublicense into ALv2 (which I think is no problem)? And what about the lack of patent license that we offer downstream, but have not received from upstream? Cheers Niclas On Sat, Dec 3, 2011 at 12:14 AM, Mark Struberg strub...@yahoo.de wrote: so this is basically Trac ++ and a fork of Trac ? Or is it a completely rewritten new approach? just curious :) LieGrue, strub - Original Message - From: Hyrum K Wright hyrum.wri...@wandisco.com To: general@incubator.apache.org Cc: Ian Wild ian.w...@wandisco.com; Greg Stein gst...@gmail.com Sent: Friday, December 2, 2011 4:53 PM Subject: [PROPOSAL] Apache Bloodhound Hello Incubator! WANdisco would like to propose the inclusion of a new project, Apache Bloodhound, to the Incubator. The proposal has been posted to the wiki[1], and is also included below. We've privately discussed this project with a number of individuals, but would now like to get the discussion rolling here. Bloodhound is new effort, based on Trac[2], to provide issue tracking and collaboration tools for developers. We realize the proposal is a work-in-progress, and as such look forward to feedback and discussion. We hope to attract mentors and other interested parties through the incubation proposal process, and further diversify the community as we move through incubation. In particular, this project is an opportunity to build a new community around the codebase, and we look forward to doing so at the ASF. -Hyrum [1] http://wiki.apache.org/incubator/BloodhoundProposal [2] http://trac.edgewall.org/ = Bloodhound - Collaborative development tools based on Trac = == Abstract == Bloodhound will be a software development collaboration tool, including issue tracking, wiki and repository browsing. Essentially an improved distribution of the well-known Trac project, Bloodhound will include the common and useful plugins to enable a more complete distribution than a typical Trac installation. == Proposal == Bloodhound will be a software development collaboration tool, based on the existing Trac project, which will include a repository browser, wiki, and defect tracker. In addition to the standard Trac installation, Bloodhound will incorporate a number of popular modules into the core distribution, and include additional improvements developed (as [[http://trac-hacks.org/|plugins]]) outside the Trac project. == Background == The [[http://trac.edgewall.org/|Trac project]] is a BSD-licensed collaboration tool used to assist in software development. It has a wide user base, a pluggable infrastructure, and is generally considered stable. By it's own recognition, however, the development community surrounding Trac has largely dissipated, with little mailing list traffic, and very few commits to the source code repository (see [2]). Private efforts to engage the existing developers in implementing features have been negatively received. At the same time, other individuals and companies, such as [[http://www.wandisco.com|WANdisco]], have expressed interest in helping continue to develop Trac. These entities would prefer this effort to be at a vendor-neutral location, with the clear process for intellectual property management that comes from the Foundation. As such, the Apache Software Foundation feels like the best fit for this new project based on Trac. == Rationale == As discussed earlier, the current Trac development community is small and reluctant to accept outside contributions. Given the Foundation’s reputation for building and maintaining communities, we feel a new project, based on Trac but incubated under the Apache umbrella, would help re-build the developer community, jump started by developer time donated by WANdisco. Additionally, as a developer tool, Bloodhound is a good fit with other, similarly-focused developer tools at the ASF. Private discussions have shown there is some interest by third-parties to release internal improvements to Trac, and Bloodhound gives them an additional venue to do so. == Initial Goals == The initial goals for Bloodhound primarily revolve around migrating the existing code base and integrating external features to make the project easy to deploy. Additional ideas will of
Re: [PROPOSAL] Apache Bloodhound
I suggest legal-discuss@ is involved to answer it. Although it is Cat A license, I don't think it is fully kosher, as we promise that the original contributor hasn't submarined any patents, but BSD doesn't state this. Maybe it is a tiny point, but more eyes from legal-discuss@ won't hurt... On Tue, Dec 6, 2011 at 6:26 AM, Hyrum K Wright hyrum.wri...@wandisco.com wrote: I don't know the proper answer to the licensing and patent questions. My understanding (standard caveats apply) is that the BSD is a Category A license, and as software distributed under it may be included in ASF software such as Bloodhound. I'm unsure what the concern about BSD notices in source file is, nor do I know if such concern is well-founded. -Hyrum On Fri, Dec 2, 2011 at 8:22 PM, Niclas Hedhman nic...@hedhman.org wrote: SO, IIUIC, the first step is to import TRAC, and we will have primarily a BSD codebase as the main body of code? Does this mean that all BSD notices in source files must live in ASF repository for all eternity, assuming that we are allowed to sublicense into ALv2 (which I think is no problem)? And what about the lack of patent license that we offer downstream, but have not received from upstream? Cheers Niclas On Sat, Dec 3, 2011 at 12:14 AM, Mark Struberg strub...@yahoo.de wrote: so this is basically Trac ++ and a fork of Trac ? Or is it a completely rewritten new approach? just curious :) LieGrue, strub - Original Message - From: Hyrum K Wright hyrum.wri...@wandisco.com To: general@incubator.apache.org Cc: Ian Wild ian.w...@wandisco.com; Greg Stein gst...@gmail.com Sent: Friday, December 2, 2011 4:53 PM Subject: [PROPOSAL] Apache Bloodhound Hello Incubator! WANdisco would like to propose the inclusion of a new project, Apache Bloodhound, to the Incubator. The proposal has been posted to the wiki[1], and is also included below. We've privately discussed this project with a number of individuals, but would now like to get the discussion rolling here. Bloodhound is new effort, based on Trac[2], to provide issue tracking and collaboration tools for developers. We realize the proposal is a work-in-progress, and as such look forward to feedback and discussion. We hope to attract mentors and other interested parties through the incubation proposal process, and further diversify the community as we move through incubation. In particular, this project is an opportunity to build a new community around the codebase, and we look forward to doing so at the ASF. -Hyrum [1] http://wiki.apache.org/incubator/BloodhoundProposal [2] http://trac.edgewall.org/ = Bloodhound - Collaborative development tools based on Trac = == Abstract == Bloodhound will be a software development collaboration tool, including issue tracking, wiki and repository browsing. Essentially an improved distribution of the well-known Trac project, Bloodhound will include the common and useful plugins to enable a more complete distribution than a typical Trac installation. == Proposal == Bloodhound will be a software development collaboration tool, based on the existing Trac project, which will include a repository browser, wiki, and defect tracker. In addition to the standard Trac installation, Bloodhound will incorporate a number of popular modules into the core distribution, and include additional improvements developed (as [[http://trac-hacks.org/|plugins]]) outside the Trac project. == Background == The [[http://trac.edgewall.org/|Trac project]] is a BSD-licensed collaboration tool used to assist in software development. It has a wide user base, a pluggable infrastructure, and is generally considered stable. By it's own recognition, however, the development community surrounding Trac has largely dissipated, with little mailing list traffic, and very few commits to the source code repository (see [2]). Private efforts to engage the existing developers in implementing features have been negatively received. At the same time, other individuals and companies, such as [[http://www.wandisco.com|WANdisco]], have expressed interest in helping continue to develop Trac. These entities would prefer this effort to be at a vendor-neutral location, with the clear process for intellectual property management that comes from the Foundation. As such, the Apache Software Foundation feels like the best fit for this new project based on Trac. == Rationale == As discussed earlier, the current Trac development community is small and reluctant to accept outside contributions. Given the Foundation’s reputation for building and maintaining communities, we feel a new project, based on Trac but incubated under the Apache umbrella, would help re-build the developer community, jump started by developer time donated by WANdisco. Additionally, as a developer tool, Bloodhound is a good fit with other, similarly-focused developer tools at the ASF.
RE: [PROPOSAL] Apache Bloodhound
Uh, here's the TRAC License: http://trac.edgewall.org/wiki/TracLicense. You have to do what it says. The language is very simple. So is the Copyright notice. If this is the codebase that you propose to be the foundation of Bloodhound development, I suspect that an SGA (Software Grant Agreement) from Edgewall Software is preferred in order to have it be licensable by Apache under the ALv2. If an SGA is possible, it would deal with the patent issue that has been raised on this thread. See http://www.apache.org/licenses/#grants. I have no idea how much the SGA is a requirement for the incubator proposal moving forward. Your champion or proposed mentors should know. I recommend that be figured out ASAP. How that will be handled might need to be added to the incubator proposal, also. - Dennis If you end up needing a plan B, it might be appropriate to move where further development under the BSD license is possible. SourceForge might be an useful choice. SourceForge offers Trac as an available feature for projects, and it also supports SVN as one of its repository services. (I only mention that because I was looking into the SourceForge 2.0 beta recently and I have some small projects there.) -Original Message- From: Niclas Hedhman [mailto:nic...@hedhman.org] Sent: Monday, December 05, 2011 18:38 To: general@incubator.apache.org Cc: Mark Struberg; Ian Wild; Greg Stein Subject: Re: [PROPOSAL] Apache Bloodhound I suggest legal-discuss@ is involved to answer it. Although it is Cat A license, I don't think it is fully kosher, as we promise that the original contributor hasn't submarined any patents, but BSD doesn't state this. Maybe it is a tiny point, but more eyes from legal-discuss@ won't hurt... On Tue, Dec 6, 2011 at 6:26 AM, Hyrum K Wright hyrum.wri...@wandisco.com wrote: I don't know the proper answer to the licensing and patent questions. My understanding (standard caveats apply) is that the BSD is a Category A license, and as software distributed under it may be included in ASF software such as Bloodhound. I'm unsure what the concern about BSD notices in source file is, nor do I know if such concern is well-founded. -Hyrum On Fri, Dec 2, 2011 at 8:22 PM, Niclas Hedhman nic...@hedhman.org wrote: SO, IIUIC, the first step is to import TRAC, and we will have primarily a BSD codebase as the main body of code? Does this mean that all BSD notices in source files must live in ASF repository for all eternity, assuming that we are allowed to sublicense into ALv2 (which I think is no problem)? And what about the lack of patent license that we offer downstream, but have not received from upstream? Cheers Niclas On Sat, Dec 3, 2011 at 12:14 AM, Mark Struberg strub...@yahoo.de wrote: so this is basically Trac ++ and a fork of Trac ? Or is it a completely rewritten new approach? just curious :) LieGrue, strub - Original Message - From: Hyrum K Wright hyrum.wri...@wandisco.com To: general@incubator.apache.org Cc: Ian Wild ian.w...@wandisco.com; Greg Stein gst...@gmail.com Sent: Friday, December 2, 2011 4:53 PM Subject: [PROPOSAL] Apache Bloodhound Hello Incubator! WANdisco would like to propose the inclusion of a new project, Apache Bloodhound, to the Incubator. The proposal has been posted to the wiki[1], and is also included below. We've privately discussed this project with a number of individuals, but would now like to get the discussion rolling here. Bloodhound is new effort, based on Trac[2], to provide issue tracking and collaboration tools for developers. We realize the proposal is a work-in-progress, and as such look forward to feedback and discussion. We hope to attract mentors and other interested parties through the incubation proposal process, and further diversify the community as we move through incubation. In particular, this project is an opportunity to build a new community around the codebase, and we look forward to doing so at the ASF. -Hyrum [1] http://wiki.apache.org/incubator/BloodhoundProposal [2] http://trac.edgewall.org/ = Bloodhound - Collaborative development tools based on Trac = == Abstract == Bloodhound will be a software development collaboration tool, including issue tracking, wiki and repository browsing. Essentially an improved distribution of the well-known Trac project, Bloodhound will include the common and useful plugins to enable a more complete distribution than a typical Trac installation. == Proposal == Bloodhound will be a software development collaboration tool, based on the existing Trac project, which will include a repository browser, wiki, and defect tracker. In addition to the standard Trac installation, Bloodhound will incorporate a number of popular modules into the core distribution, and include additional improvements developed (as [[http://trac-hacks.org/|plugins]]) outside the Trac project. == Background == The
Re: Feedback on updated NOTICE and LICENSE files (was: [VOTE] Release Kafka 0.7.0-incubating)
On Mon, Dec 5, 2011 at 6:45 PM, Niclas Hedhman nic...@hedhman.org wrote: On Tue, Dec 6, 2011 at 6:25 AM, Patrick Hunt ph...@apache.org wrote: Personally I don't believe whirr is in error. Voldemort is under Apache 2.0 license, and as such falls under this: http://www.apache.org/legal/resolved.html#required-third-party-notices See paragraph 4.4 of Apache License ver 2.0. If Voldemort contains a NOTICE file, then it must be carried forward. If it doesn't, IMHO you should have an entry in NOTICE that says the work contains the Voldemort component. Hm, it does have a notice, it's pretty big/hairy: https://github.com/voldemort/voldemort/blob/master/NOTICE perhaps you can help me understand this a bit better, 4.4 addresses Derivative Works, which afaict whirr is not: Derivative Works shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. as whirr is merely linking to the interfaces of the work (whirr pulls in the jar file of/from voldemort) and not making any revision/annotation/modifications of the original. Am I not reading that right? (IANAL) I also notice in 4.4 where is says excluding those notices that do not pertain to any part of the Derivative Works. Given that whirr is only including a single jar - from voldemort itself, not jetty/junit/etc... would it not be correct to say that these other notices do not pertain to whirr's use? Thanks! Patrick - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
