Re: Feedback on updated NOTICE and LICENSE files (was: [VOTE] Release Kafka 0.7.0-incubating)
On 1 December 2011 06:16, Dennis E. Hamilton dennis.hamil...@acm.org wrote: I notice that the NOTICE has this incomplete statement: This product includes the scala runtime and compiler (www.scala-lang.org) developed by EPFL, which includes the following license: There is not any following license. Nor should there be in the NOTICE file. I think the SCALA NOTICE should read This product includes the scala runtime and compiler (www.scala-lang.org) Copyright (c) 2002-2010 EPFL, Lausanne, unless otherwise specified. In my reading of it, that is all the license requires. This assumes that the product does indeed *include* the SCALA compiler. Otherwise the references must be removed from NOTICE and LICENSE. I also notice that the LICENSE file has copyright notices. I don't think that's a problem; they are often included in 3rd party licenses. - Dennis -Original Message- From: Neha Narkhede [mailto:neha.narkh...@gmail.com] Sent: Wednesday, November 30, 2011 18:30 To: general@incubator.apache.org Cc: kafka-us...@incubator.apache.org Subject: Feedback on updated NOTICE and LICENSE files (was: [VOTE] Release Kafka 0.7.0-incubating) Hi, The Kafka community is hoping to get some feedback on the updated NOTICE and LICENSE files for Kafka, before we post a new vote for it. http://people.apache.org/~nehanarkhede/NOTICE http://people.apache.org/~nehanarkhede/LICENSE The previous vote thread or release artifacts are here - http://apache.markmail.org/message/hntuhwkbazwlfdoe?q=Kafka+list:org.apache.incubator.general We would appreciate it if you can please take the time to review this now, since we would like to ensure a smoother vote this time around. Thanks, Neha - 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 1 December 2011 02:29, Neha Narkhede neha.narkh...@gmail.com wrote: Hi, The Kafka community is hoping to get some feedback on the updated NOTICE and LICENSE files for Kafka, before we post a new vote for it. http://people.apache.org/~nehanarkhede/NOTICE There are spurious === lines at the top of the file; these must be removed. http://people.apache.org/~nehanarkhede/LICENSE All license for 3rd party products should be present in the LICENSE file. If the identical license is shared between several products, there's only need to add it once. Add a header line before the additional licenses to say what they are for. For example: http://svn.apache.org/repos/asf/httpd/httpd/trunk/LICENSE For 3rd party products under AL 2.0, add a list at the end of the AL license text, before any other licenses. As it stands, either the NOTICE file is wrong, or the LICENSE file is wrong, because the NOTICE file should not mention 3rd party products that are not in the LICENSE file. And neither should mention code that is not actually included in the release artifacts. The previous vote thread or release artifacts are here - http://apache.markmail.org/message/hntuhwkbazwlfdoe?q=Kafka+list:org.apache.incubator.general We would appreciate it if you can please take the time to review this now, since we would like to ensure a smoother vote this time around. Thanks, Neha - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [POLL] Suitable Name Search: Drop Or Retain?
On Wed, Nov 30, 2011 at 2:15 PM, Prescott Nasser geobmx...@hotmail.com wrote: Hey Robert, its not clear to me why a suitable name search should be dropped - is that because the brand team will do this search on a projects behalf? This seems likely to me But this is a POLL. Each option has advantages and disadvantages. I see nameprotect is outdated, but a quick search by project members to see if there are conflicts is still probably a good thing. It just might not have to be as thorough if brand is ultimately going to do their own search. This seems likely to me This is how Incubator rules accumulate. Podlings needs help, so guidance is documented. Over time these conventions harden into rules. If the Incubator community wants to preserve quality with fewer rules, it need to do less. Robert - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Incubator PMC/Board report for Dec 2011 ([ppmc])
Dear podling, This email was sent by an automated system on behalf of the Apache Incubator PMC. It is an initial reminder to give you plenty of time to prepare your quarterly board report. The board meeting is scheduled for Wed, 21 December 2011, 10:00:00 PST. The report for your podling will form a part of the Incubator PMC report. The Incubator PMC requires your report to be submitted 2 weeks before the board meeting, to allow sufficient time for review and submission (Wed, Dec 7th). Please submit your report with sufficient time to allow the incubator PMC, and subsequently board members to review and digest. Again, the very latest you should submit your report is 2 weeks prior to the board meeting. Thanks, The Apache Incubator PMC Submitting your Report -- Your report should contain the following: * Your project name * A brief description of your project, which assumes no knowledge of the project or necessarily of its field * A list of the three most important issues to address in the move towards graduation. * Any issues that the Incubator PMC or ASF Board might wish/need to be aware of * How has the community developed since the last report * How has the project developed since the last report. This should be appended to the Incubator Wiki page at: http://wiki.apache.org/incubator/December2011 Note: This manually populated. You may need to wait a little before this page is created from a template. Mentors --- Mentors should review reports for their project(s) and sign them off on the Incubator wiki page. Signing off reports shows that you are following the project - projects that are not signed may raise alarms for the Incubator PMC. Incubator PMC - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Incubator PMC/Board report for Dec 2011 ([ppmc])
The tashi-dev mailing list just got the following message from an unreplyable Marvin. The Tashi project reports in January, April, July and October. Can this be ignored, or is our reporting schedule changing? Thanks, Michael. Marvin wrote: Dear podling, This email was sent by an automated system on behalf of the Apache Incubator PMC. It is an initial reminder to give you plenty of time to prepare your quarterly board report. The board meeting is scheduled for Wed, 21 December 2011, 10:00:00 PST. The report for your podling will form a part of the Incubator PMC report. The Incubator PMC requires your report to be submitted 2 weeks before the board meeting, to allow sufficient time for review and submission (Wed, Dec 7th). Please submit your report with sufficient time to allow the incubator PMC, and subsequently board members to review and digest. Again, the very latest you should submit your report is 2 weeks prior to the board meeting. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Incubator PMC/Board report for Dec 2011 ([ppmc])
The tashi-dev mailing list just got the following message from an unreplyable Marvin. The Tashi project reports in January, April, July and October. Can this be ignored, or is our reporting schedule changing? Thanks, Michael. Marvin wrote: Dear podling, This email was sent by an automated system on behalf of the Apache Incubator PMC. It is an initial reminder to give you plenty of time to prepare your quarterly board report. The board meeting is scheduled for Wed, 21 December 2011, 10:00:00 PST. The report for your podling will form a part of the Incubator PMC report. The Incubator PMC requires your report to be submitted 2 weeks before the board meeting, to allow sufficient time for review and submission (Wed, Dec 7th). Please submit your report with sufficient time to allow the incubator PMC, and subsequently board members to review and digest. Again, the very latest you should submit your report is 2 weeks prior to the board meeting. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Incubator PMC/Board report for Dec 2011 ([ppmc])
Dear podling, This email was sent by an automated system on behalf of the Apache Incubator PMC. It is an initial reminder to give you plenty of time to prepare your quarterly board report. The board meeting is scheduled for Wed, 21 December 2011, 10:00:00 PST. The report for your podling will form a part of the Incubator PMC report. The Incubator PMC requires your report to be submitted 2 weeks before the board meeting, to allow sufficient time for review and submission (Wed, Dec 7th). Please submit your report with sufficient time to allow the incubator PMC, and subsequently board members to review and digest. Again, the very latest you should submit your report is 2 weeks prior to the board meeting. Thanks, The Apache Incubator PMC Submitting your Report -- Your report should contain the following: * Your project name * A brief description of your project, which assumes no knowledge of the project or necessarily of its field * A list of the three most important issues to address in the move towards graduation. * Any issues that the Incubator PMC or ASF Board might wish/need to be aware of * How has the community developed since the last report * How has the project developed since the last report. This should be appended to the Incubator Wiki page at: http://wiki.apache.org/incubator/2011 Note: This manually populated. You may need to wait a little before this page is created from a template. Mentors --- Mentors should review reports for their project(s) and sign them off on the Incubator wiki page. Signing off reports shows that you are following the project - projects that are not signed may raise alarms for the Incubator PMC. Incubator PMC - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Incubator PMC/Board report for Dec 2011 ([ppmc])
Same thing on empire-db-dev@ I suppose Marvin (bot) somehow mailed the wrong projects. Cheers, F On Thu, Dec 1, 2011 at 2:57 AM, Michael Stroucken stroucki+apa...@andrew.cmu.edu wrote: The tashi-dev mailing list just got the following message from an unreplyable Marvin. The Tashi project reports in January, April, July and October. Can this be ignored, or is our reporting schedule changing? Thanks, Michael. Marvin wrote: Dear podling, This email was sent by an automated system on behalf of the Apache Incubator PMC. It is an initial reminder to give you plenty of time to prepare your quarterly board report. The board meeting is scheduled for Wed, 21 December 2011, 10:00:00 PST. The report for your podling will form a part of the Incubator PMC report. The Incubator PMC requires your report to be submitted 2 weeks before the board meeting, to allow sufficient time for review and submission (Wed, Dec 7th). Please submit your report with sufficient time to allow the incubator PMC, and subsequently board members to review and digest. Again, the very latest you should submit your report is 2 weeks prior to the board meeting. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- 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
Re: Incubator PMC/Board report for Dec 2011 ([ppmc])
That would explain why he claimed to have mailed BeanValidation-dev, and our yet having failed AFAIK to receive the notification. Matt On Thu, Dec 1, 2011 at 9:49 AM, Francis De Brabandere franci...@gmail.com wrote: Same thing on empire-db-dev@ I suppose Marvin (bot) somehow mailed the wrong projects. Cheers, F On Thu, Dec 1, 2011 at 2:57 AM, Michael Stroucken stroucki+apa...@andrew.cmu.edu wrote: The tashi-dev mailing list just got the following message from an unreplyable Marvin. The Tashi project reports in January, April, July and October. Can this be ignored, or is our reporting schedule changing? Thanks, Michael. Marvin wrote: Dear podling, This email was sent by an automated system on behalf of the Apache Incubator PMC. It is an initial reminder to give you plenty of time to prepare your quarterly board report. The board meeting is scheduled for Wed, 21 December 2011, 10:00:00 PST. The report for your podling will form a part of the Incubator PMC report. The Incubator PMC requires your report to be submitted 2 weeks before the board meeting, to allow sufficient time for review and submission (Wed, Dec 7th). Please submit your report with sufficient time to allow the incubator PMC, and subsequently board members to review and digest. Again, the very latest you should submit your report is 2 weeks prior to the board meeting. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- 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 - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Incubator PMC/Board report for Dec 2011 ([ppmc])
My advice is to go by the published reporting period schedule, not by Marvin. Recently work was done to consolidate some of Marvin's features into a single script, and that seemingly has an off-by-one error wrt the incubator schedule. We'll try to get it fixed before the next batch of reminders goes out. Thanks for the patience. From: Francis De Brabandere franci...@gmail.com To: general@incubator.apache.org Sent: Thursday, December 1, 2011 10:49 AM Subject: Re: Incubator PMC/Board report for Dec 2011 ([ppmc]) Same thing on empire-db-dev@ I suppose Marvin (bot) somehow mailed the wrong projects. Cheers, F On Thu, Dec 1, 2011 at 2:57 AM, Michael Stroucken stroucki+apa...@andrew.cmu.edu wrote: The tashi-dev mailing list just got the following message from an unreplyable Marvin. The Tashi project reports in January, April, July and October. Can this be ignored, or is our reporting schedule changing? Thanks, Michael. Marvin wrote: Dear podling, This email was sent by an automated system on behalf of the Apache Incubator PMC. It is an initial reminder to give you plenty of time to prepare your quarterly board report. The board meeting is scheduled for Wed, 21 December 2011, 10:00:00 PST. The report for your podling will form a part of the Incubator PMC report. The Incubator PMC requires your report to be submitted 2 weeks before the board meeting, to allow sufficient time for review and submission (Wed, Dec 7th). Please submit your report with sufficient time to allow the incubator PMC, and subsequently board members to review and digest. Again, the very latest you should submit your report is 2 weeks prior to the board meeting. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- 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
Re: Incubator PMC/Board report for Dec 2011 ([ppmc])
On Thu, Dec 1, 2011 at 9:52 AM, Matt Benson gudnabr...@gmail.com wrote: That would explain why he claimed to have mailed BeanValidation-dev, and our yet having failed AFAIK to receive the notification. Er, strike that--we got it after all. Matt On Thu, Dec 1, 2011 at 9:49 AM, Francis De Brabandere franci...@gmail.com wrote: Same thing on empire-db-dev@ I suppose Marvin (bot) somehow mailed the wrong projects. Cheers, F On Thu, Dec 1, 2011 at 2:57 AM, Michael Stroucken stroucki+apa...@andrew.cmu.edu wrote: The tashi-dev mailing list just got the following message from an unreplyable Marvin. The Tashi project reports in January, April, July and October. Can this be ignored, or is our reporting schedule changing? Thanks, Michael. Marvin wrote: Dear podling, This email was sent by an automated system on behalf of the Apache Incubator PMC. It is an initial reminder to give you plenty of time to prepare your quarterly board report. The board meeting is scheduled for Wed, 21 December 2011, 10:00:00 PST. The report for your podling will form a part of the Incubator PMC report. The Incubator PMC requires your report to be submitted 2 weeks before the board meeting, to allow sufficient time for review and submission (Wed, Dec 7th). Please submit your report with sufficient time to allow the incubator PMC, and subsequently board members to review and digest. Again, the very latest you should submit your report is 2 weeks prior to the board meeting. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- 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 - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Incubator PMC/Board report for Dec 2011 ([ppmc])
I agree. Kafka has left the three month monthly reporting window. Regards, Alan On Dec 1, 2011, at 8:23 AM, Jun Rao wrote: I think we should ignore this since Kafka is now on the Jan/Apr/Jul/Oct schedule according to the following wiki. http://wiki.apache.org/incubator/ReportingSchedule Thanks, Jun On Wed, Nov 30, 2011 at 5:08 PM, Marvin no-re...@apache.org wrote: Dear podling, This email was sent by an automated system on behalf of the Apache Incubator PMC. It is an initial reminder to give you plenty of time to prepare your quarterly board report. The board meeting is scheduled for Wed, 21 December 2011, 10:00:00 PST. The report for your podling will form a part of the Incubator PMC report. The Incubator PMC requires your report to be submitted 2 weeks before the board meeting, to allow sufficient time for review and submission (Wed, Dec 7th). Please submit your report with sufficient time to allow the incubator PMC, and subsequently board members to review and digest. Again, the very latest you should submit your report is 2 weeks prior to the board meeting. Thanks, The Apache Incubator PMC Submitting your Report -- Your report should contain the following: * Your project name * A brief description of your project, which assumes no knowledge of the project or necessarily of its field * A list of the three most important issues to address in the move towards graduation. * Any issues that the Incubator PMC or ASF Board might wish/need to be aware of * How has the community developed since the last report * How has the project developed since the last report. This should be appended to the Incubator Wiki page at: http://wiki.apache.org/incubator/2011 Note: This manually populated. You may need to wait a little before this page is created from a template. Mentors --- Mentors should review reports for their project(s) and sign them off on the Incubator wiki page. Signing off reports shows that you are following the project - projects that are not signed may raise alarms for the Incubator PMC. Incubator PMC - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Yan: [PROPOSAL] Apache DeltaSpike - CDI-Extensions project
+1 (binding) Gurkan Kimden: Mark Struberg strub...@yahoo.de Kime: general@incubator.apache.org general@incubator.apache.org Gönderildiği Tarih: 30 Kasım 2011 1:40 Çarşamba Konu: [PROPOSAL] Apache DeltaSpike - CDI-Extensions project Hi! JBoss, The Apache MyFaces CODI team and CDISource would like to propose the Apache DeltaSpike project to the Incubator. We have added the initial proposal to the Wiki[1] and its content is also included below for convenience. There are already a few people who expressed interest in contributing additional CDI Extensions and would like to join this effort. Of course, we are thankful for every helping hand! We are looking forward to feedback and/or questions on the proposal. We already have five mentors, but would very much welcome additional volunteers to help steer Apache DeltaSpike through the incubation process. LieGrue, strub [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
RE: [POLL] Suitable Name Search: Drop Or Retain?
Completely agree , if there is a rule list I dont think this needs to be on it, this is more a best practice imo Sent from my Windows Phone From: Robert Burrell Donkin Sent: 12/1/2011 4:20 AM To: general@incubator.apache.org Subject: Re: [POLL] Suitable Name Search: Drop Or Retain? On Wed, Nov 30, 2011 at 2:15 PM, Prescott Nasser geobmx...@hotmail.com wrote: Hey Robert, its not clear to me why a suitable name search should be dropped - is that because the brand team will do this search on a projects behalf? This seems likely to me But this is a POLL. Each option has advantages and disadvantages. I see nameprotect is outdated, but a quick search by project members to see if there are conflicts is still probably a good thing. It just might not have to be as thorough if brand is ultimately going to do their own search. This seems likely to me This is how Incubator rules accumulate. Podlings needs help, so guidance is documented. Over time these conventions harden into rules. If the Incubator community wants to preserve quality with fewer rules, it need to do less. Robert - 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)
As it stands, either the NOTICE file is wrong, or the LICENSE file is wrong, because the NOTICE file should not mention 3rd party products that are not in the LICENSE file. Thanks for the feedback! As I have already mentioned, we are tracking a bug to fix all non-blocker changes to the NOTICE file for the next release. I will include this feedback there. Correct me if I understood the long discussions on this list, but I don't think this blocks the current release. Add a header line before the additional licenses to say what they are for. We have the header for MIT and Nunit license. Didn't include it for the SCALA license for a project that is written in scala. Also didn't include it for the Apache license for an Apache incubator project. Hope that sounds reasonable. Thanks, Neha On Thu, Dec 1, 2011 at 12:43 AM, sebb seb...@gmail.com wrote: On 1 December 2011 02:29, Neha Narkhede neha.narkh...@gmail.com wrote: Hi, The Kafka community is hoping to get some feedback on the updated NOTICE and LICENSE files for Kafka, before we post a new vote for it. http://people.apache.org/~nehanarkhede/NOTICE There are spurious === lines at the top of the file; these must be removed. http://people.apache.org/~nehanarkhede/LICENSE All license for 3rd party products should be present in the LICENSE file. If the identical license is shared between several products, there's only need to add it once. Add a header line before the additional licenses to say what they are for. For example: http://svn.apache.org/repos/asf/httpd/httpd/trunk/LICENSE For 3rd party products under AL 2.0, add a list at the end of the AL license text, before any other licenses. As it stands, either the NOTICE file is wrong, or the LICENSE file is wrong, because the NOTICE file should not mention 3rd party products that are not in the LICENSE file. And neither should mention code that is not actually included in the release artifacts. The previous vote thread or release artifacts are here - http://apache.markmail.org/message/hntuhwkbazwlfdoe?q=Kafka+list:org.apache.incubator.general We would appreciate it if you can please take the time to review this now, since we would like to ensure a smoother vote this time around. Thanks, Neha - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [POLL] Suitable Name Search: Drop Or Retain?
On Thu, Dec 1, 2011 at 5:32 PM, Prescott Nasser geobmx...@hotmail.com wrote: Completely agree , if there is a rule list I dont think this needs to be on it, this is more a best practice imo Best practices tend to become the rule Robert - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Incubator PMC/Board report for Dec 2011 ([ppmc])
To our mentors, The September 2011 report was not signed off. Could one of you review the current December report and sign off on it? Thanks! Karl On Wed, Nov 30, 2011 at 8:09 PM, Marvin no-re...@apache.org wrote: Dear podling, This email was sent by an automated system on behalf of the Apache Incubator PMC. It is an initial reminder to give you plenty of time to prepare your quarterly board report. The board meeting is scheduled for Wed, 21 December 2011, 10:00:00 PST. The report for your podling will form a part of the Incubator PMC report. The Incubator PMC requires your report to be submitted 2 weeks before the board meeting, to allow sufficient time for review and submission (Wed, Dec 7th). Please submit your report with sufficient time to allow the incubator PMC, and subsequently board members to review and digest. Again, the very latest you should submit your report is 2 weeks prior to the board meeting. Thanks, The Apache Incubator PMC Submitting your Report -- Your report should contain the following: * Your project name * A brief description of your project, which assumes no knowledge of the project or necessarily of its field * A list of the three most important issues to address in the move towards graduation. * Any issues that the Incubator PMC or ASF Board might wish/need to be aware of * How has the community developed since the last report * How has the project developed since the last report. This should be appended to the Incubator Wiki page at: http://wiki.apache.org/incubator/2011 Note: This manually populated. You may need to wait a little before this page is created from a template. Mentors --- Mentors should review reports for their project(s) and sign them off on the Incubator wiki page. Signing off reports shows that you are following the project - projects that are not signed may raise alarms for the Incubator PMC. Incubator PMC - 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 Dec 1, 2011, at 12:55 PM, Neha Narkhede wrote: As it stands, either the NOTICE file is wrong, or the LICENSE file is wrong, because the NOTICE file should not mention 3rd party products that are not in the LICENSE file. Thanks for the feedback! As I have already mentioned, we are tracking a bug to fix all non-blocker changes to the NOTICE file for the next release. I will include this feedback there. Correct me if I understood the long discussions on this list, but I don't think this blocks the current release. My point would be that it's very likely that your LICENSE file is incorrect (i.e. it is missing necessary license information). So far, the only LICENSE file changes that have been made are the explicit issues that have been pointed out to you. I think the Kafka community needs to review all of their artifacts and make sure that their licenses/notices are accurately documented in the LICENSE (and NOTICE). I don't see any evidence that the community has attempted to do this. I think the artifacts that need to be reviewed are: ./clients/csharp/lib/nunit/2.5.9/nunit.framework.dll ./contrib/hadoop-consumer/lib/avro-1.4.0.jar ./contrib/hadoop-consumer/lib/commons-logging-1.0.4.jar ./contrib/hadoop-consumer/lib/hadoop-0.20.2-core.jar ./contrib/hadoop-consumer/lib/jackson-core-asl-1.5.5.jar ./contrib/hadoop-consumer/lib/jackson-mapper-asl-1.5.5.jar ./contrib/hadoop-consumer/lib/pig-0.8.0-core.jar ./contrib/hadoop-consumer/lib/piggybank.jar ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/commons-codec-1.2.jar ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/commons-httpclient-3.1.jar ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/commons-logging-1.0.4.jar ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/joda-time-1.6.jar ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/jopt-simple-3.2.jar ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/log4j-1.2.15.jar ./contrib/hadoop-consumer/target/scala_2.8.0/hadoop-consumer_2.8.0-0.7.0.jar ./contrib/hadoop-producer/lib/avro-1.4.0.jar ./contrib/hadoop-producer/lib/commons-logging-1.0.4.jar ./contrib/hadoop-producer/lib/hadoop-0.20.2-core.jar ./contrib/hadoop-producer/lib/jackson-core-asl-1.5.5.jar ./contrib/hadoop-producer/lib/jackson-mapper-asl-1.5.5.jar ./contrib/hadoop-producer/lib/pig-0.8.0-core.jar ./contrib/hadoop-producer/lib/piggybank.jar ./contrib/hadoop-producer/lib_managed/scala_2.8.0/compile/ant-1.7.1.jar ./contrib/hadoop-producer/lib_managed/scala_2.8.0/compile/ant-launcher-1.7.1.jar ./contrib/hadoop-producer/lib_managed/scala_2.8.0/compile/asm-3.2.jar ./contrib/hadoop-producer/lib_managed/scala_2.8.0/compile/avro-1.4.1.jar ./contrib/hadoop-producer/lib_managed/scala_2.8.0/compile/commons-collections-3.2.1.jar ./contrib/hadoop-producer/lib_managed/scala_2.8.0/compile/commons-lang-2.5.jar ./contrib/hadoop-producer/lib_managed/scala_2.8.0/compile/jackson-core-asl-1.5.5.jar ./contrib/hadoop-producer/lib_managed/scala_2.8.0/compile/jackson-mapper-asl-1.5.5.jar ./contrib/hadoop-producer/lib_managed/scala_2.8.0/compile/jetty-6.1.22.jar ./contrib/hadoop-producer/lib_managed/scala_2.8.0/compile/jetty-util-6.1.22.jar ./contrib/hadoop-producer/lib_managed/scala_2.8.0/compile/jopt-simple-3.2.jar ./contrib/hadoop-producer/lib_managed/scala_2.8.0/compile/log4j-1.2.15.jar ./contrib/hadoop-producer/lib_managed/scala_2.8.0/compile/oro-2.0.8.jar ./contrib/hadoop-producer/lib_managed/scala_2.8.0/compile/paranamer-2.2.jar ./contrib/hadoop-producer/lib_managed/scala_2.8.0/compile/paranamer-ant-2.2.jar ./contrib/hadoop-producer/lib_managed/scala_2.8.0/compile/paranamer-generator-2.2.jar ./contrib/hadoop-producer/lib_managed/scala_2.8.0/compile/qdox-1.10.1.jar ./contrib/hadoop-producer/lib_managed/scala_2.8.0/compile/servlet-api-2.5-20081211.jar ./contrib/hadoop-producer/lib_managed/scala_2.8.0/compile/slf4j-api-1.5.11.jar ./contrib/hadoop-producer/lib_managed/scala_2.8.0/compile/velocity-1.6.4.jar ./contrib/hadoop-producer/target/scala_2.8.0/hadoop-producer_2.8.0-0.7.0.jar ./core/lib/zkclient-20110412.jar ./core/lib_managed/scala_2.8.0/compile/jopt-simple-3.2.jar ./core/lib_managed/scala_2.8.0/compile/log4j-1.2.15.jar ./core/lib_managed/scala_2.8.0/compile/zookeeper-3.3.3.jar ./core/target/scala_2.8.0/kafka-0.7.0.jar ./examples/lib_managed/scala_2.8.0/compile/jopt-simple-3.2.jar ./examples/lib_managed/scala_2.8.0/compile/log4j-1.2.15.jar ./examples/target/scala_2.8.0/kafka-java-examples-0.7.0.jar ./kafka-0.7.0.jar ./lib/apache-rat-0.8-SNAPSHOT.jar ./lib/sbt-launch.jar ./project/boot/scala-2.8.0/lib/scala-compiler.jar ./project/boot/scala-2.8.0/lib/scala-library.jar I took a quick look at some of these artifacts. I definitely see licenses missing from the LICENSE file. For example: paranamer-2.2.jar -- http://paranamer.codehaus.org/info/license.html sbt-launch.jar -- has 4 license files -- license, licenses/LICENSE_Scala, licenses/LICENSE_Apache, licenses/LICENSE_JLine (2 are missing from
RE: [POLL] Suitable Name Search: Drop Or Retain?
This is perhaps an area where the incubator needs more caution before best practice turns into a rule. You can call it guidance rather than best practices, but I think you'll just say that's the same thing. I do agree with your statements though Sent from my Windows Phone From: Robert Burrell Donkin Sent: 12/1/2011 10:00 AM To: general@incubator.apache.org Subject: Re: [POLL] Suitable Name Search: Drop Or Retain? On Thu, Dec 1, 2011 at 5:32 PM, Prescott Nasser geobmx...@hotmail.com wrote: Completely agree , if there is a rule list I dont think this needs to be on it, this is more a best practice imo Best practices tend to become the rule Robert - 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 Thu, Dec 1, 2011 at 1:05 PM, Kevan Miller kevan.mil...@gmail.com wrote: I took a quick look at some of these artifacts. I definitely see licenses missing from the LICENSE file. For example: paranamer-2.2.jar -- http://paranamer.codehaus.org/info/license.html The link you reference puts this jar in the public domain and no LICENSE update is required. sbt-launch.jar -- has 4 license files -- license, licenses/LICENSE_Scala, licenses/LICENSE_Apache, licenses/LICENSE_JLine (2 are missing from your LICENSE) hadoop -- has a unique license for the org.apache.hadoop.util.bloom.* classes. Thanks for pointing these out. I'm certain that no project with lots of dependencies updates its LICENSE every time it takes an update. One gets around this by downloading dependencies rather than distributing them? I don't know how many other problems there are… I'm sorry, but I don't have time to generate this information for you (nor should I need to). This is something the Kafka community needs to take on. Thanks for what you've offered. Many of the jars contain LICENSE files. Before spending hours crawling through every dependency, can someone point to the documentation requiring that the top-level LICENSE file contain the transitive closure of all code redistributed through the artifact? -C - 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)
Does Apache has tools (like rat) to extract all the needed license? Digging out the license manually is both labour intensive and error prone. Thanks, Jun On Thu, Dec 1, 2011 at 1:05 PM, Kevan Miller kevan.mil...@gmail.com wrote: On Dec 1, 2011, at 12:55 PM, Neha Narkhede wrote: As it stands, either the NOTICE file is wrong, or the LICENSE file is wrong, because the NOTICE file should not mention 3rd party products that are not in the LICENSE file. Thanks for the feedback! As I have already mentioned, we are tracking a bug to fix all non-blocker changes to the NOTICE file for the next release. I will include this feedback there. Correct me if I understood the long discussions on this list, but I don't think this blocks the current release. My point would be that it's very likely that your LICENSE file is incorrect (i.e. it is missing necessary license information). So far, the only LICENSE file changes that have been made are the explicit issues that have been pointed out to you. I think the Kafka community needs to review all of their artifacts and make sure that their licenses/notices are accurately documented in the LICENSE (and NOTICE). I don't see any evidence that the community has attempted to do this. I think the artifacts that need to be reviewed are: ./clients/csharp/lib/nunit/2.5.9/nunit.framework.dll ./contrib/hadoop-consumer/lib/avro-1.4.0.jar ./contrib/hadoop-consumer/lib/commons-logging-1.0.4.jar ./contrib/hadoop-consumer/lib/hadoop-0.20.2-core.jar ./contrib/hadoop-consumer/lib/jackson-core-asl-1.5.5.jar ./contrib/hadoop-consumer/lib/jackson-mapper-asl-1.5.5.jar ./contrib/hadoop-consumer/lib/pig-0.8.0-core.jar ./contrib/hadoop-consumer/lib/piggybank.jar ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/commons-codec-1.2.jar ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/commons-httpclient-3.1.jar ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/commons-logging-1.0.4.jar ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/joda-time-1.6.jar ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/jopt-simple-3.2.jar ./contrib/hadoop-consumer/lib_managed/scala_2.8.0/compile/log4j-1.2.15.jar ./contrib/hadoop-consumer/target/scala_2.8.0/hadoop-consumer_2.8.0-0.7.0.jar ./contrib/hadoop-producer/lib/avro-1.4.0.jar ./contrib/hadoop-producer/lib/commons-logging-1.0.4.jar ./contrib/hadoop-producer/lib/hadoop-0.20.2-core.jar ./contrib/hadoop-producer/lib/jackson-core-asl-1.5.5.jar ./contrib/hadoop-producer/lib/jackson-mapper-asl-1.5.5.jar ./contrib/hadoop-producer/lib/pig-0.8.0-core.jar ./contrib/hadoop-producer/lib/piggybank.jar ./contrib/hadoop-producer/lib_managed/scala_2.8.0/compile/ant-1.7.1.jar ./contrib/hadoop-producer/lib_managed/scala_2.8.0/compile/ant-launcher-1.7.1.jar ./contrib/hadoop-producer/lib_managed/scala_2.8.0/compile/asm-3.2.jar ./contrib/hadoop-producer/lib_managed/scala_2.8.0/compile/avro-1.4.1.jar ./contrib/hadoop-producer/lib_managed/scala_2.8.0/compile/commons-collections-3.2.1.jar ./contrib/hadoop-producer/lib_managed/scala_2.8.0/compile/commons-lang-2.5.jar ./contrib/hadoop-producer/lib_managed/scala_2.8.0/compile/jackson-core-asl-1.5.5.jar ./contrib/hadoop-producer/lib_managed/scala_2.8.0/compile/jackson-mapper-asl-1.5.5.jar ./contrib/hadoop-producer/lib_managed/scala_2.8.0/compile/jetty-6.1.22.jar ./contrib/hadoop-producer/lib_managed/scala_2.8.0/compile/jetty-util-6.1.22.jar ./contrib/hadoop-producer/lib_managed/scala_2.8.0/compile/jopt-simple-3.2.jar ./contrib/hadoop-producer/lib_managed/scala_2.8.0/compile/log4j-1.2.15.jar ./contrib/hadoop-producer/lib_managed/scala_2.8.0/compile/oro-2.0.8.jar ./contrib/hadoop-producer/lib_managed/scala_2.8.0/compile/paranamer-2.2.jar ./contrib/hadoop-producer/lib_managed/scala_2.8.0/compile/paranamer-ant-2.2.jar ./contrib/hadoop-producer/lib_managed/scala_2.8.0/compile/paranamer-generator-2.2.jar ./contrib/hadoop-producer/lib_managed/scala_2.8.0/compile/qdox-1.10.1.jar ./contrib/hadoop-producer/lib_managed/scala_2.8.0/compile/servlet-api-2.5-20081211.jar ./contrib/hadoop-producer/lib_managed/scala_2.8.0/compile/slf4j-api-1.5.11.jar ./contrib/hadoop-producer/lib_managed/scala_2.8.0/compile/velocity-1.6.4.jar ./contrib/hadoop-producer/target/scala_2.8.0/hadoop-producer_2.8.0-0.7.0.jar ./core/lib/zkclient-20110412.jar ./core/lib_managed/scala_2.8.0/compile/jopt-simple-3.2.jar ./core/lib_managed/scala_2.8.0/compile/log4j-1.2.15.jar ./core/lib_managed/scala_2.8.0/compile/zookeeper-3.3.3.jar ./core/target/scala_2.8.0/kafka-0.7.0.jar ./examples/lib_managed/scala_2.8.0/compile/jopt-simple-3.2.jar ./examples/lib_managed/scala_2.8.0/compile/log4j-1.2.15.jar ./examples/target/scala_2.8.0/kafka-java-examples-0.7.0.jar ./kafka-0.7.0.jar ./lib/apache-rat-0.8-SNAPSHOT.jar ./lib/sbt-launch.jar ./project/boot/scala-2.8.0/lib/scala-compiler.jar ./project/boot/scala-2.8.0/lib/scala-library.jar I took a
Re: Incubator PMC/Board report for Dec 2011 ([ppmc])
Joe Schaefer wrote: My advice is to go by the published reporting period schedule, not by Marvin. Recently work was done to consolidate some of Marvin's features into a single script, and that seemingly has an off-by-one error wrt the incubator schedule. Yes good advice. Reminders are just a backup. However there is a problem. Some projects did not fix their entry in the ReportingSchedule before the start of the month. So the December2011 page is a bit confused. Please add/remove your project as needed. We'll try to get it fixed before the next batch of reminders goes out. Thanks for the patience. The reminder system should be correct now. -David - 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 1 December 2011 21:58, Chris Douglas cdoug...@apache.org wrote: On Thu, Dec 1, 2011 at 1:05 PM, Kevan Miller kevan.mil...@gmail.com wrote: I took a quick look at some of these artifacts. I definitely see licenses missing from the LICENSE file. For example: paranamer-2.2.jar -- http://paranamer.codehaus.org/info/license.html The link you reference puts this jar in the public domain and no LICENSE update is required. It should still be listed for completeness, otherwise reviewers (and possibly users) will ask the same question again. sbt-launch.jar -- has 4 license files -- license, licenses/LICENSE_Scala, licenses/LICENSE_Apache, licenses/LICENSE_JLine (2 are missing from your LICENSE) hadoop -- has a unique license for the org.apache.hadoop.util.bloom.* classes. Thanks for pointing these out. I'm certain that no project with lots of dependencies updates its LICENSE every time it takes an update. One The Apache projects I know that include 3rd party jars do update the LICENSE ( NOTICE if reqd) file every time a new library is included in the distribution. It's really not difficult. Before deciding to use a 3rd party jar, the project needs to establish the license anyway, and check it is acceptable. All the required information is then to hand for updating the NL files. For podlings there is a catch-up, but again that must be done *before* a release is made, because a release must only include code under allowable licenses. gets around this by downloading dependencies rather than distributing them? Yes, that can eliminate some of the work. However, there are still some requirements for non-included dependencies. See http://www.apache.org/legal/resolved.html I don't know how many other problems there are… I'm sorry, but I don't have time to generate this information for you (nor should I need to). This is something the Kafka community needs to take on. Thanks for what you've offered. Many of the jars contain LICENSE files. Before spending hours crawling through every dependency, can someone point to the documentation requiring that the top-level LICENSE file contain the transitive closure of all code redistributed through the artifact? -C You only need to establish the license for direct dependencies, but they do need to be in the one file. http://www.apache.org/dev/release.html#distributing-code-under-several-licenses The podling only has to do this once for each dependency. It may be tedious, but it is necessary, not least so that the end users (and the release reviewers!) have all the necessary details to hand. - 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)
Kevan- You appear to have generated your list of jars from looking at kafka-0.7.0-incubating.tar.gz, the binary distribution that has been built as a customary courtesy as part of the release attempt. This includes quite a few jars that are not included in the source tree since binary distributions do include transitive dependencies. Are you saying that entries need to be included in NOTICE and LICENSE for jars/dlls that are included in binary releases? A quick check shows that neither Hadoop, nor HBase. nor Whirr (recently with a an incubator release) do not do this. If the answer is yes, then it looks like everyone (from my quick sample) is out of compliance. If the answer is no, then it looks like the only libraries that need to be included are those that are checkedin/included-in-a-source release, which is on the order of 17, but can be decreased down to four or five if Hadoop is brought in via sbt/maven. Thanks, Jakob On Thu, Dec 1, 2011 at 4:33 PM, sebb seb...@gmail.com wrote: On 1 December 2011 21:58, Chris Douglas cdoug...@apache.org wrote: On Thu, Dec 1, 2011 at 1:05 PM, Kevan Miller kevan.mil...@gmail.com wrote: I took a quick look at some of these artifacts. I definitely see licenses missing from the LICENSE file. For example: paranamer-2.2.jar -- http://paranamer.codehaus.org/info/license.html The link you reference puts this jar in the public domain and no LICENSE update is required. It should still be listed for completeness, otherwise reviewers (and possibly users) will ask the same question again. sbt-launch.jar -- has 4 license files -- license, licenses/LICENSE_Scala, licenses/LICENSE_Apache, licenses/LICENSE_JLine (2 are missing from your LICENSE) hadoop -- has a unique license for the org.apache.hadoop.util.bloom.* classes. Thanks for pointing these out. I'm certain that no project with lots of dependencies updates its LICENSE every time it takes an update. One The Apache projects I know that include 3rd party jars do update the LICENSE ( NOTICE if reqd) file every time a new library is included in the distribution. It's really not difficult. Before deciding to use a 3rd party jar, the project needs to establish the license anyway, and check it is acceptable. All the required information is then to hand for updating the NL files. For podlings there is a catch-up, but again that must be done *before* a release is made, because a release must only include code under allowable licenses. gets around this by downloading dependencies rather than distributing them? Yes, that can eliminate some of the work. However, there are still some requirements for non-included dependencies. See http://www.apache.org/legal/resolved.html I don't know how many other problems there are… I'm sorry, but I don't have time to generate this information for you (nor should I need to). This is something the Kafka community needs to take on. Thanks for what you've offered. Many of the jars contain LICENSE files. Before spending hours crawling through every dependency, can someone point to the documentation requiring that the top-level LICENSE file contain the transitive closure of all code redistributed through the artifact? -C You only need to establish the license for direct dependencies, but they do need to be in the one file. http://www.apache.org/dev/release.html#distributing-code-under-several-licenses The podling only has to do this once for each dependency. It may be tedious, but it is necessary, not least so that the end users (and the release reviewers!) have all the necessary details to hand. - 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 - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache Accumulo 1.3.5-incubating (rc8)
+1 binding Regards, Alan On Nov 29, 2011, at 6:24 AM, Eric Newton wrote: This is the first incubator release for Apache Accumulo, with the artifacts versioned as 1.3.5-incubating. VOTE: http://www.mail-archive.com/accumulo-dev@incubator.apache.org/msg00939.html RESULT: http://www.mail-archive.com/accumulo-dev@incubator.apache.org/msg01038.html SVN source tag: http://svn.apache.org/viewvc/incubator/accumulo/tags/1.3.5rc8/ Release artifacts: http://people.apache.org/~ecn Vote closes in 72 hours. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
