Re: [VOTE] Release Pivot 1.3 RC3
On Fri, Sep 18, 2009 at 3:16 PM, Todd Volkert tvolk...@gmail.com wrote: Thanks Jukka! Can someone else please have a look? -- we're still one vote shy. -T Is this still waiting for a vote? If so i can go take a look. ...ant - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Approve the release of PDFBox 0.8.0-incubating
On Fri, Sep 18, 2009 at 6:57 PM, Niall Pemberton niall.pember...@gmail.com wrote: On Fri, Sep 18, 2009 at 4:26 PM, sebb seb...@gmail.com wrote: On 18/09/2009, Andreas Lehmkühler andr...@lehmi.de wrote: Hi, The PDFBox PPMC has voted to release version 0.8.0-incubating of PDFBox. The release candidate is available for review at http://people.apache.org/~lehmi/pdfbox/pdfbox-0.8.0-incubating/ See the attached original vote messages for more details. Please vote to approve this release. This IPMC vote is open for the next 72 hours. Is there an SVN tag that corresponds to this release? If so, what is it? http://svn.apache.org/viewvc/incubator/pdfbox/tags/0.8.0-incubating/ Niall [ ] +1 Approve the release of PDFBox 0.8.0-incubating [ ] -1 Do not approve this release because... The following three IPMC member votes were cast already on pdfbox-...@. I'm including these also in this vote. +1 Niall Pemberton +1 Jeremias Maerki +1 Jukka Zitting BR Andreas Lehmkühler - weitergeleitete Nachricht - Betreff: [RESULT][VOTE] Release PDFBox 0.8.0-incubating Datum: Fr, 18. Sep 2009 Von: Andreas Lehmkühlerandr...@lehmi.de Hi, Please vote on releasing this package as Apache PDFBox 0.8.0-incubating. The vote is open for the next 72 hours and passes if a majority of at least three +1 PDFBox PPMC votes is reached. Assuming the vote passes, I will ask the Incubator PMC to approve the release. [ ] +1 Release this package as Apache PDFBox 0.8.0-incubating [ ] -1 Do not release this package because... The vote passes as follows: +1 Andreas Lehmkühler +1 Jukka Zitting +1 Niall Pemberton +1 Daniel Wilson +1 Mel Martinez (no binding vote) +1 Phillip Koch +1 Jeremias Maerki Thanks to all for your patience and for your help reviewing this release. I'll ask the IPMC to approve the release. BR Andreas Lehmkühler Is this still waiting for votes? Its quite old now so asking before spending time looking. ...ant - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Pivot 1.3 RC3
On Thu, Oct 1, 2009 at 10:41 AM, ant elder ant.el...@gmail.com wrote: On Fri, Sep 18, 2009 at 3:16 PM, Todd Volkert tvolk...@gmail.com wrote: Thanks Jukka! Can someone else please have a look? -- we're still one vote shy. -T Is this still waiting for a vote? If so i can go take a look. ...ant Ok forget it i see its done, sorry for the noise. Sorting through lots of email after being away and for some reason gmail isn't keeping the vote and result together for some threads. ...ant - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Graduate Lucene.Net as a subproject under Apache Lucene
+1 ...ant On Thu, Oct 15, 2009 at 2:33 AM, George Aroush geo...@aroush.net wrote: Hi Folks, On behalf of Lucene.Net mentor, committers and community, this is a vote call to graduate the Lucene.Net project (http://incubator.apache.org/lucene.net/) as a sub-project under Apache Lucene. The Lucene.Net mentor, committers, and the community have voted like so: +1 Erik Hatcher (mentor) +1 George Aroush (committer) +1 Isik YIGIT (aka: DIGY) (committer) +1 Doug Sale (committer) +1 a total of 70+ Lucene.Net members / followers / users. (with no -1 or 0 votes) The vote result can be found here: http://mail-archives.apache.org/mod_mbox/incubator-lucene-net-user/200909.mb ox/%3c166a01ca3739$13947380$3abd5a...@net%3ehttp://mail-archives.apache.org/mod_mbox/incubator-lucene-net-user/200909.mb%0Aox/%3c166a01ca3739$13947380$3abd5a...@net%3e In addition, the Java Lucene PMC have casted their vote to accept Lucene.Net as a subproject under Apache Lucene. The vote result is as follow: +1 Andi Vajda +1 Andrzej Bialecki +1 Michael McCandless +1 Jukka Zitting +1 Grant Ingersoll +1 Michael Busch +1 Chris Hostetter +1 Ted Dunning +1 Otis Gospodnetic +1 Simon Willnauer (with no -1 or 0 votes) The vote result can be found here: http://mail-archives.apache.org/mod_mbox/lucene-general/200910.mbox/%3c2cd40 1ca4863$434ef290$c9ecd7...@net%3e The rationale for graduation is: * Lucene.Net has been under incubation since April 2006 (3 1/2 years now). * During incubation, Lucene.Net has: - Made, 1 official release (Incubating-Apache-Lucene.Net-2.0-004-11Mar07). - Released, as SVN tag, 18 ports of Java Lucene (from 1.9 to 2.4.0). - Released, as SVN tag, port of WordNet.Net 2.0, SpellChecker.Net 2.0, Snowball.Net 2.0, and Highlighter.Net 2.0. - Released, MSDN style documentation for the above release. - Accepted, two new committers: Isik YIGIT (DIGY) digydigy @ gmail.com and Doug Sale dsale @ myspace-inc.com were added in November 2008 (George Aroush george @ aroush.net is the original committer). - The community has grown, with a healthy followers. - Is being used by well established companies in production (I'm not sure what's the legality to mention their names here, or even if I have the complete list). - Is being used by Beagle project. * Work is already under way to port Java Lucene 2.9 to Lucene.Net 2.9 If this graduation is approved, Lucene.Net will be officially called Apache Lucene.Net Please cast your votes: [ ] +1 Graduate Lucene.Net as a sub-project under Apache Lucene. [ ] -1 Lucene.Net is not ready to graduate as a sub-project under Apache Lucene, because ... This vote will close on October 20th, 2009. Regards, -- George
Re: [VOTE] Release cassandra 0.4.1
+1 ...ant On Tue, Oct 13, 2009 at 4:12 PM, Eric Evans eev...@rackspace.com wrote: The Cassandra community voted on and approved the release of Apache Cassandra 0.4.1. We would now like to request the approval of the Incubator PMC for this release. Cassandra is a massively scalable, eventually consistent, distributed, structured key-value store. Podling vote thread: http://www.mail-archive.com/cassandra-...@incubator.apache.org/msg00987.html 0.4.1 artifacts: http://people.apache.org/~eevanshttp://people.apache.org/%7Eeevans SVN tag: https://svn.apache.org/repos/asf/incubator/cassandra/tags/cassandra-0.4.1 Project home: http://incubator.apache.org/cassandra/ Incubation status: http://incubator.apache.org/projects/cassandra.html Note: We've already received 3 binding +1s during the podding release vote[0][1][2]. The vote will remain open for 72 hours. Thank you for your time. Regards, [0] http://www.mail-archive.com/cassandra-...@incubator.apache.org/msg00995.html [1] http://www.mail-archive.com/cassandra-...@incubator.apache.org/msg00994.html [2] http://www.mail-archive.com/cassandra-...@incubator.apache.org/msg00996.html -- Eric Evans eev...@rackspace.com - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Wink 1.0
+1. Congrats on 1.0. Note the key used to sign the artifacts is not published to a public key server so you may want to do that before the artifacts go live. See http://www.apache.org/dev/release-signing.html#public-key-not-found ...ant On Fri, Oct 23, 2009 at 3:53 PM, Nicholas L Gallardo nlgal...@us.ibm.com wrote: The Wink community voted on and approved the release of Apache Wink 1.0. We would now like to request the approval of the Incubator PMC for this release. Podling vote thread: http://www.mail-archive.com/wink-...@incubator.apache.org/msg02060.html The Maven staging area is at: https://repository.apache.org/content/repositories/wink-staging-002/ The distributions are in: https://repository.apache.org/content/repositories/wink-staging-002/org/apache/wink/apache-wink/1.0-incubating/ This release is tagged at: https://svn.apache.org/repos/asf/incubator/wink/tags/wink-1.0-incubating/ Please vote using one of the options below. This vote will be open for 72 hours. [ ] +1 [ ] +0 [ ] -1 Nicholas Gallardo WebSphere - REST WebServices Development nlgal...@us.ibm.com Phone: 512-286-6258 Building: 903 / 5G-016 - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Libcloud Project
+1, sounds really interesting, I'd be happy to be a mentor too if you need another. ...ant On Tue, Oct 27, 2009 at 8:15 AM, Gavin ga...@16degrees.com.au wrote: This looks interesting, I'd be happy to help Mentor and have already put my name down. Gav... -Original Message- From: Paul Querna [mailto:p...@querna.org] Sent: Tuesday, 27 October 2009 5:00 PM To: general@incubator.apache.org Subject: [PROPOSAL] Libcloud Project Hi, I would like to propose incubating the existing Libcloud project to join the ASF: Proposal Wiki: http://wiki.apache.org/incubator/LibcloudProposal Libcloud is a unified Python API around many common cloud services provider, and I believe it could benefit greatly by joining the Apache Software Foundation. I also believe the ASF needs more Python projects, and more projects involved in the developing cloud infrastructure. We still need a few mentors, so feel free to signup :-) We would appreciate feedback and comments on the proposal. Full proposal is bellow. Thanks, Paul Libcloud, a unified interface to the cloud Abstract libcloud (http://www.libcloud.org) is a pure python client library for interacting with many of the popular cloud server providers. It was created to make it easy for developers to build products that work between any of the services that it supports. Proposal * Provide unified API for manipulating servers instances across many hosting providers who provide an API to manipulate instances. Current API includes: list, reboot, create, destroy, list images, list sizes. * (future) Provide utilities for manipulating and creating server images in many formats. (See the independent Stacklet project for ideas) * (future) Provide unified API for storing large objects on popular hosting provider storage APIs. Background While there are some projects to create open standards for interoperability within the cloud, most have failed to gain widespread adoption. Libcloud takes the approach of exposing a unified API to cover multiple vendor's APIs, and in the future to support standard APIs, assuming they become prevalent. Rationale There is a strong need in the developing cloud infrastructure for a community supported, high quality, and vendor independent tool set for managing servers and their resources. When new servers are just an API call away, traditional infrastructure models are changing quickly. Having a good library built around Apache's values and tradition will enable new server infrastructure to evolve much more quickly. Initial Goals Libcloud is an existing open source project, with patches from many different contributors. We view the moving to Apache as a way to improve this community, and look into future APIs around creating server images and large object storage. Current Status Libcloud is already open source under the ASL 2.0: * Libcloud Website http://www.libcloud.org * Libcloud Mailing Lists http://groups.google.com/group/libcloud * Libcloud Source Control http://github.com/cloudkick/libcloud Meritocracy Libcloud has involvement from members of both the ASF and other open source projects. Communication is driven by both IRC and E-Mail lists. Community Currently libcloud has several contributors, but not a large user community other than a few companies. We would like to increase our userbase as part of the incubator process. Core Developers Alex Polvi who wrote most of the original code is familiar with open source from working at OSUOSL and at Mozilla. Tom Davis drove much of the re factoring of the initial code base. Jed Smith, Ivan Meredith, Jeremy Orem, Jerry Chen and Paul Querna (ASF member) have all contributed mainly to developing provider specific drivers. Alignment Currently there are not many Apache communities involved with cloud computing or python based infrastructure. We believe introducing such a community is a good thing for the Apache Software Foundation. Known Risks Orphaned products libcloud is being used actively by Cloudkick to develop services. It is a core part of our ongoing infrastructure improvements. Inexperience with Open Source libcloud was open sourced in July 2009, during OSCON. Core contributors include former employees of Mozilla and an ASF member. Homogenous Developers Much of the initial development was done by Cloudkick, but much of the core design was re-factored by the community, and many of the drivers for each provider have been contributed by 3rd parties. Reliance on Salaried Developers The majority, but not all, of the developers are paid by their employer to work on libcloud at this time. Relationships with Other Apache Products Libcloud doesn't share many attributes with existing Apache projects due to it being in Python and addressing a new need. A Excessive Fascination with the Apache Brand Libcloud project
Re: [VOTE] Release Wink 1.0
On Tue, Oct 27, 2009 at 9:23 PM, Bryant Luk bryant@gmail.com wrote: Hi Leo, Thanks for the links. One general comment I have is that I understand this is part of the incubation process (and no offense intended to Leo since obviously taking energy and time for this) but if I can't look and see if other Apache projects are doing things the right way, I think we should have more examples of what goes in the NOTICE and LICENSE files and points out licenses/situations/projects/wording that require that they be put in LICENSE/NOTICE files and not. It seems to be a common sticking point on this list for incubator projects. I would put up a patch for the website but obviously I am still learning. On Tue, Oct 27, 2009 at 2:37 PM, Leo Simons m...@leosimons.com wrote: On Tue, Oct 27, 2009 at 4:45 PM, Bryant Luk bryant@gmail.com wrote: The source release has a LICENSE and a NOTICE file that indicates it contains a bunch of stuff it does not actually contain. AFAICS it should simply have a LICENSE that is just the Apache License and a NOTICE file that has just our standard license header. I think you're suggesting a different LICENSE/NOTICE for source versus binary distributions. Yep, I see how it looks like thatthough maybe I'm _really_ suggesting a source-only distribution :-) Look, the general rule is quite simple: LICENSE files MUST contain all the license information that applies to an artifact, and SHOULD contain only the license information that applies to that artifact. Similarly, NOTICE files MUST contain all the notices that apply to an artifact, and SHOULD contain only the notice information that applies to that artifact. Whenever you violate that SHOULD, you are turning lazyness/sloppiness into a mess for your users. For example, with this current wink distribution, you are (appear to be?) passing on a lot of CDDL obligations down to wink users, which is annoying to users that care about such things. If all your user wants to do is copy/paste the glue code from GzipHandler, that's a rather heavy license to wade through. Similarly, that user of that GzipHandler code now has to copy/paste the entire contents of the NOTICE file. Do you really want to place a burden on your users like that? I wouldn't, however just out of curiosity, how does this apply with Section 4.4 of the Apache license? If the Work includes a NOTICE text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works;... I would consider that a copied portion of just the Apache Wink code to be a Derivative Work, and none of the other NOTICE attributions (CDDL) apply to the user (hence excluding those notices so their NOTICE file is relatively brief). I'm not a lawyer but just want some clarification for this use case for personal knowledge. I did some random checking looking at some source versus binary Apache project distributions (incubator and non-incubator) and as far as I can tell, they kept their same LICENSE and NOTICE files even though they were not re-distributing the dependency binaries in the source archive. Don't mean to say we should just follow the crowd, but I don't think this is standard practice unless another thread has a viewpoint on this. Unfortunately, most apache projects are not as good at following policies as they should be, and most engineers (including me! :-) ) are not nearly as good at applying legal rules and guidelines as they should be. Agreed. http://www.apache.org/dev/release.html#license What Are The Requirements To Distribute Other Artifacts In Addition To The Source Package? ... Nothing in this section is meant to supersede the requirements defined here and here that all releases be primarily based on a signed source package. The NOTICE file for the binary release should include only those notices that are actually required by the included library dependencies, and they should reproduce the exact text of those notices. For example, the slf4j notice line should not be there since slf4j does not require it. I see varying degrees of attribution to slf4j in other Apache (incubating and non-incubating) projects (some have none, some have a line). The slf4j line was kept from the Wink 0.1 release. IMHO, this is not a release blocker, but we can remove it in a future release if it is the right thing to do. Fortunately we have quite a clear rule on this topic these days, so no opinions are necessary: http://www.apache.org/dev/release.html#notice-content What Content Is Appropriate For The NOTICE File? ... Only mandatory information required by the product's software licenses. Not suitable
Re: [VOTE] Accept Libcloud proposal for incubation
On Wed, Oct 28, 2009 at 6:39 PM, Paul Querna p...@querna.org wrote: Libcloud proposal thread went well, and we added several mentors. I would like to start the vote to incubate Libcloud into the ASF. The proposal is included below and is also at: http://wiki.apache.org/incubator/LibcloudProposal Please cast your votes: [ ] +1 Accept Libcloud for incubation [ ] +0 Indifferent to Libcloud incubation [ ] -1 Reject Libcloud for incubation +1 ...ant - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Wink 1.0 (RC-5)
Looks good to me +1 ...ant On Mon, Nov 9, 2009 at 2:23 PM, Nicholas L Gallardo nlgal...@us.ibm.comwrote: Thanks Leo, your input is much appreciated. In addition to this +1, we received a +1 from Kevan Miller in the Wink community vote. Is that vote transportable here? If so, then we just need one more +1 to release as the vote has already been open for 72 hours. Nicholas Gallardo WebSphere - REST WebServices Development nlgal...@us.ibm.com Phone: 512-286-6258 Building: 903 / 5G-016 [image: Inactive hide details for Leo Simons ---11/09/2009 06:38:57 AM---+1 from me!]Leo Simons ---11/09/2009 06:38:57 AM---+1 from me! *Leo Simons m...@leosimons.com* 11/09/2009 06:38 AM Please respond to general@incubator.apache.org To general@incubator.apache.org cc Subject Re: [VOTE] Release Wink 1.0 (RC-5) +1 from me! cheers, Leo On Thu, Nov 5, 2009 at 3:53 PM, Nicholas Gallardo nickgalla...@yahoo.com wrote: The Wink community has voted on and approved the release of Wink 1.0 (RC-5). We would now like to request the approval of the Incubator PMC for this release. Details of the Wink community vote can be found here: http://n2.nabble.com/VOTE-Release-Wink-1-0-RC-5-td3936613.html#a3936613 The Maven staging area is at: https://repository.apache.org/content/repositories/orgapachewink-011/ The distributions are in: https://repository.apache.org/content/repositories/orgapachewink-011/org/apache/wink/apache-wink/1.0-incubating/ This release is tagged at: https://svn.apache.org/repos/asf/incubator/wink/tags/wink-1.0-incubating/ (revision 832289) The vote will be open here for at least 72 hours. Regards, -Nick - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Wink 1.0 (RC-5)
Yep, I agree with what Kevan just said, so you're good to go now. ...ant On Mon, Nov 9, 2009 at 2:45 PM, Nicholas L Gallardo nlgal...@us.ibm.comwrote: Thanks Ant. Do you have any input on the question below? Is that vote [mentor/IPMC member] transportable here? Nicholas Gallardo WebSphere - REST WebServices Development nlgal...@us.ibm.com Phone: 512-286-6258 Building: 903 / 5G-016 [image: Inactive hide details for ant elder ---11/09/2009 08:43:50 AM---Looks good to me +1]ant elder ---11/09/2009 08:43:50 AM---Looks good to me +1 *ant elder ant.el...@gmail.com* 11/09/2009 08:42 AM Please respond to general@incubator.apache.org To general@incubator.apache.org cc Subject Re: [VOTE] Release Wink 1.0 (RC-5) Looks good to me +1 ...ant On Mon, Nov 9, 2009 at 2:23 PM, Nicholas L Gallardo nlgal...@us.ibm.com wrote: Thanks Leo, your input is much appreciated. In addition to this +1, we received a +1 from Kevan Miller in the Wink community vote. Is that vote transportable here? If so, then we just need one more +1 to release as the vote has already been open for 72 hours. Nicholas Gallardo WebSphere - REST WebServices Development nlgal...@us.ibm.com Phone: 512-286-6258 Building: 903 / 5G-016 [image: Inactive hide details for Leo Simons ---11/09/2009 06:38:57 AM---+1 from me!]Leo Simons ---11/09/2009 06:38:57 AM---+1 from me! *Leo Simons m...@leosimons.com* 11/09/2009 06:38 AM Please respond to general@incubator.apache.org To general@incubator.apache.org cc Subject Re: [VOTE] Release Wink 1.0 (RC-5) +1 from me! cheers, Leo On Thu, Nov 5, 2009 at 3:53 PM, Nicholas Gallardo nickgalla...@yahoo.com wrote: The Wink community has voted on and approved the release of Wink 1.0 (RC-5). We would now like to request the approval of the Incubator PMC for this release. Details of the Wink community vote can be found here: http://n2.nabble.com/VOTE-Release-Wink-1-0-RC-5-td3936613.html#a3936613 The Maven staging area is at: https://repository.apache.org/content/repositories/orgapachewink-011/ The distributions are in: https://repository.apache.org/content/repositories/orgapachewink-011/org/apache/wink/apache-wink/1.0-incubating/ This release is tagged at: https://svn.apache.org/repos/asf/incubator/wink/tags/wink-1.0-incubating/ (revision 832289) The vote will be open here for at least 72 hours. Regards, -Nick - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Request for Waiver of Make a Release requirement for Incubator graduation
On Tue, Nov 10, 2009 at 6:17 PM, Greg Stein gst...@gmail.com wrote: Hello IPMC, The Subversion podling would like a waiver of the requirement to make a release before graduation. As we understand this requirement, it is present in order to demonstrate to the podling how releases are made at the ASF. Packaging, licensing, signing, placement into the distrubtion/mirror system, announcements, among others[1]. We believe that the Subversion community already has a deep understanding of the Apache release model, based on the following qualifications of several of its committers/mentors: * Greg Stein has been a committer at Apache since before the Foundation was started. He has been involved in releases of httpd and APR, including time as Release Manager (RM) for APR. He helped to establish the APR TLP and the Commons TLP (prior incarnation; now defunct). Greg wrote the versioning guidelines for APR, which are also in use by the Subversion project. Through his 8+ years on the Board, he has read and reviewed reports from across the ASF about release, IP, and infrastructure issues. * Justin Erenkrantz has been a committer since 2001, contributing to httpd and APR, along with mentoring the stdcxx project when it was in the Incubator. He has been the RM for both httpd and APR. In fact, Justin wrote the initial guidelines for the release of httpd. Justin has been part of Infrastructure almost since its inception as a distinct group, which includes the provision of all the facilities to actually make and distribute ASF releases. Justin has spent many years on the Board, providing further insight to releases across the Foundation. * Sander Striker has been a committer since 2001, contributing to APR and then httpd. Sander acted as the RM for httpd releases, and also held a stint as the VP for httpd. Add in his time spent with Infrastructure and the Board, and he's been observing ASF releases for many years. * Garrett Rooney has been a committer since 2004, contributing and making releases of APR, and committing to httpd. He was also the VP of APR for several years, and has mentored two Incubating projects. * Daniel Rall has been a committer since 2001, contributing to many projects: Turbine, Fulcrum, Torque, and numerous Jakarta Commons projects. He established the community around XML-RPC, brought it through the Incubator, and maintained it for several years within the XML Project. He also participated in some of the bootstrapping around the Velocity and Maven prtingojects, and participated on the Infra team. The Subversion community's belief is that we have ample experience to guide us in making a release, when that time is arrives. There will certainly be variances (e.g. mirroring) from our current established procedures[2], but some simple fine-tuning should resolve that. The bulk of the existing release process already meets and exceeds that a typical Apache release. Niclas Hedman pointed out that the Subversion community has produced 32 releases over the past four years, which hopefully indicates a smooth, understood, and functional release process. Cheers, -g [1] one particular item is using a release as a gating/focal point for legal review, but we feel that can be performed as an action separate/distinct from performing a release [2] http://subversion.tigris.org/release-process.html -0 I'm not at all familiar with how the Subversion project works so as an IPMC member I don't see how I can decide this before they've even started incubating. This is a graduation issue, why can't it just wait until then and say in the graduation proposal there's not been a release but its not necessary because of x y z. ...ant - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Review-Then-Commit
On Wed, Nov 11, 2009 at 4:31 PM, Daniel Kulp dk...@apache.org wrote: As Martijn alluded to, I think we'd need some more context as to why and how they use RTC. This appears to be where it came from: http://markmail.org/message/d45dmasuwnda25wd so about 6 months ago to try to help with problems they were having, and since then 99% of the commits have been made by only two people. ...ant - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Review-Then-Commit
I agree with that. And before graduation I think it might be worth trying to get CTR used more, they do seem open this - http://markmail.org/message/i255ekzxpuesow44 ...ant On Thu, Nov 12, 2009 at 3:16 AM, Greg Stein gst...@gmail.com wrote: Not a strong opinion, but I think that RTC hampers the free-flow of ideas, experimentation, evolution, and creativity. It is a damper on expressivity. You maneuver bureaucracy to get a change in. CTR is about making a change and discussing it. But you get *forward progress*. I also feel that RTC will tend towards *exclusivity* rather than the Apache ideal of *inclusivity*. That initial review is a social and mental burden for new committers. People are afraid enough of submitting patches and trying to join into a development community, without making them run through a front-loaded process. I've participated in both styles of development. RTC is *stifling*. I would never want to see that in any Apache community for its routine development (branch releases are another matter). My opinion is that it is very unfortunate that Cassandra feels that it cannot trust its developers with a CTR model, and pushes RTC as its methodology. The group-mind smashes down the creativity of the individual, excited, free-thinking contributor. Cheers, -g On Wed, Nov 11, 2009 at 11:09, Matthieu Riou matth...@offthelip.org wrote: Hi guys, What's the take of other mentors and the IPMC on podlings practicing RTC? I'm asking because some seem to see it as a blocker for graduation whereas I see it much more as a development methodology with little community impact and therefore no real influence on graduation. Strong opinions here? Thanks, Matthieu - 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: Review-Then-Commit
On Thu, Nov 12, 2009 at 4:12 PM, Eric Evans eev...@rackspace.com wrote: On Thu, 2009-11-12 at 07:16 +, ant elder wrote: so about 6 months ago to try to help with problems they were having, and since then 99% of the commits have been made by only two people. I assume you're referring to Jonathan Ellis and myself, and I'm not sure that's exactly fair. There are only 4 active committers, and of the 4, Jonathan and I spend the most time committing patches contributed by people who can't, and quite often the review was conducted by someone else who doesn't have commit rights and we are simply acting as a proxy. This results in a lot of svn commits made by us, for contributions that are not technically ours. As a convention, we typically put something like Patch by $author; reviewed by $reviewer for $issue_id in the change description. I just went through the commits scraping out those messages and it looks like Jonathan and I account for a little more than 60%, not 99%. -- Eric Evans eev...@rackspace.com So about 40% of the committed code is coming from others and reviewed by others - great - why not make some of those others committers? ...ant - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Review-Then-Commit
On Thu, Nov 12, 2009 at 4:36 PM, Jonathan Ellis jbel...@gmail.com wrote: On Thu, Nov 12, 2009 at 10:24 AM, ant elder ant.el...@gmail.com wrote: So about 40% of the committed code is coming from others and reviewed by others - great - why not make some of those others committers? It's a long tail sort of thing. We follow the convention Johan suggested of assigning the Jira issue to the author of the change, so e.g. for 05 the contributions look like this: https://issues.apache.org/jira/secure/ConfigureReport.jspa?versionId=12314040issueStatus=allselectedProjectId=12310865reportKey=com.sourcelabs.jira.plugin.report.contributions%3AcontributionreportNext=Next That JIRA report shows a range of contributors that many TLPs would be envious of, and it shows a quite different picture from the commit history, eg: http://www.svnsearch.org/svnsearch/repos/ASF/search?from=20090801to=20091231path=%2Fincubator%2Fcassandra It would be great to get more of those contributors actually doing the commits though, maybe modifying the current commit process as is being suggested in this thread could help get that to happen. ...ant - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] release Apache VCL 2.1
On Mon, Nov 23, 2009 at 5:02 PM, Kevan Miller kevan.mil...@gmail.com wrote: On Nov 23, 2009, at 11:10 AM, sebb wrote: On 23/11/2009, Andrus Adamchik and...@objectstyle.org wrote: On Nov 23, 2009, at 5:49 PM, sebb wrote: There is only a bz2 archive. Normally projects release archives in zip andr tar.gz format which are more commonly supported. IMO, this is a release blocker Just curious why you think this is a blocker? Each project knows better what formats are common and acceptable in the target user community. There's no single distribution format and this is not a blocker IMO. The project OS targets include Windows, which does not support BZ2 natively by default, whereas Windows does now support Zip archives. AFAIK, all other ASF releases use both tar.gz and zip archives. Personally, I don't see how this is a blocking issue. It is unusual. However, I leave it up to the VCL community to decide what archive format is meeting the needs of their users. I agree with that, maybe it would be worth looking at having tar.gz and zips in later releases but this doesn't seem to me like a blocker for this one. I've reviewed the release artifacts and they look ok to me so +1 on the release. ...ant - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept Apache Clerezza into the incubator
+1 ...ant On Mon, Nov 23, 2009 at 6:32 PM, Reto Bachmann-Gmür reto.bachm...@trialox.org wrote: Please vote on accepting Apache Clerezza for incubation at the Apache Incubator. The full proposal is available at the end of this message and as a wiki page at http://wiki.apache.org/incubator/ClerezzaProposal http://wiki.apache.org/incubator/AceProposal. We ask the Incubator PMC to sponsor it, with Bertrand as the Champion, and Gianugo, Niclas, Ross, Karl and Reinhard volunteering to be Mentors. Please cast your votes: [ ] +1, bring Clerezza into Incubator [ ] +0, I don't care either way, [ ] -1, do not bring Clerezza into Incubator, because... The vote is open for the next 72 hours and only votes from the Incubator PMC are binding. - - - - - - - - - - Abstract Clerezza is an OSGi-based modular application and set of components (bundles) for building RESTFul Semantic Web applications and services. Proposal Clerezza can be used as a platform providing all the compile and runtime requirement for building semantic applications, or used as individual bundles within an OSGi framework, e.g. Apache Sling, Apache ServiceMix, or the Eclipse platform. Clerezza provides: * An API modeling the W3C RDF standard without any vendor specific additions. * Adapter for various triple stores including Sesame, Jena TDB, and Mulgara. * Front-End adaptors, currently to run applications written against the Jena API. Support for RDF2Go is planned. * A JAX-RS implementation designed to work in an OSGi environment and allowing to provide Root-Resources as OSGi services. * Web access to RDF graphs, including a SPARQL-Endpoint. * Extensions to JAX-RS allowing to bind Root-Resource classes to specific RDF-Types rather than to URI-Paths. * Templating mechanism (Renderlets) allowing to render RDF resources returned by JAX-RS resource methods to various formats * Support for Scala for writing modules, ScalaServerPages to easily write renderlets, DSL for accessing graphs. * Authentication and authorization based on JAAS and OSGi Conditional Permission Admin * Support for user bundles: Users can have a permission to upload their own sandboxed bundles. The URI space these bundles are allowed to register their JAX-RS resources can be limited with a prefix. * Scripting: Scripting based on javax.script (currently support for JRuby and Scala) * Documentation: Bundles can provide their documentation in RDF. These are used for online documentation as well as for building Maven sites (with a Maven reporting plugin) The RDF abstraction layer can be used independently of other aspects of Clerezza. It allows applications to be written regardless the used backend. In its purpose, it is similar to RDF2Go, but provides a significantly more modular interface allowing e.g. to independently switch the storage, querying, or serialization layer. Furthermore, it doesn't introduce concepts alien to the RDF model such as blank node labels, but is in its core strictly limited to RDF semantics. The JAX-RS implementation can also be used independently of any other components. It allows OSGi services to provide a RESTful interface to their methods. By being based on wymiwyg WRHAPI, it can run both on the default OSGi Web Service as well as on a jetty instance listening on a different port. Background The current web trends focusing on information sharing, interoperability and collaboration. Therefore the behaviour of the end-user has changed over the last years: end-users not only consuming information they also producing content anytime anywhere - in contrast to non-interactive websites where users are limited to the passive viewing of information that is provided to them. Since the end-users are sensitized to the possibilities of the web the web application requirements increases. Examples of such applications are social-networking sites, wikis, blogs and mashups. The REST paradigm and Semantic Web technologies support these trends and form the basis for the upcoming Web of Data (a.k.a. linked data, Web 3.0). They change the paradigms for developing complex Web applications. Clerezza allows to develop applications that integrate perfectly in the Semantic Web providing all accessible resources in machine understandable formats without imposing additional burdens on the developer. Additionally, thanks to the flexibility of the RDF model used as back-end, some tedious database related tasks required for traditional Web application development are no longer needed. Rationale Most Web application framework are not designed to leverage the full power of HTTP but often try to reproduce non Web design patterns for the Web environment. In general, application frameworks are oriented towards relational or hierarchical data structures. While attempts to overcome this such as Drupal have become very popular, they do not at their core
Re: Where to add PPMC member additions?
I'm not sure I've ever seen PPMC members listed anywhere, the only way i've found them is from the subscribers to the poddlings private list. ...ant On Wed, Nov 25, 2009 at 7:02 PM, Paul Querna p...@querna.org wrote: ping? anyone know the answer? I can't find the file referenced, nor can I find any other file where PPMCs are supposed to keep their list updated? On Mon, Nov 16, 2009 at 2:52 PM, Leif Hedstrom zw...@apache.org wrote: Hi, reading http://incubator.apache.org/guides/ppmc.html, it says (towards the end) to add new PPMC members to this SVN file: https://svn.apache.org/repos/private/committers/board/incubator-info.txt but, I get a 404 not found on that URL. Where do I add new PPMC members for our project (Traffic Server) ? I'll update our incubator page with the committer additions we're making, but I want to make sure I update everything as required here. Thanks, -- leif - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] release cassandra 0.5.0-beta1
On Mon, Nov 23, 2009 at 6:40 PM, Eric Evans eev...@rackspace.com wrote: The Cassandra community voted on and approved the release of Apache Cassandra 0.5.0-beta1. We would now like to request the approval of the Incubator PMC for this release. Cassandra is a massively scalable, eventually consistent, distributed, structured key-value store. Podling vote thread: http://thread.gmane.org/gmane.comp.db.cassandra.devel/586 0.5.0-beta1 artifacts: http://people.apache.org/~eevans SVN tag: https://svn.apache.org/repos/asf/incubator/cassandra/tags/cassandra-0.5.0-beta1 Project home: http://incubator.apache.org/cassandra/ Incubation status: http://incubator.apache.org/projects/cassandra.html We received one binding vote during the poddling vote, so we'll need 2 more. Any help with reviewing/voting from outside our mentors list would be appreciated. The vote will remain open for 72 hours (or longer if needed). Regards, -- Eric Evans eev...@rackspace.com +1 ...ant - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release RC3 as Log4PHP 2.0.0
On Sat, Dec 5, 2009 at 7:06 PM, Curt Arnold carn...@apache.org wrote: The log4php PPMC vote was opened on log4php-dev at Nov 27, 2009 and closed at Dec 4, 2009. Binding +1 votes were received from Christian Grobmeier, Christian Hammers and Curt Arnold. No other votes were received. The link in the original thread ends at the end of November. The PPMC release vote thread continues http://mail-archives.apache.org/mod_mbox/incubator-general/200912.mbox/%3cded132f10912050048u695e1353ta29b54a39e620...@mail.gmail.com%3e I did raise a concern on a previous RC that the phpdoc generated documentation does not have an ASF source header notice, but http://incubator.apache.org/guides/releasemanagement.html#notes-license-headers implied that it may not be a hard requirement. I would encourage any PHP developers to double check the PEAR packaging and particularly in terms of consistency with other Apache PHP projects. On Dec 5, 2009, at 2:48 AM, Christian Grobmeier wrote: Dear Incubator PMC, the Log4PHP has voted with 3x +1 for releasing RC3 as Log4PHP 2.0.0 (please see below). The original vote message can be found: http://mail-archives.apache.org/mod_mbox/logging-log4php-dev/200911.mbox/%3cded132f10911262256j12c0cfej21e7e5dbdcf18...@mail.gmail.com%3e Message ID is: ded132f10911262256j12c0cfej21e7e5dbdcf18bf7 We kindly ask the incubator PMC to vote on our artifacts too: [ ] +1 Yes go ahead and release the artifacts [ ] -1 No, because... Thanks, Christian - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org +1 Note that the date in the NOTICE files is 2004-2007. There was a long discussion on the date format on legal-discuss not so long ago and from what i recall this is not a release blocker. Also there's a bunch of html files in docs\log4php that don't have an Apache License header, it wasn't obvious if they are generated or not but it could be worth seeing if the header can be added to them. ...ant - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] release cassandra 0.5.0-beta2
+1 ...ant On Thu, Dec 10, 2009 at 4:23 PM, Eric Evans eev...@rackspace.com wrote: The Cassandra community voted on and approved the release of Apache Cassandra 0.5.0-beta2. We would now like to request the approval of the Incubator PMC for this release. Cassandra is a massively scalable, eventually consistent, distributed, structured key-value store. Podling vote thread: http://thread.gmane.org/gmane.comp.db.cassandra.devel/696 0.5.0-beta2 artifacts: http://people.apache.org/~eevans SVN tag: https://svn.apache.org/repos/asf/incubator/cassandra/tags/cassandra-0.5.0-beta2 Project home: http://incubator.apache.org/cassandra/ Incubation status: http://incubator.apache.org/projects/cassandra.html We received two binding votes[1][2] during the poddling vote, so we'll need 1 more. Any help with reviewing/voting from outside our mentors list would be appreciated. The vote will remain open for 72 hours (or longer if needed). Regards, [1] http://article.gmane.org/gmane.comp.db.cassandra.devel/700 [2] http://article.gmane.org/gmane.comp.db.cassandra.devel/702 -- Eric Evans eev...@rackspace.com - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Validation incubator for JSR-303 Bean Validation
A quick search so there has been some discussion on commons-dev - [1] Does this really need to be incubated - the proposal says its intended to graduate to Apache Commons and replace the existing Validator 1.x component as a new 2.0 codebase, from the discussion on commons-dev everyone seems fine with that out come, and only 2 of the 7 proposed committers are not existing Validator or ASF committers - so couldn't this just go straight to commons as a code grant and make the two new guys committers in recognition of contibuting the new code? ...ant [1] http://apache.markmail.org/search/?q=jsr+303+list%3Aorg.apache.commons.dev#query:jsr%20303%20list%3Aorg.apache.commons.dev%20order%3Adate-backward+page:1+state:facets On Fri, Dec 11, 2009 at 7:06 AM, Matthias Wessendorf mat...@apache.org wrote: Hi, what about the effort from the Jakarta/Commons Validator community? Aren't they doing that as well ? (or was it only stated to do so)? -Matthias On Fri, Dec 11, 2009 at 2:14 AM, Donald Woods dwo...@apache.org wrote: Hello everyone, I would like to present an incubator proposal for a new Validation podling, which would be a JSR-303 Bean Validation follow-on to the existing Apache Commons Validation 1.x project, but based on a new incoming codebase with a software grant from Agimatec GmbH. The proposal is available on the wiki at: http://wiki.apache.org/incubator/ValidationProposal We're looking forward to your feedback and interest in anyone wanting to join and help out on the project. Thanks, Donald - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Validation incubator for JSR-303 Bean Validation
On Fri, Dec 11, 2009 at 9:56 AM, Niall Pemberton niall.pember...@gmail.com wrote: On Fri, Dec 11, 2009 at 7:56 AM, ant elder ant.el...@gmail.com wrote: A quick search so there has been some discussion on commons-dev - [1] Does this really need to be incubated - the proposal says its intended to graduate to Apache Commons and replace the existing Validator 1.x component as a new 2.0 codebase, from the discussion on commons-dev everyone seems fine with that out come, and only 2 of the 7 proposed committers are not existing Validator or ASF committers - so couldn't this just go straight to commons as a code grant and make the two new guys committers in recognition of contibuting the new code? I raised this on priv...@commons and reported back to d...@commons on that discussion here: http://markmail.org/message/lkyjl6gaxawspgdt In summary though, there was very little support to go that route and some objections. All commons components share the same set of mailing lists which makes it easier for PMC members to provide oversight for the 30+ components that live there. As part of this proposal we want to use the commons mailing lists for commits and discussion so that by the time this podling is ready to graduate the new committers and Commons PMC will have a better knowledge of each other and there will be no issue with voting in the new committers. The use of the commons mailing lists is in the proposal and was part of the vote held on d...@commons to sponsor this incubation effort: http://markmail.org/message/mqdft736b5vasezs Niall From the first email referenced was Roman ever asked if he'd mind submitting patches for a while to earn Karma if the code did go straight to commons? Seems a bit a of a shame to need to go the whole incubation process just for one commit access. Re the the poddling use the existing commons mailing lists its may be worth pointing out this recent thread: http://apache.markmail.org/message/ifinvq7wqmeoo5ix ...ant - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Thrift 0.2.0
On Fri, Dec 11, 2009 at 2:17 AM, Todd Lipcon t...@cloudera.com wrote: Hi Kevan, Responses below: On Thu, Dec 10, 2009 at 1:24 PM, Kevan Miller kevan.mil...@gmail.com wrote: What's the license for the file: doc/thrift.tex? This was contributed by Facebook, and thus falls under the Facebook CLA as Apache 2.0 licensed. I'm not sure how it got missed in the license audit, but since it's only part of the source tree, doesn't link with anything (solely documentation), and actually doesn't get installed by make install, is it a release blocker? (ie do I need to roll an rc1 and call a new vote on thrift-dev, or can I just fix it in svn for next release?) I think its ok to add that header later, and the rest of it looks ok to me so +1 from me. ...ant - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Cassandra PPMC?
On Sat, Dec 12, 2009 at 11:38 AM, Bertrand Delacretaz bdelacre...@apache.org wrote: On Sat, Dec 12, 2009 at 5:27 AM, Matthieu Riou matthieu.r...@gmail.com wrote: ...Podlings PPMCs are reflected somewhere in asf-authorization? How so? In any case Eric is part of the Cassandra PPMC and I can co-sign if necessary Is there a public list of PPMC members somewhere? I haven't found it at either http://incubator.apache.org/projects/cassandra.html or http://incubator.apache.org/cassandra/ -Bertrand The PPMC is a bit of an artificial construct so AFAIK there is no place where PPMC membership is recorded, usually the only record of it is in the poddlings private list archive. The list of subscribers to the private list gives an indication though there'll also be all the mentors and possibly other ASF members included in that list that need to be sifted through. ...ant - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] OpenCMIS incubator for Content Mangement Interoperability Services (CMIS)
On Sun, Dec 13, 2009 at 2:42 AM, Niclas Hedhman nic...@hedhman.org wrote: The Board has in the past condemned balkanization of community, and my take on this situation is exactly that. This is not yet another web framework, which often brought forward as examples that the ASF encourages competition within. Those typically have a different angle, approach or metaphor, something making each very different beasts. But in this case we are talking about the same spec. There is no real distinguishing features and huge overlap of commonality. I think this is a NIH-syndrome in play, in the best case oh we have the code working already and the worst case we don't like to collaborate with them, and there is reason to think that that goes for both sides of the fence. I want to see Chemistry capable to absorb such contribution and collaborate heavily to bring such codebase in. And I want to see the people of the OpenCMIS proposal to show that they indeed can work with others. Exactly how the merged community goes about with the technical integration is its own business, but I am worried that the new codebase will not receive the welcome I hope, the Chemistry base will dominate, and the OpenCMIS proposer get fed up and leaves. Important Mentors understand the risks here, and keep eyes extra open for attrition, domination and forceful consensus-seeking. I agree with those sentiments. I think discussion should continue on Chemistry dev@ list. If agreement can't be reached there, then I am NOT in favor of incubating OpenCMIS separately and will vote -1 to such proposal. I will also form myself an opinion of how well Chemistry is trying to collaborate, and it may improve or deteriorate its status with me. I don't think it would be helpful for either OpenCMIS or Chemistry for the IPMC to just unilaterally dictate that it must be done in Chemistry. IMHO that would make for too unlevel a playing field which could adversely impact any attempts to collaborate (or even just get stuff done). That works both ways - it would be hard for OpenCMIS being forced to be part of Chemistry, but also potentially hard for Chemistry to all of a sudden have a significant number of new committers forced upon them and upsetting the status quo. The Incubator has always been very clear about having a very low bar of entry to incubation so IMHO it shouldn't matter that the incoming podling is doing the same spec as another poddling, thats something that could be worked out during incubation. So I'd +1 accepting this new OpenCMIS proposal (if they can find champion and mentors). If we're really concerned about having multiple spec impls then we can make this a graduation requirement - neither Chemistry or OpenCMIS graduate until they've both worked out how to exist together. This can become an excellent opportunity for all involved to show off their ApacheWay skills +1! -- Niclas - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] release cassandra 0.5.0-rc1
+1 ...ant On Mon, Dec 28, 2009 at 5:29 PM, Eric Evans eev...@rackspace.com wrote: The Cassandra community voted on and approved the release of Apache Cassandra 0.5.0-rc1. We would now like to request the approval of the Incubator PMC for this release. Cassandra is a massively scalable, eventually consistent, distributed, structured key-value store. Podling vote thread: http://thread.gmane.org/gmane.comp.db.cassandra.devel/728 0.5.0-rc1 artifacts: http://people.apache.org/~eevans SVN tag: https://svn.apache.org/repos/asf/incubator/cassandra/tags/cassandra-0.5.0-rc1 Project home: http://incubator.apache.org/cassandra/ Incubation status: http://incubator.apache.org/projects/cassandra.html We received only one (IPMC )binding vote[1] during the poddling vote, so we'll need two more. Any help with reviewing/voting from outside our mentors list would be appreciated. The vote will remain open for 72 hours (or longer if needed). Regards, [1] http://article.gmane.org/gmane.comp.db.cassandra.devel/734 -- Eric Evans eev...@rackspace.com - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Validation incubator for JSR-303 Bean Validation
On Wed, Dec 30, 2009 at 9:55 PM, Niall Pemberton niall.pember...@gmail.com wrote: This is not quite the scenario. We have a *dormant* component (validator) in Commons and a couple of ASF committers (not commons committers) have shown up proposing to re-write that component to implement the new Bean Valiadation specification. Recently one of those committers proposed adopting this existing code-base written by someone else which is already 80% complete. I was the last active committer on the Commons Validator component and all I'm trying to do is facilitate those that want to revive it and bring in the new code base. So its more a case of other people think Commons would be an appropriate home - so far none of the existing Commons committers has shown any interest in the codebase. Personally my interest in helping make this happen though is now dying 'coz this is way too painful. It doesn't have to be painful. This thread has been running a few weeks now if it really is wanted to be done in the Incubator just call a vote on that now. The champion and mentors are Incubator PMC members so it'll likely get enough +1s (though the vote might go more smoothly if the part about using the commons mailing lists is removed). The Commons PMC is effectively saying we don't want to take responsibility and giving it to the Incubator PMC who from the comments on this thread will likely think its ready to graduate almost immediately so can vote to graduate it at the earliest opportunity and give it right back to Commons. Making work for ourselves but so be it. It doesnt look like theres been any comments about this on commons dev or private since the proposal was submitted to the Incubator so it may be worth first asking there again if they'd review this thread and reconsider not doing it via the software grant route. ...ant - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] release cassandra 0.5.0-rc3
+1 ...ant On Thu, Jan 7, 2010 at 5:26 PM, Eric Evans eev...@rackspace.com wrote: The Cassandra community voted on and approved the release of Apache Cassandra 0.5.0-rc3. We would now like to request the approval of the Incubator PMC for this release. Cassandra is a massively scalable, eventually consistent, distributed, structured key-value store. Podling vote thread: http://thread.gmane.org/gmane.comp.db.cassandra.devel/764 0.5.0-rc3 artifacts: http://people.apache.org/~eevans SVN tag: https://svn.apache.org/repos/asf/incubator/cassandra/tags/cassandra-0.5.0-rc3 Project home: http://incubator.apache.org/cassandra/ Incubation status: http://incubator.apache.org/projects/cassandra.html We received one (IPMC )binding vote[1] during the poddling vote, so we'll need at least a couple more here. The vote will remain open for 72 hours (or longer if needed). Regards, [1] http://article.gmane.org/gmane.comp.db.cassandra.devel/766 -- Eric Evans eev...@rackspace.com - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Olio 0.2
+1 The Java src archive seems to include some of the binary artifacts (eg webapp.war), the license/notice covers everything so its not an issue just pointing it out in case its not intentional. ...ant On Mon, Jan 11, 2010 at 10:52 PM, Shanti Subramanyam shanti.subraman...@gmail.com wrote: A reminder to please take a look at the Olio release and Vote. Thanks Shanti -- Forwarded message -- From: Shanti Subramanyam shanti.subraman...@sun.com Date: Tue, Jan 5, 2010 at 5:39 PM Subject: [VOTE] Release Olio 0.2 To: general@incubator.apache.org The Olio community has voted to release Olio 0.2. We now request the Incubator PMC for a vote. The proposed release artifacts are located at http://people.apache.org/~shanti/olio_0.2. There are 3 versions (PHP, Rails and Java) in both binary and source formats. Each package is available in both tar and zip format and include asc and md5 checksums. The file names should be self-explanatory. The rat outputs are in *rat-0.2.out. The link to the voting thread can be found here : http://mail-archives.apache.org/mod_mbox/incubator-olio-dev/200912.mbox/browser Please do review the artifacts and we would appreciate it if you could cast your vote by Jan 12. Thanks in advance Shanti - 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: Fw: [VOTE] Imperius 1.0.0 rc6
+1 ...ant On Tue, Jan 12, 2010 at 3:30 PM, Neeraj Joshi jnee...@us.ibm.com wrote: Hi All, We still need two more binding votes for our first release. Would really appreciate it if anyone can take some time to review our release. Thanks Neeraj ~ It is hard enough to remember my opinions, without also remembering my reasons for them. -Friedrich Wilhelm Nietzsche Neeraj Joshi (knee-rudge) Apache Imperius - http://incubator.apache.org/imperius ~ - Forwarded by Neeraj Joshi/Durham/IBM on 01/12/2010 10:28 AM - From: Neeraj Joshi/Durham/i...@ibmus To: general@incubator.apache.org Date: 12/14/2009 04:43 PM Subject: [VOTE] Imperius 1.0.0 rc6 The Imperius community voted on and approved the release of Apache Imperius 1.0.0. We would now like to request the approval of the Incubator PMC for this release. Imperius is a rule-based policy evaluation engine based on the CIM-SPL language from Distributed Management Task Force (dtmf.org). The Imperius 1.0.0 RC6 release candidate has been tagged, packaged, and is ready for a vote. The artifacts, KEYS file, RAT report and release notes can be found at http://people.apache.org/~jneeraj/apache-imperius-1.0.0-rc6/ The tag from which the release artifacts were generated can be found at http://svn.apache.org/repos/asf/incubator/imperius/tags/release1.0.0rc6/ Revision no is 887217 In addition, my PGP public code signing key can be found at the MIT key server (http://pgp.mit.edu/) The KEYS file is checked in at http://svn.apache.org.repos/asf/incubator/imperius/KEYS Please vote to publish this release by Tuesday, Dec 17 18:00 EST., please include the testing you performed to arrive at your vote [ ] +1 Publish [ ] 0 Abstain [ ] -1 Don't publish, because... Below is a summary of the vote on the Imperius mailing list (and further below is the original vote email) Thanks Neeraj ~ Neeraj Joshi (knee-rudge) IBM WebSphere ComputeGrid Apache Imperius - http://incubator.apache.org/imperius ~ From: Neeraj Joshi/Durham/i...@ibmus To: imperius-...@incubator.apache.org Date: 12/14/2009 03:45 PM Subject: [VOTE][RESULT] Imperius 1.0.0 rc6 Hello All, Voting on the Imperius 1.0.0rc6 candidate release has concluded Results: 1 binding +1 vote 6 non-binding +1 votes Kevan Miller(*) +1 David Kaminsky +1 David Wood +1 Mark Carlson +1 Erik Bengston +1 Xiping Wang +1 Jorge Lobo +1 Comments received: 1. Comments from Erik Bengston - In the zip/tar file we have a /log.txt file that should be removed. - Inside the jars we have a /META-INF/maven that should be removed too. - imperius-splcore-1.0.0.jar does not have NOTICE.txt and LICENSE.txt - IMO, the lib/javaspl-samples-1.0.0.jar should be moved to samples/lib/javaspl-samples-1.0.0.jar - IMO, NOTICE.txt and LICENSE.txt files in jar files should lie in META-INF folder. It was concluded that it is too early to make all/any Apache Imperius artifacts available in the Maven repository The other issues did not violate Apache policies and would be accommodated in subsequent releases. 2. Comments from Kevan Miller I note that the source distribution contains the following file: imperius-cimsplclientsideprovider/customexpressions.properties which is not in the svn tag. The contents of this file are: SPL_CUSTOM_EXPRESSIONS SPL_CUSTOM_ACTIONS This file is innocuous and gets generated during JUnit testing I will now take this vote to the general mailing list for a final vote. We still need 2 +1 votes from IPMC members. Thanks Neeraj ~ Neeraj Joshi (knee-rudge) Apache Imperius - http://incubator.apache.org/imperius ~ From: Neeraj Joshi/Durham/i...@ibmus To: imperius-...@incubator.apache.org Date: 12/04/2009 10:06 AM Subject: [VOTE] Imperius 1.0.0 rc6 Hi All, The Imperius 1.0.0 RC6 release candidate has been tagged, packaged, and is ready for a vote. The artifacts, KEYS file, RAT report and release notes can be found at http://people.apache.org/~jneeraj/apache-imperius-1.0.0-rc6/ The tag from which the release artifacts were generated can be found at http://svn.apache.org/repos/asf/incubator/imperius/tags/release1.0.0rc6/ Revision no is 887217 In addition, my PGP public code signing key can be found at the MIT key server (http://pgp.mit.edu/) The KEYS file is checked in at http://svn.apache.org.repos/asf/incubator/imperius/KEYS Please vote to publish this release by Tuesday, Dec 08 18:00 EST., please include the testing you performed to arrive at your vote [ ] +1 Publish [ ] 0 Abstain [ ] -1 Don't publish, because... Upon a positive majority of binding votes and no binding
Re: [Discuss] Apache Shindig as a TLP
I had a quick look at things like mailing list activity, votes, releases, committers, commits etc, looks good to go to me. ...ant On Wed, Jan 13, 2010 at 7:41 PM, Upayavira u...@odoko.co.uk wrote: On Tue, 2010-01-12 at 12:04 -0500, Vincent Siveton wrote: Hi folks FYI, the Shindig community has successfully voted for graduation [1]. If no objection on the charter or other, I will start a formal acceptance vote soon. So, from the relative silence on this thread, I am assuming that everyone is quite happy to see Shindig graduate and that no-one has any issues... Regards, Upayavira - 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] Graduate Apache Shindig as an Apache Top Level Project
+1 ...ant On Thu, Jan 14, 2010 at 11:41 AM, Vincent Siveton vsive...@apache.org wrote: Hi, Thanks for the positive feedback on the proposal to graduate Shindig as a TLP [1]. I would like to start an official vote to recommend the graduation of Apache Shindig as a Top Level Project to the Board. To that end I have prepared the resolution for the Board below to be presented for consideration at the upcoming Board meeting. Community graduation vote thread: http://shindig-dev.markmail.org/message/c47amdxjtntkjij5 Please cast your vote: [ ] +1 to recommend Shindig's graduation [ ] 0 don't care [ ] -1 no, don't recommend yet, because ... The vote will be open for 72 hours. Cheers, Vincent [1] http://apache.markmail.org/message/qvpyymihv6gyh5a7 --- Begin Proposed Board Resolution --- WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project Management Committee, charged with the creation and maintenance of open-source software related to the implementation of an OpenSocial container and OpenSocial API specifications, for distribution at no charge to the public. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the Apache Shindig PMC, is hereby established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Shindig Project be and hereby is responsible for the creation and maintenance of software related to the OpenSocial API specifications, based on software licensed to the Foundation; and be it further RESOLVED, that the office of Vice President, Apache Shindig be and hereby is created, the person holding such office to serve at the direction of the Board of Directors as the chair of Apache Shindig, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Shindig PMC; and be it further RESOLVED, that the persons listed immediately below be and hereby are appointed to serve as the initial members of the Apache Shindig PMC: * Ian Boston (ieb at apache dot org) * Kevin Brown (etnu at apache dot org) * Chris Chabot(chabotc at apache dot org) * Chico Charlesworth (chico at apache dot org) * Cassie Doll (doll at apache dot org) * Evan Gilbert (evan at apache dot org) * John Hjelmstad (johnh at apache dot org) * Paul Lindner (lindner at apache dot org) * Daniel Peterson (dpeterson at apache dot org) * Louis Ryan (lryan at apache dot org) * Henning Schmiedehausen (henning at apache dot org) * Vincent Siveton (vsiveton at apache dot org) * Upayavira (upayavira at apache dot org) * Adam Winer (awiner at apache dot org) NOW, THEREFORE, BE IT FURTHER RESOLVED, that Paul Lindner be appointed to the office of Vice President, Apache Shindig, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed; and be it further RESOLVED, that Apache Shindig be and hereby is tasked with the migration and rationalization of the Apache Incubator Shindig podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator Shindig podling encumbered upon the Apache Incubator PMC are hereafter discharged. --- End Proposed Board Resolution --- - 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] Imperius 1.0.0 rc6
+1 ...ant On Mon, Dec 14, 2009 at 9:41 PM, Neeraj Joshi jnee...@us.ibm.com wrote: The Imperius community voted on and approved the release of Apache Imperius 1.0.0. We would now like to request the approval of the Incubator PMC for this release. Imperius is a rule-based policy evaluation engine based on the CIM-SPL language from Distributed Management Task Force (dtmf.org). The Imperius 1.0.0 RC6 release candidate has been tagged, packaged, and is ready for a vote. The artifacts, KEYS file, RAT report and release notes can be found at http://people.apache.org/~jneeraj/apache-imperius-1.0.0-rc6/ The tag from which the release artifacts were generated can be found at http://svn.apache.org/repos/asf/incubator/imperius/tags/release1.0.0rc6/ Revision no is 887217 In addition, my PGP public code signing key can be found at the MIT key server (http://pgp.mit.edu/) The KEYS file is checked in at http://svn.apache.org.repos/asf/incubator/imperius/KEYS Please vote to publish this release by Tuesday, Dec 17 18:00 EST., please include the testing you performed to arrive at your vote [ ] +1 Publish [ ] 0 Abstain [ ] -1 Don't publish, because... Below is a summary of the vote on the Imperius mailing list (and further below is the original vote email) Thanks Neeraj ~ Neeraj Joshi (knee-rudge) IBM WebSphere ComputeGrid Apache Imperius - http://incubator.apache.org/imperius ~ From: Neeraj Joshi/Durham/i...@ibmus To: imperius-...@incubator.apache.org Date: 12/14/2009 03:45 PM Subject: [VOTE][RESULT] Imperius 1.0.0 rc6 Hello All, Voting on the Imperius 1.0.0rc6 candidate release has concluded Results: 1 binding +1 vote 6 non-binding +1 votes Kevan Miller(*) +1 David Kaminsky +1 David Wood +1 Mark Carlson +1 Erik Bengston +1 Xiping Wang +1 Jorge Lobo +1 Comments received: 1. Comments from Erik Bengston - In the zip/tar file we have a /log.txt file that should be removed. - Inside the jars we have a /META-INF/maven that should be removed too. - imperius-splcore-1.0.0.jar does not have NOTICE.txt and LICENSE.txt - IMO, the lib/javaspl-samples-1.0.0.jar should be moved to samples/lib/javaspl-samples-1.0.0.jar - IMO, NOTICE.txt and LICENSE.txt files in jar files should lie in META-INF folder. It was concluded that it is too early to make all/any Apache Imperius artifacts available in the Maven repository The other issues did not violate Apache policies and would be accommodated in subsequent releases. 2. Comments from Kevan Miller I note that the source distribution contains the following file: imperius-cimsplclientsideprovider/customexpressions.properties which is not in the svn tag. The contents of this file are: SPL_CUSTOM_EXPRESSIONS SPL_CUSTOM_ACTIONS This file is innocuous and gets generated during JUnit testing I will now take this vote to the general mailing list for a final vote. We still need 2 +1 votes from IPMC members. Thanks Neeraj ~ Neeraj Joshi (knee-rudge) Apache Imperius - http://incubator.apache.org/imperius ~ From: Neeraj Joshi/Durham/i...@ibmus To: imperius-...@incubator.apache.org Date: 12/04/2009 10:06 AM Subject: [VOTE] Imperius 1.0.0 rc6 Hi All, The Imperius 1.0.0 RC6 release candidate has been tagged, packaged, and is ready for a vote. The artifacts, KEYS file, RAT report and release notes can be found at http://people.apache.org/~jneeraj/apache-imperius-1.0.0-rc6/ The tag from which the release artifacts were generated can be found at http://svn.apache.org/repos/asf/incubator/imperius/tags/release1.0.0rc6/ Revision no is 887217 In addition, my PGP public code signing key can be found at the MIT key server (http://pgp.mit.edu/) The KEYS file is checked in at http://svn.apache.org.repos/asf/incubator/imperius/KEYS Please vote to publish this release by Tuesday, Dec 08 18:00 EST., please include the testing you performed to arrive at your vote [ ] +1 Publish [ ] 0 Abstain [ ] -1 Don't publish, because... Upon a positive majority of binding votes and no binding vetoes, the results of this vote will be brought to the Incubator PMC and voted upon there. Thanks, -Neeraj Change log: 1. Checked in the build.xml from the release artifact into the SVN tag. All the release artifacts from previous candidate (r5) are the same. 2. Updated the SVN revision number. 3. Left the redundant zip/gz files as is. ~ It is hard enough to remember my opinions, without also remembering my reasons for them. -Friedrich Wilhelm Nietzsche Neeraj Joshi (knee-rudge) WebSphere XD - Compute Grid AIM, IBM Apache Imperius - http://incubator.apache.org/imperius
Re: [Discuss] Apache Cassandra as a TLP
I echo Matthieu's comments about Cassandra being ready to graduate, I'll vote +1 for it in a vote. Not sure if that PMC list is actually the complete list as I thought there was talk of adding others, i'll ask about it on their private list. ...ant On Tue, Jan 19, 2010 at 8:49 AM, Matthias Wessendorf mat...@apache.org wrote: On Tue, Jan 19, 2010 at 9:39 AM, Bertrand Delacretaz bdelacre...@apache.org wrote: On Tue, Jan 19, 2010 at 2:25 AM, Matthieu Riou matthieu.r...@gmail.com wrote: ...By the way if you have a few minutes, some feedback about the resolution that Eric attached would be cool... The resolution looks good to me, but the proposed PMC is really small: * Jonathan Ellis jbel...@apache.org * Eric Evans eev...@apache.org * Jun Rao jun...@apache.org * Chris Goffinet goffi...@apache.org And all of its members are currently active in Cassandra only. Would it be possible for (some of) the mentors to stay onboard for a while? With only 4 PMC members to start with, the risk of being unable to get 3 votes on issues is real. that's a good point, Bertrand. Those that are involved in other communities are the mentors, like Torsten, Matthieu or Brian (according to [1]). Looks like the only exception is Johan Oskarsson, but I am not to familiar with the community itself and its activity. However I noted that Johan voted for the graduation... I am also not sure why the proposed PMC is that small. Some try to expand their PPMC during incubation with all the active folks (mailings and commits). So, I am not sure on the reason why there is this small (P)PMC. -Matthias [1] http://people.apache.org/~jim/committers.html -Bertrand - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [Discuss] Apache Cassandra as a TLP
On Mon, Jan 18, 2010 at 3:10 PM, Eric Evans eev...@rackspace.com wrote: Greetings, The Cassandra community has successfully voted for graduation[1]. Before calling for a recommendation vote, I'd like to see if anyone here has any concerns or objections, or has any feedback on the draft resolution. Regards, [1] http://thread.gmane.org/gmane.comp.db.cassandra.user/1875 Other than the PMC makeup which is being taken care of one thing that sometimes causes debate is the resolution words, so to highlight that to try to avoid voting hiccups: ...creation and maintenance of open-source software related to fully distributed storage of structured data, ... Does anyone have any issues or comments with that? ...ant - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release UIMA 2.3.0-rc9
It is quite huge. I haven't looked at every artifact but the ones i did all the licensing etc looked ok and it looks like they understand what they're doing. The copyright in some NOTICE files is Copyright 2006, 2007 which could probably do with being updated, though others are 2009 and from the discussion on legal-discuss a while back i'm not sure thats a blocking issue so +1 from me. ...ant On Thu, Jan 21, 2010 at 10:13 AM, Jukka Zitting jukka.zitt...@gmail.com wrote: Hi, On Mon, Jan 18, 2010 at 2:48 AM, Jukka Zitting jukka.zitt...@gmail.com wrote: Others, please review and vote! The release is pretty complex so it's a bit of work to review it, but it would be great if at least two other IPMC members could spare some time on this. Anyone? BR, Jukka Zitting - 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] Graduate Apache Cassandra to an Apache TLP
+1 ...ant On Thu, Jan 28, 2010 at 7:59 PM, Eric Evans eev...@rackspace.com wrote: Greetings, We took the feedback from the earlier discussion[1] here and added our active mentors to the proposed PMC, (for a total of 7 people), then ran that through a new community vote[2]. [1] http://thread.gmane.org/gmane.comp.apache.incubator.general/24427 [2] http://thread.gmane.org/gmane.comp.db.cassandra.user/2157 There didn't seem to be any other feedback, so I'd like to start an official vote to recommend graduation of Apache Cassandra to a top-level project. Please cast your vote: [ ] +1 to recommend Cassandra's graduation [ ] 0 don't care [ ] -1 no, don't recommend yet, (because...) The vote will be open for 72 hours. Thanks, -- Eric Evans eev...@rackspace.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
Re: [Vote] Release Kato M1-incubating
+1 ...ant On Fri, Jan 29, 2010 at 4:20 PM, Stuart Monteith stuk...@stoo.me.uk wrote: The Kato community has voted to release Kato M1-incubating. We now request the Incubator PMC for a vote. The proposed release artifacts are located at: http://people.apache.org/~monteith/kato/apache-kato-M1-incubating-RC3/ There are packages for the Java binaries with documentation, source and native libaries for Linux and Windows x86. Each package is available in tar.gz and zip form, expect for the native packages. asc, md5 and sha1 (SHA512) files are generated for each. rat*.txt files have been generated for each of the packages contents. The mapping is: apache-kat-M1-incubating-bin.(tar.gz|zip) - rat-bin.txt apache-kat-M1-incubating-src.(tar.gz|zip) - rat-src.txt apache-kat-M1-incubating-native-bin-linux-i386.tar.gz - rat-bin-linux.txt apache-kat-M1-incubating-native-bin-windows-i386.zip - rat-bin-windows.txt Please review the artifacts and cast your vote by Thursday 4th February. Thanks in advance, Stuart Monteith -- Stuart Monteith http://blog.stoo.me.uk/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache libcloud 0.2.0
+1 ...ant On Thu, Feb 11, 2010 at 2:30 PM, Paul Querna p...@querna.org wrote: The Apache Libcloud project is currently voting on our first release, 0.2.0. As required by Incubator policy, we need IPMC approval for this release. There is a concurrent release vote ongoing on libcl...@incubator.apache.org. The current (passing) RAT output can be seen at: http://ci.apache.org/projects/libcloud/rat-output.txt Test tarballs for Apache Libcloud 0.2.0 are available at: http://people.apache.org/~pquerna/lc-0.2.0/ Please test and place your votes please; +/- 1 [ ] Release Apache Libcloud 0.2.0 Vote closes on Monday February 15, 2010 at 1pm PST. Thanks, Paul - 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] - Graduate Log4PHP as a subproject of Logging project
+1 ...ant On Thu, Mar 4, 2010 at 10:18 PM, Gav... ga...@16degrees.com.au wrote: Hi All, The Log4PHP community has voted [1] with 5 +1 votes and no other votes as follows, to graduate to become a sub-project of the Logging Project. * Gavin McDonald * Christian Hammers * Jim Jagielski * Jesus Christian (non binding) * Christian Grobmeier The Logging PMC has voted [2] with 7 +1 votes and no other votes as follows, to accept Log4PHP as a sub-project. * Ceki Gülcü * Niclas Hedhman * Curt Arnold * Scott Deboy * Paul Smith * Ron Grabowski * Christian Grobmeier The Log4PHP community feels it has fulfilled all graduation requirements to become a sub-project. This vote is to ask that the IPMC approve the graduation of Log4PHP as a sub-project of Apache Logging. The vote starts now and will run for a minimum of 72 hours. [ ] - +1 - Graduate Log4PHP as a sub-project of Apache Logging. [ ] - +/-0 - Don't care, whatever the majority decides. [ ] - -1 - Strongly object to this graduation (because ... Thanks All, Gav... [1] - Message-ID: ded132f11003032357v5f4edbb2k7579ffbb3be22...@mail.gmail.com [2] - Message-ID: ded132f11003032352h5d11607ene1811d34b9670...@mail.gmail.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
Re: [VOTE] Approve the release of apache-trafficserver-incubating-2.0.0-alpha
On Sat, Mar 6, 2010 at 8:21 AM, Leif Hedstrom zw...@apache.org wrote: Hi, The Traffic Server PPMC has voted on and approved the release of TS v2.0.0-alpha. We would now like to request the approval from the Incubator PMC for this release. The original vote thread is Message-ID: 4b8d5deb.2050...@apache.org The release candidate artifact and checksums / signature can be found at: http://people.apache.org/~zwoop/ http://people.apache.org/~zwoop/apache-trafficserver-incubating-2.0.0-alpha.tar.bz2 http://people.apache.org/~zwoop/apache-trafficserver-incubating-2.0.0-alpha.tar.bz2.md5 http://people.apache.org/~zwoop/apache-trafficserver-incubating-2.0.0-alpha.tar.bz2.sha1 http://people.apache.org/~zwoop/apache-trafficserver-incubating-2.0.0-alpha.tar.bz2.asc The .asc signature is signed by me (Leif Hedstrom (CODE SIGNING KEY) zw...@apache.org). The checksums are md5sum: 18f914f3873bc4d22c5f3115b9db011f sha1sum: f735a19a70c2aa69d97d4ea239a5192258dadf17 Please vote on releasing this package as Apache trafficserver-incubating-2.0.0-alpha: [ ] +1 Publish [ ] 0 Abstain [ ] -1 Don't publish, because... Below is a summary of the vote on the mailing list. Thanks, -- Leif Subject: [RESULT] [VOTE] Release candidate for Traffic Server 2.0.0-alpha The vote for release passes with six +1 votes, and no -1 or 0 votes. I will request for the IPMC to release this. Thanks! -- leif [+1] Leif Hedstrom [+1] George Paul [+1] John Plevyak [+1] Bryan Call [+1] Jean-Frederic Clere [+1] Doug Cutting I had a look. Unfortunately the main release artifact apache-trafficserver-incubating-2.0.0-alpha.tar.bz2 is missing the top level LICENSE and NOTICE files. Those are mentioned in the README and do look like they're in SVN so maybe there is just a problem with the release build, but they are a requirement of every artifact being released so i think you'll need a respin to fix that. The key included at ~zwoop/ with the release artifacts that was used to sign the artifacts does work ok but it doesn't look like thats published in a public key server like http://pgp.surfnet.nl/ so doing that would be good (though thats not a release requirement). Other that everything looks good from the ASF/legal perspective and the Incubator disclaimer is included in the README file. ...ant - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Approve the release of apache-trafficserver-incubating-2.0.0-alpha
On Tue, Mar 9, 2010 at 1:14 PM, Leif Hedstrom l...@ogre.com wrote: On 03/08/2010 05:09 PM, ant elder wrote: O I had a look. Unfortunately the main release artifact apache-trafficserver-incubating-2.0.0-alpha.tar.bz2 is missing the top level LICENSE and NOTICE files. Those are mentioned in the README and Are you sure? I just downloaded it (as linked above): loki (17:10) 258/0 $ wget http://people.apache.org/~zwoop/apache-trafficserver-incubating-2.0.0-alpha.tar.bz2 loki (17:10) 259/0 $ tar xf apache-trafficserver-incubating-2.0.0-alpha.tar.bz2 loki (17:10) 260/0 $ cd apache-trafficserver-incubating-2.0.0-alpha loki (17:10) 261/0 $ ls aclocal.m4 configure* emacs-style libinktomi++/ Makefile.am rc/ build-aux/ configure.ac example/ librecords/ Makefile.in README CHANGES contrib/ INSTALL LICENSE NOTICE STATUS ci/ doc/ iocore/ m4/ proxy/ loki (17:10) 262/0 $ ls -lrt LICENSE -rw-r--r-- 1 leif users 19098 2010-02-09 20:41 LICENSE loki (17:10) 263/0 $ ls -lrt NOTICE -rw-r--r-- 1 leif users 776 2010-02-12 07:24 NOTICE What am I missing? Thats odd, unless I'm going blind there is definitely no LICENSE file when I have look. I'm using windows and winzip though, could that be doing something funny when unzipping the .bz2 file? ...ant - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache River 2.1.2
Looks ok to me, +1. As an aside there are still Java package names that are using com.sun instead of org.apache, are they going to be changed before graduation (I forget what the feeling is about this these days in the Incubator PMC)? ...ant On Sat, Mar 20, 2010 at 9:37 AM, Jukka Zitting jukka.zitt...@gmail.com wrote: Hi, On Thu, Mar 18, 2010 at 4:54 PM, Jukka Zitting jukka.zitt...@gmail.com wrote: On Wed, Mar 10, 2010 at 10:39 AM, Peter Firmstone j...@zeus.net.au wrote: Please vote on releasing Apache River 2.1.2 +1 (sorry for the delay) PS. IPMC members; we still need two more IPMC votes to make this release official. Hmm, looks like I forgot to cc general@ on this. We're still lacking one IPMC vote to make this release official. Getting this release prepared was a huge effort and IMHO the biggest positive sign of community activity in River since the podling was started. Let's not stall the release for a missing IPMC vote! BR, Jukka Zitting - 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: [libcloud] [VOTE] Release Apache Libcloud 0.3.1
+1 One minor nit is the Changes file still talks about 0.3.0. ...ant On Fri, May 7, 2010 at 12:09 AM, Paul Querna p...@querna.org wrote: Test tarballs for Apache Libcloud 0.3.1 are available at: http://people.apache.org/~pquerna/libcloud-0.3.1/ Please test and place your votes please; +/- 1 [ ] Release Apache Libcloud 0.3.1 Vote closes on Monday May 10, 2010 at 1pm PST. This release fixes several issues related to the license blocks, NOTICE file, and test cases that were noticed in the scrubbed 0.3.0 release. It is based upon this tag: https://svn.apache.org/repos/asf/incubator/libcloud/tags/0.3.1 Thanks, Paul - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache Empire-db 2.0.6-incubating (rc4)
+1 ...ant On Wed, May 5, 2010 at 8:17 PM, Martijn Dashorst martijn.dasho...@gmail.com wrote: +1 (again). Could someone from the IPMC take a look at the release? The team is eager to release it, but lacks 2 +1 binding votes. Martijn On Wed, May 5, 2010 at 4:22 PM, Rainer Döbele doeb...@esteam.de wrote: +1 Rainer Francis De Brabandere wrote: re: [VOTE] Release Apache Empire-db 2.0.6-incubating (rc4) Hi, We have just prepared the fourth 2.0.6-incubating release candidate and we are now looking for approval of the IPMC to publish the release. PMC vote thread: http://mail-archives.apache.org/mod_mbox/incubator-empire-db- dev/201004.mbox/browser We already have one binding vote. These are the major change from our previous 2.0.5-incubating release: - Code-Generator allows generation of Data Model code files for existing databases - Maven plugin for DB-Code-Generator - New example to demonstrate interoperability between Empire-db and Spring - Provided jars are now OSGi compatible Changelog: http://svn.apache.org/viewvc/incubator/empire-db/tags/apache-empire-db- 2.0.6-incubating-rc4/CHANGELOG.txt?view=co Subversion tag: https://svn.apache.org/repos/asf/incubator/empire-db/tags/apache- empire-db-2.0.6-incubating-rc4 Maven staging repository: https://repository.apache.org/content/repositories/orgapacheempire-db- 020/ Distribution files are located here http://people.apache.org/~francisdb/empire-db/ Rat report for the tag is available here: http://people.apache.org/~francisdb/empire-db/rat.txt Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 -- http://www.somatik.be Microsoft gives you windows, Linux gives you the whole house. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Become a Wicket expert, learn from the best: http://wicketinaction.com Apache Wicket 1.4 increases type safety for web applications Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.4.7 - 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] Approval to release Apache Aries (Incubating) version 0.1-incubating
On Mon, May 10, 2010 at 7:31 PM, Jeremy Hughes hugh...@apache.org wrote: The Aries community has voted on its first release. From the Aries home page: The Aries project is delivering a set of pluggable Java components enabling an enterprise OSGi application programming model. This includes implementations and extensions of application-focused specifications defined by the OSGi Alliance Enterprise Expert Group (EEG) and an assembly format for multi-bundle applications, for deployment to a variety of OSGi based runtimes. Aries is a multi-module project. The vote thread on aries-dev for RC5: http://mail-archives.apache.org/mod_mbox/incubator-aries-dev/201005.mbox/%3cl2wadbf02b11005050801hdb720bfse0dd3f748f81a...@mail.gmail.com%3e concluded with 14 votes, all of them +1, four of which were binding Incubator PMC votes from Jarek Gawor, Kevan Miller, Guillaume Nodet Davanum Srinivas. The following Aries top level modules are staged and tagged in https://svn.apache.org/repos/asf/incubator/aries/tags/ at revision 941288. Modules staged at https://repository.apache.org/content/repositories/orgapachearies-009/ parent eba-maven-plugin testsupport util blueprint jndi transaction web jmx Modules staged at https://repository.apache.org/content/repositories/orgapachearies-004/ jpa samples Modules staged at https://repository.apache.org/content/repositories/orgapachearies-010/ application The RAT and IANAL build checks passed. The KEYS file located here: https://svn.apache.org/repos/asf/incubator/aries/KEYS contains the code signing key for myself, Jeremy Hughes, the release manager for this release. We already have 4 binding +1 IPMC votes on the aries-dev list, and I'm opening up this thread for 72 hours for any further feedback on the staged artifacts for release. Thank you, Jeremy Its a slightly unusual release structure so apologies if I'm missing it but where is the source release? If i'm not missing some other link then something may have gone wrong in the release build, as an example, in the folder: https://repository.apache.org/content/repositories/orgapachearies-009/org/apache/aries/blueprint/org.apache.aries.blueprint/0.1-incubating/ the source jar org.apache.aries.blueprint-0.1-incubating-sources.jar is mostly empty and doesn't contain the source of org.apache.aries.blueprint-0.1-incubating.jar. ...ant - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Approval to release Apache Aries (Incubating) version 0.1-incubating
Ok thanks I see them now. Looks good to me, +1 ...ant On Tue, May 11, 2010 at 12:14 PM, Jeremy Hughes hugh...@apache.org wrote: On 11 May 2010 07:19, ant elder ant.el...@gmail.com wrote: On Mon, May 10, 2010 at 7:31 PM, Jeremy Hughes hugh...@apache.org wrote: The Aries community has voted on its first release. From the Aries home page: The Aries project is delivering a set of pluggable Java components enabling an enterprise OSGi application programming model. This includes implementations and extensions of application-focused specifications defined by the OSGi Alliance Enterprise Expert Group (EEG) and an assembly format for multi-bundle applications, for deployment to a variety of OSGi based runtimes. Aries is a multi-module project. The vote thread on aries-dev for RC5: http://mail-archives.apache.org/mod_mbox/incubator-aries-dev/201005.mbox/%3cl2wadbf02b11005050801hdb720bfse0dd3f748f81a...@mail.gmail.com%3e concluded with 14 votes, all of them +1, four of which were binding Incubator PMC votes from Jarek Gawor, Kevan Miller, Guillaume Nodet Davanum Srinivas. The following Aries top level modules are staged and tagged in https://svn.apache.org/repos/asf/incubator/aries/tags/ at revision 941288. Modules staged at https://repository.apache.org/content/repositories/orgapachearies-009/ parent eba-maven-plugin testsupport util blueprint jndi transaction web jmx Modules staged at https://repository.apache.org/content/repositories/orgapachearies-004/ jpa samples Modules staged at https://repository.apache.org/content/repositories/orgapachearies-010/ application The RAT and IANAL build checks passed. The KEYS file located here: https://svn.apache.org/repos/asf/incubator/aries/KEYS contains the code signing key for myself, Jeremy Hughes, the release manager for this release. We already have 4 binding +1 IPMC votes on the aries-dev list, and I'm opening up this thread for 72 hours for any further feedback on the staged artifacts for release. Thank you, Jeremy Its a slightly unusual release structure so apologies if I'm missing it but where is the source release? There are 12 top level modules, most with sub modules. For 'blueprint' the source-release.zip is here: https://repository.apache.org/content/repositories/orgapachearies-009/org/apache/aries/blueprint/blueprint/0.1-incubating/blueprint-0.1-incubating-source-release.zip The pattern is repo_root/org/apache/aries/module/module/0.1-incubating/module-0.1-incubating-source-release.zip If i'm not missing some other link then something may have gone wrong in the release build, as an example, in the folder: https://repository.apache.org/content/repositories/orgapachearies-009/org/apache/aries/blueprint/org.apache.aries.blueprint/0.1-incubating/ the source jar org.apache.aries.blueprint-0.1-incubating-sources.jar is mostly empty and doesn't contain the source of org.apache.aries.blueprint-0.1-incubating.jar. Each of the sub-modules contain sources jars. These are for the convenience of attaching to binaries in IDEs for example. The one you mention is for a sub-module which acts as a collector to collect up other sub-modules into a bundle. So it doesn't have any sources of its own, so I guess technically that sources jar isn't required. ...ant - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Wink 1.1 (incubating)
Looks ok to me, +1 ...ant On Tue, May 11, 2010 at 5:06 PM, Mike Rheinheimer r...@apache.org wrote: I should have mentioned this, Wink 1.1 release already has two IPMC binding votes from: Davanum Srinivas Kevan Miller Wink 1.1. release needs only one more IPMC binding vote to pass. Thanks. mike On Tue, May 11, 2010 at 10:43 AM, Mike Rheinheimer r...@apache.org wrote: IPMCers, Wink 1.1 release voting has completed successfully on the wink-dev list. I'm now calling the IPMC vote to release Wink 1.1 (incubating) per the process indicated here: http://incubator.apache.org/guides/releasemanagement.html#best-practice-incubator-release-vote The Maven staging area is at: https://repository.apache.org/content/repositories/orgapachewink-007/ The distributions are in: https://repository.apache.org/content/repositories/orgapachewink-007/org/apache/wink/apache-wink/1.1-incubating/ This release is tagged at: https://svn.apache.org/repos/asf/incubator/wink/tags/wink-1.1-incubating (revision 941046) The vote will be open here for at least 72 hours (ending Friday, May 14, 10:45am US CST). Please indicate your vote: [ ] +1 to release Wink 1.1 incubating [ ] +0 [ ] -1 NOT to release Wink 1.1 incubating (and why) Thanks! mike - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Deltacloud Project
+1 ...ant On Thu, May 13, 2010 at 1:45 AM, David Lutterkort lut...@redhat.com wrote: Hi all, after the discussion so far [1], I'd like to put Detlacloud for a vote for acceptance into the Apache Incubator according to the proposal[2] I _think_ I've added everybody who expressed interest in being a mentor or initial committer to the proposal - if I have forgotten anybody, please holler. Please reply to this mail with your vote. David [1] http://mail-archives.apache.org/mod_mbox/incubator-general/201005.mbox/%3c1273174879.7253.99.ca...@avon.watzmann.net%3e [2] http://wiki.apache.org/incubator/DeltacloudProposal - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release PhotArk M2-incubating (RC1)
On Thu, May 13, 2010 at 8:33 PM, Luciano Resende luckbr1...@gmail.com wrote: On Tue, May 11, 2010 at 9:44 AM, Luciano Resende luckbr1...@gmail.com wrote: The PhotArk community has completed a vote on it's second milestone release (PhotArk M2-Incubating) and is now looking for IPMC approval to publish the release. Please review and vote on approving the M2-incubating release artifacts of PhotArk. The artifacts are available for review at: http://people.apache.org/~lresende/photark/M2-incubating-RC1/ This includes the signed binary and source distributions, the RAT report, and the Maven staging repository. The release tag is available at : http://svn.apache.org/repos/asf/incubator/photark/tags/M2-incubating-RC1/ -- Here is my +1, any others available to review the release ? The distribution archives still contain SNAPSHOT in the name which may be unintentional but its not a blocker and I don't see any others so ... +1 from me. ...ant - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Shiro version 1.0.0-incubating
On Tue, May 25, 2010 at 11:32 PM, Kalle Korhonen kalle.o.korho...@gmail.com wrote: This is the first incubator release for Apache Shiro, version 1.0.0-incubating. The release is made following the standard Apache/Maven release process as documented at http://maven.apache.org/developers/release/apache-release.html. This is a lazy consensus vote as we already received 3 binding IPMC +1 votes for the PPMC release vote on shiro-dev. PPMC release vote thread: http://mail-archives.apache.org/mod_mbox/incubator-shiro-dev/201005.mbox/%3caanlktik_mke9dwlatmxnzq7kwcdbs3amsu5ulymkp...@mail.gmail.com%3e The issues solved for 1.0.0 (after the project entered Apache incubator): https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310950styleName=Htmlversion=12314078 The tag to be voted upon: http://svn.apache.org/repos/asf/incubator/shiro/tags/shiro-root-1.0.0-incubating/ Staging repo for binaries: https://repository.apache.org/content/repositories/orgapacheshiro-005/ Staging site: http://incubator.apache.org/shiro/static/1.0.0-incubating/ Project website (just for informational purposes, not to be voted upon): http://incubator.apache.org/shiro/ Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Lazy consensus, vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 I can't find all the source for the release. AFAICT the only way to recreate all the release artifacts would be from the svn tag but thats not enough as an ASF release must include a source release. If I've just missed it and all the source is there somewhere then could you provide the link? Two other comments are: There is no incubation DISCLAIMER file in any of the release artifacts which is required as per http://incubator.apache.org/incubation/Incubation_Policy.html#Releases. That needs to be present either as a separate file next to the LICENSE/NOTICE files or the text may be included in the top level README, for an example see: https://svn.apache.org/repos/asf/incubator/kato/tags/apache-kato-M1-incubating/DISCLAIMER.txt Looking back now we seem to be missing this in other releases recently too so perhaps this could be fixed on the next release if there isn't a new RC needed for anything else. I don't think the NOTICE file needs those extra comments about SoftHashMap and Spring, and perhaps the SoftHashMap comments would be better in the LICENSE file. There has been a lot of confusion about what should go in the NOTICE file and extra info is far better than missing info so up to the project what if anything to do about this. Other than that it looks good, the missing source is a problem though so sorry but my vote is -1 until that is cleared up. ...ant - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Shiro version 1.0.0-incubating
On Wed, May 26, 2010 at 2:59 PM, Alan D. Cabrera l...@toolazydogs.com wrote: On May 26, 2010, at 2:00 AM, ant elder wrote: On Tue, May 25, 2010 at 11:32 PM, Kalle Korhonen kalle.o.korho...@gmail.com wrote: This is the first incubator release for Apache Shiro, version 1.0.0-incubating. The release is made following the standard Apache/Maven release process as documented at http://maven.apache.org/developers/release/apache-release.html. This is a lazy consensus vote as we already received 3 binding IPMC +1 votes for the PPMC release vote on shiro-dev. PPMC release vote thread: http://mail-archives.apache.org/mod_mbox/incubator-shiro-dev/201005.mbox/%3caanlktik_mke9dwlatmxnzq7kwcdbs3amsu5ulymkp...@mail.gmail.com%3e The issues solved for 1.0.0 (after the project entered Apache incubator): https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310950styleName=Htmlversion=12314078 The tag to be voted upon: http://svn.apache.org/repos/asf/incubator/shiro/tags/shiro-root-1.0.0-incubating/ Staging repo for binaries: https://repository.apache.org/content/repositories/orgapacheshiro-005/ Staging site: http://incubator.apache.org/shiro/static/1.0.0-incubating/ Project website (just for informational purposes, not to be voted upon): http://incubator.apache.org/shiro/ Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Lazy consensus, vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 I can't find all the source for the release. AFAICT the only way to recreate all the release artifacts would be from the svn tag but thats not enough as an ASF release must include a source release. If I've just missed it and all the source is there somewhere then could you provide the link? All the artifacts have sources and javadocs in the same directories. https://repository.apache.org/content/repositories/orgapacheshiro-005/org/apache/shiro/shiro-all/1.0.0-incubating/ AIUI all ASF releases MUST have _buildable_ source. The source jars included in those directories are not buildable. The idea behind this is that the ASF deals with source code and releases are of source packages that enable anyone to go tinker with that source, but you can't do so much useful tinkering if you can't build the source. See http://www.apache.org/dev/release.html#what-must-every-release-contain and various emails that fly around on other mailing lists. I believe the latest Maven release plugin and Apache parent pom.xml will create the correct packages now. You probably could reconstruct a buildable source from whats in the Maven repo and if this was a small release like a single Maven plugin or something it could have been argued that this was ok and could just be updated to the new Maven release for next release, but this is something like 20 modules so to recreate it would be quite a job - working out and recreating the correct directory structure, unzip all the source jars into the correct place, download all the pom.xml's and rename them and put them in the right place etc. Or anyone leap in here and explain i've misunderstood the policy. ...ant - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Shiro version 1.0.0-incubating
On Wed, May 26, 2010 at 5:39 PM, Les Hazlewood l...@hazlewood.com wrote: On Wed, May 26, 2010 at 8:11 AM, ant elder ant.el...@gmail.com wrote: I can't find all the source for the release. AFAICT the only way to recreate all the release artifacts would be from the svn tag but thats not enough as an ASF release must include a source release. If I've just missed it and all the source is there somewhere then could you provide the link? It is part of the staging repo under the provided URL: https://repository.apache.org/content/repositories/orgapacheshiro-005 Specifically, the complete buildable source package is here: https://repository.apache.org/content/repositories/orgapacheshiro-005/org/apache/shiro/shiro-root/1.0.0-incubating/ Les Smashing, ok i change my vote to +1 then. ...ant - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Nuvem Project
On Tue, Jun 15, 2010 at 7:16 AM, Luciano Resende luckbr1...@gmail.com wrote: On Wed, Jun 9, 2010 at 12:06 PM, Luciano Resende luckbr1...@gmail.com wrote: Hi, I would like to propose the Nuvem project for addition to the Apache incubator. The initial proposal is available at the the Wiki[1], and it is also included below for convenience. We are looking forward to any and all feedback and/or questions on the proposal. We are also looking for a Champion and mentors, and would very much welcome additional volunteers to help steer Nuvem through the incubation process. [1] http://wiki.apache.org/incubator/Nuvem We are still looking for mentors, any volunteers to help ? Hi Luciano, you can add me as a mentor which with Paul will give you the required three mentors. The proposal doesn't list a champion yet - isn't that you? ...ant - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Move Chukwa to incubator
On Wed, Jun 23, 2010 at 9:53 AM, Bernd Fondermann bernd.fonderm...@googlemail.com wrote: On Wed, Jun 23, 2010 at 07:54, Eric Yang ey...@yahoo-inc.com wrote: Besides DOAP file and the incubator nomenclature, I may need help identify the addition responsibilities for Apache PMC. One problem, Chukwa community did not have a vote for PMC Chair because we are not sure what is the right process for this. Meanwhile, I have been writing quarterly report like any other Apache project, only recipient of the report is different. Chukwa releases have been voted by Chukwa community which is similar to Hadoop releases, and managed incremental changes using patches and committers. Code audit has been performed by the committers to ensure we don't bring in license incompatible libraries into Chukwa. Owen O'Malley had trained us these procedures roughly two years ago, and we have been executing the same process ever since. This translate for me into: Chukwa didn't have proper oversight by a PMC (a committee that is, not a single person) at Hadoop. Incubation would fix this using established processes. I think this is the right track, and the people involved, including the Hadoop PMC, ultimatively did the right thing. (Except for not simply growing the Hadoop PMC over time to include committers from every product.) Chukwa has a community of exist user base of 35 people. It would be nice to make Chukwa a special case to skip incubator nomenclature. This would ease the migration path for the existing Chukwa community. Ok with me, at least as far as MLs or SVN are concerned. However, Chukwa must be aware that it is changing PMCs from Hadoop to Incubator. So different rules might apply, like marking release artifacts as -incubating. Let's gather some more feedback on this. Most projects that come to incubate would likely prefer to go straight to the TLP naming. The last time i recall this came up was here: http://apache.markmail.org/message/ifinvq7wqmeoo5ix IMHO we should insist on using the incubator naming for the Chukwa website/svn/MLs because I think Chukwa should just go directly to a TLP and if they have to use the incubator naming it may help them decide that the direct to TLP route really is better ;-) ...ant - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Move Chukwa to incubator
On Thu, Jun 24, 2010 at 8:21 PM, William A. Rowe Jr. wr...@apache.org wrote: On 6/23/2010 8:12 AM, Bernd Fondermann wrote: On Wed, Jun 23, 2010 at 14:45, ant elder ant.el...@gmail.com wrote: IMHO we should insist on using the incubator naming for the Chukwa website/svn/MLs because I think Chukwa should just go directly to a TLP and if they have to use the incubator naming it may help them decide that the direct to TLP route really is better ;-) I see you blinking here, so I guess this is not just for putting up a strawman ;-) Well folks, it's a fun debate and all, but it isn't helping bring this vote to a conclusion :) Is anyone in agreement with ant? Otherwise we should just move ahead and can hold a separate vote on allowing tlp resource creation at this time. If the proposers want (Eric?) a three choice vote, 1. recommend TLP with guides to help the initial pmc, 2. accept incubating with tlp resource naming, but -incubating release naming, or 3. accept incubating requiring all incubator naming conventions, that might help the incubator simplify this decision. At this point, I personally guess that 1. might be the most sensible in terms of resource creation and management; Option 1. sounds most sensible to me too. ...ant - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [Result][Vote] Move Chukwa to incubator
On Thu, Jul 1, 2010 at 11:03 AM, Chris Douglas cdoug...@apache.org wrote: On Thu, Jul 1, 2010 at 1:26 AM, Bernd Fondermann bernd.fonderm...@googlemail.com wrote: [snip] Fair point. The naming debate is only about the location of the project in svn and the mailing lists, right? Conducting the vote with this variable has become more arduous than all the INFRA and site work it implies; let's drop it. Eric, could you just change the naming in the proposal to match the convention? Unless there are other open issues, a straight, up/down vote should be possible with that modification. Bernd, would you mind conducting the next vote so that it runs to your satisfaction? IMHO, Either Hadoop decides to run a TLP movement, or the Incubator conducts a proper vote. The Hadoop PMC vote to recommend Chukwa as a TLP directly did not pass. -C I've been suggesting it would be simpler for Chukwa to go directly to TLP but if thats not going to happen then you have my support to incubate if thats what they really want to do, and I agree a new vote might making things clearer. It seems a shame to require more renaming of mailing lists etc than necessary, another alternative could be to just keep the existing naming that Chukwa currently uses during the incubation and only do renaming when graduating to TLP. That avoids one renaming and might get more IPMC votes for the proposal than it did when using the TLP naming. ...ant - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Future of RAT
How about keeping it here at the Incubator? It could be a showcase project that demonstrates how to do things like releases, as well as an eat your own dog food type place to help avoid any unnecessarily burdensome IPMC processes and procedures ;) ...ant On Tue, Aug 10, 2010 at 11:55 AM, Siegfried Goeschl siegfried.goes...@it20one.at wrote: Hi Jochen, not sure if Commons is the right place sine RAT has a very spezialized scope or to state it differently I would not look for RAT in Commons. What about Maven TLP? Cheers, Siegfried Goeschl On 10.08.10 12:40, Jochen Wiedmann wrote: Hi, having just published a release of Apache RAT with the -incubating label, I'd though it is time to discuss the future of RAT. RAT is an incubator project since 18 months. It is not an overly busy project: The occasional feature request, which is handled, a bug report from time to time, and so on. OTOH, it definitely lives: People are interested and, what's more, it is very widely adopted by all Java projects I am aware of and perhaps even by a few non-Java projects. If there will ever be a migration to a new license like ASL 3 or a another change of the header policy, then RAT will likely play a very important part in the process. Even now, the RAT report is carefully studied as part of every release vote. (Funnily, RAT is very rarely used to inspect itself, because so far I didn't find a possibility to run a previous version of the RAT Maven plugin as part of a build. In fact, RAT is the only project I am aware of, which doesn't publish a RAT report. :-) IMO, RAT could very well leave the incubator. It's 10 or so committers [1] are all part of an organization called ASF since years, so you might question the diversity, but I don't believe anyone will actually do that. ;-) The source code has been developed under ASL and by Apache committers right from the start, so licensing was never an issue. The question is: What's the target? RAT is way too small for an independent project. And I cannot imagine anybody of the current committers writing board reports. To me, a Rat TLP is no option. So we have the second possibility: Put it under the hat of another TLP. The only one that comes to my mind is the Apache Commons project. But Commons would be an excellent choice: Most, or even all of the RAT committers are Commons committers as well. Commons was one of the drivers for integration of RAT into every release build. I admit that I wouldn't like to change the package name or the Maven group ID again, but either Commons developers could accept that exception from the rule or I'd force myself to do the required changes. WDYT? Jochen [1] http://incubator.apache.org/rat/team-list.html - 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: Future of RAT
On Tue, Aug 10, 2010 at 1:09 PM, Stefan Bodewig bode...@apache.org wrote: On 2010-08-10, ant elder wrote: How about keeping it here at the Incubator? I was going to suggest that as well - as a subproject, not as an eternal podling. But I understand Ross point of sending the wrong signal. Infra would be fine with me if infra wanted to absorb rat. A thing with being part of infra is that the rat people are less likely to be so actively involved with other infra pmc work and perhaps visa versa, if it was here at the Incubator i'd hope that it could really be one pmc group with everyone interested in what rat is doing and how that relates to what Incubator reviews do. ...ant - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Future of RAT
On Tue, Aug 10, 2010 at 2:45 PM, Mattmann, Chris A (388J) chris.a.mattm...@jpl.nasa.gov wrote: However, I'm not sure I get the whole reasoning below RE: TLP? Why not have a RAT TLP? The overhead of filing board reports and not knowing anyone on the team that would be able to? Hen files them all the time (well he used to as Attic VP). And the other names I see on that list [1] below are all people I widely respect at the ASF and folks who pop up on board@, members@ and other foundation-wide lists from time to time. I don't want to speak for anybody, but what would be the issue with any of them filing board reports? Or, yourself for that matter? :) You see to get this whole release process thing - how is the board report sent monthly for the first few months, then quarterly after such a big deal? So, what's the problem with being a TLP? Yep i agree, there are already other small TLPs so it doesn't need to be an issue, so going TLP does sound ideal. ...ant - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: an experiment
On Wed, Aug 11, 2010 at 6:45 PM, Joe Schaefer joe_schae...@yahoo.com wrote: The second idea is more controversial: to hold IPMC votes to admit all significant committers to those projects to the IPMC itself. The purpose of this concept is to allow those who best know the codebase to provide IPMC oversight over it, especially as it pertains to releases. Without some more explanation I'm not that convinced about doing that. The main purpose of the IPMC is to vote on the graduation of poddlings, why should some random ASF poddling newbie get a binding vote on the graduation of _any_ poddling? I'm guessing the motivation for this proposal is not to give poddling committers binding votes on other poddling graduations but to give them binding votes on their own poddling activities, and that i agree with. The things they need binding votes on is their committer votes, ppmc votes (they already have that), and release votes - lets just give them those. ...ant - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: an experiment
On Wed, Aug 11, 2010 at 11:28 PM, Davanum Srinivas dava...@gmail.com wrote: Ant, My personal opinion (and i am hoping!) was that such individuals from ppmc's who end up in ipmc would help build bridges between podlings and will help get lessons learned (when any ppmc has issues/problems/roadblocks) back to their ppmc. Isn't that sort of thing exactly what hasn't happened in past projects with sub projects and why these days sub projects often get moved out to be TLPs? If a poddlings active committers warrent being on the IPMC why not graduate the poddling or give the poddling its own PMC? It would be good for poddlings to have more control over their own activities like voting committers and releases and this would give them that which is good so i guess I wouldn't stand in the way of trying it, but doing it with this approach does feel like we'd just be creating another great big umbrella project with all the issues that has. ...ant - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Bean Validation 0.2-incubating RC2
Looks good to me too, i can't see anything at all to comment on. +1 ...ant On Mon, Aug 16, 2010 at 9:28 PM, Kevan Miller kevan.mil...@gmail.com wrote: +1 Signature/checksums, build, source (RAT), and general snooping around with emacs all looked good. Thanks Donald! --kevan On Aug 13, 2010, at 1:38 PM, Donald Woods wrote: A Bean Validation 0.2-incubating release candidate #2 has been created with the following artifacts up for a vote: SVN source tag (r985290): https://svn.apache.org/repos/asf/incubator/bval/tags/0.2-incubating/ Maven staging repo: https://repository.apache.org/content/repositories/orgapachebval-102/ Source release: https://repository.apache.org/content/repositories/orgapachebval-102/org/apache/bval/bval-parent/0.2-incubating/bval-parent-0.2-incubating-source-release.zip Javadoc staging site: http://people.apache.org/~dwoods/bval/0.2-incubating/staging-site/apidocs/ PGP release keys (signed using D018E6B1): https://svn.apache.org/repos/asf/incubator/bval/KEYS Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Thanks, Donald - 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] Change name of Lucene Connectors Framework to Apache Connectors Framework
On Wed, Sep 8, 2010 at 1:18 PM, Grant Ingersoll gsing...@apache.org wrote: Hi, After much debate both here and on the connectors mailing list, the LCF community has voted (see http://mail-archives.apache.org/mod_mbox/incubator-connectors-dev/201008.mbox/browser) and would like to officially change our name to be the Apache Connectors Framework. We would like the Incubator PMC to vote to make this official. [] +1 Change the Lucene Connector Framework to the Apache Connector Framework [] 0 Don't care [] -1 Don't change it Since this is a procedural vote (http://www.apache.org/foundation/voting.html), it is a majority rule vote with binding votes coming from IPMC members. The vote is open for 72 hours. Here's my +1 (binding). Thanks, Grant -0 I agree with the comments from David and others such as [1] and the suggestion at [2] to call it something more abstract like Apache Connecto. Thats IMHO anyway, I'm not sure that the IPMC should be the ones with binding votes on this but it would be good if the poddling could take into consideration our views. ...ant [1] http://apache.markmail.org/message/ryf4eebpzpsvq3hr [2] http://apache.markmail.org/message/zyiodmx4hbqfjek3 - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Change name of Lucene Connectors Framework to Apache Connectors Framework
On Thu, Sep 9, 2010 at 1:32 PM, Karl Wright daddy...@gmail.com wrote: Grant proposed that we simply go from LCF to ACF at that time, and posted accordingly to this group. He received several positive responses, and only one that raised any concerns. After a week's delay, we presumed that all was well, That may be the cause of all this - there was a concern raised but instead of being taken on board it was ignored. Looking at the vote result of options [1] Apache Manifold is the second highest choice and has a good amount of support and is far less contentious than ACF so why not just go with that? I agree with Upayavira's comment [2] - while it may not be down to the IPMC to veto a name the board may well do so. So if you want to reduce the chance of a book title being messed up when the project goes TLP then i'd go with something abstract like Apache Manifold now (or else atleast ping the board now to see if they'll comment). ...ant [1] http://mail-archives.apache.org/mod_mbox/incubator-connectors-dev/201009.mbox/%3caanlktikd9fglbnyybrha6emr8ordzdlejaf85qvpf...@mail.gmail.com%3e [2] http://apache.markmail.org/message/vbuq6hqfpuodouyp - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Apache Chemistry OpenCMIS 0.1.0-incubating (RC2)
I've had a look, and it all looks good. The licensing and legal doc in the artifacts looks fine, the sigs verify, src builds etc. +1 ...ant On Tue, Sep 14, 2010 at 1:02 PM, Gabriele Columbro gabri...@apache.org wrote: Dear Incubator PMC members, on behalf of the Chemistry dev team, I'd like to ask your approval to release the RC2 packages as Chemistry OpenCMIS 0.1.0-incubating. Legal and packaging issues - that blocked RC1- should have been now resolved (https://issues.apache.org/jira/browse/CMIS-224), while detailed release notes can be found in Jira at: https://issues.apache.org/jira/browse/CMIS/fixforversion/12315133. The release has passed the Chemistry incubator PMC vote: http://mail-archives.apache.org/mod_mbox/incubator-chemistry-dev/201009.mbox/%3cf6d8594e-4913-4af6-aaab-a1b30e951...@apache.org%3e. During the vote, also 2 IPMC (Nick Burch Jukka Zitting) votes have been collected, so we'd need one more IPMC +1 to proceed with the release. Main release candidate packages (for distribution at apache.org/dist) are at: http://people.apache.org/~gabriele/chemistry/opencmis/0.1.0-incubating-rc2/dist/ The full set of Maven artifacts (for distribution at repository.apache.org) is at: https://repository.apache.org/content/repositories/orgapachechemistry-012/ Sources tag can be found at: http://svn.apache.org/repos/asf/incubator/chemistry/opencmis/tags/chemistry-opencmis-0.1.0-incubating-RC2/ The staging maven documentation site is at : http://people.apache.org/~gabriele/chemistry/opencmis/0.1.0-incubating-rc2/site/ (full integration tests at: http://bit.ly/b07hK8) Artifacts have been signed using key D0383AE5 (publicly available at http://pgp.mit.edu:11371/pks/lookup?op=vindexsearch=0xB0E9DD9ED0383AE5 and under http://svn.apache.org/repos/asf/incubator/chemistry/opencmis/trunk/KEYS). The vote is open for 72 hours. Please cast your votes! [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Thanks in advance! Gabriele -- Gabriele Columbro Alfresco Software, Ltd. http://www.mindthegab.com http://twitter.com/mindthegabz Keyboard not found. Press F1 to continue. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Whirr version 0.1.0-incubating
Looks ok, +1. The binary jar whirr-cli-0.1.0-incubating.jar is missing the incubator DISCLAIMER file but that file is in the other artifacts like the src distro so i guess its enough to just fix that next time. Its also a bit hard to work out if all the licenses are included for all the stuff thats included in that jar as theres so much in it, it did have a few i check but it would be helpful to have something like the main LICENSE file or a README summarise whats there and the licensing. ...ant On Tue, Sep 14, 2010 at 7:19 PM, Tom White tomwh...@apache.org wrote: This is the first incubator release for Apache Whirr, version 0.1.0-incubating. We already received one binding IPMC +1 vote for the PPMC release vote on whirr-dev, so are looking for two more. PPMC release vote thread: http://mail-archives.apache.org/mod_mbox/incubator-whirr-dev/201009.mbox/%3caanlktinio1np6d+gbnm4w6jjcg-6koe7x8begkuxr...@mail.gmail.com%3e The issues fixed for 0.1.0-incubating https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12315111styleName=HtmlprojectId=1230 Source and binary files: http://people.apache.org/~tomwhite/whirr-releases/ Maven staging repo: https://repository.apache.org/content/repositories/orgapachewhirr-009 The tag to be voted upon: http://svn.apache.org/repos/asf/incubator/whirr/tags/release-0.1.0-incubating The vote is open for 72 hours. [ ] +1 [ ] +0 [ ] -1 Thanks, Tom - 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] Apache SIS 0.1-incubating Release Candidate #2
On Wed, Nov 10, 2010 at 2:03 PM, Mattmann, Chris A (388J) chris.a.mattm...@jpl.nasa.gov wrote: Hi Folks, I have posted a 2nd candidate for the Apache SIS 0.1-incubating release. The source code is at: http://people.apache.org/~mattmann/apache-sis-0.1-incubating/rc2/ This release addresses the following comments from IPMC members during the RC #1 VOTE: - add Incubator disclaimer per comments from Ant Elder. http://incubator.apache.org/guides/branding.html#disclaimers - add JDOM license to NOTICE.txt and upgrade to apache parent 7 per comments from Mark Struberg. - note that ROME and Georss-ROME are under the ASLv2 per Kevan Miller's comments. See the included CHANGES.txt file for details on release contents and latest changes. The release was made using the Maven2 release plugin, according to Jukka Zitting's notes from Tika-ville: http://tinyurl.com/yz2cqls Caveat: we aren't publishing to Maven Central yet. I've filed INFRA-3177 [1] to make this happen for our next release. See the included README.txt file for an example of how to use Apache SIS in a Tomcat environment and how to run the demo. This plugin creates a Apache SIS 0.1-incubating tag at: http://svn.apache.org/repos/asf/incubator/sis/tags/0.1-incubating/ Please vote on releasing these packages as Apache SIS 0.1-incubating. The vote is open for the next 72 hours. Only votes from Incubator PMC are binding, but everyone is welcome to check the release candidate and voice their approval or disapproval. The vote passes if at least three binding +1 votes are cast. [ ] +1 Release the packages as Apache SIS 0.1-incubating. [ ] -1 Do not release the packages because... Thanks! Cheers, Chris P.S. Here's my +1. [1] https://issues.apache.org/jira/browse/INFRA-3177 I think this release src distribution has too much unnecessary stuff in its LICENSE and NOTICE files. Unfortunately you've hit one of those potentially painful parts of doing a release on general@ - the contents of the LICENSE and NOTICE file - and most likely everyone you ask will tell you a slightly different thing of what it should be like. Here's what I say: 1) Each artifact being released needs to include the licenses for everything in the artifact (Thats often all in the single LICENSE file but its also ok to have just the Apache License in the LICENSE file and any other license somewhere obvious). 2) The NOTICE file has some standard text (see http://www.apache.org/legal/src-headers.html#notice ) and then maybe some mention of other things. More often than not the mention of other things is unnecessary. This release is a source only release and AFAICT there is nothing included in apache-sis-0.1-incubating-src.tar.gz that is licensed with anything other than the Apache license so the LICENSE text needs to have just the Apache License text. Similarly the NOTICE file doesn't need to include anything other than the standard NOTICE text. If this release was including a binary release artifact then the LICENSE file of that binary release would need to include the licenses of any included dependencies, eg i think thats what this src release LICENSE now has. If this release was including a binary release artifact then the NOTICE file should still (IMHO) just include the standard NOTICE text. All that other stuff that you've now added to the NOTICE shouldn't be there as none of it is required third-party notices. You could argue that it doesn't really matter that there is some extra stuff in the LICENSE and NOTICE and maybe thats true but as this is the first Apache release its probably worth having the debate. ...ant - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Apache SIS 0.1-incubating Release Candidate #2
On Wed, Nov 10, 2010 at 9:54 PM, Mattmann, Chris A (388J) chris.a.mattm...@jpl.nasa.gov wrote: Hi Ant, Thanks. Do you see any of the below as a blocker to the first release? What extra stuff, specifically, do you see that wasn’t present in the prior where that you +1’ed and thought was OK as a first release? Cheers, Chris In NOTICE file http://svn.apache.org/repos/asf/incubator/sis/tags/0.1-incubating/NOTICE.txt everything after the line The Apache Software Foundation (http://www.apache.org/). shouldn't be there. In the LICENSE file http://svn.apache.org/repos/asf/incubator/sis/tags/0.1-incubating/LICENSE.txt everything including and after the line APACHE TIKA SUBCOMPONENTS shouldn't be there (should it? what is using those extra licenses?). I'd not noticed the extra stuff in the LICENSE file in RC1 but its the RC2 NOTICE file that i think is the blocker - license text does not belong in the NOTICE file. ...ant - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Apache SIS 0.1-incubating Release Candidate #3
Looks good to me, +1. ...ant On Fri, Nov 12, 2010 at 3:47 AM, Mattmann, Chris A (388J) chris.a.mattm...@jpl.nasa.gov wrote: Hi Folks, I have posted a 3rd candidate for the Apache SIS 0.1-incubating release. The source code is at: http://people.apache.org/~mattmann/apache-sis-0.1-incubating/rc3/ This release addresses the following comments from IPMC members during the RC #2 VOTE: From Ant Elder: In NOTICE file http://svn.apache.org/repos/asf/incubator/sis/tags/0.1-incubating/NOTICE.txt everything after the line The Apache Software Foundation (http://www.apache.org/). shouldn't be there. In the LICENSE file http://svn.apache.org/repos/asf/incubator/sis/tags/0.1-incubating/LICENSE.tx t everything including and after the line APACHE TIKA SUBCOMPONENTS shouldn't be there (should it? what is using those extra licenses?). See the included CHANGES.txt file for details on release contents and latest changes. The release was made using the Maven2 release plugin, according to Jukka Zitting's notes from Tika-ville: http://tinyurl.com/yz2cqls Caveat: we aren't publishing to Maven Central yet. I've filed INFRA-3177 [1] to make this happen for our next release. See the included README.txt file for an example of how to use Apache SIS in a Tomcat environment and how to run the demo. This plugin creates a Apache SIS 0.1-incubating tag at: http://svn.apache.org/repos/asf/incubator/sis/tags/0.1-incubating/ Please vote on releasing these packages as Apache SIS 0.1-incubating. The vote is open for the next 72 hours. Only votes from Incubator PMC are binding, but everyone is welcome to check the release candidate and voice their approval or disapproval. The vote passes if at least three binding +1 votes are cast. [ ] +1 Release the packages as Apache SIS 0.1-incubating. [ ] -1 Do not release the packages because... Thanks! Cheers, Chris P.S. Here's my +1. [1] https://issues.apache.org/jira/browse/INFRA-3177 ++ Chris Mattmann, Ph.D. Senior Computer Scientist NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA Office: 171-266B, Mailstop: 171-246 Email: chris.mattm...@jpl.nasa.gov WWW: http://sunset.usc.edu/~mattmann/ ++ Adjunct Assistant Professor, Computer Science Department University of Southern California, Los Angeles, CA 90089 USA ++ - 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
[DISCUSS] Poddling new committer process
I'd like to propose that the process for Incubator poddlings to make someone a new committer is simplified so that all that is needed are votes from poddling committers and that there is no longer any need for votes from Incubator PMC members or a separate Incubator PMC vote. As justification, this is the process that was in place some years ago and it worked fine like that, there is the experiment currently in place with some poddlings doing this which seems to be working ok, and the board has said they're ok with it. ...ant - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept Jena into the incubator
+1 ...ant On Wed, Nov 17, 2010 at 1:10 PM, Ross Gardler rgard...@apache.org wrote: Please vote on the acceptance of JENA into the incubator. The proposal can be found at http://wiki.apache.org/incubator/JenaProposal and is copied below. [ ] +1 Accept Jena for incubation [ ] +0 Don't care [ ] -1 Reject for the following reason: The vote is open for at least 72 hours. Thanks, Ross = Jena, a Semantic Web Framework = == Abstract == Jena is a semantic web framework for Java, based on W3C standards. == Proposal == Jena provides a semantic web framework in Java that implements the key W3C recommendations for the core semantic web technologies of RDF and SPARQL. Jena is a number of components and modules built on this core system. It currently includes: * an API for working with RDF * Parsers and writers for the RDF formats (RDF/XML, Turtle, N-triples, NQuads, TriG) * an implementation of SPARQL, the W3C standard RDF query language * multiple storage systems for RDF data including in-memory, file-backed, in SQL databases and in custom scalable storage systems * an API for manipulation of OWL * a rule-based inference engine * an implementation of GRDDL for extraction of RDF from XML formats * a standards compliant IRI library. The project includes facilities based around this core to encourage the creation of components and contributions both as part of Jena and also as companion open source activities. This proposal includes the main components of Jena: the main Jena download, ARQ, GRDDL, SDB, TDB, the IRI library and Joseki. Other components may be contributed later - we're just starting with the main part of Jena for now. == Background == The W3C recommendations provide detailed specifications and it is important to follow these standards so that independently built applications can exchange data over the web. Jena provides high quality Java implementations of RDF input/output and storage so that application writers can concentrate on the application, not the low-level details. W3C Semantic Web: http://www.w3.org/standards/semanticweb/ Jena has been on !SourceForge since 2001. http://sourceforge.net/projects/jena/ == Rationale == The open source project was originally created as part of a research activity in HPLabs. In building new systems, the researchers identified the value of a common platform that dealt with the low level details of the standards. This lead to engagement with the standards process and the creation of a framework that provided a library to deal with the details of semantic web standards. This work was released as Jena. The developers have contributed implementation experience back to the working groups. None of the contributors now work for HP. Providing a uniform contributor and licensing framework assists commercial use of Jena. == Current Status == Jena is already an established project with a large user base in industry and academia. It currently uses a BSD-style three-clause license with a number of contributing copyright holders. Support is primarily provided via the jena-...@groups.yahoo.com mailing list. The majority of the team was employed in HPLabs, and HP holds the majority of the copyright over the code - there are contributions from non-HP companies. HP decided to close the research group as of October 2009 and the people from HPLabs connected with the project have moved on to several different semantic web companies. This change does not immediately affect Jena because the people who were in HP still remain active contributors to Jena. The project continues to be supported and actively enhanced. There is now the opportunity to become an open source project without a single large organisation involved. === Meritocracy === The Jena team has always been self-determining; there has not been a project manager in charge of the effort. Instead, it has grown through individuals contributing to the codebase as part of their research activities. The team has organised itself to create the framework for builds, releases and public support, and people who had worked on Jena in HP, and moved to other companies and institutions, have continued to contribute. === Core developers === Jena originated within a research activity in HPLabs, starting around 2000. Contributors to jena have been active in W3C working groups including chairing the RDF Core working group and acting as document editors on several other working groups. W3C processes are public; jena contributors have been involved in public debate and decision making. People have since moved on from HP to several semantic web forced companies and to university positions. === Alignment === Jena is already in use in many commercial systems as well as widely used in academic research and teaching. We want to continue making this easy and at the same time encourage contribution in a
Re: [DISCUSS] Poddling new committer process
On Wed, Nov 17, 2010 at 11:53 PM, Craig L Russell craig.russ...@oracle.com wrote: Assuming that no one comes forward with a significant reason to disallow this, I'd just request that you not call a VOTE until you have an update to the incubator page that describes the process. In other words, let's DISCUSS and then VOTE on the change to the process page. I don't think a VOTE is necessary because the page being updated is not a policy page so changes use CTR not RTC. For an enjoyable sense of symmetry see: http://apache.markmail.org/message/h7lvpedsn46g72lf ...ant - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Poddling new committer process
On Fri, Nov 12, 2010 at 8:20 AM, ant elder ant.el...@gmail.com wrote: I'd like to propose that the process for Incubator poddlings to make someone a new committer is simplified so that all that is needed are votes from poddling committers and that there is no longer any need for votes from Incubator PMC members or a separate Incubator PMC vote. As justification, this is the process that was in place some years ago and it worked fine like that, there is the experiment currently in place with some poddlings doing this which seems to be working ok, and the board has said they're ok with it. ...ant Ok its been nearly a week and there is overwhelming support for doing this so I have gone ahead and made an update to the PPMC guide to reflect this. The text is a copy of what is already there for voting in a new PPMC member updated as necessary for being a committer. The new text reads: -- Any member of the PPMC can propose a new committer. The proposal should be discussed in private on the PPMC private alias, with a subject line of [DISCUSS] Joe Bob as committer. If there is consensus that the proposed member is suitable, then there should be a formal vote in the PPMC private alias, with the subject line of [VOTE] Joe Bob as committer. The [VOTE] message should be forwarded to the IPMC ( priv...@incubator.apache.org) to notify them that the vote is underway. If the vote is successful, the proposer should send a message to the PPMC private alias, with the subject line of [VOTE][RESULT] Joe Bob as committer. Note that to be successful the vote requires at least one +1 from a poddling mentor, or, if no mentors are available from an Incubator PMC member. -- ...ant - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Accept Wave for incubation
On Wed, Nov 24, 2010 at 5:26 AM, Greg Stein gst...@gmail.com wrote: On Tue, Nov 23, 2010 at 22:45, Ralph Goers ralph.go...@dslextreme.com wrote: On Nov 23, 2010, at 6:06 PM, Greg Stein wrote: On Tue, Nov 23, 2010 at 20:47, Ralph Goers ralph.go...@dslextreme.com wrote: ... OK - Have they explicitly OK'd Apache Wave? While Apache Wave would certainly be unique to Apache, if Google intends to keep using Google Wave (and Wave as a shorthand) this would get very confusing. Don't you think that by proposing Wave to the Incubator that Google has OK'd this? I don't work for Google and don't know the people proposing this so no, I have no idea whether Google has OK'd this. Simple review: the original email was sent by Dan Peterson from his google.com address. I imagine that if Google had a problem with it, then he wouldn't be working there tomorrow :-D ... or if this was some kind of spurious one-guy-goes-batshit-crazy, then how could he line up so many people? And sure, while you couldn't know this, Dan is a great guy. I worked with him while at Google. This proposal is straight-up. My simple point is: please accept proposals at face value rather than pushing back with paranoid thoughts about malfeasance on the part of the people wanting to join our efforts here at the ASF. Ralph's question seemed reasonable to me, the ASF trademarks people are a often mentioning problems with using trademarked names like this. However its something that can be sorted out with those ASF trademarks folks during incubation, its not a barrier for entry to incubation. Anyway, seems like a fine proposal to me, +1 for it coming to Apache. ...ant - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept Wave into the incubator
+1 ...ant On Tue, Nov 30, 2010 at 6:52 AM, Dan Peterson dpeter...@google.com wrote: Hi everyone, Please vote on the acceptance of Wave into the Apache incubator. The proposal is available at: http://wiki.apache.org/incubator/WaveProposal (for your convenience, a snapshot is also copied below) The earlier discussion thread can be found at: http://apache.markmail.org/message/3ebtccdxvipp2732?q=general%40incubator.apache.org+list:org.apache.incubator.general+order:date-backwardpage=2 The vote options: [ ] +1 Accept Wave for incubation [ ] +0 Don't care [ ] -1 Reject for the following reason: The vote is open for 72 hours. Thanks, -Dan Apache Wave Proposal (Apache Incubator) = Abstract = Apache Wave is the project where wave technology is developed at Apache. Wave in a Box (WIAB) is the name of the main product at the moment, which is a server that hosts and federates waves, supports extensive APIs, and provides a rich web client. This project also includes an implementation of the Wave Federation protocol, to enable federated collaboration systems (such as multiple interoperable Wave In a Box instances). = Proposal = A wave is a hosted, live, concurrent data structure for rich communication. It can be used like email, chat, or a document. WIAB is a server that hosts waves. The best analogy for this is a mail server with a web client. WIAB is comprised of a few high-level components: the client and the server. They have the following major functionality (though this is not an exhaustive list): * Client *A dynamic web client for users to create, edit, and search waves. Users can access this client by directly visiting the server in a browser. * Gadgets provide the ability to insert, view, and modify the UI -- exposing the Wave Gadgets API ( http://code.google.com/apis/wave/extensions/gadgets/guide.html) * A console client that can create and edit waves via a command-line-like interface. * Server * Hosts and stores waves. WIAB comes with a default storage mechanism. The administrators of the server may configure it to use alternative storage mechanisms. * Indexing, allowing for searching the waves a user has access to. * Basic authentication, configurable to delegate to other systems. * Federation, allowing separate Wave in a Box servers to communicate with each other using the Wave Federation Protocol ( http://www.waveprotocol.org/federation). * Robots, using the Wave Robots API, ( http://code.google.com/apis/wave/extensions/robots/) may interact with waves on a WIAB instance. = Background = Wave expresses a new metaphor for communication: hosted conversations. This was created by Lars and Jens Rasmussen after observation of people's use of many separate forms of communication to get something done, e.g, email, chat, docs, blogs, twitter, etc. The vision has always been to better the way people communicate and collaborate. Building open protocols and sharing code available in an open and free way is a critical part of that vision. Anyone should be able to bring up their own wave server and communicate with others (much like SMTP). We hope this project will allow everyone to easily gain the benefits of Wave with a standard implementation of Wave – in a box. = Rationale = Wave has shown it excels at small group collaboration when hosted by Google. Although Wave will not continue as a standalone Google product, there is a lot of interest from many organizations in both running Wave and building upon the technology for new products. We are confident that with the community-centric development environment fostered by the Apache Software Foundation, WIAB will thrive. = Initial Goals = The initial goals of the project are: 1. To migrate the codebase from code.google.com and integrate the project with the ASF infrastructure (issue management, build, project site, etc). 1. To quickly reach a state where it is possible to continue the development of the Wave In a Box implementation under the ASF project. 1. To add new committers to the project and grow the community in The Apache Way. = Current Status = The open source Wave in a Box project has existed in various forms for approximately 16 months (starting out life as the FedOne open source project). FedOne began in July 2009 in order to accelerate adoption of the wave federation protocol, and serve as a proof of concept that a non-Google implementation of the wave federation protocol could interoperate with the Google production instance. It worked. FedOne's existence lead to a prototype by Novell that demonstrated federation between Google Wave and Novell Pulse (now known as Vibe). In addition, in May of 2010, SAP unveiled a prototype version of SAP StreamWork that federated with both Novell Pulse and Google Wave. All three systems interoperated, sharing real-time state, and gadget updates. In May 2010 Google released significantly
Re: [VOTE] Release Apache ManifoldCF 0.1
On Thu, Jan 6, 2011 at 1:12 PM, Grant Ingersoll gsing...@apache.org wrote: Hi, The Apache ManifoldCF community has voted to release our first set of artifacts and now would like an Incubator vote. Since this is our first release, extra attention to detail is appreciated. You can find the artifacts at http://people.apache.org/~kwright/ Thanks, Grant I've reviewed this and think it mostly fine. The NOTICE file does include some unnecessary things, i don't think thats technically a blocking issue but as this is the first RC of the first release it should probably be cleaned up and another RC done. The NOTICE file should only include required notices that other text if its really needed could go in a README file, see http://www.apache.org/legal/src-headers.html#notice I think this current source+binary distribution is fine. The rule is that you can only release binary artifacts which also have the source released, but there are no rules saying the source distribution must not include any binary artifacts, so if this is what the project thinks works best then its fine. It is missing the Incubating disclaimer text which should be included in the README or a DISCLAIMER file, see http://incubator.apache.org/guides/branding.html#disclaimers I tried building it with ant build and that failed, don't know if that my environment or something else: BUILD FAILED C:\ASF\manifoldcf\apache-manifoldcf-0.1-incubator\build.xml:353: The following error occurred while executing this line: C:\ASF\manifoldcf\apache-manifoldcf-0.1-incubator\connectors\jdbc\build.xml:52: C:\ASF\manifoldcf\apache-manifoldcf-0.1-incubator\co nnectors\jdbc\jdbc-drivers does not exist. Other than that it looks ok to me. Its big and inlcudes some duplicate stuff but if thats what the project thinks is the best approach then its fine, there are plenty of other big projects being distributed. ..ant - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache ManifoldCF 0.1
On Fri, Jan 7, 2011 at 11:13 AM, Karl Wright daddy...@gmail.com wrote: - I have made no changes to NOTICE and LICENSE, because the incubator and community advice seemed contradictory. I would like a general sense of how many people feel that the current NOTICE and LICENSE files are unacceptable before I make changes. The NOTICE file is still incorrect and includes a lot of unnecessary stuff. Understanding how to do releases with the correct legal files is one of the important parts of incubation and as this is the first release for the poddling i think this needs to be sorted out. For the NOTICE file, start with the following text (between the ---'s): --- Apache ManifestCF Copyright 2010 The Apache Software Foundation This product includes software developed by The Apache Software Foundation (http://www.apache.org/). --- and then add _nothing_ unless you can find explicit policy documented somewhere in the ASF that says it is required. If someone wants to add something ask for the URL where the requirement is documented. The NOTICE file should only include required notices, the other text thats in the current NOTICE file could go in a README file, see http://www.apache.org/legal/src-headers.html#notice For the LICENSE file, it should start with the AL as the current one does, and then include the text for all the other licenses used in the distribution. Those license that are currently in the NOTICE file should be moved to the LICENSE file and then you need to verify that all the 3rd party dependencies in the src and binary distributions are also in the LICENSE files of those distributions. ...ant - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache ManifoldCF 0.1
That NOTICE file still contains additional text about Jetty and HSQLDB, why is that needed? The Apache License section 4d describes what must be included in the NOTICE and AIUI it says you only need to include in your NOTICE the notices from Jetty and HSQLDB if you distribute derivitave works of them. Thats not what you're doing you are distributing copies of the them not Derivative Works so nothing is needed in your NOTICE file. ...ant On Sat, Jan 8, 2011 at 11:05 AM, Karl Wright daddy...@gmail.com wrote: Rather than spin a whole new RC and upload it, which takes me two hours, I've attached the revised proposed NOTICE and LICENSE here, so people can comment directly. Karl On Sat, Jan 8, 2011 at 5:51 AM, Karl Wright daddy...@gmail.com wrote: The current NOTICE file has exactly what you specify, plus a preamble describing components and their licenses. I will remove the preamble - it was based on the Solr/Lucene NOTICE which I was told to use as an example. The LICENSE file, on the other hand, should currently have everything that's in the NOTICE file in expanded form. If you think I should move the preamble to the LICENSE file as well, this would be the time to indicate that. Otherwise, the preamble will just be deleted. Karl On Sat, Jan 8, 2011 at 5:06 AM, ant elder ant.el...@gmail.com wrote: On Fri, Jan 7, 2011 at 11:13 AM, Karl Wright daddy...@gmail.com wrote: - I have made no changes to NOTICE and LICENSE, because the incubator and community advice seemed contradictory. I would like a general sense of how many people feel that the current NOTICE and LICENSE files are unacceptable before I make changes. The NOTICE file is still incorrect and includes a lot of unnecessary stuff. Understanding how to do releases with the correct legal files is one of the important parts of incubation and as this is the first release for the poddling i think this needs to be sorted out. For the NOTICE file, start with the following text (between the ---'s): --- Apache ManifestCF Copyright 2010 The Apache Software Foundation This product includes software developed by The Apache Software Foundation (http://www.apache.org/). --- and then add _nothing_ unless you can find explicit policy documented somewhere in the ASF that says it is required. If someone wants to add something ask for the URL where the requirement is documented. The NOTICE file should only include required notices, the other text thats in the current NOTICE file could go in a README file, see http://www.apache.org/legal/src-headers.html#notice For the LICENSE file, it should start with the AL as the current one does, and then include the text for all the other licenses used in the distribution. Those license that are currently in the NOTICE file should be moved to the LICENSE file and then you need to verify that all the 3rd party dependencies in the src and binary distributions are also in the LICENSE files of those distributions. ...ant - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache ManifoldCF 0.1
On Sat, Jan 8, 2011 at 4:40 PM, Karl Wright daddy...@gmail.com wrote: I've attached a new proposed version of README.txt, NOTICE.TXT, and LICENSE.txt. Any further comments? Karl These look good to me. Its a long thread so a bit hard to keep track of without a new RC but i think what you have now it all looks fine. I don't think the size is an issue. One last comment is that the some of the doc files like the README and DISCLAIMER have the Apache License header which i don't think is necessary and the README is the first thing people look at so having a big glob of legal text right at the top isn't so attractive. ...ant - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [libcloud] Re: [VOTE] Release Apache Libcloud 0.4.2
+1 ...ant On Tue, Jan 11, 2011 at 6:00 AM, Jerry Chen je...@apache.org wrote: Hi all, With 6x +1 votes (including 2 binding), and no -1 votes, the vote seeks the approval of the IPMC. Thanks, Jerry On Jan 8, 2011, at 12:10 AM, Jerry Chen wrote: Hi all, Test tarballs for Apache Libcloud 0.4.2 are available at: http://people.apache.org/~jerry/libcloud-0.4.2/ Please test and place your votes: +/- 1 [ ] Release Apache Libcloud 0.4.2 Vote closes on Sunday January 9, 2011 at 10pm PST. This release includes the EC2NodeLocations fix to restore backward compatibility in the EC2 driver, as well as new drivers, improvements to deployment capabilities, and libcloud.security module for SSL certificate verification. For more information on SSL verification: http://wiki.apache.org/incubator/LibcloudSSL For the full list of changes, see: https://svn.apache.org/repos/asf/incubator/libcloud/tags/0.4.2/CHANGES Cheers, Jerry - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [libcloud] Re: [VOTE] Release Apache Libcloud 0.4.2
By my count libcloud still needs one more binding +1 for this release, does any other Incubator PMC member have a minute to review and vote? ...ant On Thu, Jan 13, 2011 at 8:46 PM, ant elder ant.el...@gmail.com wrote: +1 ...ant On Tue, Jan 11, 2011 at 6:00 AM, Jerry Chen je...@apache.org wrote: Hi all, With 6x +1 votes (including 2 binding), and no -1 votes, the vote seeks the approval of the IPMC. Thanks, Jerry On Jan 8, 2011, at 12:10 AM, Jerry Chen wrote: Hi all, Test tarballs for Apache Libcloud 0.4.2 are available at: http://people.apache.org/~jerry/libcloud-0.4.2/ Please test and place your votes: +/- 1 [ ] Release Apache Libcloud 0.4.2 Vote closes on Sunday January 9, 2011 at 10pm PST. This release includes the EC2NodeLocations fix to restore backward compatibility in the EC2 driver, as well as new drivers, improvements to deployment capabilities, and libcloud.security module for SSL certificate verification. For more information on SSL verification: http://wiki.apache.org/incubator/LibcloudSSL For the full list of changes, see: https://svn.apache.org/repos/asf/incubator/libcloud/tags/0.4.2/CHANGES Cheers, Jerry - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Apache Libcloud 0.4.2 Released!
On Wed, Jan 19, 2011 at 6:33 PM, Luciano Resende luckbr1...@gmail.com wrote: On Tue, Jan 18, 2011 at 6:43 PM, Ross Gardler rgard...@apache.org wrote: What specific questions you have ? Is it the project calling themselves Apache Libcloud without a incubating disclaimer ? That's the main one, yes. It's also the wording being pretty much identical to a TLP release announcement. Anyway, following the download page, the release artifacts are suffixed with incubating (apache-libcloud-incubating-0.4.2.zip) and they also contain the DISCLAIMER file saying they are under incubating. That's great (the home page doesn't have such a disclaimer, but does have the incubator logo). I'm not meaning to pick on Libcloud, I'm just trying to understand where the lines are drawn. Ross The release management guidelines are very light on announcements requirements [1], but looking at the past announcements, this seems like following the general practice [2] [1] http://incubator.apache.org/guides/releasemanagement.html#announcements [2] http://markmail.org/search/%5Bannounce%5D+list:org.apache.incubator.general Most of those announcements do seem to at least mention something about incubating, the release management guide is a bit sparse though, I think we should update the release management guide to at least mention that announcements must follow the branding guidelines at http://incubator.apache.org/guides/branding.html, and say poddling announcements must mention that its incubating and perhaps include the full disclaimer text in the email. ...ant - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Apache Chemistry OpenCMIS 0.2.0-incubating (RC1)
+1 from me. Though a little reluctantly because while it looks mostly good the chemistry-opencmis-client-impl-0.2.0-incubating-with-dependencies.zip does not include the text of all the licenses of the included dependencies it only has URLs to the license text. I thought including the full license text was a requirement but hunting around now i can't find anything that states that. ...ant On Wed, Jan 19, 2011 at 3:17 PM, Gabriele Columbro colum...@gmail.com wrote: Hi all, just a reminder for this vote, which is now been open for a full week. On Jan 17, 2011, at 1:04 PM, Nick Burch wrote: Just need one more IPMC +1 and we're done. Anyone able to review and vote? As Nick correctly mentions here, we just need one more IPMC +1 to get this release out. Would be great if someone can take this on, so we can move forward with pushing out the release. Thanks in advance, Gab Nick - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Eng. Gabriele Columbro Alfresco Software, Ltd. Blog: http://www.mindthegab.com Twitter: http://twitter.com/mindthegabz - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release PhotArk M3-incubating (RC2a)
+1 to releasing most of this. I do think the duplicate and incorrect
legal files should be cleaned up as Stefan commented, and because of
those the webapp modules in the maven repo look like they have ended
up with the wrong license/notice files. I also think it would be
better to change from having the binary distribution which wrappers
the two webapps to instead just release the two webapps on their own.
...ant
On Sun, Jan 23, 2011 at 7:52 PM, Luciano Resende luckbr1...@gmail.com wrote:
On Fri, Jan 21, 2011 at 3:27 AM, Stefan Seelmann seelm...@apache.org wrote:
+1
RAT report looks good.
Source distribution exists.
Binary distributions and WAR contain licenses and notices of included
libraries.
Some notes, maybe you can fix that in the next release: the war file
contains multiple NOTICE and LICENSE files in
- META-INF
- WEB-INF/classes
- WEB-INF/classes/META-INF
I understand that the files in META-INF contain licenses and notices
for all included libraries which is fine. But I don't know if the
files in WEB-INF are required.
Also please note that the WEB-INF/classes/NOTICE still contains the
${pom.name} variable.
Kind Regards,
Stefan
Thanks Stefan, we will look into this for our next release.
Others, we need one more vote here, any volunteers ?
--
Luciano Resende
http://people.apache.org/~lresende
http://twitter.com/lresende1975
http://lresende.blogspot.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
Re: [VOTE][PROPOSAL] EasyAnt incubator
+1 You only have two mentors, if you need a third i would help out. ...ant On Mon, Jan 24, 2011 at 5:14 PM, Antoine Levy-Lambert anto...@gmx.de wrote: I would like to present for a vote the following proposal to be sponsored by the Ant PMC for a new EasyAnt podling. The proposal is available on the wiki at and included below: http://wiki.apache.org/incubator/EasyAntProposal [] +1 to accept EasyAnt into the Incubator [] 0 don't care [] -1 object and reason why. Thanks, Antoine Levy-Lambert --- Proposal text from the wiki --- EasyAnt Proposal The following presents the proposal for creating a new EasyAnt project within the Apache Software Foundation. = Abstract = Easyant is a build system based on Apache Ant and Apache Ivy. = Proposal = EasyAnt goals are : * to leverage popularity and flexibility of Ant. * to integrate Apache Ivy, such that the build system combines a ready-to-use dependency manager. * to simplify standard build types, such as building web applications, JARs etc, by providing ready to use builds. * to provide conventions and guidelines. * to make plugging-in of fresh functionalities easy as writing simple Ant scripts as Easyant plugins. To still remain adaptable, * Though Easyant comes with a lot of conventions, we never lock you in. * Easyant allows you to easily extend existing modules or create and use your own modules. * Easyant makes migration from Ant very simple. Your legacy Ant scripts could still be leveraged with Easyant. = Rationale = On the Ivy and Ant mailing list, an often asked question is Why Ivy is not shipped with Ant ?. Ant users (and some opponents) complains also about the bootstrapping of an Ant based build system: it is mainly about copying an existing one. EasyAnt is intended to response to both of these requirements: a prepackaged Ant + Ivy solution with standard build script ready to be used. Also taking inspiration from the success of Apache Maven, EasyAnt is adopting the convention over configuration principle. Then it could be easy to build standard project at least for all commons steps (no more need to reinvent the wheel between each projects). The common part should be easy enough to tune parameters without having deep ant knowledge (example changing the default directory of sources, force compilation to be java 1.4 compatible, etc...). Last but not least, EasyAnt is intended to provide a plugin based architecture to make it easy to contribute on a specific step of the build. Build plugins are pieces of functionality that can be plugged into or removed from a project. Plugins could actually perform a piece of your regular build, e.g. compile java classes during build of a complete war. Or, do a utility action, e.g. deploy your built web application onto a packaged Jetty server! = Current Status = == Meritocracy == Some of the core developers are already committers and members of the Apache Ant PMC, so they understand what it means to have a process based on meritocracy. == Community == EasyAnt have a really small community (around 100 downloads per release). It is not a problem as the team is currently making restructuring changes. The team plans to make more promotion after those changes and strongly believe that community is the priority as the tool is designed to be easy to use. == Core Developers == Xavier Hanin and Nicolas Lalev ¡ ée are members of the PMC of Apache Ant. Jerome Benois is an Acceleo committer, he was a committer in Eclipse MDT Papyrus for two years and he's an active contributor in Eclipse Modeling and Model Driven community. He's a committer on Bushel project now contribute to the Ivy code base. He leads the EasyAnt for Eclipse plugin development. Jason Trump is leading Beet project on sourceforge (http://beet.sourceforge.net/). Jean-Louis Boudart is Hudson committer. == Alignment == EasyAnt is based on Apache Ant and Ivy. Being part of Apache could help for a closer collaboration between projects. The team plans to reinject as much as possible stuff into Ant or Ivy like they've done in the past on : * extensionPoint : kind of IoC for targets (Ant) * import/include mechanism (Ant) * module inheritance (Ivy) = Known risks = == Orphaned products == Jean-Louis Boudart is the main developer of EasyAnt. Other developers got interested in this project and are now touching to every aspect of EasyAnt. Thus the risk of being orphaned is quite limited. == Inexperience with Open Source == Many of the committers have experience working on open source projects. Two of them have experience as committers on other Apache projects. == Homogenous Developers == The existing committers are spread over a number of countries and employers. == Reliance on Salaried Developers == None of the developers rely on EasyAnt for consulting work. == Relationships with Other Apache Products == As already stated above, EasyAnt is
Re: [VOTE] Release Apache ManifoldCF 0.1 incubating, RC8
+1 ...ant On Thu, Jan 27, 2011 at 8:44 AM, Karl Wright daddy...@gmail.com wrote: Thanks for the votes! Still need one more binding +1... Karl On Tue, Jan 25, 2011 at 11:45 AM, Mattmann, Chris A (388J) chris.a.mattm...@jpl.nasa.gov wrote: Hi Karl, +1 from me (binding). Signatures check out: [chipotle:~/tmp/apache-manifoldcf-0.1-incubating] mattmann% gpg --import *.KEYS gpg: key 03824582: Karl David Wright (CODE SIGNING KEY) kwri...@apache.org not changed gpg: key FE045966: Grant Ingersoll (CODE SIGNING KEY) gsing...@apache.org not changed gpg: Total number processed: 2 gpg: unchanged: 2 [chipotle:~/tmp/apache-manifoldcf-0.1-incubating] mattmann% gpg --verify apache-manifoldcf-0.1-incubating-bin.tar.gz.asc gpg: Signature made Tue Jan 11 14:19:16 2011 PST using RSA key ID 03824582 gpg: Good signature from Karl David Wright (CODE SIGNING KEY) kwri...@apache.org gpg: WARNING: This key is not certified with a trusted signature! gpg: There is no indication that the signature belongs to the owner. Primary key fingerprint: E74B 06A0 454F 6E92 400A 3450 FD1F F09C 0382 4582 [chipotle:~/tmp/apache-manifoldcf-0.1-incubating] mattmann% gpg --verify apache-manifoldcf-0.1-incubating-bin.zip.asc gpg: Signature made Tue Jan 11 14:19:07 2011 PST using RSA key ID 03824582 gpg: Good signature from Karl David Wright (CODE SIGNING KEY) kwri...@apache.org gpg: WARNING: This key is not certified with a trusted signature! gpg: There is no indication that the signature belongs to the owner. Primary key fingerprint: E74B 06A0 454F 6E92 400A 3450 FD1F F09C 0382 4582 [chipotle:~/tmp/apache-manifoldcf-0.1-incubating] mattmann% gpg --verify apache-manifoldcf-0.1-incubating-src.tar.gz.asc gpg: Signature made Tue Jan 11 14:18:59 2011 PST using RSA key ID 03824582 gpg: Good signature from Karl David Wright (CODE SIGNING KEY) kwri...@apache.org gpg: WARNING: This key is not certified with a trusted signature! gpg: There is no indication that the signature belongs to the owner. Primary key fingerprint: E74B 06A0 454F 6E92 400A 3450 FD1F F09C 0382 4582 [chipotle:~/tmp/apache-manifoldcf-0.1-incubating] mattmann% gpg --verify apache-manifoldcf-0.1-incubating-src.zip.asc gpg: Signature made Tue Jan 11 14:18:41 2011 PST using RSA key ID 03824582 gpg: Good signature from Karl David Wright (CODE SIGNING KEY) kwri...@apache.org gpg: WARNING: This key is not certified with a trusted signature! gpg: There is no indication that the signature belongs to the owner. Primary key fingerprint: E74B 06A0 454F 6E92 400A 3450 FD1F F09C 0382 4582 [chipotle:~/tmp/apache-manifoldcf-0.1-incubating] mattmann% [chipotle:~/tmp/apache-manifoldcf-0.1-incubating] mattmann% cat *.md5 C7CA5B01ADC5A785F63ED559169B4390 *apache-manifoldcf-0.1-incubating-bin.tar.gz CF1744BF9ACF2EFD17F705A875691B02 *apache-manifoldcf-0.1-incubating-bin.zip D134D3F1D01060F2B6800FB19572A576 *apache-manifoldcf-0.1-incubating-src.tar.gz BA2F388B9AF5E66FC0F1437C98EDF846 *apache-manifoldcf-0.1-incubating-src.zip [chipotle:~/tmp/apache-manifoldcf-0.1-incubating] mattmann% md5sum *-bin*.tar.gz *-bin*.zip *-src*.tar.gz *-src*.zip c7ca5b01adc5a785f63ed559169b4390 apache-manifoldcf-0.1-incubating-bin.tar.gz cf1744bf9acf2efd17f705a875691b02 apache-manifoldcf-0.1-incubating-bin.zip d134d3f1d01060f2b6800fb19572a576 apache-manifoldcf-0.1-incubating-src.tar.gz ba2f388b9af5e66fc0f1437c98edf846 apache-manifoldcf-0.1-incubating-src.zip [chipotle:~/tmp/apache-manifoldcf-0.1-incubating] mattmann% Thanks for including CHANGES.txt and KEYS. That really helped. Great job and great working the process! Cheers, Chris On Jan 24, 2011, at 9:54 PM, Karl Wright wrote: Oh, forgot to mention that the release candidate tag is at: http://svn.apache.org/repos/asf/incubator/lcf/tags/release-0.1-incubating-RC8/ Karl On Thu, Jan 20, 2011 at 9:48 PM, Karl Wright daddy...@gmail.com wrote: Calling the official vote for release of ManifoldCF 0.1 incubating, RC8, which can be found at http://people.apache.org/~kwright . The community has voted for release of the new RC, so we're ready to go ahead with an incubator vote on the same. Thanks in advance! Karl - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org ++ Chris Mattmann, Ph.D. Senior Computer Scientist NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA Office: 171-266B, Mailstop: 171-246 Email: chris.a.mattm...@nasa.gov WWW: http://sunset.usc.edu/~mattmann/ ++ Adjunct Assistant Professor, Computer Science Department University of Southern California, Los Angeles, CA 90089 USA
Re: License text needed for dependencies or URL is enough? (was: Re: [VOTE] Apache Chemistry OpenCMIS 0.2.0-incubating (RC1))
The best way to get this clarified would be to ask the the ASF legal folks, http://www.apache.org/legal/, either be emailing legal-disc...@apache.org, or best, raise a JIRA at https://issues.apache.org/jira/browse/LEGAL. ...ant On Fri, Jan 21, 2011 at 5:41 PM, Gabriele Columbro colum...@gmail.com wrote: Hi Ant, first off thanks for taking time for testing this release and giving us the final and so much needed +1. Will send vote result email right away. About licensing concerns, our first release (0.1.0 RC1) was rejected for this kind of reasons and we *should* have fixed those in 0.1.0-RC2 (as per https://issues.apache.org/jira/browse/CMIS-224). @IPMC: any comments on whether license URL is fine or the full license text should be included for dependencies? I'm also wondering how other projects using the standard Maven Apache release process deal with this, as our DEPENDENCIES file are generated according to that logic. Thanks for any comment! Gab On Jan 20, 2011, at 3:22 PM, ant elder wrote: +1 from me. Though a little reluctantly because while it looks mostly good the chemistry-opencmis-client-impl-0.2.0-incubating-with-dependencies.zip does not include the text of all the licenses of the included dependencies it only has URLs to the license text. I thought including the full license text was a requirement but hunting around now i can't find anything that states that. ...ant On Wed, Jan 19, 2011 at 3:17 PM, Gabriele Columbro colum...@gmail.com wrote: Hi all, just a reminder for this vote, which is now been open for a full week. On Jan 17, 2011, at 1:04 PM, Nick Burch wrote: Just need one more IPMC +1 and we're done. Anyone able to review and vote? As Nick correctly mentions here, we just need one more IPMC +1 to get this release out. Would be great if someone can take this on, so we can move forward with pushing out the release. Thanks in advance, Gab Nick - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Eng. Gabriele Columbro Alfresco Software, Ltd. Blog: http://www.mindthegab.com Twitter: http://twitter.com/mindthegabz - 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 -- Eng. Gabriele Columbro Alfresco Software, Ltd. Blog: http://www.mindthegab.com Twitter: http://twitter.com/mindthegabz - 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][REMINDER] Release Apache Chemistry cmislib 0.4 incubating
Did you see the -1 vote from Stefan - http://apache.markmail.org/message/bba6t6xifdgfwwxg Probably need to address that, even if its just to ask lets just fix it in the next release. ...ant On Tue, Feb 1, 2011 at 9:06 PM, Jeff Potts jeffpott...@gmail.com wrote: Incubator PMC members, This is the second reminder that the Apache Chemistry project is still looking for two +1 IPMC votes to approve the 0.4 incubating release of cmislib. The vote has been open for one week. Please let me know if there is anything I can do to facilitate your review and approval. Jeff Begin forwarded message: From: Jeff Potts jeffpott...@gmail.com Date: January 28, 2011 11:39:45 AM CST To: general@incubator.apache.org Subject: [VOTE][REMINDER] Release Apache Chemistry cmislib 0.4 incubating Incubator PMC members, Just a quick reminder that the Apache Chemistry project is still looking for two +1 IPMC votes to approve the 0.4 incubating release of cmislib. If there is anything I can do to facilitate your review and approval, please let me know. Jeff Begin forwarded message: From: Jeff Potts jeffpott...@gmail.com Date: January 25, 2011 8:36:43 AM CST To: general@incubator.apache.org Cc: chemistry-...@incubator.apache.org Subject: [VOTE] Release Apache Chemistry cmislib 0.4 incubating Incubator PMC members, The cmislib sub-project of Apache Chemistry is ready for its first release since joining the Chemistry project. On behalf of the Chemistry dev team, I'd like to ask your approval to release the packages referenced below as Chemistry cmislib 0.4 incubating. The release has passed the Chemistry PMC vote: http://bit.ly/eqXU2X During the vote, 1 IPMC vote was collected (Nick Burch), so we need 2 more IPMC +1 votes to proceed with the release. You can find the main release candidate artifacts (for distribution at apache.org/dist) at: http://people.apache.org/~jpotts/chemistry/cmislib/0.4/dist These artifacts represent what is currently in cmislib head. The vote is open for 72 hours so please cast your votes! [ ] +1 Release this package as Apache Chemistry cmislib 0.4 incubating [ ] -1 Do not release this package because... Thanks, Jeff - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [WITHDRAW][VOTE] Release Apache Chemistry cmislib 0.4 incubating
If it helps to save a little time, a lot of times people run votes, especially second votes, in parallel on both the dev list and general@ by just CC'ing both on the vote email. ...ant On Wed, Feb 2, 2011 at 6:53 PM, Jeff Potts jeffpott...@gmail.com wrote: I am withdrawing this vote based on Stefan Seelmann's -1 vote. We will address those issues, re-vote in the Chemistry PPMC, and then re-submit here once successful. Jeff - 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: Voting waiting period
On Fri, Feb 4, 2011 at 8:11 PM, Alan D. Cabrera a...@toolazydogs.com wrote: It's my understanding that all voting takes place during a 72 hour period. If that period ends on a weekend then it's customary to wait until Monday to complete. I don't see this documented on http://incubator.apache.org/guides/ppmc.html. We may also need to explain that all correspondence on behalf of the PPMC should cc the PPMC private list. Thoughts? Regards, Alan Well i've found this an interesting thread, i'd always thought the at least 72 hours was one of the rules so it was interesting to hear people saying it was flexible, and after looking i've not found any policy doc saying it MUST be at least 72 hours. Thanks for bring it up. ...ant - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept Howl as an Incubator Project
On Wed, Feb 23, 2011 at 3:59 PM, Kevan Miller kevan.mil...@gmail.com wrote: On Feb 23, 2011, at 4:55 AM, Alex Karasulu wrote: +1 However there might be a name conflict with the Howl transaction log over at object web here: http://howl.ow2.org/ http://howl.ow2.org/Originally from the title, I immediately thought the proposal was for OW's HOWL implementation to enter the incubator. Agreed about the name conflict. I made the same assumption. And I also did too. IMHO this should pick a different name. And i think this should be resolved before the incubation starts so that if the decision is taken to rename then all the mailing lists etc don't need to get renamed after they're created. ...ant ...ant - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept Howl as an Incubator Project
The naming conflict was discussed but it doesn't seem resolved to me - even just in this vote thread there's a bunch of people bringing it up again. I'd guess thats just going to continue while the name is kept, which be avoided by picking a new name now. I expect there will be enough votes in this thread to carry on with the incubation regardless, but as i said IMHO it would be better to just bite the bullet and pick a new name now. ...ant On Wed, Feb 23, 2011 at 4:40 PM, Alan Gates ga...@yahoo-inc.com wrote: The naming conflict issue was brought up and resolved during the discussion of the proposal. Please see http://tinyurl.com/5w7y9p9. Alan. On Feb 23, 2011, at 8:22 AM, dsh wrote: http://www.porchdogsoft.com/ as well provides a Zeroconf implementation called Howl and I am not sure whether Porchdog Software finally got acquired by Apple. The favicon and certain information on the site could make you think Apple did exactly that. Cheers Daniel On Wed, Feb 23, 2011 at 5:17 PM, ant elder ant.el...@gmail.com wrote: On Wed, Feb 23, 2011 at 3:59 PM, Kevan Miller kevan.mil...@gmail.com wrote: On Feb 23, 2011, at 4:55 AM, Alex Karasulu wrote: +1 However there might be a name conflict with the Howl transaction log over at object web here: http://howl.ow2.org/ http://howl.ow2.org/Originally from the title, I immediately thought the proposal was for OW's HOWL implementation to enter the incubator. Agreed about the name conflict. I made the same assumption. And I also did too. IMHO this should pick a different name. And i think this should be resolved before the incubation starts so that if the decision is taken to rename then all the mailing lists etc don't need to get renamed after they're created. ...ant ...ant - 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 - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept Rave into the Incubator
+1 ...ant On Fri, Feb 25, 2011 at 12:08 AM, Ate Douma a...@douma.nu wrote: Given the feedback received so far I think the Rave proposal is in good shape so I'd like to bring up the vote for accepting Rave into the Incubator. The proposal is at: http://wiki.apache.org/incubator/RaveProposal and also copied as text below. Please vote. [ ] +1 Accept Rave into the incubator [ ] +0 Don't care' [ ] -1 Reject for the following reason: I'll close the vote at Tuesday morning 1st March CET to accommodate for the coming weekend. That's a little over 5 days from now. Regards, Ate - COPY OF PROPOSAL FROM http://wiki.apache.org/incubator/RaveProposal - = Apache Rave Proposal = == Abstract == Apache Rave is A new WEb And SOcial Mashup Engine. It will provide an out-of-the-box as well as an extendible lightweight Java platform to host, serve and aggregate (Open)Social Gadgets and services through a highly customizable and Web 2.0 friendly front-end. Rave is targeted as engine for internet and intranet portals and as building block to provide context-aware personalization and collaboration features for multi-site/multi-channel (mobile) oriented and content driven websites and (social) network oriented services and platforms. For the [[http://www.opensocial.org/|OpenSocial]] container and services the (Java) [[http://shindig.apache.org|Apache Shindig]] will be integrated. At a later stage further generalization is envisioned to also transparently support [[http://www.w3.org/TR/widgets/|W3C Widgets]] using [[http://incubator.apache.org/wookie/|Apache Wookie]]. == Proposal == The reason for starting Rave is to bring together and combine several existing projects and teams currently working towards more or less the same or overlapping goals but each in their own small(er) target audience and community. The goal for Rave is to become a lightweight and open-standards based extendible platform for using, integrating and hosting !OpenSocial and W3C Widget related features, technologies and services. It will also provide strong context-aware personalization, collaboration and content integration capabilities and a high quality out-of-the-box installation as well as be easy to integrate in other platforms and solutions. The initial features for Rave will at least be based on the current capabilities from the contributing external projects, for which they will provide the necessary code contributions. However, the code base for Rave will be built anew with strong focus on generalization, customization and extendibility to support the intended multi-purpose adoption and integration. The contributing external projects will start using and switch to the new Rave based solution as soon as the initial features become available to ensure the continued participation and interest from their side as well as their own communities. The intended initial features include: '''Core Features''' 1. Advanced !OpenSocial compliance and optional features support 1. !OpenSocial persistence and SPI (Service Provider Interface) implementation 1. Self-service application administration including security, gadget management and page templates 1. User and group management with full privacy model 1. Gadget repository with life-cycle management (install/update/remove) and extended meta data (categories, comments, ratings, etc.) 1. Dynamic and highly customizable front-end engine (skins, pages, tabs, layouts, navigation) 1. Full OAuth support 1. Support for security restrictions on both Gadgets and page/tag/layout customizations 1. Set of common and general purpose Gadgets to be usable out-of-the-box 1. Support for inter-gadget messaging with examples '''Extensible Features''' 1. Pluggable persistence 1. Pluggable security model with example modules for authentication and authorization 1. Support for !OpenSocial extensions not (yet) defined in the specification 1. Support for other (non-standard, yet) pluggable container services and extensions Beyond these initial features the vision and scope for Rave goes much further and includes integrating and providing other highly desired/needed features like: * native W3C Widgets support through [[http://incubator.apache.org/wookie|Apache Wookie]] * pluggable and extendible content integration and management services * space extensions and management features, like http://wiki.opensocial.org/index.php?title=Space_extension * context aware features and extensions integration for personalized and social network and (mobile) device oriented sites and channels * enhanced client-side widget messaging, coordination and co-location support like using [[http://www.openajax.org|OpenAjax]] Hub and Registry * space, page and Gadget based linking, navigation, coordination and collaboration * inline widget rendering, like http://issues.apache.org/jira/browse/SHINDIG-1402 *
Re: [PROPOSAL] MRUnit entry into the Apache Incubator
On Sun, Feb 27, 2011 at 10:00 PM, Eric Sammer esam...@cloudera.com wrote: == Rationale == MRUnit has existed as a contrib component of Apache Hadoop. This has served to introduce users to the library and to provide necessary functionality to developers in the form of development support. That said, MRUnit is not necessarily an intrinsic component of Hadoop proper and could benefit from being a standalone project in that: * A separate project would support an independent development and release schedule allowing for faster iteration and response to user requests. * Separating adjunct projects from the core Hadoop codebase simplifies Hadoop's build and release. * MRUnit users can get a simpler artifact in a way most appropriate to development time (i.e. Maven or Ivy repositories). * MRUnit can build out independent support for different versions of Hadoop without requiring circular dependencies or testing issues. I don't know, none of those things really sound like justification for a separate TLP, keeping something like this nearby to Hadoop MapReduce seems like it would help give it a better chance of long term survival to me. Wouldn't simply moving mrunit out from hadoop/mapreduce/trunk/src to somewhere else so it can do its own releases and deploy its artifacts achieve all those objectives? ...ant - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] MRUnit entry into the Apache Incubator
On Mon, Feb 28, 2011 at 2:57 PM, Mattmann, Chris A (388J) chris.a.mattm...@jpl.nasa.gov wrote: Hi Guys, I don't know, none of those things really sound like justification for a separate TLP, keeping something like this nearby to Hadoop MapReduce seems like it would help give it a better chance of long term survival to me. Wouldn't simply moving mrunit out from hadoop/mapreduce/trunk/src to somewhere else so it can do its own releases and deploy its artifacts achieve all those objectives?... Personally I don't believe that the project has any chance for survival at Apache unless this Incubator project happens. The Hadoop community has been VOTE'ing over the past month to abandon development of portions of their code base (namely contrib portions that no developers or users are maintaining or leveraging). MRUnit came up as one of those contribs, and what was discovered was that some of the issues with the Hadoop community (electing new committers, having too many products tied to a single release cycle, too many infrequent releases) had stagnated the development of MRUnit so much that a small sect of Hadoop developers had forked MRUnit into Github and were developing it there. So there *was* active development going on, it just wasn't at Apache. A few of us members (myself, Patrick and Nige) were willing to step up and volunteer that in contrast to seeing an ASF product and its community head over to Github and continue development there, we'd like the product to stick around at the ASF. There is no hard and fast rule as to the size of a community for TLP-status, and that's far down the road anyways aka why are we worrying about that now during a [PROPOSAL] phase when it's an *exit criteria* for the Incubator? The point of Incubation is to help grow that community and sort that stuff out and I have no doubt in my mind that these folks here on the proposal who are willing and trying to develop something successful at Apache can't meet that challenge. You're right about the entry criteria, there's a very low bar to becoming an Incubator poddling so if you all really want to I'm pretty sure you'll be able to make it happen. But this is a proposal discussion thread which asks for feedback so thats what i gave. Now that you've explained further I even more think it doesn't seem quite right. Sounds to me like the Hadoop PMC is a bit disfunctional if they couldn't make these guys committers and pushed them off to github and maybe it would be better to just fix that. Or split MapReduce out of Hadoop to its own new TLP which you'd think would be more willing to embrace MRUnit. ...ant - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] MRUnit entry into the incubator
As commented in the proposal thread I'm pretty dubious that incubation is the best approach for this, so i vote 0. The potential committers for MRUnit are MapReduce users and developers so moving this away and having separate mailing lists means they'll lose all sight of it. At the very least I think there should not be a mrunit-user list created and instead the MapReduce user list should be used to keep some visibility over there. I don't understand the reasons why its hard to have a separate release cycle for this within Hadoop - just svn move the code up out of from being within mapreduce like is done with the other Hadoop subprojects. Hopefully this would graduate to being a sub-project of Hadoop so thats exactly where it will end up. ...ant On Wed, Mar 2, 2011 at 1:16 AM, Eric Sammer esam...@cloudera.com wrote: All: Discussions from the [PROPOSAL] thread seem to have tapered off so I'd like to call a vote on accepting MRUnit into the incubator. I'm re-pasting the proposal for simplicity. We'll leave the vote open for 72 hours. Thanks! = MRUnit, a library to support unit testing of Hadoop MapReduce jobs = == Abstract == MRUnit is a java library that provides mocks and infrastructure for writing unit tests for Hadoop MapReduce jobs and related components. == Proposal == MRUnit is a java library to facilitate unit testing of Hadoop MapReduce jobs by providing drivers and mock objects to simulate the Hadoop runtime environment of a map reduce job. This code base already exists as a subproject of the Apache Hadoop MapReduce project and lives in the contrib directory of the source tree. == Background == Writing unit tests of MapReduce jobs can be a tedious process. User code can quickly become entangled with Hadoop APIs making testing difficult and error prone. In many cases, users will simply forgo testing given the complexity of the environment. MRUnit was created as a simple library users can use in conjunction with test suites like JUnit to provide a harness for injecting appropriate mock objects. == Rationale == MRUnit has existed as a contrib component of Apache Hadoop. This has served to introduce users to the library and to provide necessary functionality to developers in the form of development support. That said, MRUnit is not necessarily an intrinsic component of Hadoop proper and could benefit from being a standalone project in that: * A separate project would support an independent development and release schedule allowing for faster iteration and response to user requests. * Separating adjunct projects from the core Hadoop codebase simplifies Hadoop's build and release. * MRUnit users can get a simpler artifact in a way most appropriate to development time (i.e. Maven or Ivy repositories). * MRUnit can build out independent support for different versions of Hadoop without requiring circular dependencies or testing issues. Having greater development and tooling support for Hadoop makes the project accessible to a wider audience by reducing the chance of bugs. == Initial Goals == * Provide a new home for the existing codebase. * Make artifacts available via Maven and / or Ivy. * Expand test support for other Hadoop components (e.g. Partitioners) * Establish a lightweight, independent release cycle. == Current Status == === Meritocracy === MRUnit was originally created by Aaron Kimball, and has had some contributions from members of the Hadoop community. By becoming its own project, significant contributors to MRUnit would become committers, and allow the project to grow. === Community === The MRUnit community is predominantly composed of engineers who author MapReduce jobs running against Apache Hadoop. Given that this library appeals to a specific subset of the overall Apache Hadoop community, it makes sense to decouple its release cycle from that of Hadoop as a whole, to allow more rapid iteration in this space. === Core developers === Aaron Kimball wrote most of the original code and is familiar with open source and Apache-style development, being a Hadoop committer. A number of other contributors have provided patches to this codebase over time. Eric Sammer has worked as a committer on Flume, a github-based open source project. === Alignment === MRUnit aligns with Hadoop as it aims to be a testing harness and framework for the Hadoop MapReduce framework. == Known Risks == === Orphaned products === All members of the team are committed to making MRUnit a success. === Inexperience with Open Source === The initial code comes from Hadoop where it was developed in an open-source, collaborative way. All the initial committers are committers on other Apache projects (with the exception of Eric who is experienced with open source development at Github and other communities), and are experienced in working with new contributors. === Homogenous Developers === The initial set of committers is
Re: [VOTE] Release Apache Lucene.Net 2.9.2-incubating-RC2
Looks good to me, +1. It would be nice to include some sort of release notes or changes file within the distributions ...ant On Wed, Mar 2, 2011 at 8:17 AM, Troy Howard thowar...@gmail.com wrote: All, I'm happy to announce that Lucene.Net 2.9.2-incubating-RC2 is available and ready for your testing and voting. This will be our first release since returning to the Incubator. We look forward to your input. Release candidate artifacts: http://people.apache.org/~thoward/Lucene.Net/2.9.2-incubating-RC2/dist/ SVN tag revision: http://svn.apache.org/repos/asf/incubator/lucene.net/tags/Lucene.Net_2_9_2_RC2 PPMC Vote Thread: http://bit.ly/eGcbYY The vote is open for 72 hours and passes if a majority of at least three +1 Lucene.Net PMC votes are cast. Please cast your votes! [ ] +1 Release this package as Apache Lucene.Net 2.9.2-incubating [ ] -1 Do not release this package because... Thanks to everyone involved for the hard work and contributions which made this release possible. Thanks, Troy - 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
