Re: [VOTE] Release Droids 0.1-incubating RC2
On 6/14/2011 8:14 PM, Marvin Humphrey wrote: O There should be archived VOTE threads on the droids-private list, which were cc'd to private@incubator.a.o. Hopefully they were for PPMC membership. If not, there will be some cleanup work to do. The votes were handled on the droids-dev list (like they should) and were committer votes. So Bertil and I aren't on the PPMC. Excellent. Was your work documented anywhere? Ideally, there would be a JIRA issue I can read over explaining why each dependency with a non-category-A license is OK. http://www.apache.org/legal/resolved.html No, there is no JIRA ticket. There are no category-X defined dependencies. The notice file includes notices for all the category B defined dependencies: JUnit and javax.servlet. Those are fairly common in Apache projects and the requirements were met. See below. Attached is the dependency hierarchy. All of the Apache projects are full projects, so they are all good. That leaves: NekoHTML - AL2 SLF4J - MIT mockito - MIT Google Guava - AL2 Spring - AL2 JUnit - CPL v1 - Category B, binary only, appropriately labeled in the NOTICE.txt file javax.servlet - Included in the Jetty notice, which states it is CDDLv1 and copyright Sun Microsystems and ASF. Notice text copied from Solr Jetty 6 - AL2, but requires notice (in place) CGLib - AL2 Further help and guidance of course is always welcome. You are gracious. I'll defer to others on guidance; I see my role as more that of a QC engineer. And to start off my QC, I'll note that there are some oddities in the top level directory of the archive. Here's the file list: DEPENDENCIES LICENSE LICENSE.txt NOTICE NOTICE.txt README.TXT droids-core droids-norobots droids-solr droids-spring droids-tika droids-wicket pom.xml The LICENSE and LICENSE.txt files are essentially duplicates of each other, having only whitespace differences. However, the NOTICE and NOTICE.txt files are quite distinct (diff below my sig). I think this is a blocker. That's Maven. LICENSE.txt and NOTICE.txt are the two in svn. We may need to rename them to be without the .txt so Maven doesn't do its own thing there. While without txt is preferred, it is allowable to use the .txt file names. I'm not sure what the DEPENDENCIES file is supposed to tell us, but it contains minimal information. Presumably it's some Maven thing I just don't grok. That was Maven generated and I don't understand it either. I used the defined method of releasing via Apache Maven, including using the latest parent pom. Lastly, I think it's worth commenting on the contents of README.TXT, which starts off like so: A p a c h eD r o i d s -- by Thorsten Scherlerthorsten at apache.org That credit is obviously inaccurate and seems quite unusual for an Apache project. I know that other projects have gone out of their way to delete all @author tags. Perhaps Droids might consider doing likewise. Yes, that file needs to be cleaned up. I do see there are two source files with @author in them. I've fixed them in trunk. I don't think either of these two things are a blocker. I also intend to run a RAT report, and to pore over LICENSE and NOTICE more thoroughly, but I'm out of time for today and wanted to get you this feedback sooner rather than later. Thanks for the feedback. I poured over the LICENSE.txt and NOTICE.txt files quite carefully. The RAT report was ran until it came back clean twice. Those should be good. org.apache.droids:droids-core:jar:0.1 +- org.apache.droids:droids-norobots:jar:0.1:compile +- commons-logging:commons-logging:jar:1.1.1:compile +- org.apache.httpcomponents:httpclient:jar:4.0.1:compile | +- org.apache.httpcomponents:httpcore:jar:4.0.1:compile | \- commons-codec:commons-codec:jar:1.3:compile +- net.sourceforge.nekohtml:nekohtml:jar:1.9.14:compile | \- xerces:xercesImpl:jar:2.9.1:compile +- com.google.guava:guava:jar:r07:compile +- org.slf4j:slf4j-api:jar:1.6.1:compile +- junit:junit:jar:4.5:test +- org.mockito:mockito-all:jar:1.8.5:test \- org.slf4j:slf4j-simple:jar:1.6.1:test org.apache.droids:droids-spring:jar:0.1 +- org.apache.droids:droids-core:jar:0.1:compile | +- org.apache.droids:droids-norobots:jar:0.1:compile | +- org.apache.httpcomponents:httpclient:jar:4.0.1:compile | | +- org.apache.httpcomponents:httpcore:jar:4.0.1:compile | | \- commons-codec:commons-codec:jar:1.3:compile | +- net.sourceforge.nekohtml:nekohtml:jar:1.9.14:compile | | \- xerces:xercesImpl:jar:2.9.1:compile | +- com.google.guava:guava:jar:r07:compile | \- org.slf4j:slf4j-api:jar:1.6.1:compile +- commons-logging:commons-logging:jar:1.1.1:compile +- org.apache.cocoon:cocoon-spring-configurator:jar:2.0.0:compile | +- org.apache.cocoon:cocoon-configuration-api:jar:1.0.2:compile | +-
Re: [VOTE] Release Droids 0.1-incubating RC2
On Tue, 2011-06-14 at 18:14 -0700, Marvin Humphrey wrote: On Tue, Jun 14, 2011 at 01:39:20PM -0500, Richard Frovarp wrote: Looks like this is the inaugural ASF release for Droids, right? Thank you for looking at this. Yes, it will be. w00t! Yes, the page needs to be updated. Ross has provided us with a link to the page on how to update that information. I personally haven't had time to do it. I think I'm on the PPMC, but for the Incubator, I'm not quite sure the distinction between a PPMC member and a committer. The roles are just as distinct as they are between a Committer and a PMC member for a top-level project, and there are separate voting procedures. Some projects add both roles at once: http://incubator.apache.org/guides/ppmc.html#Voting+in+a+new+committer http://incubator.apache.org/guides/ppmc.html#Voting+in+a+new+PPMC+member For projects which wish to have all committers also be PPMC members, the Voting in a new PPMC member guide below should then be followed, noting that if desired it is possible to run a joint committership and PPMC vote, providing that the guidance for both is followed. There should be archived VOTE threads on the droids-private list, which were cc'd to private@incubator.a.o. Hopefully they were for PPMC membership. If not, there will be some cleanup work to do. ... Thorsten is not on the IPMC right now, though as an ASF Member he can simply request to join. Once that happens, you'll have 1 IPMC vote. But he is. Several months ago the board acked his request, but it would appear that the IPCM membership roster hasn't been updated. OK, great! That's resolved. Ross participated in a previous vote that didn't pass as we found things we need to clean up. It would seem he didn't have the time to participate this time. OK, that's reassuring. :) (Looks like OOo is already starting to impact our volunteer resources.) FYI, at this point I still plan to gate my vote on a +1 vote from a Droids Mentor. IMO, it would be less than ideal to have an inaugural release approved by one interested party (Thorsten) augmented by freelancers, even if one or more Mentors has expressed some measure of support in the past. Actually I stepped up as mentor when Grant resigned. Message-id: ce9e361e-737d-47e5-bf7a-bbcbffea3...@apache.org References: f7bb5fb8-eb7f-4203-91d7-c7ea1cdb7...@apache.org 08051FA22EC442FA9D0A116651FBEE63@developer 510143ac0910190738s17179ba3k46170bffdc01b...@mail.gmail.com I need to search in my send mail folder but I actually wrote an request to the private incubator list to add me as mentor. ... Lastly, I think it's worth commenting on the contents of README.TXT, which starts off like so: A p a c h eD r o i d s -- by Thorsten Scherler thorsten at apache.org That credit is obviously inaccurate and seems quite unusual for an Apache project. I know that other projects have gone out of their way to delete all @author tags. Perhaps Droids might consider doing likewise. If you read this file to the end you will find: Please report feedback to the labs mailing list. Meaning this file have not changed since it was first created in Apache Labs. That is the only reason for this unusual credit. It started as personal research project and we have not reviewed this file ever since. Thanks for pointing this out, I will fix it right away. salu2 -- Thorsten Scherler thorsten.at.apache.org codeBusters S.L. - web based systems consulting, training and solutions http://www.codebusters.es/ smime.p7s Description: S/MIME cryptographic signature
Re: [PROPOSAL] Bigtop for the Apache Incubator
I'm happy to see this project joining the Foundation. As an Apache
Whirr committer I feel a lot of pain when it comes to testing
compatibility for multiple services across multiple operating systems
(and multiple cloud providers).
I would love to join the Bigtop team as one of the initial committers
an do some of testing work we are already doing in Whirr.
PS: having ready to use .rpm and .deb packages sounds really great!
Cheers,
-- Andrei Savu / andreisavu.ro
On Tue, Jun 14, 2011 at 7:26 AM, Tom White tomwh...@apache.org wrote:
Hi,
I would like to propose Bigtop to be an Apache Incubator project.
Bigtop is a project for the development of packaging and tests of the
Hadoop ecosystem. The goal is to do testing at various levels
(packaging, platform, runtime, upgrade, etc...) developed by a
community with a focus on the system as a whole, rather than
individual projects.
Here's a link to the proposal on the wiki
http://wiki.apache.org/incubator/BigtopProposal
I've also included the initial contents below.
Cheers,
Tom
= Bigtop - Apache Hadoop Ecosystem Packaging and Test =
== Abstract ==
Bigtop - a project for the development of packaging and tests of the
Hadoop ecosystem.
== Proposal ==
The primary goal of Bigtop is to build a community around the
packaging and interoperability testing of Hadoop-related projects.
This includes testing at various levels (packaging, platform, runtime,
upgrade, etc...) developed by a community with a focus on the system
as a whole, rather than individual projects.
Build, packaging and integration test code that depends upon official
releases of the Apache Hadoop-related projects (HDFS, MapReduce,
HBase, Hive, Pig, ZooKeeper, etc...) will be developed and released by
this project. As bugs and other issues are found we expect these to be
fixed upstream.
== Background ==
The initial packaging and test code for Bigtop was developed by
Cloudera to package projects from the Apache Hadoop ecosystem and
provide a consistent, inter-operable framework.
== Rationale ==
Hadoop defines itself as:
{{{
The Apache Hadoop project develops open-source software for reliable,
scalable, distributed computing. Hadoop includes these subprojects:
* Hadoop Common: The common utilities that support the other Hadoop
subprojects.
* HDFS: A distributed file system that provides high throughput access
to application data.
* MapReduce: A software framework for distributed processing of large
data sets on compute clusters.
}}}
There are also several other Hadoop-related projects at Apache. Some
TLP examples include HBase, Hive, Mahout, ZooKeeper, and Pig. There
are also several new projects in the Incubator such as HCatalog and
Sqoop.
There is limited interoperability testing done the projects
themselves. The intent of this project is to build a community where
the projects are brought together, packaged, and tested for
interoperability.
Projects such as Apache Whirr (incubating), which deploy and use a
collection of Hadoop-related projects, would benefit from the
interoperability testing done by Bigtop, rather than picking and
testing project combinations themselves.
== Initial Goals ==
Much of the code for Bigtop has been released by Cloudera under the
Apache 2.0 license for over two years.
Some current goals include:
* create a set of packages for the Hadoop ecosystem, over a wide
range of platforms
* interoperability test these projects
* document project sets that are known to work well together
Bigtop’s release artifact would consist of a single tarball of
packaging and test code that, when built, would produce source and
binary Linux packages for the upstream projects.
= Current Status =
== Meritocracy ==
Bigtop was originally developed and released as an open source
packaging infrastructure, CDH, by Cloudera.
== Community ==
The community is primarily the original developers at Cloudera,
however a number of contributions to the packaging specifications have
been accepted from outside contributors. Growing a diverse community
is the main reason to bring Bigtop to the Apache Incubator.
== Core Developers ==
The core developers for Bigtop project are:
* Andrew Bayer has extensive expertise with build tools, specifically
Jenkins continuous integration and Maven.
* Peter Linnell has contributed to the RPM packaging.
* Bruno Mahé has overseen much of the development of the RPM and
Debian packaging system.
* Roman Shaposhnik designed and implemented the system testing framework.
Many of the committers to the Bigtop project have contributed towards
Hadoop or related Apache projects (Alejandro Abdelnur, Eli Collins,
Patrick Hunt, John Sichi, Michael Stack, Tom White) and are familiar
with Apache principals and philosophy for community driven software
development.
== Alignment ==
We expect projects in Bigtop to be drawn from Hadoop and related
projects at Apache. Bigtop
Re: [PROPOSAL] Bigtop for the Apache Incubator
Edward, Andrei - thanks for volunteering to help out as initial
committers. Please add your names to the proposal on the wiki.
Cheers,
Tom
On Wed, Jun 15, 2011 at 6:15 AM, Andrei Savu as...@apache.org wrote:
I'm happy to see this project joining the Foundation. As an Apache
Whirr committer I feel a lot of pain when it comes to testing
compatibility for multiple services across multiple operating systems
(and multiple cloud providers).
I would love to join the Bigtop team as one of the initial committers
an do some of testing work we are already doing in Whirr.
PS: having ready to use .rpm and .deb packages sounds really great!
Cheers,
-- Andrei Savu / andreisavu.ro
On Tue, Jun 14, 2011 at 7:26 AM, Tom White tomwh...@apache.org wrote:
Hi,
I would like to propose Bigtop to be an Apache Incubator project.
Bigtop is a project for the development of packaging and tests of the
Hadoop ecosystem. The goal is to do testing at various levels
(packaging, platform, runtime, upgrade, etc...) developed by a
community with a focus on the system as a whole, rather than
individual projects.
Here's a link to the proposal on the wiki
http://wiki.apache.org/incubator/BigtopProposal
I've also included the initial contents below.
Cheers,
Tom
= Bigtop - Apache Hadoop Ecosystem Packaging and Test =
== Abstract ==
Bigtop - a project for the development of packaging and tests of the
Hadoop ecosystem.
== Proposal ==
The primary goal of Bigtop is to build a community around the
packaging and interoperability testing of Hadoop-related projects.
This includes testing at various levels (packaging, platform, runtime,
upgrade, etc...) developed by a community with a focus on the system
as a whole, rather than individual projects.
Build, packaging and integration test code that depends upon official
releases of the Apache Hadoop-related projects (HDFS, MapReduce,
HBase, Hive, Pig, ZooKeeper, etc...) will be developed and released by
this project. As bugs and other issues are found we expect these to be
fixed upstream.
== Background ==
The initial packaging and test code for Bigtop was developed by
Cloudera to package projects from the Apache Hadoop ecosystem and
provide a consistent, inter-operable framework.
== Rationale ==
Hadoop defines itself as:
{{{
The Apache Hadoop project develops open-source software for reliable,
scalable, distributed computing. Hadoop includes these subprojects:
* Hadoop Common: The common utilities that support the other Hadoop
subprojects.
* HDFS: A distributed file system that provides high throughput access
to application data.
* MapReduce: A software framework for distributed processing of large
data sets on compute clusters.
}}}
There are also several other Hadoop-related projects at Apache. Some
TLP examples include HBase, Hive, Mahout, ZooKeeper, and Pig. There
are also several new projects in the Incubator such as HCatalog and
Sqoop.
There is limited interoperability testing done the projects
themselves. The intent of this project is to build a community where
the projects are brought together, packaged, and tested for
interoperability.
Projects such as Apache Whirr (incubating), which deploy and use a
collection of Hadoop-related projects, would benefit from the
interoperability testing done by Bigtop, rather than picking and
testing project combinations themselves.
== Initial Goals ==
Much of the code for Bigtop has been released by Cloudera under the
Apache 2.0 license for over two years.
Some current goals include:
* create a set of packages for the Hadoop ecosystem, over a wide
range of platforms
* interoperability test these projects
* document project sets that are known to work well together
Bigtop’s release artifact would consist of a single tarball of
packaging and test code that, when built, would produce source and
binary Linux packages for the upstream projects.
= Current Status =
== Meritocracy ==
Bigtop was originally developed and released as an open source
packaging infrastructure, CDH, by Cloudera.
== Community ==
The community is primarily the original developers at Cloudera,
however a number of contributions to the packaging specifications have
been accepted from outside contributors. Growing a diverse community
is the main reason to bring Bigtop to the Apache Incubator.
== Core Developers ==
The core developers for Bigtop project are:
* Andrew Bayer has extensive expertise with build tools, specifically
Jenkins continuous integration and Maven.
* Peter Linnell has contributed to the RPM packaging.
* Bruno Mahé has overseen much of the development of the RPM and
Debian packaging system.
* Roman Shaposhnik designed and implemented the system testing framework.
Many of the committers to the Bigtop project have contributed towards
Hadoop or related Apache projects (Alejandro Abdelnur, Eli Collins,
Patrick Hunt, John Sichi, Michael Stack, Tom
Re: [PROPOSAL] Bigtop for the Apache Incubator
Hi, I would like my name to be added to the committer list. I am assembling and integration-testing Hadoop stacks at Yahoo. I look forward to participate in developing a community-accepted framework for packaging Hadoop components, and assembly and validation of Hadoop stacks. Thanks -- Andre Arcilla - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Bigtop for the Apache Incubator
On Wed, Jun 15, 2011 at 11:43 AM, Andre Arcilla arci...@yahoo-inc.com wrote: Hi, I would like my name to be added to the committer list. I am assembling and integration-testing Hadoop stacks at Yahoo. I look forward to participate in developing a community-accepted framework for packaging Hadoop components, and assembly and validation of Hadoop stacks. A strong +1. Being able to tackle some of the use cases that a company the size of Yahoo! would have to offer is definitely going to be a major factor for Bigtop success. Thanks, Roman. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Droids 0.1-incubating RC2
On Wed, Jun 15, 2011 at 11:19:41AM +0200, Thorsten Scherler wrote: (Looks like OOo is already starting to impact our volunteer resources.) FYI, at this point I still plan to gate my vote on a +1 vote from a Droids Mentor. IMO, it would be less than ideal to have an inaugural release approved by one interested party (Thorsten) augmented by freelancers, even if one or more Mentors has expressed some measure of support in the past. Actually I stepped up as mentor when Grant resigned. My primary concern is IP clearance for an inaugural ASF release. As a freelancer, I can perform a superficial examination of the existing artifacts, but I was not there while the IP that makes them up was being imported or committed. However, if the IPMC has seen fit to appoint you as a Mentor, I will defer to the collective judgment and assume that sufficient care has been exercised. Message-id: ce9e361e-737d-47e5-bf7a-bbcbffea3...@apache.org References: f7bb5fb8-eb7f-4203-91d7-c7ea1cdb7...@apache.org 08051FA22EC442FA9D0A116651FBEE63@developer 510143ac0910190738s17179ba3k46170bffdc01b...@mail.gmail.com I need to search in my send mail folder but I actually wrote an request to the private incubator list to add me as mentor. Googling these message id's only turns up this post; since I'm not an ASF Member, I don't have access to the ap-mail archives on people.apache.org; sending mail to the private-get.1-2000@incubator.a.o failed; searching droids-dev and general@incubator.a.o via MarkMail did not turn up any indication of where the Mentorship appointment took place. Can somebody please help out with confirmation that Thorsten's request to become a Mentor for Droids went through? Lastly, I think it's worth commenting on the contents of README.TXT, which starts off like so: A p a c h eD r o i d s -- by Thorsten Scherler thorsten at apache.org That credit is obviously inaccurate and seems quite unusual for an Apache project. I know that other projects have gone out of their way to delete all @author tags. Perhaps Droids might consider doing likewise. If you read this file to the end you will find: Please report feedback to the labs mailing list. Meaning this file have not changed since it was first created in Apache Labs. That is the only reason for this unusual credit. It started as personal research project and we have not reviewed this file ever since. Thanks for pointing this out, I will fix it right away. Fab, that's great. :) Marvin Humphrey - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Droids 0.1-incubating RC2
On Tue, Jun 14, 2011 at 09:35:05PM -0500, Richard Frovarp wrote: There should be archived VOTE threads on the droids-private list, which were cc'd to private@incubator.a.o. Hopefully they were for PPMC membership. If not, there will be some cleanup work to do. The votes were handled on the droids-dev list (like they should) and were committer votes. So Bertil and I aren't on the PPMC. OK... In my opinion, the intent of the community to make this release is perfectly clear. None of the people who are officially on the PPMC objected to it, nor did anyone raise any concerns about the validity of votes from Committers who aren't on the PPMC. Furthermore, the three +1 votes come from the three top podling committers by commit volume: http://svnsearch.org/svnsearch/repos/ASF/search?path=%2Fincubator%2Fdroids The community is small and some people are MIA, but it seems like those who are active are exhibiting exactly what the Incubator wants to see: responsible self-governance by stakeholders. The fact that two votes come from people who were elected as Committers but not PPMC members is a technical oversight. The Incubation Policy page sets out clear rules for how a release happens, and I don't see a way to overlook or overrule the SHALL and SHALL NOT portions of the text without a formal IPMC vote: http://incubator.apache.org/incubation/Incubation_Policy.html#Releases ... Podlings in Incubation SHALL NOT perform any releases of software without the explicit approval of the Incubator PMC. Such approval SHALL be given only after the Incubator PMC has followed the process detailed in these guidelines, and SHALL NOT occur until all source has been legally transferred to the ASF. Therefore, should a Podling decide it wishes to perform a release, the Podling SHALL hold a vote on the Podling's public -dev list. At least three +1 votes are required (see the Apache Voting Process page). If the majority of all votes is positive, then the Podling SHALL send a summary of that vote to the Incubator's general list and formally request the Incubator PMC approve such a release. Three +1 Incubator PMC votes are required. Below is an example showing how an incubating project managed this process: The by-the-book remedy is for the existing Droids PPMC members to vote in the people who are obviously driving this project forward, and for a new release vote to be taken. I'm pained by the delays that will introduce, and if there's anything I can do to expedite the process I'd like to help, but as a newcomer to the IPMC I don't see it as being my place to suggest alternative approaches. No, there is no JIRA ticket. OK, no problem -- this thread will suffice. There are no category-X defined dependencies. Check! The notice file includes notices for all the category B defined dependencies: JUnit and javax.servlet. Those are fairly common in Apache projects and the requirements were met. See below. Attached is the dependency hierarchy. All of the Apache projects are full projects, so they are all good. That leaves: NekoHTML - AL2 SLF4J - MIT mockito - MIT Google Guava - AL2 Spring - AL2 JUnit - CPL v1 - Category B, binary only, appropriately labeled in the NOTICE.txt file javax.servlet - Included in the Jetty notice, which states it is CDDLv1 and copyright Sun Microsystems and ASF. Notice text copied from Solr Jetty 6 - AL2, but requires notice (in place) CGLib - AL2 OK, excellent -- no fundamental problems, so it's just a matter of dotting our i's and crossing our t's. I see that the Droids LICENSE.txt only contains the ALv2, yet Droids has dependencies on non-ALv2 libraries. http://www.apache.org/dev/release.html#distributing-code-under-several-licenses However, it looks as though Droids isn't *bundling* either JUnit or javax.servlet, in either in source or binary form -- you're expecting Maven to resolve and install the dependency. Therefore, I don't believe it's required to include the license texts which apply to those components. I'm not even sure whether you even need attributions in NOTICE.txt for components you aren't bundling. As best I can tell, the Droids distro archive does not contain either source or binary materials belonging to or derived from either JUnit or javax.servlet IP. In summary, unless someone corrects my interpretation, LICENSE.txt is fine and NOTICE.txt has some info which is arguably superfluous, but the presence of that extra info does not block the release. I consider the matter provisionally resolved. (If Droids ever *starts* bundling JUnit or javax.servlet, I'm pretty sure you'll need *both* the notice and the license texts.) That's Maven. LICENSE.txt and NOTICE.txt are the two in svn. We may need to rename them to be without the .txt so Maven doesn't do its own thing there. While without txt is preferred, it is allowable to use the .txt file names. OK.
Re: [alois] Incubation failed?
Christian Grobmeier wrote: I would like to propose Dormant or Retired status for the alois project - not sure what is more matching or what the difference between these two is. Unfortunately I have not found any docs about this process. I suggest search the mail lists for past similar situations. We did have a recent discussion too about the process. IIRC, the Leo Simons was very helpful. Clutch provides some links: http://incubator.apache.org/clutch.html#h-Retire However there is more involved. When we find/create/enhance some docs, we can add to those pointers. Ah yes, one of those links goes to INCUBATOR-100 -David - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Droids 0.1-incubating RC2
On 12 June 2011 04:43, Richard Frovarp rfrov...@apache.org wrote: Please vote on the release cndidate for Apache Droids Incubating, version 0.1-incubating. I've received one binding IPMC +1 votes and 2 non-binding +1 votes. PPMC release vote thread: http://mail-archives.apache.org/mod_mbox/incubator-droids-dev/201106.mbox/%3c4de7d6cc.8080...@apache.org%3E Source files: http://people.apache.org/~rfrovarp/droids/ Maven staging repo: https://repository.apache.org/content/repositories/orgapachedroids-011/ SVN source tag (r1127762): https://svn.apache.org/repos/asf/incubator/droids/tags/0.1-incubating/ PGP release keys (signed using 3698A2B1): https://svn.apache.org/repos/asf/incubator/droids/KEYS [ ] +1 [ ] +0 [ ] -1 There must be a disclaimer saying that the project is undergoing Incubation. This is normally in a DISCLAIMER file, which should be in SVN, source and binary archives. The website should also carry a prominent disclaimer, nromally at the start of the index page. The NOTICE file must only contain required notices, and only for items that are actually included in the release, not run-time dependencies that are downloaded by Maven. E.g. is JUnit included in the release? If not, remove the reference. Do not add any extraneous text to the Notice file - e.g explanations and headings - it should be as short as possible (but no shorter). The project name should be shown as Apache Droids in the Notice file(s). I think the above all need to be fixed before release. The source archive contents agree with SVN (apart from extra files generated by Maven). Sigs and hashes are OK; key is in public PGP repo. Contents of jar files look good; there are NL files in the META-INF dir. The source and javadoc jar manifests could include the Specification entries. It would be useful to include the Java source and target versions in the binary jar manifests. The SVN properties don't appear to have been set on many of the source files, which suggests that some committers have not set up their SVN defaults correctly. (I'll raise a JIRA for correcting the properties) Thanks, Richard - 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
process for going Dormant/Retired
David Crossley wrote: Christian Grobmeier wrote: I would like to propose Dormant or Retired status for the alois project - not sure what is more matching or what the difference between these two is. Unfortunately I have not found any docs about this process. I suggest search the mail lists for past similar situations. We did have a recent discussion too about the process. IIRC, the Leo Simons was very helpful. Clutch provides some links: http://incubator.apache.org/clutch.html#h-Retire However there is more involved. When we find/create/enhance some docs, we can add to those pointers. Ah yes, one of those links goes to INCUBATOR-100 Giving this discussion a new name and linking from JIRA. -David - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Commented] (INCUBATOR-100) document the process for a podling that has decided to go to dormant status
[ https://issues.apache.org/jira/browse/INCUBATOR-100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13050185#comment-13050185 ] David Crossley commented on INCUBATOR-100: -- Permanent links to some discussion: Re: TripleSoup going into dormant mode http://s.apache.org/d2s Re: process for going Dormant/Retired http://s.apache.org/oN document the process for a podling that has decided to go to dormant status --- Key: INCUBATOR-100 URL: https://issues.apache.org/jira/browse/INCUBATOR-100 Project: Incubator Issue Type: Task Components: site Reporter: David Crossley Document the process. Some steps were thoughtfully provided by Leo and Matthieu for TripleSoup: Re: TripleSoup going into dormant mode http://markmail.org/message/kavm65g65x55wqr5 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept OpenOffice.org for incubation
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 +1 (binding) Past the 72 hour notation below but I didn't see a final tally. On Jun 10, 2011, at 12:02 PM, Sam Ruby wrote: *** Please change your Subject: line for any [DISCUSSION] of this [VOTE] As the discussions on the OpenOfficeProposal threads seem to be winding down, I would like to initiate the vote to accept OpenOffice.org as an Apache Incubator project. At the end of this mail, I've put a copy of the current proposal. Here is a link to the document in the wiki: http://wiki.apache.org/incubator/OpenOfficeProposal?action=recallrev=207 As the proposal discussion threads are numerous, I encourage people to scan and review the archives for this month: http://mail-archives.apache.org/mod_mbox/incubator-general/201106.mbox/browser Please cast your votes: [ ] +1 Accept OpenOffice.org for incubation [ ] +0 Indifferent to OpenOffice.org incubation [ ] -1 Reject OpenOffice.org for incubation This vote will close 72 hours from now. - Sam Ruby = OpenOffice.org - An open productivity environment = == Abstract == !OpenOffice.org is comprised of six personal productivity applications: a word processor (and its web-authoring component), spreadsheet, presentation graphics, drawing, equation editor, and database. !OpenOffice.org is released on Windows, Solaris, Linux and Macintosh operation systems, with more [[http://porting.openoffice.org/|communities]] joining, including a mature [[http://porting.openoffice.org/freebsd/|FreeBSD port]]. !OpenOffice.org is localized, supporting over 110 languages worldwide. == Proposal == Apache !OpenOffice.org will continue the mission pursued by the !OpenOffice.org project while under the sponsorship of Sun and Oracle, namely: To create, as a community, the leading international office suite that will run on all major platforms and provide access to all functionality and data through open-component based APIs and an XML-based file format. In addition to to building the !OpenOffice.org product, as an end-user facing product with many existing individual and corporate users, this project will also be active in supporting end-users via tutorials, user forums, document template repositories, etc. The project will also work to further enable !OpenOffice.org to be used as a programmable module in document automation scenarios. == Background == !OpenOffice.org was launched as an open source project by Sun Microsystems in June 2000. !OpenOffice.org was originally developed under the name of StarOffice by Star Division, a German company, which was acquired by Sun Microsystems in 1999. Sun released this as open source in 2000. !OpenOffice.org is the leading alternative to MS-Office available. Its most recent major version, the 3.x series saw over [[http://www.webmasterpro.de/portal/news/2010/02/05/international-openoffice-market-shares.html|100 million downloads]] in its first year. The [[http://www.webmasterpro.de/portal/news/2010/02/05/international-openoffice-market-shares.html|most recent estimates]] suggest a market share on the order of 8-15%. The !OpenOffice source is written in C++ and delivers language-neutral and scriptable functionality. This source technology introduces the next-stage architecture, allowing use of the suite elements as separate applications or as embedded components in other applications. Numerous other features are also present including XML-based file formats based on the vendor-neutral !OpenDocument Format (ODF) standard from OASIS and other resources. == Rationale == !OpenOffice.org core development would continue at Apache following the contribution by Oracle, in accordance with Apache bylaws and its usual open development processes. Both Oracle and ASF agree that the !OpenOffice.org development community, previously fragmented, would re-unite under ASF to ensure a stable and long term future for OpenOffice.org. ASF would enable corporate, non-profit, and volunteer stakeholders to contribute code in a collaborative fashion. Supporting tooling projects will accompany the !OpenOffice.org contribution, providing APIs for extending and customizing !OpenOffice.org. Both !OpenOffice.org and the related tooling projects support the OASIS Open Document Format, and will attract an ecosystem of developers, ISVs and Systems Integrators. ODF ensures the users of !OpenOffice.org and related solutions will own their document data, and be free to choose the application or solution that best meets their requirements. The !OpenOffice.org implementation will serve as a reference implementation of the Open Document Format standard. = Current Status = == Meritocracy == We understand the intention and value of meritocracy at Apache. We are particularly gratified to learn, during the discussion on this proposal, that there is a strong role for non-coders
Re: [VOTE] Accept OpenOffice.org for incubation
On 6/15/2011 9:58 PM, Matt Hogstrom wrote: +1 (binding) Past the 72 hour notation below but I didn't see a final tally. Then you missed the note. [Hint: search for the subject RESULT] ---BeginMessage--- On Thu, Jun 9, 2011 at 12:00 PM, Sam Ruby ru...@intertwingly.net wrote: Binding votes are ones that are cast by Incubator PMC members. Quorum is 3 binding +1 yes votes. Once quorum is met, if more +1 votes are received than -1, the vote carries. Otherwise, the vote fails. Vote started on Friday, June 10th at 12:02pm EDT: http://s.apache.org/VgS Voting is now closed. Quorum was achieved, and the vote passes. Voting results: --- Summary --- Binding: +1: 41 --: 1 -0: 1 -1: 5 Non-binding: +1: 45 +0: 2 ±0: 1 -0: 1 -1: 8 --- Details --- Binding: +1 aadamchikAndrus Adamchik +1 adc Alan Cabrera +1 akarasuluAlex Karasulu -- antelder Anthony Elder +1 ate Ate Douma +1 bdelacretaz Bertrand Delacretaz +1 bimargulies Benson Margulies +1 brettBrett Porter +1 clr Craig Russell +1 curcuru Shane Curcuru +1 danese Danese Cooper +1 dims Davanum Srinivas +1 dirkxDirk-Willem van Gulik +1 elecharnyEmmanuel Lecharny -0 gnodet Guillaume Nodet +1 grobmeierChristian Grobmeier +1 gstein Greg Stein +1 jim Jim Jagielski +1 joes Joe Schaefer +1 jukkaJukka Zitting +1 jvermillard Julien Vermillard +1 kevanKevan Lee Miller +1 leosimonsLeo Simons +1 lresende Luciano Resende +1 marrsMarcel Offermans +1 marvin Marvin Humphrey +1 mattmann Chris Mattmann +1 mturkMladen Turk -1 niallp Niall Pemberton +1 nick Nick Burch -1 niclas Par Niclas Hedhman +1 noel Noel J. Bergman +1 noirin Noirin Plunkett +1 paulsKarl Pauls -1 psteitz Phil Steitz +1 rdonkin Robert Burrell Donkin +1 rgardler Ross Duncan Gardler +1 rgoers Ralph Goers +1 rhirsch Richard Hirsch +1 rubysSam Ruby -1 sanjiva Sanjiva Weerawarana +1 sdeboy Scott Deboy +1 stoddard Bill Stoddard +1 struberg Mark Struberg -1 twilliamsTim Williams +1 upayaviraUpayavira +1 wroweWilliam A. Rowe Jr. +1 zwoopLeif Hedstrom Non-binding: +1 aaf Alexei Fedotov +0 aku Andreas Kuckartz +1 asavory Andrew Savory +1 bayard Henri Yandell +1 damjan Damjan Jovanovic (v) +1 eric Eric Charles +1 edwardsmjMike Edwards +1 florent Florent André (v) +1 jkosin James Kosin -1 stevel Steve Loughran +1 mikemccand Michael McCandless -1 niq Nick Kew +1 ngn Niklas Gustavsson +1 rickhall Richard S. Hall -0 seelmann Stefan Seelmann +1 scottbw Scott Wilson +1 sgalaSantiago Gala +1 svanderwaal Sander van der Waal +1 wave Dave Fisher (v) +1 yegorYegor Kozlov (v) +1 --- Eric Bachard (v) +1 --- Mathias Bauer (v) -1 --- Thorsten Behrens +1 --- Stephan Bergmann (v) +1 --- Raphael Bircher (v) +1 --- Andy Brown (v) +1 --- Alexandro Colorado (v) -1 --- Keith Curtis -1 --- Florian Effenberger +1 --- Roman H. Gelbort (v) +1 --- Pedro Giffuni +1 --- Larry Gusaas +1 --- Daniel Haischt +1 --- Dennis E. Hamilton (v) +1 --- Don Harbison (v) +1 --- Kazunari Hirano (v) +1 --- Christoph Jopp +1 --- Steve Lee (v) +1 --- Dieter Loeschky (v) +1 --- Ian Lynch (v) +1 --- Carl Marcum (v) +1 --- Marcus +1 --- Ingrid von der Mehden (v) -1 --- Volker Merschmann +0 --- Cor Nouws +1 --- Simon Phipps ±0 --- Manfred A. Reiter +1 --- Phillip Rhodes (v) +1 --- Andrew Rist (v) +1 --- Jürgen Schmidt (v) -1 --- André Schnabel +1 --- Jomar Silva (v) +1 --- Louis Suárez-Potts (v) +1 --- Malte Timmermann (v) +1 --- Jochen Wiedmann +1 --- Donald Whytock -1 --- Simos Xenitellis - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org ---End Message--- - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Issue Comment Edited] (INCUBATOR-100) document the process for a podling that has decided to go to dormant status
[ https://issues.apache.org/jira/browse/INCUBATOR-100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13050185#comment-13050185 ] David Crossley edited comment on INCUBATOR-100 at 6/16/11 3:40 AM: --- Permanent links to some discussion: Re: TripleSoup going into dormant mode Re: how to close down / put into dormant mode an incubator project / podling http://s.apache.org/d2s Re: process for going Dormant/Retired http://s.apache.org/oN Re: Bluesky status and plans http://s.apache.org/NLL was (Author: crossley): Permanent links to some discussion: Re: TripleSoup going into dormant mode http://s.apache.org/d2s Re: process for going Dormant/Retired http://s.apache.org/oN document the process for a podling that has decided to go to dormant status --- Key: INCUBATOR-100 URL: https://issues.apache.org/jira/browse/INCUBATOR-100 Project: Incubator Issue Type: Task Components: site Reporter: David Crossley Document the process. Some steps were thoughtfully provided by Leo and Matthieu for TripleSoup: Re: TripleSoup going into dormant mode http://markmail.org/message/kavm65g65x55wqr5 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
