Re: [PROPOSAL] Stonehenge
Bertrand Great feedback. I think we should keep a clear statement in the SVN and distros that identifies which parts of the project use which dependencies. I also think we should structure the build so that each different framework implementation of each application is a separate build target. We can then put together an overall build that does cross-framework build and test. Thanks Paul On Wed, Nov 12, 2008 at 7:47 AM, Bertrand Delacretaz [EMAIL PROTECTED] wrote: On Tue, Nov 4, 2008 at 5:34 PM, Paul Fremantle [EMAIL PROTECTED] wrote: ...The full proposal is here: http://wiki.apache.org/incubator/StonehengeProposal.. That says future contributions could depend on proprietary systems such as Microsoft .Net or commercial JEE servers, which IIUC means that some parts of Stonehenge might not be buildable or testable using open source tools. We certainly already have some such code in our projects, and I'm no against that - but I'd like the Stonehenge people to keep such parts well separated, to allow people who only use open source tools to benefit from the project as well. As the project is about interoperability, that's somewhat obvious anyway, but still worth mentioning IMHO. -Bertrand - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Paul Fremantle Co-Founder and CTO, WSO2 Apache Synapse PMC Chair OASIS WS-RX TC Co-chair blog: http://pzf.fremantle.org [EMAIL PROTECTED] Oxygenating the Web Service Platform, www.wso2.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [REPORTS] missing: Abdera BlueSky Buildr Droids Hama JSecurity Lokahi Olio PDFBox PhotArk Tashi VCL WSRP4J XAP
Bertrand Delacretaz wrote: Please add your reports at http://wiki.apache.org/incubator/November2008 Real Soon. -Bertrand - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Hmmm... JSecurity is still due ? I thought it was ok as soon as it provided the 4 first monthly reports. If so, I will try to whip a quick report by tonite. Thanks ! -- -- cordialement, regards, Emmanuel Lécharny www.iktek.com directory.apache.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [REPORTS] missing: Abdera BlueSky Buildr Droids Hama JSecurity Lokahi Olio PDFBox PhotArk Tashi VCL WSRP4J XAP
On Wed, Nov 12, 2008 at 10:02 AM, Emmanuel Lecharny [EMAIL PROTECTED] wrote: ...Hmmm... JSecurity is still due ? I thought it was ok as soon as it provided the 4 first monthly reports It's still listed under monthly at http://wiki.apache.org/incubator/ReportingSchedule, but you're right, after 3 months a podling goes to the normal schedule. So I think you can remove it from monthly at http://wiki.apache.org/incubator/ReportingSchedule, and remove it from http://wiki.apache.org/incubator/November2008 -Bertrand - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [REPORTS] missing: Abdera BlueSky Buildr Droids Hama JSecurity Lokahi Olio PDFBox PhotArk Tashi VCL WSRP4J XAP
Bertrand Delacretaz wrote: On Wed, Nov 12, 2008 at 10:02 AM, Emmanuel Lecharny [EMAIL PROTECTED] wrote: ...Hmmm... JSecurity is still due ? I thought it was ok as soon as it provided the 4 first monthly reports It's still listed under monthly at http://wiki.apache.org/incubator/ReportingSchedule, but you're right, after 3 months a podling goes to the normal schedule. So I think you can remove it from monthly at http://wiki.apache.org/incubator/ReportingSchedule, and remove it from http://wiki.apache.org/incubator/November2008 Ok, done. I still have added a very short report on JSecurity this month, just to inform that we have moved the codee base to the ASF repo. Thanks Bertrand ! -- -- cordialement, regards, Emmanuel Lécharny www.iktek.com directory.apache.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Graduate Buildr as TLP
On Wednesday 12 November 2008 9:05:55 am Alex Boisvert wrote: Hi Paul, I cross-checked all the votes with this file: https://svn.apache.org/repos/private/committers/board/committee-info.txt (r15883) And did not see Daniel Kulp's name listed under the Incubator PMC. Did I miss something? Looks like Noel hasn't been keeping the list up to date with the acks from the board :-( Dan alex On Tue, Nov 11, 2008 at 11:09 PM, Paul Fremantle [EMAIL PROTECTED] wrote: Actually Daniel K's vote is binding, but that doesn't change the outcome. Congratulations! Paul On Wed, Nov 12, 2008 at 5:50 AM, Alex Boisvert [EMAIL PROTECTED] wrote: The vote to approve the graduation of Buildr as a top-level project has now ended with 13 +1 votes (incl. 8 binding) and no other votes. Binding: * Martijn Dashorst * Bertrand Delacrétaz * Paul Fremantle * Jim Jagielski * Gianugo Rabellino * Matthieu Riou * Craig L. Russell * Yoav Shapira Non-binding: * Niklas Gustavsson * Erik Hatcher * Daniel Kulp * Luciano Resende * Carl Trieloff Thank you for your participation and congratulations to the Buildr project for this important milestone! alex On Thu, Nov 6, 2008 at 9:03 AM, Alex Boisvert [EMAIL PROTECTED] wrote: Hi, The Buildr community is requesting to graduate from the incubator as a top-level project. We've recently held a vote http://n2.nabble.com/-VOTE--Graduation-Board-Resolution-td1347057.htmlto gauge the support of the community and feedback was all positive. The project meets all incubator requirements and guidelines and has been in the incubator for a little more than one year. There have been several releases, the community is growing steadily, no pending IP issues and development is pretty active. For background you can see our incubation status page: http://incubator.apache.org/projects/buildr.html After soliciting feedback on this list 5 days ago, I am now asking the Incubator PMC to approve this graduation. Please vote on approving the graduation of Buildr. This vote is open for the next 72 hours and only votes from Incubator PMC members are binding. [ ] +1 Approve graduation of Buildr as a Top-Level Project [ ] -1 Buildr is not ready to graduate --- 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 a Ruby-based build system that is suitable for small and large projects and multi-lingual integration, for distribution at no charge to the public. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the The Apache Buildr Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that The Apache Buildr Project be and hereby is responsible for the creation and maintenance of a software project related to a Ruby-based build system that is suitable for small and large projects and multi-lingual integration. RESOLVED, that the office of Vice President, Apache Buildr be and hereby is created, the person holding such office to serve at the direction of the Board of Directors as the chair of The Apache Buildr Project, and to have primary responsibility for management of the projects within the scope of responsibility of The Apache Buildr Project; 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 Buildr Project: - Assaf Arkin ([EMAIL PROTECTED]) - Alex Boisvert ([EMAIL PROTECTED]) - Victor Hugo Borja ([EMAIL PROTECTED]) - Antoine Contal ([EMAIL PROTECTED]) - Matthieu Riou ([EMAIL PROTECTED]) NOW, THEREFORE, BE IT FURTHER RESOLVED, that Alex Boisvert be and hereby is appointed to the office of Vice President, Apache Buildr, 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 the initial Apache Buildr PMC be and hereby is tasked with the creation of a set of bylaws intended to encourage open development and increased participation in the Apache Buildr Project; and be it further RESOLVED, that the initial Apache Buildr Project be and hereby is tasked with the migration and rationalization of the Apache Incubator Buildr podling; and be it further RESOLVED, that all responsibility pertaining to the Apache Incubator
Re: [REPORTS] missing: Abdera BlueSky Buildr Droids Hama JSecurity Lokahi Olio PDFBox PhotArk Tashi VCL WSRP4J XAP
Nope, JSecurity reported from July to October 2008 and is now on three month schedule. This reminder was generated from out-of-date info. Craig On Nov 12, 2008, at 1:02 AM, Emmanuel Lecharny wrote: Bertrand Delacretaz wrote: Please add your reports at http://wiki.apache.org/incubator/November2008 Real Soon. -Bertrand - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Hmmm... JSecurity is still due ? I thought it was ok as soon as it provided the 4 first monthly reports. If so, I will try to whip a quick report by tonite. Thanks ! -- -- cordialement, regards, Emmanuel Lécharny www.iktek.com directory.apache.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Craig L Russell Architect, Sun Java Enterprise System http://db.apache.org/jdo 408 276-5638 mailto:[EMAIL PROTECTED] P.S. A good JDO? O, Gasp! smime.p7s Description: S/MIME cryptographic signature
Re: [REPORTS] missing: Abdera BlueSky Buildr Droids Hama JSecurity Lokahi Olio PDFBox PhotArk Tashi VCL WSRP4J XAP
On Wed, Nov 12, 2008 at 4:22 PM, Craig L Russell [EMAIL PROTECTED] wrote: Nope, JSecurity reported from July to October 2008 and is now on three month schedule. This reminder was generated from out-of-date info which is a good trigger for updating said info ;-) -Bertrand - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [REPORTS] missing: Abdera BlueSky Buildr Droids Hama JSecurity Lokahi Olio PDFBox PhotArk Tashi VCL WSRP4J XAP
Craig L Russell wrote: Nope, JSecurity reported from July to October 2008 and is now on three month schedule. This reminder was generated from out-of-date info. The info has been updated since then. -- -- cordialement, regards, Emmanuel Lécharny www.iktek.com directory.apache.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Graduate Buildr as TLP
Hi Paul, I cross-checked all the votes with this file: https://svn.apache.org/repos/private/committers/board/committee-info.txt (r15883) And did not see Daniel Kulp's name listed under the Incubator PMC. Did I miss something? alex On Tue, Nov 11, 2008 at 11:09 PM, Paul Fremantle [EMAIL PROTECTED] wrote: Actually Daniel K's vote is binding, but that doesn't change the outcome. Congratulations! Paul On Wed, Nov 12, 2008 at 5:50 AM, Alex Boisvert [EMAIL PROTECTED] wrote: The vote to approve the graduation of Buildr as a top-level project has now ended with 13 +1 votes (incl. 8 binding) and no other votes. Binding: * Martijn Dashorst * Bertrand Delacrétaz * Paul Fremantle * Jim Jagielski * Gianugo Rabellino * Matthieu Riou * Craig L. Russell * Yoav Shapira Non-binding: * Niklas Gustavsson * Erik Hatcher * Daniel Kulp * Luciano Resende * Carl Trieloff Thank you for your participation and congratulations to the Buildr project for this important milestone! alex On Thu, Nov 6, 2008 at 9:03 AM, Alex Boisvert [EMAIL PROTECTED] wrote: Hi, The Buildr community is requesting to graduate from the incubator as a top-level project. We've recently held a vote http://n2.nabble.com/-VOTE--Graduation-Board-Resolution-td1347057.htmlto gauge the support of the community and feedback was all positive. The project meets all incubator requirements and guidelines and has been in the incubator for a little more than one year. There have been several releases, the community is growing steadily, no pending IP issues and development is pretty active. For background you can see our incubation status page: http://incubator.apache.org/projects/buildr.html After soliciting feedback on this list 5 days ago, I am now asking the Incubator PMC to approve this graduation. Please vote on approving the graduation of Buildr. This vote is open for the next 72 hours and only votes from Incubator PMC members are binding. [ ] +1 Approve graduation of Buildr as a Top-Level Project [ ] -1 Buildr is not ready to graduate --- 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 a Ruby-based build system that is suitable for small and large projects and multi-lingual integration, for distribution at no charge to the public. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the The Apache Buildr Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that The Apache Buildr Project be and hereby is responsible for the creation and maintenance of a software project related to a Ruby-based build system that is suitable for small and large projects and multi-lingual integration. RESOLVED, that the office of Vice President, Apache Buildr be and hereby is created, the person holding such office to serve at the direction of the Board of Directors as the chair of The Apache Buildr Project, and to have primary responsibility for management of the projects within the scope of responsibility of The Apache Buildr Project; 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 Buildr Project: - Assaf Arkin ([EMAIL PROTECTED]) - Alex Boisvert ([EMAIL PROTECTED]) - Victor Hugo Borja ([EMAIL PROTECTED]) - Antoine Contal ([EMAIL PROTECTED]) - Matthieu Riou ([EMAIL PROTECTED]) NOW, THEREFORE, BE IT FURTHER RESOLVED, that Alex Boisvert be and hereby is appointed to the office of Vice President, Apache Buildr, 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 the initial Apache Buildr PMC be and hereby is tasked with the creation of a set of bylaws intended to encourage open development and increased participation in the Apache Buildr Project; and be it further RESOLVED, that the initial Apache Buildr Project be and hereby is tasked with the migration and rationalization of the Apache Incubator Buildr podling; and be it further RESOLVED, that all responsibility pertaining to the Apache Incubator Buildr podling encumbered upon the Apache Incubator PMC are hereafter discharged. --- End Proposed Board Resolution --- -- Paul Fremantle Co-Founder and CTO, WSO2 Apache Synapse PMC Chair OASIS WS-RX TC Co-chair blog: http://pzf.fremantle.org [EMAIL PROTECTED] Oxygenating the Web Service Platform,
RE: [PROPOSAL] Stonehenge
+1 -Original Message- From: Paul Fremantle [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 12, 2008 12:22 AM To: general@incubator.apache.org Subject: Re: [PROPOSAL] Stonehenge Bertrand Great feedback. I think we should keep a clear statement in the SVN and distros that identifies which parts of the project use which dependencies. I also think we should structure the build so that each different framework implementation of each application is a separate build target. We can then put together an overall build that does cross-framework build and test. Thanks Paul On Wed, Nov 12, 2008 at 7:47 AM, Bertrand Delacretaz [EMAIL PROTECTED] wrote: On Tue, Nov 4, 2008 at 5:34 PM, Paul Fremantle [EMAIL PROTECTED] wrote: ...The full proposal is here: http://wiki.apache.org/incubator/StonehengeProposal.. That says future contributions could depend on proprietary systems such as Microsoft .Net or commercial JEE servers, which IIUC means that some parts of Stonehenge might not be buildable or testable using open source tools. We certainly already have some such code in our projects, and I'm no against that - but I'd like the Stonehenge people to keep such parts well separated, to allow people who only use open source tools to benefit from the project as well. As the project is about interoperability, that's somewhat obvious anyway, but still worth mentioning IMHO. -Bertrand - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Paul Fremantle Co-Founder and CTO, WSO2 Apache Synapse PMC Chair OASIS WS-RX TC Co-chair blog: http://pzf.fremantle.org [EMAIL PROTECTED] Oxygenating the Web Service Platform, www.wso2.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: any Incubator committer can edit the site
Thanks for the help, Craig. I was able to commit the updates and the website appears to have synced as well. - Michael -Original Message- From: David Crossley [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 12, 2008 2:28 AM To: general@incubator.apache.org Subject: any Incubator committer can edit the site Niclas Hedhman wrote: Craig L Russell wrote: Hi Michael, I found a problem that might be the problem. Can you try it now? To decrypt: The Subversion authorisation was missing the section that enabled the tashi group to edit Incubator pages. Hmmm I thought the STATUS page was a Mentor headache. What a relief! Yes, this is a very important point. Each podling's group of committers can edit the Incubator site, including their status page under i.a.o/projects/ and the general guides documentation. This gets them used to acting as a PMC and not relying on others. If anyone notices documentation that is out-of-date or unclear, then jump in and fix it. http://incubator.apache.org/guides/website.html -David - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[IP CLEARANCE] OpenXML4J
Hi All As per the IP Clearance template, POI has received a software grant for OpenXML4J, and we'd like to get the OK for this. The template in svn is filled out as openxml4j.xml, and the source bundle is available from http://people.apache.org/~nick/OpenXML4J-Grant/ . An appropriate software grant has been received and filed, as have the ccla/iclas. Lazy consensus 72 hours would appear to run to 18:00 GMT on Friday 14th. Please do let me know if we've anything wrong in the process :) Thanks Nick - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [REPORTS] missing: Abdera BlueSky Buildr Droids Hama JSecurity Lokahi Olio PDFBox PhotArk Tashi VCL WSRP4J XAP
I have updated the wiki with the PhotArk report [1] [1] http://wiki.apache.org/incubator/November2008#head-0e5d39e727acbdf47dc06f1dbb0fd2b00e109b86 On Wed, Nov 12, 2008 at 7:34 AM, Emmanuel Lecharny [EMAIL PROTECTED] wrote: Craig L Russell wrote: Nope, JSecurity reported from July to October 2008 and is now on three month schedule. This reminder was generated from out-of-date info. The info has been updated since then. -- -- cordialement, regards, Emmanuel Lécharny www.iktek.com directory.apache.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Luciano Resende Apache Tuscany, Apache PhotArk http://people.apache.org/~lresende http://lresende.blogspot.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: STATUS page confusion.
On Wed, Nov 12, 2008 at 3:37 AM, Niclas Hedhman [EMAIL PROTECTED] wrote: On Wed, Nov 12, 2008 at 11:32 AM, Craig L Russell [EMAIL PROTECTED] wrote: There are a few things wrong with the STATUS template. It also gets the order of graduation votes wrong. Ok. My vote is still to have a JIRA Task template (with subtasks pre-populate) instead. So much more accessible, flexible and accurate. +1 - robert - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[VOTE] Qpid Graduation - for top level
It is with the support of our mentors and a community vote on our dev list that Qpid would like to graduate. In our last graduation vote the incubator PMC felt that the Qpid project should increase its diversity. Over the intervening months Qpid has added more independents to the project PPMC, bringing the diversity to 7 legally independent parties (not counting those mentors who will stay on to help advise), with the PPMC diversity at 5 legally independent parties (also not counting mentors). Qpid also continues to attract more contributors (both independents and large corporates), so the committer pool and diversity should continue to expand as contributors are voted in as committers. Qpid has also made an additional release since the last graduation attempt and is currently working through close down of the next release. Qpid was accepted into the incubator August 2006. Attached is the graduation resolution, Please consider your vote for our graduation. many thanks. Carl. --- 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 distributed messaging, 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 Qpid Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Qpid Project be and hereby is responsible for the creation and maintenance of software related to distributed messaging; a multiple language implementation providing daemons and APIs for publish subscribe, eventing and a wide range of message distribution patterns based on the Advanced Message Queuing Protocol (AMQP) and related technologies such as (transaction management, federation, security, management); and be it further RESOLVED, that the office of Vice President, Qpid be and hereby is created, the person holding such office to serve at the direction of the Board of Directors as the chair of the Apache Qpid Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Qpid Project; 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 Qpid Project: * Aidan Skinner * Alan Conway * Arnaud Simon * Carl Trieloff * Craig Russell * Gordon Sim * Jonathan Robie * John O'Hara * Kim van der Riet * Marnie McCormack * Martin Ritchie * Manuel Teira * Paul Fremantle * Nuno Santos * Rafael Schloming * Rajith Attapattu * Robert Greig * Robert Godfrey * Steve Huston * Ted Ross * Yoav Shapira NOW, THEREFORE, BE IT FURTHER RESOLVED, that Carl Trieloff be appointed to the office of Vice President, Qpid, 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 all responsibility pertaining to the Qpid encumbered upon the Apache Incubator be hereafter discharged.
Re: [VOTE] Qpid Graduation - for top level
+1 ...ant On Wed, Nov 12, 2008 at 8:51 PM, Carl Trieloff [EMAIL PROTECTED] wrote: It is with the support of our mentors and a community vote on our dev list that Qpid would like to graduate. In our last graduation vote the incubator PMC felt that the Qpid project should increase its diversity. Over the intervening months Qpid has added more independents to the project PPMC, bringing the diversity to 7 legally independent parties (not counting those mentors who will stay on to help advise), with the PPMC diversity at 5 legally independent parties (also not counting mentors). Qpid also continues to attract more contributors (both independents and large corporates), so the committer pool and diversity should continue to expand as contributors are voted in as committers. Qpid has also made an additional release since the last graduation attempt and is currently working through close down of the next release. Qpid was accepted into the incubator August 2006. Attached is the graduation resolution, Please consider your vote for our graduation. many thanks. Carl. --- 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 distributed messaging, 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 Qpid Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Qpid Project be and hereby is responsible for the creation and maintenance of software related to distributed messaging; a multiple language implementation providing daemons and APIs for publish subscribe, eventing and a wide range of message distribution patterns based on the Advanced Message Queuing Protocol (AMQP) and related technologies such as (transaction management, federation, security, management); and be it further RESOLVED, that the office of Vice President, Qpid be and hereby is created, the person holding such office to serve at the direction of the Board of Directors as the chair of the Apache Qpid Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Qpid Project; 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 Qpid Project: * Aidan Skinner * Alan Conway * Arnaud Simon * Carl Trieloff * Craig Russell * Gordon Sim * Jonathan Robie * John O'Hara * Kim van der Riet * Marnie McCormack * Martin Ritchie * Manuel Teira * Paul Fremantle * Nuno Santos * Rafael Schloming * Rajith Attapattu * Robert Greig * Robert Godfrey * Steve Huston * Ted Ross * Yoav Shapira NOW, THEREFORE, BE IT FURTHER RESOLVED, that Carl Trieloff be appointed to the office of Vice President, Qpid, 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 all responsibility pertaining to the Qpid encumbered upon the Apache Incubator be hereafter discharged. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Qpid Graduation - for top level
My +1 (mentor/IPMC) Paul On Wed, Nov 12, 2008 at 9:03 PM, ant elder [EMAIL PROTECTED] wrote: +1 ...ant On Wed, Nov 12, 2008 at 8:51 PM, Carl Trieloff [EMAIL PROTECTED] wrote: It is with the support of our mentors and a community vote on our dev list that Qpid would like to graduate. In our last graduation vote the incubator PMC felt that the Qpid project should increase its diversity. Over the intervening months Qpid has added more independents to the project PPMC, bringing the diversity to 7 legally independent parties (not counting those mentors who will stay on to help advise), with the PPMC diversity at 5 legally independent parties (also not counting mentors). Qpid also continues to attract more contributors (both independents and large corporates), so the committer pool and diversity should continue to expand as contributors are voted in as committers. Qpid has also made an additional release since the last graduation attempt and is currently working through close down of the next release. Qpid was accepted into the incubator August 2006. Attached is the graduation resolution, Please consider your vote for our graduation. many thanks. Carl. --- 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 distributed messaging, 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 Qpid Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Qpid Project be and hereby is responsible for the creation and maintenance of software related to distributed messaging; a multiple language implementation providing daemons and APIs for publish subscribe, eventing and a wide range of message distribution patterns based on the Advanced Message Queuing Protocol (AMQP) and related technologies such as (transaction management, federation, security, management); and be it further RESOLVED, that the office of Vice President, Qpid be and hereby is created, the person holding such office to serve at the direction of the Board of Directors as the chair of the Apache Qpid Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Qpid Project; 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 Qpid Project: * Aidan Skinner * Alan Conway * Arnaud Simon * Carl Trieloff * Craig Russell * Gordon Sim * Jonathan Robie * John O'Hara * Kim van der Riet * Marnie McCormack * Martin Ritchie * Manuel Teira * Paul Fremantle * Nuno Santos * Rafael Schloming * Rajith Attapattu * Robert Greig * Robert Godfrey * Steve Huston * Ted Ross * Yoav Shapira NOW, THEREFORE, BE IT FURTHER RESOLVED, that Carl Trieloff be appointed to the office of Vice President, Qpid, 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 all responsibility pertaining to the Qpid encumbered upon the Apache Incubator be hereafter discharged. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Paul Fremantle Co-Founder and CTO, WSO2 Apache Synapse PMC Chair OASIS WS-RX TC Co-chair blog: http://pzf.fremantle.org [EMAIL PROTECTED] Oxygenating the Web Service Platform, www.wso2.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Qpid Graduation - for top level
On Wed, Nov 12, 2008 at 6:05 PM, Paul Fremantle [EMAIL PROTECTED] wrote: My +1 (mentor/IPMC) I never know if we need to vote again ;) My +1 as well, with both mentor and IPMC hats. Yoav - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: STATUS page confusion.
Niclas Hedhman wrote: Craig L Russell wrote: There are a few things wrong with the STATUS template. It also gets the order of graduation votes wrong. Ok. My vote is still to have a JIRA Task template (with subtasks pre-populate) instead. So much more accessible, flexible and accurate. How about reducing the content of those Status pages to the bare essentials, and follow a well-defined template for the actual steps to be done. -David - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Qpid Graduation - for top level
Over the past several months, I've watched the qpid community work together and I'm persuaded that the project is ready to graduate. +1 Craig On Nov 12, 2008, at 12:51 PM, Carl Trieloff wrote: It is with the support of our mentors and a community vote on our dev list that Qpid would like to graduate. In our last graduation vote the incubator PMC felt that the Qpid project should increase its diversity. Over the intervening months Qpid has added more independents to the project PPMC, bringing the diversity to 7 legally independent parties (not counting those mentors who will stay on to help advise), with the PPMC diversity at 5 legally independent parties (also not counting mentors). Qpid also continues to attract more contributors (both independents and large corporates), so the committer pool and diversity should continue to expand as contributors are voted in as committers. Qpid has also made an additional release since the last graduation attempt and is currently working through close down of the next release. Qpid was accepted into the incubator August 2006. Attached is the graduation resolution, Please consider your vote for our graduation. many thanks. Carl. Craig L Russell Architect, Sun Java Enterprise System http://db.apache.org/jdo 408 276-5638 mailto:[EMAIL PROTECTED] P.S. A good JDO? O, Gasp! smime.p7s Description: S/MIME cryptographic signature
Re: [VOTE] Qpid Graduation - for top level
Good job on the community work !!! +1 (non-binding) On Wed, Nov 12, 2008 at 3:51 PM, Craig L Russell [EMAIL PROTECTED] wrote: Over the past several months, I've watched the qpid community work together and I'm persuaded that the project is ready to graduate. +1 Craig On Nov 12, 2008, at 12:51 PM, Carl Trieloff wrote: It is with the support of our mentors and a community vote on our dev list that Qpid would like to graduate. In our last graduation vote the incubator PMC felt that the Qpid project should increase its diversity. Over the intervening months Qpid has added more independents to the project PPMC, bringing the diversity to 7 legally independent parties (not counting those mentors who will stay on to help advise), with the PPMC diversity at 5 legally independent parties (also not counting mentors). Qpid also continues to attract more contributors (both independents and large corporates), so the committer pool and diversity should continue to expand as contributors are voted in as committers. Qpid has also made an additional release since the last graduation attempt and is currently working through close down of the next release. Qpid was accepted into the incubator August 2006. Attached is the graduation resolution, Please consider your vote for our graduation. many thanks. Carl. Craig L Russell Architect, Sun Java Enterprise System http://db.apache.org/jdo 408 276-5638 mailto:[EMAIL PROTECTED] P.S. A good JDO? O, Gasp! -- Luciano Resende Apache Tuscany, Apache PhotArk http://people.apache.org/~lresende http://lresende.blogspot.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: STATUS page confusion.
Niclas Hedhman wrote: Gang, The STATUS template says; quote Ask infrastructure to create source repository modules and grant the committers karma. /quote But I have also been told on lists that the PMC Chair is responsible for Authorization. So what is it? Missing punctuation, perhaps. Ask infrastructure to create source repository modules. Grant the committers karma. Would be better as separate steps. These documents explain that chairs do the second step: http://incubator.apache.org/guides/mentor.html#Set+Up+Repository Those item notes in the project's Status file should link directly to the relevant sections of the Guides documents. The brief item notes are confusing. -David - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Qpid Graduation - for top level
+1 binding Dan On Wednesday 12 November 2008 3:51:31 pm Carl Trieloff wrote: It is with the support of our mentors and a community vote on our dev list that Qpid would like to graduate. In our last graduation vote the incubator PMC felt that the Qpid project should increase its diversity. Over the intervening months Qpid has added more independents to the project PPMC, bringing the diversity to 7 legally independent parties (not counting those mentors who will stay on to help advise), with the PPMC diversity at 5 legally independent parties (also not counting mentors). Qpid also continues to attract more contributors (both independents and large corporates), so the committer pool and diversity should continue to expand as contributors are voted in as committers. Qpid has also made an additional release since the last graduation attempt and is currently working through close down of the next release. Qpid was accepted into the incubator August 2006. Attached is the graduation resolution, Please consider your vote for our graduation. many thanks. Carl. --- 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 distributed messaging, 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 Qpid Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Qpid Project be and hereby is responsible for the creation and maintenance of software related to distributed messaging; a multiple language implementation providing daemons and APIs for publish subscribe, eventing and a wide range of message distribution patterns based on the Advanced Message Queuing Protocol (AMQP) and related technologies such as (transaction management, federation, security, management); and be it further RESOLVED, that the office of Vice President, Qpid be and hereby is created, the person holding such office to serve at the direction of the Board of Directors as the chair of the Apache Qpid Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Qpid Project; 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 Qpid Project: * Aidan Skinner * Alan Conway * Arnaud Simon * Carl Trieloff * Craig Russell * Gordon Sim * Jonathan Robie * John O'Hara * Kim van der Riet * Marnie McCormack * Martin Ritchie * Manuel Teira * Paul Fremantle * Nuno Santos * Rafael Schloming * Rajith Attapattu * Robert Greig * Robert Godfrey * Steve Huston * Ted Ross * Yoav Shapira NOW, THEREFORE, BE IT FURTHER RESOLVED, that Carl Trieloff be appointed to the office of Vice President, Qpid, 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 all responsibility pertaining to the Qpid encumbered upon the Apache Incubator be hereafter discharged. -- Daniel Kulp [EMAIL PROTECTED] http://dankulp.com/blog - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[RESULT] [VOTE] Graduate CouchDB as TLP (Was: Re: Asking for Feedback: CouchDB Graduation)
On Nov 8, 2008, at 15:17 , Jan Lehnardt wrote: thank you all for your comments on whether CouchDB should graduate from the Incubator to a top level project. I think we have your support. On behalf of the Apache CouchDB PPMC I am now calling a vote: [ ] Yes, CouchDB is ready to become a top lavel project at the ASF and the IPMC will recommend the proposed resolution quoted below to the Board. Binding (9 +1, no 0 or -1): - Ted Leung - Matthieu Riou - Niclas Hedhman - Bertrand Delacretaz - Jim Jagielski - Dirk-Willem van Gulik - Craig L Russell - Brian McCallister - Robert Burrell Donkin Non Binding (4 +1, no 0 or -1): - Jan Lehnardt - Noah Slater - Damien Katz - Chris Anderson Thanks everybody! What a great result :) I'm going to propose the resolution to the board now. Cheers Jan -- [ ] No, CouchDB is not yet ready, it should stay in the Incubator. Thank you. Cheers Jan -- On Nov 3, 2008, at 18:19, Jan Lehnardt wrote: Dear Incubator General List, The community and developers of Apache CouchDB deem the project ready for graduation to a top level Apache project. [EMAIL PROTECTED] vote summary: http://mail-archives.apache.org/mod_mbox/incubator-couchdb-dev/200810.mbox/[EMAIL PROTECTED] Message IDs for informal(*) PPMC vote to appoint Damien Katz to become Vice President, CouchDB: [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] (* Sorry we didn't to a formal vote and hence no formal [RESULT] message) -- We would like to ask the IPMC to discuss the following Board resolution to be recommended to the Board. Once your feedback is collected and integrated, we will ask you to vote on the final resolution. Thank you! -- Proposed Board Resolution: Establish the Apache CouchDB project 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 implementing a distributed, fault- tolerant and schema-free document-oriented database 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 CouchDB Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache CouchDB Project be and hereby is responsible for the creation and maintenance of software related to implementing a distributed, fault-tolerant and schema-free document-oriented database; and be it further RESOLVED, that the office of Vice President, CouchDB be and hereby is created, the person holding such office to serve at the direction of the Board of Directors as the chair of the Apache CouchDB Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache CouchDB Project; 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 CouchDB Project: * J Chris Anderson ([EMAIL PROTECTED]) * Damien Katz ([EMAIL PROTECTED]) * Christopher Lenz ([EMAIL PROTECTED]) * Jan Lehnardt ([EMAIL PROTECTED]) * Noah Slater ([EMAIL PROTECTED]) NOW, THEREFORE, BE IT FURTHER RESOLVED, that Damien Katz be appointed to the office of Vice President, CouchDB, 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 the initial Apache CouchDB Project be and hereby is tasked with the creation of a set of bylaws intended to encourage open development and increased participation in the CouchDB Project; and be it further RESOLVED, that the initial Apache CouchDB Project be and hereby is tasked with the migration and rationalization of the Apache Incubator CouchDB podling; and be it further RESOLVED, that all responsibility pertaining to the Apache Incubator CouchDB podling encumbered upon the Apache Incubator PMC are hereafter discharged. -- Again, thanks for your cooperation! For the Apache CouchDB PPMC, Jan -- PS: Thanks to Noah Slater for proofreading. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: STATUS page confusion.
On Thu, Nov 13, 2008 at 7:43 AM, David Crossley [EMAIL PROTECTED] wrote: Niclas Hedhman wrote: Craig L Russell wrote: There are a few things wrong with the STATUS template. It also gets the order of graduation votes wrong. Ok. My vote is still to have a JIRA Task template (with subtasks pre-populate) instead. So much more accessible, flexible and accurate. How about reducing the content of those Status pages to the bare essentials, and follow a well-defined template for the actual steps to be done. I guess bare essentials are highly subjective. I would probably define that as; Apache Etch - Status https://issues.apache.org/jira/browse/INCUBATOR-83 https://issues.apache.org/jira/browse/ETCH-2 and so on... or maybe even a single JIRA issue for the entire Incubation process, linking to the 'start phase' (INCUBATOR-83) and other important issues along the way. Cheers Niclas - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Incubator Project Dissolution for NMaven
Do we have an official process for dissolving a project in the incubator? We had a vote amongst the IPMC members for NMaven yesterday and 3/4 IPMC members voted to dissolve the NMaven project and take it out of the incubator. Is there any official process or do we just update the documentation? Thanks, Jason -- Jason van Zyl Founder, Apache Maven jason at sonatype dot com -- A party which is not afraid of letting culture, business, and welfare go to ruin completely can be omnipotent for a while. -- Jakob Burckhardt
Incubator Project Dissolution for NMaven
Do we have an official process for dissolving a project in the incubator? We had a vote amongst the IPMC members for NMaven yesterday and 3/4 IPMC members voted to dissolve the NMaven project and take it out of the incubator. Is there any official process or do we just update the documentation? Thanks, Jason -- Jason van Zyl Founder, Apache Maven jason at sonatype dot com -- A party which is not afraid of letting culture, business, and welfare go to ruin completely can be omnipotent for a while. -- Jakob Burckhardt
Re: Incubator Project Dissolution for NMaven
Depends on what take it out of the incubator means: - graduation to TLP - graduation to sub project - stop incubation altogether and possibly continue elsewhere Graduation is covered in the graduation guide [1], stopping (aka failing) is not covered in a guide (yet). I assume a formal vote on general@ might be in order, and when that is completed, all resources should be shelved: svn - attic, status page - set status to stopped/failed, remove project from reporting schedule, remove project from active project list on site, add to stopped/failed project list. Close down wiki, update project site to reflect status. Martijn On Thu, Nov 13, 2008 at 4:27 AM, Jason van Zyl [EMAIL PROTECTED] wrote: Do we have an official process for dissolving a project in the incubator? We had a vote amongst the IPMC members for NMaven yesterday and 3/4 IPMC members voted to dissolve the NMaven project and take it out of the incubator. Is there any official process or do we just update the documentation? Thanks, Jason -- Jason van Zyl Founder, Apache Maven jason at sonatype dot com -- A party which is not afraid of letting culture, business, and welfare go to ruin completely can be omnipotent for a while. -- Jakob Burckhardt -- Become a Wicket expert, learn from the best: http://wicketinaction.com Apache Wicket 1.3.4 is released Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: STATUS page confusion.
Niclas Hedhman wrote: David Crossley wrote: Niclas Hedhman wrote: Craig L Russell wrote: There are a few things wrong with the STATUS template. It also gets the order of graduation votes wrong. Ok. My vote is still to have a JIRA Task template (with subtasks pre-populate) instead. So much more accessible, flexible and accurate. How about reducing the content of those Status pages to the bare essentials, and follow a well-defined template for the actual steps to be done. I guess bare essentials are highly subjective. I would probably define that as; Apache Etch - Status https://issues.apache.org/jira/browse/INCUBATOR-83 https://issues.apache.org/jira/browse/ETCH-2 and so on... or maybe even a single JIRA issue for the entire Incubation process, linking to the 'start phase' (INCUBATOR-83) and other important issues along the way. I was referring to each podlings status page, e.g. http://incubator.apache.org/projects/etch.html The status pages need to list the various resources (Website, Tracker, etc.) because they are not consistent across all projects. Clutch gets some information from http://wiki.apache.org/incubator/ReportingSchedule and some more from http://incubator.apache.org/projects/index.html Then it gets hints from each project's status page regarding Website, Tracker, etc. If the hints are wrong or missing, then it tries to guess. Then it parses the news section of each status page. So that is the information that i see as essential. Then Clutch can automatically determine things like the current number of committers and link to the relevant section of Jim's page for the list of podling committers. We IPMC members can then readily follow the state of all podlings at a glance, and go to the various linked resources for more detail. http://incubator.apache.org/clutch.html One more piece of essential information would be the link to the podling's Jira issue, as you propose above, to control the set-up process. If that was defined on each podling's status page then Clutch could add a column for it. -David - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Incubator Project Dissolution for NMaven
On Thu, Nov 13, 2008 at 6:50 AM, Jason Van Zyl [EMAIL PROTECTED] wrote: Do we have an official process for dissolving a project in the incubator? We had a vote amongst the IPMC members for NMaven yesterday and 3/4 IPMC members voted to dissolve the NMaven project and take it out of the incubator. Uhhh I have not seen any vote regarding NMaven in the Incubator PMC. I must assume you meant PPMC or perhaps even Maven PMC. Is there any official process or do we just update the documentation? I think that you have Incubator PMC consensus, so unless someone yells, documentation needs to be updated. Off my head; * STATUS page - Add a note that it is retired. * Website (if any), saying that Incubation retired. * site-author/stylesheets/project.xml - Remove NMaven link. * site-author/projects/index.xml - Move it to Retired section. * Reporting Schedule - http://wiki.apache.org/incubator/ReportingSchedule Cheers Niclas - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [REPORTS] missing: Abdera BlueSky Buildr Droids Hama JSecurity Lokahi Olio PDFBox PhotArk Tashi VCL WSRP4J XAP
According to http://wiki.apache.org/incubator/ReportingSchedule, Hama seems be on December. On Thu, Nov 13, 2008 at 3:01 AM, Luciano Resende [EMAIL PROTECTED] wrote: I have updated the wiki with the PhotArk report [1] [1] http://wiki.apache.org/incubator/November2008#head-0e5d39e727acbdf47dc06f1dbb0fd2b00e109b86 On Wed, Nov 12, 2008 at 7:34 AM, Emmanuel Lecharny [EMAIL PROTECTED] wrote: Craig L Russell wrote: Nope, JSecurity reported from July to October 2008 and is now on three month schedule. This reminder was generated from out-of-date info. The info has been updated since then. -- -- cordialement, regards, Emmanuel Lécharny www.iktek.com directory.apache.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Luciano Resende Apache Tuscany, Apache PhotArk http://people.apache.org/~lresende http://lresende.blogspot.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Best Regards, Edward J. Yoon @ NHN, corp. [EMAIL PROTECTED] http://blog.udanax.org
Re: Incubator Project Dissolution for NMaven
Martijn Dashorst wrote: Depends on what take it out of the incubator means: - graduation to TLP - graduation to sub project - stop incubation altogether and possibly continue elsewhere Graduation is covered in the graduation guide [1], stopping (aka failing) is not covered in a guide (yet). I assume a formal vote on general@ might be in order, and when that is completed, all resources should be shelved: svn - attic, status page - set status to stopped/failed, remove project from reporting schedule, remove project from active project list on site, add to stopped/failed project list. Close down wiki, update project site to reflect status. Some items are listed at: https://issues.apache.org/jira/browse/INCUBATOR-100 document the process for a podling that has decided to go to dormant status -David Jason van Zyl wrote: Do we have an official process for dissolving a project in the incubator? We had a vote amongst the IPMC members for NMaven yesterday and 3/4 IPMC members voted to dissolve the NMaven project and take it out of the incubator. Is there any official process or do we just update the documentation? Thanks, Jason - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: STATUS page confusion.
On Thu, Nov 13, 2008 at 3:20 PM, David Crossley [EMAIL PROTECTED] wrote: Clutch gets some information from http://wiki.apache.org/incubator/ReportingSchedule and some more from http://incubator.apache.org/projects/index.html Then it gets hints from each project's status page regarding Website, Tracker, etc. If the hints are wrong or missing, then it tries to guess. Cool, but shouldn't we then step up and make DOAP format compulsory instead. If Incubator 'leads the way' and show how to utilize doap files into a better greater good, we could get this accepted into ASF on a wider and more visible scale. Cheers Niclas - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [REPORTS] missing: Abdera BlueSky Buildr Droids Hama JSecurity Lokahi Olio PDFBox PhotArk Tashi VCL WSRP4J XAP
On Thu, Nov 13, 2008 at 3:24 PM, Edward J. Yoon [EMAIL PROTECTED] wrote: According to http://wiki.apache.org/incubator/ReportingSchedule, Hama seems be on December. I just removed; * Hama (June - Aug) from the Monthly section. Mentors: You need to get better at this! Cheers Niclas - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Qpid Graduation - for top level
On Wed, Nov 12, 2008 at 9:51 PM, Carl Trieloff [EMAIL PROTECTED] wrote: ...Attached is the graduation resolution, Please consider your vote for our graduation... +1 -Bertrand - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
