Re: [VOTE] Release Hama 0.3-incubating (RC2)
Presumably this means the vote is cancelled, because the ZIP being voted on hasn't been updated? Also... 1. as I understand it, notices and licenses for 3rd party products should not go in NOTICE and LICENSE, but should go in DEPENDENCIES. This can be generated automatically using maven-remote-resources-plugin; missing information can go in supplemental-models.xml file. The apache-incubator-disclaimer-resource-bundle (for maven-remote-resources-plugin) also allows the DEPENDENCIES text to be customized. 2. The NOTICE, in particular, should not be modified at all. I know there are many Apache projects that haven't caught up with this guidance, but this is what the apache-incubator-disclaimer-resource-bundle specifies. See [1] 3. I noticed that hama v0.2 was released to maven central repo. Why aren't the artifacts (including the source zip) uploaded to a staging repo on repository.apache.org? 4. the source release seems to contain jar files (in the lib folder). This doesn't seem right to me. 5. rather than use javax.servlet from Sun (under CDDL), you could use those from geronimo specs (under ASL). Dan [1] http://jira.codehaus.org/browse/MRRESOURCES-32 On 06/07/2011 02:27, Edward J. Yoon wrote: Hi, Stefan Thanks for your review. I've added CDDLv1.0 license and notice. http://svn.apache.org/repos/asf/incubator/hama/branches/0.3/NOTICE.txt http://svn.apache.org/repos/asf/incubator/hama/branches/0.3/LICENSE.txt Could you please check the files again? Thanks. On Wed, Jul 6, 2011 at 6:57 AM, Stefan Seelmannseelm...@apache.org wrote: Hi Edward, I found an issue which is a blocker IMO: jsp-2.1-6.1.4.jar and jsp-api-2.1-6.1.4.jar from Jetty are included. To my knowlege they are licensed under CDDL*. This is a Category B [4] license so either - add the license [1] and the notice excerp [2] to the Hama LICENSE and NOTICE files or - try to use the JSP API and implementation from Tomcat [3] (preferred) Another thing I noticed is that the including hama-examples-0.3.0-incubating.jar is a shaded jar and contains all dependencies. I just wanted to let you know, not sure if that's intended. All other things look good. Kind Regards, Stefan * According to Jetty's notice file [2] the JSP implementation is provided from Glassfish. When looking into the sources (http://repo1.maven.org/maven2/org/mortbay/jetty/jsp-api-2.1/6.1.4/jsp-api-2.1-6.1.4-sources.jar and http://repo1.maven.org/maven2/org/mortbay/jetty/jsp-2.1/6.1.4/jsp-2.1-6.1.4-sources.jar) there are Java files from Sun with CDDL license header. [1] http://svn.codehaus.org/jetty/jetty/tags/jetty-6.1.4/LICENSES/CDDLv1.0.txt [2] http://svn.codehaus.org/jetty/jetty/tags/jetty-6.1.4/LICENSES/NOTICE.txt [3] http://repo1.maven.org/maven2/org/apache/tomcat/jsp-api/6.0.32/ [4] http://apache.org/legal/resolved.html#category-b On Fri, Jul 1, 2011 at 5:36 PM, Edward J. Yoonedwardy...@apache.org wrote: Hi all, The Apache Hama community voted on and approved a proposal to release Apache Hama 0.3-incubating (RC2). This release contains performance improvements and new features e.g., maven build, web UI for Hama cluster, MessageBundle, Dijkstra's Shortest Path and PageRank examples. Please vote on the RC2 for Apache Hama 0.3-Incubating. We've already received 2 binding IPMC +1 votes. Vote thread: http://markmail.org/thread/qx4u3kjflwe524pf Artifact and signatures: http://people.apache.org/~edwardyoon/dist/0.3.0-RC2/ SVN Tag: https://svn.apache.org/repos/asf/incubator/hama/tags/0.3-RC2/ PGP release keys: https://svn.apache.org/repos/asf/incubator/hama/site/publish/KEYS [ ] +1 Release the packages as Apache Hama 0.3-incubating [ ] -1 Do not release the packages because... Thanks. -- Best Regards, Edward J. Yoon @eddieyoon - 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] Deft to join the incubator
+1 (Binding) On Tue, Jul 5, 2011 at 12:35 PM, Niklas Gustavsson nik...@protocol7.com wrote: Hi, With three mentors graciously signed up and the discussion around the proposal settling, it's time for a vote on Deft joining the incubator. The latest proposal can be found below, or in the wiki: http://wiki.apache.org/incubator/DeftProposal For discussions: http://www.mail-archive.com/general@incubator.apache.org/msg29659.html Please cast your votes: [ ] +1 Accept Deft for incubation [ ] +0 Indifferent to Deft incubation [ ] -1 Reject Deft for incubation Vote will be running for 72 hours. /niklas = Deft Proposal = == Abstract == Deft is a non-blocking, asynchronous, event driven high performance web framework running on the JVM. == Proposal == Deft is a web framework that makes using it feel a bit like ordinary Java servlets, but with additional tools and optimizations to take advantage of the underlying non-blocking infrastructure. The framework is distinct from most mainstream Java web server frameworks because it is non-blocking and reasonably fast. It's ideal for real-time web services because it can support thousands of simultaneous idle connections. Key features: * Optimized for thousands of simultaneous connections * Using pure Java NIO (java.nio java.nio.channels) * Asynchronous (nonblocking I/O) * Event driven == Background == Deft was initially inspired by Facebook's (actually !FriendFeed's ) Tornado open source project. Tornado is written in python and was open sourced by Facebook September 2009. Deft was started in October 2010 by Roger Schildmeijer and Jim Petersson, since then, a number of other developers (from different parts of the world) have submitted patches to the project. External contributors have also been involved in the pre-commit review process that Deft has adopted from Apache Cassandra. Currently the project is hosted on github and has 134 watchers and 19 forks. == Rationale == The goals of the project are very much aligned with the goals of the Apache Software Foundation. i.e there is interest in (continuing to) foster a collaborative, consensus based development process, using an open and pragmatic software license, and a desire to create high quality software that leads the way in its field. == Initial Goals == Even though the basic functionality is in place we would like to see the following features included in future releases: * More third party libraries that works within Deft's IOLoop * Https support for the async http client * Optimized buffer usage in the async socket abstraction * Template engine * Chunked transfer-encoding * Websockets * Https support * Improved Http 1.1 compliance = Current Status = == Meritocracy == Deft has been an open source project since day one. The project has transformed from being primarily a two person led (and funded) project to one with a number of diverse participants. Any potentially controversial architecture change is discussed on the public mailing list. Development has been coordinated primarily through a mailing list, pull requests and with some IRC. == Community == Building an active open source community will be one of Deft's top priority. The amount of interest in the project from social networks (like twitter and github) and individual developers and users suggests a strong community will develop once the framework to support one is in place. Currently the Deft community exists out of the core developers, and the users integration Deft in an end-user products (the actual number is unknown). == Core Developers == * Roger Schildmeijer * Jim Petersson * Johnathan Meehan * Nicholas Whitehead * Séven Le Mesle Other contributors to the project include: William Edwards, Jacob Kristhammar, Rickard Böttcher, ilmich, 1730wang (Nemo), Khaled Essghaier, Mikael Piotrowski == Alignment == Deft is a web framework with a strong focus on speed and asynchronous principles. Some parts of Deft are a complex (especiallt the asynchronous parts) and it makes sense to have a supporting/developing community. Apache provides a solid base with established processes and rules to create such community. == Known Risks == === Inexperience with Open Source === The current code that has been developed for Deft is open sourced under the Apache 2.0 license. The majority of the initial developers of Deft are familiar with the Apache model for open-source development. === Orphaned Products === All participants are active users and contributors to open source. One of them (Roger Schildmeijer) has experience as a contributor on the Apache Cassandra open source project. === Homogeneous Developers === Deft's initial set of committers include people that have a strong JVM background, and are spread over a number of countries and different employers. === Reliance on Salaried Developers === None of the developers
Re: [VOTE] Deft to join the incubator
On Tue, Jul 5, 2011 at 6:35 AM, Niklas Gustavsson nik...@protocol7.com wrote: Hi, With three mentors graciously signed up and the discussion around the proposal settling, it's time for a vote on Deft joining the incubator. The latest proposal can be found below, or in the wiki: http://wiki.apache.org/incubator/DeftProposal For discussions: http://www.mail-archive.com/general@incubator.apache.org/msg29659.html Please cast your votes: [ ] +1 Accept Deft for incubation [ ] +0 Indifferent to Deft incubation [ ] -1 Reject Deft for incubation Vote will be running for 72 hours. +1, best wishes... --tim - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Hama 0.3-incubating (RC2)
Thanks, BTW, if adding CDDL license and notice is enough to release, I'd like to do at the moment. Because we're trying to release monthly, and maven pom can be improved next time. I'm going to upload RC3 again. On Wed, Jul 6, 2011 at 4:52 PM, Dan Haywood dkhayw...@gmail.com wrote: Presumably this means the vote is cancelled, because the ZIP being voted on hasn't been updated? Also... 1. as I understand it, notices and licenses for 3rd party products should not go in NOTICE and LICENSE, but should go in DEPENDENCIES. This can be generated automatically using maven-remote-resources-plugin; missing information can go in supplemental-models.xml file. The apache-incubator-disclaimer-resource-bundle (for maven-remote-resources-plugin) also allows the DEPENDENCIES text to be customized. 2. The NOTICE, in particular, should not be modified at all. I know there are many Apache projects that haven't caught up with this guidance, but this is what the apache-incubator-disclaimer-resource-bundle specifies. See [1] 3. I noticed that hama v0.2 was released to maven central repo. Why aren't the artifacts (including the source zip) uploaded to a staging repo on repository.apache.org? 4. the source release seems to contain jar files (in the lib folder). This doesn't seem right to me. 5. rather than use javax.servlet from Sun (under CDDL), you could use those from geronimo specs (under ASL). Dan [1] http://jira.codehaus.org/browse/MRRESOURCES-32 On 06/07/2011 02:27, Edward J. Yoon wrote: Hi, Stefan Thanks for your review. I've added CDDLv1.0 license and notice. http://svn.apache.org/repos/asf/incubator/hama/branches/0.3/NOTICE.txt http://svn.apache.org/repos/asf/incubator/hama/branches/0.3/LICENSE.txt Could you please check the files again? Thanks. On Wed, Jul 6, 2011 at 6:57 AM, Stefan Seelmannseelm...@apache.org wrote: Hi Edward, I found an issue which is a blocker IMO: jsp-2.1-6.1.4.jar and jsp-api-2.1-6.1.4.jar from Jetty are included. To my knowlege they are licensed under CDDL*. This is a Category B [4] license so either - add the license [1] and the notice excerp [2] to the Hama LICENSE and NOTICE files or - try to use the JSP API and implementation from Tomcat [3] (preferred) Another thing I noticed is that the including hama-examples-0.3.0-incubating.jar is a shaded jar and contains all dependencies. I just wanted to let you know, not sure if that's intended. All other things look good. Kind Regards, Stefan * According to Jetty's notice file [2] the JSP implementation is provided from Glassfish. When looking into the sources (http://repo1.maven.org/maven2/org/mortbay/jetty/jsp-api-2.1/6.1.4/jsp-api-2.1-6.1.4-sources.jar and http://repo1.maven.org/maven2/org/mortbay/jetty/jsp-2.1/6.1.4/jsp-2.1-6.1.4-sources.jar) there are Java files from Sun with CDDL license header. [1] http://svn.codehaus.org/jetty/jetty/tags/jetty-6.1.4/LICENSES/CDDLv1.0.txt [2] http://svn.codehaus.org/jetty/jetty/tags/jetty-6.1.4/LICENSES/NOTICE.txt [3] http://repo1.maven.org/maven2/org/apache/tomcat/jsp-api/6.0.32/ [4] http://apache.org/legal/resolved.html#category-b On Fri, Jul 1, 2011 at 5:36 PM, Edward J. Yoonedwardy...@apache.org wrote: Hi all, The Apache Hama community voted on and approved a proposal to release Apache Hama 0.3-incubating (RC2). This release contains performance improvements and new features e.g., maven build, web UI for Hama cluster, MessageBundle, Dijkstra's Shortest Path and PageRank examples. Please vote on the RC2 for Apache Hama 0.3-Incubating. We've already received 2 binding IPMC +1 votes. Vote thread: http://markmail.org/thread/qx4u3kjflwe524pf Artifact and signatures: http://people.apache.org/~edwardyoon/dist/0.3.0-RC2/ SVN Tag: https://svn.apache.org/repos/asf/incubator/hama/tags/0.3-RC2/ PGP release keys: https://svn.apache.org/repos/asf/incubator/hama/site/publish/KEYS [ ] +1 Release the packages as Apache Hama 0.3-incubating [ ] -1 Do not release the packages because... Thanks. -- Best Regards, Edward J. Yoon @eddieyoon - 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 -- Best Regards, Edward J. Yoon @eddieyoon - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Hama 0.3-incubating (RC2)
Hi Edward... In that case would you please cancel this [VOTE] thread and start a new one. Notice that when producing the RC3 you would have to start a [VOTE] thread on your dev@ first and when passed you start a [VOTE] again here in general@. On Wed, Jul 6, 2011 at 12:46 PM, Edward J. Yoon edwardy...@apache.org wrote: Thanks, BTW, if adding CDDL license and notice is enough to release, I'd like to do at the moment. Because we're trying to release monthly, and maven pom can be improved next time. I'm going to upload RC3 again. On Wed, Jul 6, 2011 at 4:52 PM, Dan Haywood dkhayw...@gmail.com wrote: Presumably this means the vote is cancelled, because the ZIP being voted on hasn't been updated? Also... 1. as I understand it, notices and licenses for 3rd party products should not go in NOTICE and LICENSE, but should go in DEPENDENCIES. This can be generated automatically using maven-remote-resources-plugin; missing information can go in supplemental-models.xml file. The apache-incubator-disclaimer-resource-bundle (for maven-remote-resources-plugin) also allows the DEPENDENCIES text to be customized. 2. The NOTICE, in particular, should not be modified at all. I know there are many Apache projects that haven't caught up with this guidance, but this is what the apache-incubator-disclaimer-resource-bundle specifies. See [1] 3. I noticed that hama v0.2 was released to maven central repo. Why aren't the artifacts (including the source zip) uploaded to a staging repo on repository.apache.org? 4. the source release seems to contain jar files (in the lib folder). This doesn't seem right to me. 5. rather than use javax.servlet from Sun (under CDDL), you could use those from geronimo specs (under ASL). Dan [1] http://jira.codehaus.org/browse/MRRESOURCES-32 On 06/07/2011 02:27, Edward J. Yoon wrote: Hi, Stefan Thanks for your review. I've added CDDLv1.0 license and notice. http://svn.apache.org/repos/asf/incubator/hama/branches/0.3/NOTICE.txt http://svn.apache.org/repos/asf/incubator/hama/branches/0.3/LICENSE.txt Could you please check the files again? Thanks. On Wed, Jul 6, 2011 at 6:57 AM, Stefan Seelmannseelm...@apache.org wrote: Hi Edward, I found an issue which is a blocker IMO: jsp-2.1-6.1.4.jar and jsp-api-2.1-6.1.4.jar from Jetty are included. To my knowlege they are licensed under CDDL*. This is a Category B [4] license so either - add the license [1] and the notice excerp [2] to the Hama LICENSE and NOTICE files or - try to use the JSP API and implementation from Tomcat [3] (preferred) Another thing I noticed is that the including hama-examples-0.3.0-incubating.jar is a shaded jar and contains all dependencies. I just wanted to let you know, not sure if that's intended. All other things look good. Kind Regards, Stefan * According to Jetty's notice file [2] the JSP implementation is provided from Glassfish. When looking into the sources (http://repo1.maven.org/maven2/org/mortbay/jetty/jsp-api-2.1/6.1.4/jsp-api-2.1-6.1.4-sources.jar and http://repo1.maven.org/maven2/org/mortbay/jetty/jsp-2.1/6.1.4/jsp-2.1-6.1.4-sources.jar) there are Java files from Sun with CDDL license header. [1] http://svn.codehaus.org/jetty/jetty/tags/jetty-6.1.4/LICENSES/CDDLv1.0.txt [2] http://svn.codehaus.org/jetty/jetty/tags/jetty-6.1.4/LICENSES/NOTICE.txt [3] http://repo1.maven.org/maven2/org/apache/tomcat/jsp-api/6.0.32/ [4] http://apache.org/legal/resolved.html#category-b On Fri, Jul 1, 2011 at 5:36 PM, Edward J. Yoonedwardy...@apache.org wrote: Hi all, The Apache Hama community voted on and approved a proposal to release Apache Hama 0.3-incubating (RC2). This release contains performance improvements and new features e.g., maven build, web UI for Hama cluster, MessageBundle, Dijkstra's Shortest Path and PageRank examples. Please vote on the RC2 for Apache Hama 0.3-Incubating. We've already received 2 binding IPMC +1 votes. Vote thread: http://markmail.org/thread/qx4u3kjflwe524pf Artifact and signatures: http://people.apache.org/~edwardyoon/dist/0.3.0-RC2/ SVN Tag: https://svn.apache.org/repos/asf/incubator/hama/tags/0.3-RC2/ PGP release keys: https://svn.apache.org/repos/asf/incubator/hama/site/publish/KEYS [ ] +1 Release the packages as Apache Hama 0.3-incubating [ ] -1 Do not release the packages because... Thanks. -- Best Regards, Edward J. Yoon @eddieyoon - 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:
[CANCELED][VOTE] Release Hama 0.3-incubating (RC2)
This VOTE is canceled. On Wed, Jul 6, 2011 at 7:50 PM, Mohammad Nour El-Din nour.moham...@gmail.com wrote: Hi Edward... In that case would you please cancel this [VOTE] thread and start a new one. Notice that when producing the RC3 you would have to start a [VOTE] thread on your dev@ first and when passed you start a [VOTE] again here in general@. On Wed, Jul 6, 2011 at 12:46 PM, Edward J. Yoon edwardy...@apache.org wrote: Thanks, BTW, if adding CDDL license and notice is enough to release, I'd like to do at the moment. Because we're trying to release monthly, and maven pom can be improved next time. I'm going to upload RC3 again. On Wed, Jul 6, 2011 at 4:52 PM, Dan Haywood dkhayw...@gmail.com wrote: Presumably this means the vote is cancelled, because the ZIP being voted on hasn't been updated? Also... 1. as I understand it, notices and licenses for 3rd party products should not go in NOTICE and LICENSE, but should go in DEPENDENCIES. This can be generated automatically using maven-remote-resources-plugin; missing information can go in supplemental-models.xml file. The apache-incubator-disclaimer-resource-bundle (for maven-remote-resources-plugin) also allows the DEPENDENCIES text to be customized. 2. The NOTICE, in particular, should not be modified at all. I know there are many Apache projects that haven't caught up with this guidance, but this is what the apache-incubator-disclaimer-resource-bundle specifies. See [1] 3. I noticed that hama v0.2 was released to maven central repo. Why aren't the artifacts (including the source zip) uploaded to a staging repo on repository.apache.org? 4. the source release seems to contain jar files (in the lib folder). This doesn't seem right to me. 5. rather than use javax.servlet from Sun (under CDDL), you could use those from geronimo specs (under ASL). Dan [1] http://jira.codehaus.org/browse/MRRESOURCES-32 On 06/07/2011 02:27, Edward J. Yoon wrote: Hi, Stefan Thanks for your review. I've added CDDLv1.0 license and notice. http://svn.apache.org/repos/asf/incubator/hama/branches/0.3/NOTICE.txt http://svn.apache.org/repos/asf/incubator/hama/branches/0.3/LICENSE.txt Could you please check the files again? Thanks. On Wed, Jul 6, 2011 at 6:57 AM, Stefan Seelmannseelm...@apache.org wrote: Hi Edward, I found an issue which is a blocker IMO: jsp-2.1-6.1.4.jar and jsp-api-2.1-6.1.4.jar from Jetty are included. To my knowlege they are licensed under CDDL*. This is a Category B [4] license so either - add the license [1] and the notice excerp [2] to the Hama LICENSE and NOTICE files or - try to use the JSP API and implementation from Tomcat [3] (preferred) Another thing I noticed is that the including hama-examples-0.3.0-incubating.jar is a shaded jar and contains all dependencies. I just wanted to let you know, not sure if that's intended. All other things look good. Kind Regards, Stefan * According to Jetty's notice file [2] the JSP implementation is provided from Glassfish. When looking into the sources (http://repo1.maven.org/maven2/org/mortbay/jetty/jsp-api-2.1/6.1.4/jsp-api-2.1-6.1.4-sources.jar and http://repo1.maven.org/maven2/org/mortbay/jetty/jsp-2.1/6.1.4/jsp-2.1-6.1.4-sources.jar) there are Java files from Sun with CDDL license header. [1] http://svn.codehaus.org/jetty/jetty/tags/jetty-6.1.4/LICENSES/CDDLv1.0.txt [2] http://svn.codehaus.org/jetty/jetty/tags/jetty-6.1.4/LICENSES/NOTICE.txt [3] http://repo1.maven.org/maven2/org/apache/tomcat/jsp-api/6.0.32/ [4] http://apache.org/legal/resolved.html#category-b On Fri, Jul 1, 2011 at 5:36 PM, Edward J. Yoonedwardy...@apache.org wrote: Hi all, The Apache Hama community voted on and approved a proposal to release Apache Hama 0.3-incubating (RC2). This release contains performance improvements and new features e.g., maven build, web UI for Hama cluster, MessageBundle, Dijkstra's Shortest Path and PageRank examples. Please vote on the RC2 for Apache Hama 0.3-Incubating. We've already received 2 binding IPMC +1 votes. Vote thread: http://markmail.org/thread/qx4u3kjflwe524pf Artifact and signatures: http://people.apache.org/~edwardyoon/dist/0.3.0-RC2/ SVN Tag: https://svn.apache.org/repos/asf/incubator/hama/tags/0.3-RC2/ PGP release keys: https://svn.apache.org/repos/asf/incubator/hama/site/publish/KEYS [ ] +1 Release the packages as Apache Hama 0.3-incubating [ ] -1 Do not release the packages because... Thanks. -- Best Regards, Edward J. Yoon @eddieyoon - 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
NOTICE and LICENSE [WAS Re: [VOTE] Release Hama 0.3-incubating (RC2)]
On Wed, Jul 6, 2011 at 8:52 AM, Dan Haywood dkhayw...@gmail.com wrote: snip (Apologies if I've missed any changes in Apache policy - please jump in and correct me) 1. as I understand it, notices and licenses for 3rd party products should not go in NOTICE and LICENSE, but should go in DEPENDENCIES. This can be generated automatically using maven-remote-resources-plugin; missing information can go in supplemental-models.xml file. The apache-incubator-disclaimer-resource-bundle (for maven-remote-resources-plugin) also allows the DEPENDENCIES text to be customized. AIUI DEPENDENCIES is fine for plain libraries [5]. Providing that the information is complete, then it's ok for other stuff but best practice is to ship every license as text, rather than by reference. (To use a public license, you need to be issued with a copy. So, it's convenient to be able to have a copy included by Apache.) 2. The NOTICE, in particular, should not be modified at all. I know there are many Apache projects that haven't caught up with this guidance, AIUI the Apache policy on NOTICEs remains the same [1] include only what's required and nothing more. For most projects, this means the plain NOTICE but there are some exceptional cases, for example [2] and [4]. One day hopefully this complexity will be automated... Robert [1] http://www.apache.org/legal/src-headers.html#notice [2] when a project includes source licensed as per [3] [3] a license requiring an attribution NOTICE of some kind [4] shipped an artifact licensed as per [3] without including it's NOTICE (some jars in Maven central fall into this category eg. some spring releases) [5] ie those that don't aggregate dependencies - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Oozie to join the Incubator
On Wed, Jun 29, 2011 at 8:10 PM, Mohammad Islam misla...@yahoo.com wrote: snip [ X] +1 Accept Oozie for incubation [ ] +0 Indifferent to Oozie incubation [ ] -1 Reject Oozie for incubation Robert - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Interested Contributors [WAS Re: [VOTE] Oozie to join the Incubator]
On Wed, Jun 29, 2011 at 8:14 PM, Suresh Marru sma...@apache.org wrote: Hi Suresh I am interested to contribute to this project, since any one did not vote yet, can I add my name to the Initial Committers? The proposal is fixed when the VOTE thread starts (so that everyone is voting on the same proposition). But please join the list and get involved by starting to contributing patches. To leave the incubator, the podling needs to demonstrate that it understands how to build a broader community. So, podlings need to review patches promptly, to offer encouragement and mentoring so that contributors quickly progress into committers. and anyway IMHO it's much more satisifying to become the first elected committer for a podling :-) Robert - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Interested Contributors [WAS Re: [VOTE] Oozie to join the Incubator]
On Jul 6, 2011, at 7:09 AM, Robert Burrell Donkin wrote: On Wed, Jun 29, 2011 at 8:14 PM, Suresh Marru sma...@apache.org wrote: Hi Suresh I am interested to contribute to this project, since any one did not vote yet, can I add my name to the Initial Committers? The proposal is fixed when the VOTE thread starts (so that everyone is voting on the same proposition). But please join the list and get involved by starting to contributing patches. To leave the incubator, the podling needs to demonstrate that it understands how to build a broader community. So, podlings need to review patches promptly, to offer encouragement and mentoring so that contributors quickly progress into committers. and anyway IMHO it's much more satisifying to become the first elected committer for a podling :-) Thanks Robert, will plan to do so. Oozie is synergistic with what we work in the Airavata podling and would like to learn more and get involved. Suresh Robert - 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: NOTICE and LICENSE [WAS Re: [VOTE] Release Hama 0.3-incubating (RC2)]
On 06/07/2011 11:57, Robert Burrell Donkin wrote: (Apologies if I've missed any changes in Apache policy - please jump in and correct me) Relating to the NOTICE file, it would seem that [1] is inconsistent with [2]. If these discussions on legal did occur, then it would seem that no-one on the legal team updated [1] to reflect new policy. [1] http://www.apache.org/legal/src-headers.html#notice [2] http://jira.codehaus.org/browse/MRRESOURCES-32 - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: NOTICE and LICENSE [WAS Re: [VOTE] Release Hama 0.3-incubating (RC2)]
Hi Dan, On Wed, Jul 6, 2011 at 1:37 PM, Dan Haywood dkhayw...@gmail.com wrote: ...Relating to the NOTICE file, it would seem that [1] is inconsistent with [2]. If these discussions on legal did occur, then it would seem that no-one on the legal team updated [1] to reflect new policy. I think [1] is correct, the important bit is that NOTICE is for *required* third-party notices, the idea is to minimize what's in there. See also related discussions here: http://markmail.org/message/ik3o5vl24o57lfsx http://markmail.org/message/a5xkiggxirc77xnv -Bertrand [1] http://www.apache.org/legal/src-headers.html#notice [2] http://jira.codehaus.org/browse/MRRESOURCES-32 - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Retire ALOIS podling
After the initial import only a few commits happened. All changes are from the initial committers with CLA on file (no external contributors). Therefore I consider this code is fine to stay in SVN. I really don't know what other kinds of elbow grease I can apply Cheers Christian On Tue, Jul 5, 2011 at 10:52 PM, Henri Yandell flame...@gmail.com wrote: Seems good. Once said grease is applied, we should update the website to sign off on copyright; then close down the podling. Hen On Tue, Jul 5, 2011 at 9:29 AM, Craig L Russell craig.russ...@oracle.com wrote: There is a grant on file (documents/grants/imsec-alois.pdf) from IMSEC GmbH for ALOIS (code and all documentation) dated 4-Oct-2010. This plus some elbow grease should allow a mentor to definitively establish provenance of the code... Craig On Jul 5, 2011, at 9:13 AM, Christian Grobmeier wrote: Do you have any tipps how I can make sure the source is covered by the CLAs? As I understood we just have the initial import in SVN. All committers have CLAs on file. Is that enough? It depends on who the copyright owners/licensees of the original import were. Identify that set, then remove those with CLAs and see if anyone is left. Contacting the mentors for project history would be a good start, reviewing the early emails and also the proposal to join the Incubator. Well, I am one of them :-) There has not been much commits, most of them from the id flavio, some less from ulerch. Both have an CLA on file. No issues with patches were contributed. There must be a grant from the donating company- not sure where. The company donated everything ALOIS releated to the ASF, and most of it has been done by the initial committers. So, I don't think there are any problems with leaving the code where it is now. Do you think otherwise? Cheers, Christian - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org Craig L Russell Secretary, Apache Software Foundation Chair, OpenJPA PMC c...@apache.org http://db.apache.org/jdo - 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 -- http://www.grobmeier.de - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Deft to join the incubator
On Tue, Jul 5, 2011 at 12:35 PM, Niklas Gustavsson nik...@protocol7.com wrote: With three mentors graciously signed up and the discussion around the proposal settling, it's time for a vote on Deft joining the incubator. ... Please cast your votes: +1 (binding) -Bertrand - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Project shutdown guide?
On Tue, Jul 5, 2011 at 10:53 PM, Henri Yandell flame...@gmail.com wrote: Currently I'd describe it as: http://attic.apache.org/process.html So, is a failed incubation project going into the attic? I don't think so. In addition i don't think board needs to approve that, this is incubator business. So my list would be with what Henri said: * Check copyright checkbox is signed off on. ** If not, then dig in to see if it can be signed off on. *** If so, sign off with current date. *** If not, remove source. Plus: - Update incubator status page with message: 2006-06-24 Project requested to be withdrawn from incubation. - Move project in projects.xml to retired section - Update the project DOAP file - make SVN readonly - make Jira/Bugzilla readonly - Turn off automated builds - Remove from incubator.apache.org main navigation, but leave it in the retired section of projects.xml - close mailinglists - Announce on general@incubator.apache.org - make wiki readonly (if possible) - remove from reporting schedule What is with user accounts of people who are not active in other apache projects and started at the ASF with the retired project? Are the accounts closed too? Any more ideas? I am +1 for creating a page on the incubator site with a shutdown guide, btw. Cheers, Christian + * Check copyright checkbox is signed off on. ** If not, then dig in to see if it can be signed off on. *** If so, sign off with current date. *** If not, remove source. Hen On Tue, Jul 5, 2011 at 10:05 AM, Daniel Kulp dk...@apache.org wrote: Is there a list someplace of the steps to take to shutdown a project? On the website, I see entry guides, podling guides, graduation guides, etc but not a shutdown/termination guide. -- Daniel Kulp dk...@apache.org http://dankulp.com/blog Talend - http://www.talend.com - 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 -- http://www.grobmeier.de - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Retired vs dormant
Here are to sections, retired and dormant: http://incubator.apache.org/projects/index.html What is the actual difference between these two? I think we should only have one term and one section, be it retired or dormant. Cheers Christian - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Retire ALOIS podling
We're interested in the history of the initial revision in svn; subsequent commits will be covered by CLAs etc per our usual process. In this case it sounds good. If this was a commercial entity contributing, and they signed a software grant then we'd be covered. Update the Incubator website to indicate you're signing off on the first Copyright item; then retire them. Hen On Wed, Jul 6, 2011 at 5:48 AM, Christian Grobmeier grobme...@gmail.com wrote: After the initial import only a few commits happened. All changes are from the initial committers with CLA on file (no external contributors). Therefore I consider this code is fine to stay in SVN. I really don't know what other kinds of elbow grease I can apply Cheers Christian On Tue, Jul 5, 2011 at 10:52 PM, Henri Yandell flame...@gmail.com wrote: Seems good. Once said grease is applied, we should update the website to sign off on copyright; then close down the podling. Hen On Tue, Jul 5, 2011 at 9:29 AM, Craig L Russell craig.russ...@oracle.com wrote: There is a grant on file (documents/grants/imsec-alois.pdf) from IMSEC GmbH for ALOIS (code and all documentation) dated 4-Oct-2010. This plus some elbow grease should allow a mentor to definitively establish provenance of the code... Craig On Jul 5, 2011, at 9:13 AM, Christian Grobmeier wrote: Do you have any tipps how I can make sure the source is covered by the CLAs? As I understood we just have the initial import in SVN. All committers have CLAs on file. Is that enough? It depends on who the copyright owners/licensees of the original import were. Identify that set, then remove those with CLAs and see if anyone is left. Contacting the mentors for project history would be a good start, reviewing the early emails and also the proposal to join the Incubator. Well, I am one of them :-) There has not been much commits, most of them from the id flavio, some less from ulerch. Both have an CLA on file. No issues with patches were contributed. There must be a grant from the donating company- not sure where. The company donated everything ALOIS releated to the ASF, and most of it has been done by the initial committers. So, I don't think there are any problems with leaving the code where it is now. Do you think otherwise? Cheers, Christian - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org Craig L Russell Secretary, Apache Software Foundation Chair, OpenJPA PMC c...@apache.org http://db.apache.org/jdo - 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 -- http://www.grobmeier.de - 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: Project shutdown guide?
On Wed, Jul 6, 2011 at 5:56 AM, Christian Grobmeier grobme...@gmail.com wrote: On Tue, Jul 5, 2011 at 10:53 PM, Henri Yandell flame...@gmail.com wrote: Currently I'd describe it as: http://attic.apache.org/process.html So, is a failed incubation project going into the attic? I don't think so. In addition i don't think board needs to approve that, this is incubator business. Agreed. The attic will link over to the Incubator's retired page. So my list would be with what Henri said: * Check copyright checkbox is signed off on. ** If not, then dig in to see if it can be signed off on. *** If so, sign off with current date. *** If not, remove source. Plus: - Update incubator status page with message: 2006-06-24 Project requested to be withdrawn from incubation. - Move project in projects.xml to retired section - Update the project DOAP file - make SVN readonly - make Jira/Bugzilla readonly - Turn off automated builds - Remove from incubator.apache.org main navigation, but leave it in the retired section of projects.xml - close mailinglists - Announce on general@incubator.apache.org - make wiki readonly (if possible) - remove from reporting schedule Seems good. What is with user accounts of people who are not active in other apache projects and started at the ASF with the retired project? Are the accounts closed too? No need imo. If individuals don't connect for X years and infra want to tighten things up then they can make accounts dormant in a separate process. I don't think there's a need to drive out committers who don't have any permissions to commit to a project. Any more ideas? I am +1 for creating a page on the incubator site with a shutdown guide, btw. Go for it :) Hen - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Retire ALOIS podling
OK, finally I understood. I will sign it off then. Thanks for your patience and your explains On Wed, Jul 6, 2011 at 5:26 PM, Henri Yandell flame...@gmail.com wrote: We're interested in the history of the initial revision in svn; subsequent commits will be covered by CLAs etc per our usual process. In this case it sounds good. If this was a commercial entity contributing, and they signed a software grant then we'd be covered. Update the Incubator website to indicate you're signing off on the first Copyright item; then retire them. Hen On Wed, Jul 6, 2011 at 5:48 AM, Christian Grobmeier grobme...@gmail.com wrote: After the initial import only a few commits happened. All changes are from the initial committers with CLA on file (no external contributors). Therefore I consider this code is fine to stay in SVN. I really don't know what other kinds of elbow grease I can apply Cheers Christian On Tue, Jul 5, 2011 at 10:52 PM, Henri Yandell flame...@gmail.com wrote: Seems good. Once said grease is applied, we should update the website to sign off on copyright; then close down the podling. Hen On Tue, Jul 5, 2011 at 9:29 AM, Craig L Russell craig.russ...@oracle.com wrote: There is a grant on file (documents/grants/imsec-alois.pdf) from IMSEC GmbH for ALOIS (code and all documentation) dated 4-Oct-2010. This plus some elbow grease should allow a mentor to definitively establish provenance of the code... Craig On Jul 5, 2011, at 9:13 AM, Christian Grobmeier wrote: Do you have any tipps how I can make sure the source is covered by the CLAs? As I understood we just have the initial import in SVN. All committers have CLAs on file. Is that enough? It depends on who the copyright owners/licensees of the original import were. Identify that set, then remove those with CLAs and see if anyone is left. Contacting the mentors for project history would be a good start, reviewing the early emails and also the proposal to join the Incubator. Well, I am one of them :-) There has not been much commits, most of them from the id flavio, some less from ulerch. Both have an CLA on file. No issues with patches were contributed. There must be a grant from the donating company- not sure where. The company donated everything ALOIS releated to the ASF, and most of it has been done by the initial committers. So, I don't think there are any problems with leaving the code where it is now. Do you think otherwise? Cheers, Christian - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org Craig L Russell Secretary, Apache Software Foundation Chair, OpenJPA PMC c...@apache.org http://db.apache.org/jdo - 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 -- http://www.grobmeier.de - 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 -- http://www.grobmeier.de - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Project shutdown guide?
On Wednesday, July 06, 2011 2:56:49 PM Christian Grobmeier wrote: What is with user accounts of people who are not active in other apache projects and started at the ASF with the retired project? Are the accounts closed too? Any more ideas? I am +1 for creating a page on the incubator site with a shutdown guide, btw. +1 I did find this page on the wiki: http://wiki.apache.org/incubator/RetiringPodlings but I definitely think an official guide on the web page would be more appropriate. Dan Cheers, Christian + * Check copyright checkbox is signed off on. ** If not, then dig in to see if it can be signed off on. *** If so, sign off with current date. *** If not, remove source. Hen On Tue, Jul 5, 2011 at 10:05 AM, Daniel Kulp dk...@apache.org wrote: Is there a list someplace of the steps to take to shutdown a project? On the website, I see entry guides, podling guides, graduation guides, etc but not a shutdown/termination guide. -- Daniel Kulp dk...@apache.org http://dankulp.com/blog Talend - http://www.talend.com - 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 -- Daniel Kulp dk...@apache.org http://dankulp.com/blog Talend - http://www.talend.com - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Retire ALOIS podling
Hi Christian, On Jul 6, 2011, at 5:48 AM, Christian Grobmeier wrote: After the initial import only a few commits happened. All changes are from the initial committers with CLA on file (no external contributors). The work you did to research and verify this, is the grease I was talking about. Therefore I consider this code is fine to stay in SVN. I really don't know what other kinds of elbow grease I can apply That's it for me. I have no problems with this code staying around in case anyone in future cares to care for it. Craig Cheers Christian On Tue, Jul 5, 2011 at 10:52 PM, Henri Yandell flame...@gmail.com wrote: Seems good. Once said grease is applied, we should update the website to sign off on copyright; then close down the podling. Hen On Tue, Jul 5, 2011 at 9:29 AM, Craig L Russell craig.russ...@oracle.com wrote: There is a grant on file (documents/grants/imsec-alois.pdf) from IMSEC GmbH for ALOIS (code and all documentation) dated 4-Oct-2010. This plus some elbow grease should allow a mentor to definitively establish provenance of the code... Craig On Jul 5, 2011, at 9:13 AM, Christian Grobmeier wrote: Do you have any tipps how I can make sure the source is covered by the CLAs? As I understood we just have the initial import in SVN. All committers have CLAs on file. Is that enough? It depends on who the copyright owners/licensees of the original import were. Identify that set, then remove those with CLAs and see if anyone is left. Contacting the mentors for project history would be a good start, reviewing the early emails and also the proposal to join the Incubator. Well, I am one of them :-) There has not been much commits, most of them from the id flavio, some less from ulerch. Both have an CLA on file. No issues with patches were contributed. There must be a grant from the donating company- not sure where. The company donated everything ALOIS releated to the ASF, and most of it has been done by the initial committers. So, I don't think there are any problems with leaving the code where it is now. Do you think otherwise? Cheers, Christian - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org Craig L Russell Secretary, Apache Software Foundation Chair, OpenJPA PMC c...@apache.org http://db.apache.org/jdo - 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 -- http://www.grobmeier.de - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org Craig L Russell Architect, Oracle http://db.apache.org/jdo 408 276-5638 mailto:craig.russ...@oracle.com P.S. A good JDO? O, Gasp! - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Retire ALOIS podling
The work you did to research and verify this, is the grease I was talking about. Therefore I consider this code is fine to stay in SVN. I really don't know what other kinds of elbow grease I can apply That's it for me. I have no problems with this code staying around in case anyone in future cares to care for it. Ok thanks. I just wanted to make it proper - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: NOTICE and LICENSE [WAS Re: [VOTE] Release Hama 0.3-incubating (RC2)]
On Wed, Jul 6, 2011 at 1:49 PM, Bertrand Delacretaz bdelacre...@apache.org wrote: Hi Dan, On Wed, Jul 6, 2011 at 1:37 PM, Dan Haywood dkhayw...@gmail.com wrote: ...Relating to the NOTICE file, it would seem that [1] is inconsistent with [2]. If these discussions on legal did occur, then it would seem that no-one on the legal team updated [1] to reflect new policy. I think [1] is correct, the important bit is that NOTICE is for *required* third-party notices, the idea is to minimize what's in there. See also related discussions here: http://markmail.org/message/ik3o5vl24o57lfsx http://markmail.org/message/a5xkiggxirc77xnv (Thanks for digging out these links 8-) This is the way I understand the situation as well [1] http://www.apache.org/legal/src-headers.html#notice [2] http://jira.codehaus.org/browse/MRRESOURCES-32 IMO generating and verify that assembled applications have correct LICENSE and NOTICE attributes is not trivial, and requires tooling beyond remote-resources... Robert - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Deft for incubation
On Mon, Jul 4, 2011 at 8:59 PM, Roger Schildmeijer schildmei...@gmail.com wrote: Hi again, Been examining the asyncweb project in more details (atleast the asyncweb.client and asyncwebserver components). Below is my notes (simple draft). asyncweb notes -client module * https support for Deft's AHC (AsynchronousHttpClient) could borrow some details from asyncweb (o.a.asyncweb.client.SimpleTrustManagerFactory) * Improve the http request decoding (org.apache.ahc.codec.HttpDecoder, eg. decode[line, status, header, cookie]) -server module * like the simple and elegant design of o.a.asyncweb.server.resolver.ServiceResolver (and its concrete impl., eg. PatternMatchResolver (comparable to Deft's Capturing groups) and ExactMatchURIServiceResolver) * o.a.asyncweb.server.HttpClientListener (interface with callbacks clientDisconnected, clientIdle, register listeners on HttpServiceContext). I like the idea. Useful for comet/longpoll (could be worth to add to Deft). Conclusion: Ofcourse there are overlaps between the two projects. I agree with Emanuel Emmanuel Lécharny regarding that It's almost as difficult to write from scratch some piece of code than to reuse some other with lost support... Deft is built (tightly integrated) around the event-loop (org.deftserver.io.IOLoop) which the modules (e.g the web server component and the async http client) heavily depend upon. Asyncweb is built on top of the Apache MINA network framework and to merge these two project (Asyncweb and deft) is non trivial, therefor I propose we don't. Also, I guess asyncweb was abandoned for a reason? Took a look at Deft, I know well AsyncWeb, and the two projects are really similar. AsyncWeb was abandoned for some weird community issues (the merge of MINA and AsyncWeb communities was badly managed) and because it's much funnier to redo an HTTP from scratch than taking back and abandoned project :) We are currently recoding MINA from scratch (v3.0) so we can share ideas about asynchronous API for network operations, perf tests, etc.. I think the two projects should stay in touch and share background ideas. Julien - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Retired vs dormant
Given the PPMC is closed down, I think it has to be retired. Dormant implies a PPMC is taking some time off. Basically this is a larger version of don't be afraid to delete a line of code; it's in version control. Hen On Wed, Jul 6, 2011 at 5:59 AM, Christian Grobmeier grobme...@gmail.com wrote: Here are to sections, retired and dormant: http://incubator.apache.org/projects/index.html What is the actual difference between these two? I think we should only have one term and one section, be it retired or dormant. Cheers Christian - 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
[VOTE][RESULT] Oozie to join the Incubator
Hi, After passing 72 hours of voting, I tallied the vote and the proposal to include Oozie as an Apache Incubator project has passed. The summary of vote is as follows: * 9 +1's from IPMC members. * 10 +1 from non-binding * No -1 * No 0 Binding +1 votes (9): Doug Cutting Tom White Alan D Cabrera Bertrand Delacretaz Mohammad Nour El-Din Robert Burrell Donkin Chris Douglas Nigel Daley Chris Mattmann Non-Binding +1 votes (10): Eric Sammer Jonathan Hsieh Chao Wang Ahmed Redwan Mayank Bansal Roman Shaposhnik Arvind Pravhakar Alejandro Abdelnur Ashish Edward J Yoon Thanks everyone who participated. Regards, Mohammad Islam
