Re: [VOTE] Qpid Graduation - for top level
+1 On Wed, Nov 12, 2008 at 9: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. -- 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]
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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Missing project reports
Hi, The following reports are missing from the wiki page [1]: BlueSky Buildr Droids Lokahi Olio Tashi VCL WSRP4J XAP [1] http://wiki.apache.org/incubator/November2008 BR, Jukka Zitting - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Missing project reports
Hi, On Thu, Nov 13, 2008 at 1:01 PM, Jukka Zitting [EMAIL PROTECTED] wrote: The following reports are missing from the wiki page [1]: Hmm, I somehow missed the thread already started by Bertrand. So please ignore this and use Bertrand's thread instead. BR, Jukka Zitting - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [OpenWebBeans] request for mailing lists and SVN
We really need for these stuffs to efficiently continue on the development. There are some great open source developers to work on the project, but I want that setting up all artifacts of the project in the Apache side, svn, jira, mailing lists etc is done before this. I think that discussions must be on the dev mailing lists, and assigning task to us using JIRA for good bookmarking. How long does it take that all these stuffs are done by the infra team? Thanks GE 2008/11/6 Matthias Wessendorf [EMAIL PROTECTED] FYI -- Forwarded message -- From: Matthias Wessendorf [EMAIL PROTECTED] Date: Thu, Nov 6, 2008 at 10:07 AM Subject: [OpenWebBeans] request for mailing lists and SVN To: Infrastructure Apache [EMAIL PROTECTED] Hi infra@ team, I am a mentor of the OpenWebBeans podling ([1]). The project was accepted to go into incubation mode. To get this shindig started, we need some mailing lists: * [EMAIL PROTECTED] * [EMAIL PROTECTED] * [EMAIL PROTECTED] * [EMAIL PROTECTED] Moderator (currently) will be me matzew AT apache DOT org. We also need a SVN repo (see [1]): https://svn.apache.org/repos/asf/incubator/openwebbeans and a JIRA would be great, too: https://issues.apache.org/jira/browse/OPEN-WEBBEANS Or, do you want me to file JIRA tickets for this ? Thanks, Matthias [1] http://wiki.apache.org/incubator/OpenWebBeansProposal -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Gurkan Erdogdu http://gurkanerdogdu.blogspot.com
Re: OpenWebBeans status page (Was: svn commit: r711682)
SVN is not setting now. But you can download all the sources from the sourceforge side [1] for the time being. [1] http://bigfaces.svn.sourceforge.net/viewvc/bigfaces/webbeansimpl/. GE 2008/11/13 Mohammad Nour El-Din [EMAIL PROTECTED] Hi I am interested to access the src code of OpenWenBeans. But the svn repo is not working yet. When it is going to be avail ? On Thu, Nov 13, 2008 at 1:07 PM, Gurkan Erdogdu [EMAIL PROTECTED] wrote: How will we progress on this? As a committer can I produce these pages? Or mentors of the project should do? Thanks; Gurkan 2008/11/6 David Crossley [EMAIL PROTECTED] Author: kevan Date: Wed Nov 5 12:14:38 2008 New Revision: 711682 URL: http://svn.apache.org/viewvc?rev=711682view=rev Log: Generate OpenWebBeans status page Added: incubator/public/trunk/site-author/projects/openwebbeans.xml (with props) incubator/public/trunk/site-publish/projects/openwebbeans.html (with props) Great, but there is more needed. Please see the instructions: http://incubator.apache.org/guides/mentor.html#Initialize+Podling+Status+Page http://incubator.apache.org/guides/website.html#Edit+your+project+status+report It needs to be added to the index page and right-hand panel. -David - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Gurkan Erdogdu http://gurkanerdogdu.blogspot.com -- Thanks - Mohammad Nour - LinkedIn: http://www.linkedin.com/in/mnour Life is like riding a bicycle. To keep your balance you must keep moving - Albert Einstein - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Gurkan Erdogdu http://gurkanerdogdu.blogspot.com
Re: [PROPOSAL] Stonehenge
On 11/12/08, 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. good point apache has developed open source Java stuff for years, even when it was a closed, proprietary platform. but the status of java (closed but no charge) was well and widely known, and open source tools were developed to build and test. this is probably less true in this case. IMHO effective communication to new users and developers will be important, and contributors need to be comfortable working with open source people and tools. so i'd like to throw out a few points for discussion... 1. There should be no barrier for ports of open source code dependent on a proprietary platform to an open one (for example .net to - hypothetically - mono). One great thing about FOSS is that the code gains a life independent of it's creators. I think that everyone involved needs to be comfortable about this possibility, and accept that it's fine to happen on shore (as part of the project) rather than off shore. 2. when developing open source software for proprietary platforms, using open, publicly document APIs is important. AIUI this is the case for .NET 3. payment for development tools to contribute to the project may prove a barrier to new contributions. apache has always used open source build and test tools. this allows anyone with energy to dive in and contribute. i would hope that there would be no barriers to supporting open source build and test environments if volunteers stepped up to create and maintain them. 4. running continuous integration on shore may require licenses. it's important that contributors understand this and don't just start diving in. it may be better to start off shore. 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. pioneering something like http://www.apache.org/legal/3party.html#labeling might be useful more widely - robert - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[VOTE] Abdera Graduation to TLP
After some brief discussion here and a vote on the Abdera private list, it seems everyone is in favor of this, so I'd like to propose that we ask the board to make Abdera a new TLP. It's been quite the long incubation process (started in May 2006!), but I think the Abdera community, while small, is now diverse enough that I have no question as to its ability to survive as its own Apache project. So please vote away. A +1 vote is for sending the following motion to the board for its approval. -garrett 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 framework for building clients and servers for the Atom Publishing Protocol and other related technology, 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 Abdera Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that The Apache Abdera Project be and hereby is responsible for the creation and maintenance of a software project related to a framework for building clients and servers for the Atom Publishing Protocol and other related technology. RESOLVED, that the office of Vice President, Apache Abdera 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 Abdera Project, and to have primary responsibility for management of the projects within the scope of responsibility of The Apache Abdera 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 Abdera Project: - James M. Snell ([EMAIL PROTECTED]) - Garrett Rooney ([EMAIL PROTECTED]) - Stephen Duncan Jr. ([EMAIL PROTECTED]) - Ugo Cei ([EMAIL PROTECTED]) - Dan Diephouse ([EMAIL PROTECTED]) - David Calavera ([EMAIL PROTECTED]) - Jim Ancona ([EMAIL PROTECTED]) NOW, THEREFORE, BE IT FURTHER RESOLVED, that Garrett Rooney be and hereby is appointed to the office of Vice President, Apache Abdera, 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 Abdera 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 Abdera Project; and be it further RESOLVED, that the initial Apache Abdera Project be and hereby is tasked with the migration and rationalization of the Apache Incubator Abdera podling; and be it further RESOLVED, that all responsibility pertaining to the Apache Incubator Abdera podling encumbered upon the Apache Incubator PMC are hereafter discharged. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Abdera Graduation to TLP
On Thu, Nov 13, 2008 at 8:59 AM, Garrett Rooney [EMAIL PROTECTED] wrote: After some brief discussion here and a vote on the Abdera private list, it seems everyone is in favor of this, so I'd like to propose that we ask the board to make Abdera a new TLP. It's been quite the long incubation process (started in May 2006!), but I think the Abdera community, while small, is now diverse enough that I have no question as to its ability to survive as its own Apache project. So please vote away. A +1 vote is for sending the following motion to the board for its approval. Oh, and it goes without saying, +1 from me ;-) -garrett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: OpenWebBeans status page (Was: svn commit: r711682)
Hi I am interested to access the src code of OpenWenBeans. But the svn repo is not working yet. When it is going to be avail ? On Thu, Nov 13, 2008 at 1:07 PM, Gurkan Erdogdu [EMAIL PROTECTED] wrote: How will we progress on this? As a committer can I produce these pages? Or mentors of the project should do? Thanks; Gurkan 2008/11/6 David Crossley [EMAIL PROTECTED] Author: kevan Date: Wed Nov 5 12:14:38 2008 New Revision: 711682 URL: http://svn.apache.org/viewvc?rev=711682view=rev Log: Generate OpenWebBeans status page Added: incubator/public/trunk/site-author/projects/openwebbeans.xml (with props) incubator/public/trunk/site-publish/projects/openwebbeans.html (with props) Great, but there is more needed. Please see the instructions: http://incubator.apache.org/guides/mentor.html#Initialize+Podling+Status+Page http://incubator.apache.org/guides/website.html#Edit+your+project+status+report It needs to be added to the index page and right-hand panel. -David - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Gurkan Erdogdu http://gurkanerdogdu.blogspot.com -- Thanks - Mohammad Nour - LinkedIn: http://www.linkedin.com/in/mnour Life is like riding a bicycle. To keep your balance you must keep moving - Albert Einstein - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: OpenWebBeans status page (Was: svn commit: r711682)
How will we progress on this? As a committer can I produce these pages? Or mentors of the project should do? Thanks; Gurkan 2008/11/6 David Crossley [EMAIL PROTECTED] Author: kevan Date: Wed Nov 5 12:14:38 2008 New Revision: 711682 URL: http://svn.apache.org/viewvc?rev=711682view=rev Log: Generate OpenWebBeans status page Added: incubator/public/trunk/site-author/projects/openwebbeans.xml (with props) incubator/public/trunk/site-publish/projects/openwebbeans.html (with props) Great, but there is more needed. Please see the instructions: http://incubator.apache.org/guides/mentor.html#Initialize+Podling+Status+Page http://incubator.apache.org/guides/website.html#Edit+your+project+status+report It needs to be added to the index page and right-hand panel. -David - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Gurkan Erdogdu http://gurkanerdogdu.blogspot.com
Re: [VOTE] Abdera Graduation to TLP
On Thu, Nov 13, 2008 at 2:59 PM, Garrett Rooney [EMAIL PROTECTED] wrote: ...So please vote away. A +1 vote is for sending the following motion to the board for its approval +1, congrats! -Bertrand - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: OpenWebBeans status page (Was: svn commit: r711682)
you can produce them and upload them to a jira ticket. I doubt that you have write access on the page On Thu, Nov 13, 2008 at 12:07 PM, Gurkan Erdogdu [EMAIL PROTECTED] wrote: How will we progress on this? As a committer can I produce these pages? Or mentors of the project should do? Thanks; Gurkan 2008/11/6 David Crossley [EMAIL PROTECTED] Author: kevan Date: Wed Nov 5 12:14:38 2008 New Revision: 711682 URL: http://svn.apache.org/viewvc?rev=711682view=rev Log: Generate OpenWebBeans status page Added: incubator/public/trunk/site-author/projects/openwebbeans.xml (with props) incubator/public/trunk/site-publish/projects/openwebbeans.html (with props) Great, but there is more needed. Please see the instructions: http://incubator.apache.org/guides/mentor.html#Initialize+Podling+Status+Page http://incubator.apache.org/guides/website.html#Edit+your+project+status+report It needs to be added to the index page and right-hand panel. -David - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Gurkan Erdogdu http://gurkanerdogdu.blogspot.com -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Abdera Graduation to TLP
+1 Dan On Thursday 13 November 2008 8:59:05 am Garrett Rooney wrote: After some brief discussion here and a vote on the Abdera private list, it seems everyone is in favor of this, so I'd like to propose that we ask the board to make Abdera a new TLP. It's been quite the long incubation process (started in May 2006!), but I think the Abdera community, while small, is now diverse enough that I have no question as to its ability to survive as its own Apache project. So please vote away. A +1 vote is for sending the following motion to the board for its approval. -garrett 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 framework for building clients and servers for the Atom Publishing Protocol and other related technology, 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 Abdera Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that The Apache Abdera Project be and hereby is responsible for the creation and maintenance of a software project related to a framework for building clients and servers for the Atom Publishing Protocol and other related technology. RESOLVED, that the office of Vice President, Apache Abdera 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 Abdera Project, and to have primary responsibility for management of the projects within the scope of responsibility of The Apache Abdera 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 Abdera Project: - James M. Snell ([EMAIL PROTECTED]) - Garrett Rooney ([EMAIL PROTECTED]) - Stephen Duncan Jr. ([EMAIL PROTECTED]) - Ugo Cei ([EMAIL PROTECTED]) - Dan Diephouse ([EMAIL PROTECTED]) - David Calavera ([EMAIL PROTECTED]) - Jim Ancona ([EMAIL PROTECTED]) NOW, THEREFORE, BE IT FURTHER RESOLVED, that Garrett Rooney be and hereby is appointed to the office of Vice President, Apache Abdera, 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 Abdera 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 Abdera Project; and be it further RESOLVED, that the initial Apache Abdera Project be and hereby is tasked with the migration and rationalization of the Apache Incubator Abdera podling; and be it further RESOLVED, that all responsibility pertaining to the Apache Incubator Abdera podling encumbered upon the Apache Incubator PMC are hereafter discharged. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Daniel Kulp [EMAIL PROTECTED] http://dankulp.com/blog - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Abdera Graduation to TLP
On Thu, Nov 13, 2008 at 2:59 PM, Garrett Rooney [EMAIL PROTECTED] wrote: After some brief discussion here and a vote on the Abdera private list Why wasn't this done on dev@ (especially the vote)? The Apache Way(tm) suggests that these decisions should be done in public (a quick poll on private@ is not a problem) So please vote away. A +1 vote is for sending the following motion to the board for its approval. I've glanced through the status page, read the last reports and checked the archives and didn't discover an immediate concern—seems like a good time to graduate to me. +1 Martijn - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Abdera Graduation to TLP
On Thu, Nov 13, 2008 at 9:22 AM, Martijn Dashorst [EMAIL PROTECTED] wrote: On Thu, Nov 13, 2008 at 2:59 PM, Garrett Rooney [EMAIL PROTECTED] wrote: After some brief discussion here and a vote on the Abdera private list Why wasn't this done on dev@ (especially the vote)? The Apache Way(tm) suggests that these decisions should be done in public (a quick poll on private@ is not a problem) The discussion included determining the list of people to put on the final PMC list. The actual list of Abdera committers was larger, but many of them had not participated in the project in some time or at all, or had explicitly left the project. Since I didn't want to come right out in a public forum and say you know, I think committer X doesn't deserve to be on the PMC I started the discussion in private. -garrett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Qpid Graduation - for top level
+1 ! (PS: Please add Email addresses to the Resolution). On Nov 12, 2008, at 3: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. --- 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
Jim Jagielski wrote: +1 ! (PS: Please add Email addresses to the Resolution). ack, will do so before I submit it to the board. many thanks Carl. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Abdera Graduation to TLP
+1 On Nov 13, 2008, at 8:59 AM, Garrett Rooney wrote: After some brief discussion here and a vote on the Abdera private list, it seems everyone is in favor of this, so I'd like to propose that we ask the board to make Abdera a new TLP. It's been quite the long incubation process (started in May 2006!), but I think the Abdera community, while small, is now diverse enough that I have no question as to its ability to survive as its own Apache project. So please vote away. A +1 vote is for sending the following motion to the board for its approval. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Abdera Graduation to TLP
On Thu, Nov 13, 2008 at 3:31 PM, Garrett Rooney [EMAIL PROTECTED] wrote: Why wasn't this done on dev@ (especially the vote)? The Apache Way(tm) suggests that these decisions should be done in public (a quick poll on private@ is not a problem) The discussion included determining the list of people to put on the final PMC list. The actual list of Abdera committers was larger, but many of them had not participated in the project in some time or at all, or had explicitly left the project. Since I didn't want to come right out in a public forum and say you know, I think committer X doesn't deserve to be on the PMC I started the discussion in private. OK, good enough for me, though the graduation vote, grafting project task for inclusion in the resolution and (final) proposal could've been done in public. Anyway, good luck on abdera.apache.org! Martijn - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: OpenWebBeans status page (Was: svn commit: r711682)
Thanks a lot On Thu, Nov 13, 2008 at 3:13 PM, Gurkan Erdogdu [EMAIL PROTECTED] wrote: SVN is not setting now. But you can download all the sources from the sourceforge side [1] for the time being. [1] http://bigfaces.svn.sourceforge.net/viewvc/bigfaces/webbeansimpl/. GE 2008/11/13 Mohammad Nour El-Din [EMAIL PROTECTED] Hi I am interested to access the src code of OpenWenBeans. But the svn repo is not working yet. When it is going to be avail ? On Thu, Nov 13, 2008 at 1:07 PM, Gurkan Erdogdu [EMAIL PROTECTED] wrote: How will we progress on this? As a committer can I produce these pages? Or mentors of the project should do? Thanks; Gurkan 2008/11/6 David Crossley [EMAIL PROTECTED] Author: kevan Date: Wed Nov 5 12:14:38 2008 New Revision: 711682 URL: http://svn.apache.org/viewvc?rev=711682view=rev Log: Generate OpenWebBeans status page Added: incubator/public/trunk/site-author/projects/openwebbeans.xml (with props) incubator/public/trunk/site-publish/projects/openwebbeans.html (with props) Great, but there is more needed. Please see the instructions: http://incubator.apache.org/guides/mentor.html#Initialize+Podling+Status+Page http://incubator.apache.org/guides/website.html#Edit+your+project+status+report It needs to be added to the index page and right-hand panel. -David - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Gurkan Erdogdu http://gurkanerdogdu.blogspot.com -- Thanks - Mohammad Nour - LinkedIn: http://www.linkedin.com/in/mnour Life is like riding a bicycle. To keep your balance you must keep moving - Albert Einstein - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Gurkan Erdogdu http://gurkanerdogdu.blogspot.com -- Thanks - Mohammad Nour - LinkedIn: http://www.linkedin.com/in/mnour Life is like riding a bicycle. To keep your balance you must keep moving - Albert Einstein - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PROPOSAL] Stonehenge
Robert Excellent points: ...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. good point apache has developed open source Java stuff for years, even when it was a closed, proprietary platform. but the status of java (closed but no charge) was well and widely known, and open source tools were developed to build and test. this is probably less true in this case. The only pay-for requirement is a Windows OS to run the .NET tools at this point. So for a pure OSS developer, there will be parts of the project which will not be buildable, until MONO implements those parts. However, many Apache projects have Windows builds (e.g. Apache HTTPD), so this won't be unique. 1. There should be no barrier for ports of open source code dependent on a proprietary platform to an open one (for example .net to - hypothetically - mono). +1. I believe that everything Stonehenge is potentially doing is covered by Microsoft's OSPA. Maybe Kamal can comment. One great thing about FOSS is that the code gains a life independent of it's creators. I think that everyone involved needs to be comfortable about this possibility, and accept that it's fine to happen on shore (as part of the project) rather than off shore. +1 2. when developing open source software for proprietary platforms, using open, publicly document APIs is important. AIUI this is the case for .NET +1 3. payment for development tools to contribute to the project may prove a barrier to new contributions. apache has always used open source build and test tools. this allows anyone with energy to dive in and contribute. i would hope that there would be no barriers to supporting open source build and test environments if volunteers stepped up to create and maintain them. I believe that Microsoft already makes all the requirements to build and test the .NET code available to Apache Committers via the MSDN subscriptions it offers. So that is at least a help, if not the final answer. 4. running continuous integration on shore may require licenses. it's important that contributors understand this and don't just start diving in. it may be better to start off shore. +1, tho again an MSDN license should help. 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. pioneering something like http://www.apache.org/legal/3party.html#labeling might be useful more widely +1! Paul - 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: Incubator Project Dissolution for NMaven
On 13-Nov-08, at 2:23 AM, Niclas Hedhman wrote: 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. Sorry, the NMaven IPMC. 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] Thanks, Jason -- Jason van Zyl Founder, Apache Maven jason at sonatype dot com -- You are never dedicated to something you have complete confidence in. No one is fanatically shouting that the sun is going to rise tomorrow. They know it is going to rise tomorrow. When people are fanatically dedicated to political or religious faiths or any other kind of dogmas or goals, it's always because these dogmas or goals are in doubt. -- Robert Pirzig, Zen and the Art of Motorcycle Maintenance - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Abdera Graduation to TLP
On Thu, Nov 13, 2008 at 8:59 AM, Garrett Rooney [EMAIL PROTECTED] wrote: After some brief discussion here and a vote on the Abdera private list, it seems everyone is in favor of this, so I'd like to propose that we ask the board to make Abdera a new TLP. It's been quite the +1. Yoav - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [PROPOSAL] Stonehenge
I'd also point out that there are free SDKs and Express versions of most of the Microsoft development tools [1], targeted at non-commercial developers. See [2] for a neutral discussion of what has been left out of the Express editions. So, while these tools are not open source, there are no barriers that I know of against using them to build and test open source software. [1] http://www.microsoft.com/express/ (Designed for, but usable without Silverlight) [2] http://en.wikipedia.org/wiki/Microsoft_Visual_Studio_Express -Original Message- From: Paul Fremantle [mailto:[EMAIL PROTECTED] Sent: Thursday, November 13, 2008 7:15 AM To: general@incubator.apache.org Subject: Re: [PROPOSAL] Stonehenge 3. payment for development tools to contribute to the project may prove a barrier to new contributions. apache has always used open source build and test tools. this allows anyone with energy to dive in and contribute. i would hope that there would be no barriers to supporting open source build and test environments if volunteers stepped up to create and maintain them. I believe that Microsoft already makes all the requirements to build and test the .NET code available to Apache Committers via the MSDN subscriptions it offers. So that is at least a help, if not the final answer. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Incubator Project Dissolution for NMaven
On 13-Nov-08, at 2:16 AM, 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 Take it out of the incubator and Apache all together. 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] Thanks, Jason -- Jason van Zyl Founder, Apache Maven jason at sonatype dot com -- A man enjoys his work when he understands the whole and when he is responsible for the quality of the whole -- Christopher Alexander, A Pattern Language - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Incubator Project Dissolution for NMaven
The vote was among the NMaven PPMC. Is it required to have an additional IPMC vote or can we just start wrapping it up, letting the developer community know the next steps? Thanks, Shane On Thu, Nov 13, 2008 at 7:11 AM, Jason van Zyl [EMAIL PROTECTED] wrote: On 13-Nov-08, at 2:23 AM, Niclas Hedhman wrote: 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. Sorry, the NMaven IPMC. 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] Thanks, Jason -- Jason van Zyl Founder, Apache Maven jason at sonatype dot com -- You are never dedicated to something you have complete confidence in. No one is fanatically shouting that the sun is going to rise tomorrow. They know it is going to rise tomorrow. When people are fanatically dedicated to political or religious faiths or any other kind of dogmas or goals, it's always because these dogmas or goals are in doubt. -- Robert Pirzig, Zen and the Art of Motorcycle Maintenance - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[VOTE] Accept Stonehenge into the Incubator
The Stonehenge proposal has been around for discussion for a while, and we now have a wide set of contributors and mentors, so I'd like to call a vote. I know there are some other potential mentors and or contributors still considering getting involved, but the normal Apache process of course allows that at any time. The proposal is here: http://wiki.apache.org/incubator/StonehengeProposal And also included at the end: Please vote +1 to accept, or -1 with reasons to not accept as a podling. Paul StonehengeProposal Project Stonehenge Abstract Stonehenge is a set of example applications for Service Oriented Architecture that spans languages and platforms and demonstrates best practise and interoperability. Proposal The aim of the Stonehenge project is to develop a set of sample applications to demonstrate seamless interoperability across multiple underlying platform technologies by using currently defined W3C and OASIS standard protocols. We are proposing this incubator project because we believe that a project that includes a set of sample applications, with multiple language and framework implementations will become a useful and important part of the SOA landscape. It will: * illustrate and develop best practice for interoperable applications that communicate via distributed protocols, * demonstrate interoperability between platforms, * provide sample code upon which SOA developers can build, * help identify interoperability issues and their solutions, and * build confidence in cross-platform deployment of SOA technologies. We believe that pursuit of these objectives at Apache has a number of significant benefits: 1. Attractiveness of Apache to the wide range of vendors and customers willing to participate in the conception, development, and implementation of new scenarios. 2. A well-established, neutral forum and process for architectural design and implementation. 3. The flexibility of the Apache License to allow users to leverage Stonehenge without onerous conditions. Initially WSO2 will contribute an application called StockTrader, which is currently implemented in various languages based on Axis2/Java and Axis2/C including Java, PHP, Ruby, Perl, Python, and Spring. This will form the first of several applications which will be built in this incubator podling. In addition, we will invite contributions of other stock trader applications, including the Microsoft StockTrader sample found at [WWW] http://msdn.microsoft.com/en-us/netframework/bb499684.aspx. We also invite contributions from any other organization who has similar applications or technologies. Interoperability between the WSO2 StockTrader 2.0 application and the Microsoft StockTrader 2.0 has already been demonstrated and we expect to demonstrate wider interoperability. Going beyond StockTrader, we expect to develop additional applications that demonstrate SOA principles in an open and collaborative manner within the Stonehenge community. Current Status The development to date of the StockTrader application has successfully shown the benefits of cross-platform interoperability and have provided a useful example to developers on those platforms. However, the StockTrader application as currently implemented has limitations, including a limited repertoire of technologies (e.g. focusing primarily on WS-Security), and a limited number of implementation platforms (Axis2/Java, Axis2/C). We expect that this podling would expand the scope of this effort to a wider set of implementation platforms (including but not limited to Apache technologies such as Apache CXF) as well as bring in a wider, more diverse community of participants. Meritocracy One of the core aims of the Stonehenge proposal is to encourage meritocracy and contribution. One core aim in coming to Apache is to use the well-defined governance model that Apache has and to encourage the developers of frameworks to get involved and contribute implementations of the core components. A good proportion of the project participants are experienced Apache contributors and totally understand the Apache meritocracy approach. Everyone involved see that as being crucial to the success of this project. Core Developers The core developers are all listed in the initial committers list later in this proposal. Alignment The project already uses core libraries from the [WWW] Apache WS project including [WWW] Apache Axis2/Java, [WWW] Rampart and [WWW] Sandesha2. In addition, the PHP, Perl, and Python versions use the [WWW] Apache Axis2/C libraries. We hope to develop versions that utilize at least the [WWW] Apache CXF and [WWW] Apache Qpid projects in the future. For build we intend to use [WWW] Apache Maven. Known Risks Orphaned Products We are enthusiastic about the potential to participate on the Stonehenge project if it goes forward. The StockTrader application and other applications are already
Re: [VOTE] Abdera Graduation to TLP
+1 Craig On Nov 13, 2008, at 5:59 AM, Garrett Rooney wrote: After some brief discussion here and a vote on the Abdera private list, it seems everyone is in favor of this, so I'd like to propose that we ask the board to make Abdera a new TLP. It's been quite the long incubation process (started in May 2006!), but I think the Abdera community, while small, is now diverse enough that I have no question as to its ability to survive as its own Apache project. So please vote away. A +1 vote is for sending the following motion to the board for its approval. -garrett 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] Accept Stonehenge into the Incubator
Paul Fremantle wrote: The Stonehenge proposal has been around for discussion for a while, and we now have a wide set of contributors and mentors, so I'd like to call a vote. I know there are some other potential mentors and or contributors still considering getting involved, but the normal Apache process of course allows that at any time. The proposal is here: http://wiki.apache.org/incubator/StonehengeProposal And also included at the end: Please vote +1 to accept, or -1 with reasons to not accept as a podling. +1 (non-binding) I think this proposal points in a very interesting direction, and am looking forward to seeing what kind of pickup it'll get over time. --Glen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Abdera Graduation to TLP
+1 (non-binding) On Thu, Nov 13, 2008 at 10:21 AM, Craig L Russell [EMAIL PROTECTED] wrote: +1 Craig On Nov 13, 2008, at 5:59 AM, Garrett Rooney wrote: After some brief discussion here and a vote on the Abdera private list, it seems everyone is in favor of this, so I'd like to propose that we ask the board to make Abdera a new TLP. It's been quite the long incubation process (started in May 2006!), but I think the Abdera community, while small, is now diverse enough that I have no question as to its ability to survive as its own Apache project. So please vote away. A +1 vote is for sending the following motion to the board for its approval. -garrett 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: [VOTE] Abdera Graduation to TLP
On Thu, Nov 13, 2008 at 6:59 AM, Garrett Rooney [EMAIL PROTECTED] wrote: After some brief discussion here and a vote on the Abdera private list, it seems everyone is in favor of this, so I'd like to propose that we ask the board to make Abdera a new TLP. It's been quite the long incubation process (started in May 2006!), but I think the Abdera community, while small, is now diverse enough that I have no question as to its ability to survive as its own Apache project. So please vote away. A +1 vote is for sending the following motion to the board for its approval. +1 Bruce -- perl -e 'print unpack(u30,D0G)[EMAIL PROTECTED]5R\F)R=6-E+G-N61ED\!G;6%I;\YC;VT* );' Apache ActiveMQ - http://activemq.org/ Apache Camel - http://activemq.org/camel/ Apache ServiceMix - http://servicemix.org/ Blog: http://bruceblog.org/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Abdera Graduation to TLP
On Thu, Nov 13, 2008 at 8:59 AM, Garrett Rooney [EMAIL PROTECTED] wrote: After some brief discussion here and a vote on the Abdera private list, it seems everyone is in favor of this, so I'd like to propose that we ask the board to make Abdera a new TLP. It's been quite the long incubation process (started in May 2006!), but I think the Abdera community, while small, is now diverse enough that I have no question as to its ability to survive as its own Apache project. So please vote away. A +1 vote is for sending the following motion to the board for its approval. +1. -- justin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Accept Stonehenge into the Incubator
On Thu, Nov 13, 2008 at 6:41 PM, Paul Fremantle [EMAIL PROTECTED] wrote: ...Please vote +1 to accept, or -1 with reasons to not accept as a podling... +1 -Bertrand - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Qpid Graduation - for top level
+1 Niall 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] Abdera Graduation to TLP
+1 Niall On Thu, Nov 13, 2008 at 1:59 PM, Garrett Rooney [EMAIL PROTECTED] wrote: After some brief discussion here and a vote on the Abdera private list, it seems everyone is in favor of this, so I'd like to propose that we ask the board to make Abdera a new TLP. It's been quite the long incubation process (started in May 2006!), but I think the Abdera community, while small, is now diverse enough that I have no question as to its ability to survive as its own Apache project. So please vote away. A +1 vote is for sending the following motion to the board for its approval. -garrett 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 framework for building clients and servers for the Atom Publishing Protocol and other related technology, 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 Abdera Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that The Apache Abdera Project be and hereby is responsible for the creation and maintenance of a software project related to a framework for building clients and servers for the Atom Publishing Protocol and other related technology. RESOLVED, that the office of Vice President, Apache Abdera 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 Abdera Project, and to have primary responsibility for management of the projects within the scope of responsibility of The Apache Abdera 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 Abdera Project: - James M. Snell ([EMAIL PROTECTED]) - Garrett Rooney ([EMAIL PROTECTED]) - Stephen Duncan Jr. ([EMAIL PROTECTED]) - Ugo Cei ([EMAIL PROTECTED]) - Dan Diephouse ([EMAIL PROTECTED]) - David Calavera ([EMAIL PROTECTED]) - Jim Ancona ([EMAIL PROTECTED]) NOW, THEREFORE, BE IT FURTHER RESOLVED, that Garrett Rooney be and hereby is appointed to the office of Vice President, Apache Abdera, 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 Abdera 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 Abdera Project; and be it further RESOLVED, that the initial Apache Abdera Project be and hereby is tasked with the migration and rationalization of the Apache Incubator Abdera podling; and be it further RESOLVED, that all responsibility pertaining to the Apache Incubator Abdera podling encumbered upon the Apache Incubator PMC are hereafter discharged. - 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: [REPORTS] missing: Abdera BlueSky Buildr Droids Hama JSecurity Lokahi Olio PDFBox PhotArk Tashi VCL WSRP4J XAP
On Tue, Nov 11, 2008 at 11:34 PM, Bertrand Delacretaz [EMAIL PROTECTED] wrote: Please add your reports at http://wiki.apache.org/incubator/November2008 Real Soon. Buildr report added, sorry for the delay. Assaf -Bertrand - 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: [VOTE] Accept Stonehenge into the Incubator
+1 Niall On Thu, Nov 13, 2008 at 5:41 PM, Paul Fremantle [EMAIL PROTECTED] wrote: The Stonehenge proposal has been around for discussion for a while, and we now have a wide set of contributors and mentors, so I'd like to call a vote. I know there are some other potential mentors and or contributors still considering getting involved, but the normal Apache process of course allows that at any time. The proposal is here: http://wiki.apache.org/incubator/StonehengeProposal And also included at the end: Please vote +1 to accept, or -1 with reasons to not accept as a podling. Paul StonehengeProposal Project Stonehenge Abstract Stonehenge is a set of example applications for Service Oriented Architecture that spans languages and platforms and demonstrates best practise and interoperability. Proposal The aim of the Stonehenge project is to develop a set of sample applications to demonstrate seamless interoperability across multiple underlying platform technologies by using currently defined W3C and OASIS standard protocols. We are proposing this incubator project because we believe that a project that includes a set of sample applications, with multiple language and framework implementations will become a useful and important part of the SOA landscape. It will: * illustrate and develop best practice for interoperable applications that communicate via distributed protocols, * demonstrate interoperability between platforms, * provide sample code upon which SOA developers can build, * help identify interoperability issues and their solutions, and * build confidence in cross-platform deployment of SOA technologies. We believe that pursuit of these objectives at Apache has a number of significant benefits: 1. Attractiveness of Apache to the wide range of vendors and customers willing to participate in the conception, development, and implementation of new scenarios. 2. A well-established, neutral forum and process for architectural design and implementation. 3. The flexibility of the Apache License to allow users to leverage Stonehenge without onerous conditions. Initially WSO2 will contribute an application called StockTrader, which is currently implemented in various languages based on Axis2/Java and Axis2/C including Java, PHP, Ruby, Perl, Python, and Spring. This will form the first of several applications which will be built in this incubator podling. In addition, we will invite contributions of other stock trader applications, including the Microsoft StockTrader sample found at [WWW] http://msdn.microsoft.com/en-us/netframework/bb499684.aspx. We also invite contributions from any other organization who has similar applications or technologies. Interoperability between the WSO2 StockTrader 2.0 application and the Microsoft StockTrader 2.0 has already been demonstrated and we expect to demonstrate wider interoperability. Going beyond StockTrader, we expect to develop additional applications that demonstrate SOA principles in an open and collaborative manner within the Stonehenge community. Current Status The development to date of the StockTrader application has successfully shown the benefits of cross-platform interoperability and have provided a useful example to developers on those platforms. However, the StockTrader application as currently implemented has limitations, including a limited repertoire of technologies (e.g. focusing primarily on WS-Security), and a limited number of implementation platforms (Axis2/Java, Axis2/C). We expect that this podling would expand the scope of this effort to a wider set of implementation platforms (including but not limited to Apache technologies such as Apache CXF) as well as bring in a wider, more diverse community of participants. Meritocracy One of the core aims of the Stonehenge proposal is to encourage meritocracy and contribution. One core aim in coming to Apache is to use the well-defined governance model that Apache has and to encourage the developers of frameworks to get involved and contribute implementations of the core components. A good proportion of the project participants are experienced Apache contributors and totally understand the Apache meritocracy approach. Everyone involved see that as being crucial to the success of this project. Core Developers The core developers are all listed in the initial committers list later in this proposal. Alignment The project already uses core libraries from the [WWW] Apache WS project including [WWW] Apache Axis2/Java, [WWW] Rampart and [WWW] Sandesha2. In addition, the PHP, Perl, and Python versions use the [WWW] Apache Axis2/C libraries. We hope to develop versions that utilize at least the [WWW] Apache CXF and [WWW] Apache Qpid projects in the future. For build we intend to use [WWW] Apache Maven. Known Risks Orphaned Products We
RE: [VOTE] Accept Stonehenge into the Incubator
+1 Kamal -Original Message- From: Niall Pemberton [mailto:[EMAIL PROTECTED] Sent: Thursday, November 13, 2008 3:51 PM To: general@incubator.apache.org Subject: Re: [VOTE] Accept Stonehenge into the Incubator +1 Niall On Thu, Nov 13, 2008 at 5:41 PM, Paul Fremantle [EMAIL PROTECTED] wrote: The Stonehenge proposal has been around for discussion for a while, and we now have a wide set of contributors and mentors, so I'd like to call a vote. I know there are some other potential mentors and or contributors still considering getting involved, but the normal Apache process of course allows that at any time. The proposal is here: http://wiki.apache.org/incubator/StonehengeProposal And also included at the end: Please vote +1 to accept, or -1 with reasons to not accept as a podling. Paul StonehengeProposal Project Stonehenge Abstract Stonehenge is a set of example applications for Service Oriented Architecture that spans languages and platforms and demonstrates best practise and interoperability. Proposal The aim of the Stonehenge project is to develop a set of sample applications to demonstrate seamless interoperability across multiple underlying platform technologies by using currently defined W3C and OASIS standard protocols. We are proposing this incubator project because we believe that a project that includes a set of sample applications, with multiple language and framework implementations will become a useful and important part of the SOA landscape. It will: * illustrate and develop best practice for interoperable applications that communicate via distributed protocols, * demonstrate interoperability between platforms, * provide sample code upon which SOA developers can build, * help identify interoperability issues and their solutions, and * build confidence in cross-platform deployment of SOA technologies. We believe that pursuit of these objectives at Apache has a number of significant benefits: 1. Attractiveness of Apache to the wide range of vendors and customers willing to participate in the conception, development, and implementation of new scenarios. 2. A well-established, neutral forum and process for architectural design and implementation. 3. The flexibility of the Apache License to allow users to leverage Stonehenge without onerous conditions. Initially WSO2 will contribute an application called StockTrader, which is currently implemented in various languages based on Axis2/Java and Axis2/C including Java, PHP, Ruby, Perl, Python, and Spring. This will form the first of several applications which will be built in this incubator podling. In addition, we will invite contributions of other stock trader applications, including the Microsoft StockTrader sample found at [WWW] http://msdn.microsoft.com/en-us/netframework/bb499684.aspx. We also invite contributions from any other organization who has similar applications or technologies. Interoperability between the WSO2 StockTrader 2.0 application and the Microsoft StockTrader 2.0 has already been demonstrated and we expect to demonstrate wider interoperability. Going beyond StockTrader, we expect to develop additional applications that demonstrate SOA principles in an open and collaborative manner within the Stonehenge community. Current Status The development to date of the StockTrader application has successfully shown the benefits of cross-platform interoperability and have provided a useful example to developers on those platforms. However, the StockTrader application as currently implemented has limitations, including a limited repertoire of technologies (e.g. focusing primarily on WS-Security), and a limited number of implementation platforms (Axis2/Java, Axis2/C). We expect that this podling would expand the scope of this effort to a wider set of implementation platforms (including but not limited to Apache technologies such as Apache CXF) as well as bring in a wider, more diverse community of participants. Meritocracy One of the core aims of the Stonehenge proposal is to encourage meritocracy and contribution. One core aim in coming to Apache is to use the well-defined governance model that Apache has and to encourage the developers of frameworks to get involved and contribute implementations of the core components. A good proportion of the project participants are experienced Apache contributors and totally understand the Apache meritocracy approach. Everyone involved see that as being crucial to the success of this project. Core Developers The core developers are all listed in the initial committers list later in this proposal. Alignment The project already uses core libraries from the [WWW] Apache WS project including [WWW] Apache Axis2/Java, [WWW] Rampart and [WWW] Sandesha2. In addition, the PHP, Perl, and Python versions use the [WWW] Apache
Re: [VOTE] Abdera Graduation to TLP
Garrett Rooney wrote: After some brief discussion here and a vote on the Abdera private list, it seems everyone is in favor of this, so I'd like to propose that we ask the board to make Abdera a new TLP. It's been quite the long incubation process (started in May 2006!), but I think the Abdera community, while small, is now diverse enough that I have no question as to its ability to survive as its own Apache project. So please vote away. A +1 vote is for sending the following motion to the board for its approval. +1 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Accept Stonehenge into the Incubator
+1. Paul Fremantle wrote: The Stonehenge proposal has been around for discussion for a while, and we now have a wide set of contributors and mentors, so I'd like to call a vote. I know there are some other potential mentors and or contributors still considering getting involved, but the normal Apache process of course allows that at any time. The proposal is here: http://wiki.apache.org/incubator/StonehengeProposal And also included at the end: Please vote +1 to accept, or -1 with reasons to not accept as a podling. Paul StonehengeProposal Project Stonehenge Abstract Stonehenge is a set of example applications for Service Oriented Architecture that spans languages and platforms and demonstrates best practise and interoperability. Proposal The aim of the Stonehenge project is to develop a set of sample applications to demonstrate seamless interoperability across multiple underlying platform technologies by using currently defined W3C and OASIS standard protocols. We are proposing this incubator project because we believe that a project that includes a set of sample applications, with multiple language and framework implementations will become a useful and important part of the SOA landscape. It will: * illustrate and develop best practice for interoperable applications that communicate via distributed protocols, * demonstrate interoperability between platforms, * provide sample code upon which SOA developers can build, * help identify interoperability issues and their solutions, and * build confidence in cross-platform deployment of SOA technologies. We believe that pursuit of these objectives at Apache has a number of significant benefits: 1. Attractiveness of Apache to the wide range of vendors and customers willing to participate in the conception, development, and implementation of new scenarios. 2. A well-established, neutral forum and process for architectural design and implementation. 3. The flexibility of the Apache License to allow users to leverage Stonehenge without onerous conditions. Initially WSO2 will contribute an application called StockTrader, which is currently implemented in various languages based on Axis2/Java and Axis2/C including Java, PHP, Ruby, Perl, Python, and Spring. This will form the first of several applications which will be built in this incubator podling. In addition, we will invite contributions of other stock trader applications, including the Microsoft StockTrader sample found at [WWW] http://msdn.microsoft.com/en-us/netframework/bb499684.aspx. We also invite contributions from any other organization who has similar applications or technologies. Interoperability between the WSO2 StockTrader 2.0 application and the Microsoft StockTrader 2.0 has already been demonstrated and we expect to demonstrate wider interoperability. Going beyond StockTrader, we expect to develop additional applications that demonstrate SOA principles in an open and collaborative manner within the Stonehenge community. Current Status The development to date of the StockTrader application has successfully shown the benefits of cross-platform interoperability and have provided a useful example to developers on those platforms. However, the StockTrader application as currently implemented has limitations, including a limited repertoire of technologies (e.g. focusing primarily on WS-Security), and a limited number of implementation platforms (Axis2/Java, Axis2/C). We expect that this podling would expand the scope of this effort to a wider set of implementation platforms (including but not limited to Apache technologies such as Apache CXF) as well as bring in a wider, more diverse community of participants. Meritocracy One of the core aims of the Stonehenge proposal is to encourage meritocracy and contribution. One core aim in coming to Apache is to use the well-defined governance model that Apache has and to encourage the developers of frameworks to get involved and contribute implementations of the core components. A good proportion of the project participants are experienced Apache contributors and totally understand the Apache meritocracy approach. Everyone involved see that as being crucial to the success of this project. Core Developers The core developers are all listed in the initial committers list later in this proposal. Alignment The project already uses core libraries from the [WWW] Apache WS project including [WWW] Apache Axis2/Java, [WWW] Rampart and [WWW] Sandesha2. In addition, the PHP, Perl, and Python versions use the [WWW] Apache Axis2/C libraries. We hope to develop versions that utilize at least the [WWW] Apache CXF and [WWW] Apache Qpid projects in the future. For build we intend to use [WWW] Apache Maven. Known Risks Orphaned Products We are enthusiastic about the potential to participate on the Stonehenge project if it goes forward. The StockTrader application and other
Re: [PROPOSAL] Stonehenge
Bertrand Delacretaz 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. That is not a problem, if the project's aim is to provide similar functionality to users of many different tools. The fact is that most of the logic running under commercial JEE can likely be built using either open JEE frameworks such as Geronimo or Glassfish, and that .NET tools are free (while you may need to pay to run such an operating system). Of course that doesn't preclude at least proving up the implementation under the likes of mono :) 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. I'm satisfied this isn't a showstopper to this effort. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PROPOSAL] Stonehenge
Robert Burrell Donkin wrote: 4. running continuous integration on shore may require licenses. it's important that contributors understand this and don't just start diving in. it may be better to start off shore. As a US based Deleware 501(c)3 that wouldn't protect us. As far as continuous integration solutions, I believe we can work with the companies to ensure sufficient (gratis) licenses to do so on the ASF infrastructure. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Abdera Graduation to TLP
Garrett Rooney wrote: The discussion included determining the list of people to put on the final PMC list. The actual list of Abdera committers was larger, but many of them had not participated in the project in some time or at all, or had explicitly left the project. Since I didn't want to come right out in a public forum and say you know, I think committer X doesn't deserve to be on the PMC I started the discussion in private. I'm presuming there was not a dev@ vote yet by the Abdera community itself? If not, could you please call that vote ASAP in parallel with the general@ vote? Monday evening is not to late to put this on the board agenda. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Abdera Graduation to TLP
On Thu, Nov 13, 2008 at 10:37 PM, William A. Rowe, Jr. [EMAIL PROTECTED] wrote: Garrett Rooney wrote: The discussion included determining the list of people to put on the final PMC list. The actual list of Abdera committers was larger, but many of them had not participated in the project in some time or at all, or had explicitly left the project. Since I didn't want to come right out in a public forum and say you know, I think committer X doesn't deserve to be on the PMC I started the discussion in private. I'm presuming there was not a dev@ vote yet by the Abdera community itself? If not, could you please call that vote ASAP in parallel with the general@ vote? Monday evening is not to late to put this on the board agenda. There was already a vote on the abdera private list with more than 50% of the developers voting +1 and none voting -1. If you're really concerned that it's not on the dev list I can restart the vote there, but it seems awfully futile. -garrett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Accept Stonehenge into the Incubator
Just two concerns... The project already uses core libraries from the Apache WS project including Apache Axis2/Java, Rampart and Sandesha2. In addition, the PHP, Perl, and Python versions use the Apache Axis2/C libraries. We hope to develop versions that utilize at least the Apache CXF and Apache Qpid projects in the future. For build we intend to use Apache Maven. Is it anticipated this will graduate into the WS TLP? If so, has WS voted to sponsor the project into incubation? The proposed developers come from n companies. I presume n==6, could you update the wiki? Paul Fremantle wrote: The Stonehenge proposal has been around for discussion for a while, and we now have a wide set of contributors and mentors, so I'd like to call a vote. I know there are some other potential mentors and or contributors still considering getting involved, but the normal Apache process of course allows that at any time. The proposal is here: http://wiki.apache.org/incubator/StonehengeProposal And also included at the end: Please vote +1 to accept, or -1 with reasons to not accept as a podling. Paul StonehengeProposal Project Stonehenge Abstract Stonehenge is a set of example applications for Service Oriented Architecture that spans languages and platforms and demonstrates best practise and interoperability. Proposal The aim of the Stonehenge project is to develop a set of sample applications to demonstrate seamless interoperability across multiple underlying platform technologies by using currently defined W3C and OASIS standard protocols. We are proposing this incubator project because we believe that a project that includes a set of sample applications, with multiple language and framework implementations will become a useful and important part of the SOA landscape. It will: * illustrate and develop best practice for interoperable applications that communicate via distributed protocols, * demonstrate interoperability between platforms, * provide sample code upon which SOA developers can build, * help identify interoperability issues and their solutions, and * build confidence in cross-platform deployment of SOA technologies. We believe that pursuit of these objectives at Apache has a number of significant benefits: 1. Attractiveness of Apache to the wide range of vendors and customers willing to participate in the conception, development, and implementation of new scenarios. 2. A well-established, neutral forum and process for architectural design and implementation. 3. The flexibility of the Apache License to allow users to leverage Stonehenge without onerous conditions. Initially WSO2 will contribute an application called StockTrader, which is currently implemented in various languages based on Axis2/Java and Axis2/C including Java, PHP, Ruby, Perl, Python, and Spring. This will form the first of several applications which will be built in this incubator podling. In addition, we will invite contributions of other stock trader applications, including the Microsoft StockTrader sample found at [WWW] http://msdn.microsoft.com/en-us/netframework/bb499684.aspx. We also invite contributions from any other organization who has similar applications or technologies. Interoperability between the WSO2 StockTrader 2.0 application and the Microsoft StockTrader 2.0 has already been demonstrated and we expect to demonstrate wider interoperability. Going beyond StockTrader, we expect to develop additional applications that demonstrate SOA principles in an open and collaborative manner within the Stonehenge community. Current Status The development to date of the StockTrader application has successfully shown the benefits of cross-platform interoperability and have provided a useful example to developers on those platforms. However, the StockTrader application as currently implemented has limitations, including a limited repertoire of technologies (e.g. focusing primarily on WS-Security), and a limited number of implementation platforms (Axis2/Java, Axis2/C). We expect that this podling would expand the scope of this effort to a wider set of implementation platforms (including but not limited to Apache technologies such as Apache CXF) as well as bring in a wider, more diverse community of participants. Meritocracy One of the core aims of the Stonehenge proposal is to encourage meritocracy and contribution. One core aim in coming to Apache is to use the well-defined governance model that Apache has and to encourage the developers of frameworks to get involved and contribute implementations of the core components. A good proportion of the project participants are experienced Apache contributors and totally understand the Apache meritocracy approach. Everyone involved see that as being crucial to the success of
Re: [VOTE] Abdera Graduation to TLP
Garrett Rooney wrote: On Thu, Nov 13, 2008 at 10:37 PM, William A. Rowe, Jr. [EMAIL PROTECTED] wrote: Garrett Rooney wrote: The discussion included determining the list of people to put on the final PMC list. The actual list of Abdera committers was larger, but many of them had not participated in the project in some time or at all, or had explicitly left the project. Since I didn't want to come right out in a public forum and say you know, I think committer X doesn't deserve to be on the PMC I started the discussion in private. I'm presuming there was not a dev@ vote yet by the Abdera community itself? If not, could you please call that vote ASAP in parallel with the general@ vote? Monday evening is not to late to put this on the board agenda. There was already a vote on the abdera private list with more than 50% of the developers voting +1 and none voting -1. If you're really concerned that it's not on the dev list I can restart the vote there, but it seems awfully futile. seems like a waste of time for all involved to run yet another vote. -Paul - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Abdera Graduation to TLP
Garrett Rooney wrote: On Thu, Nov 13, 2008 at 10:37 PM, William A. Rowe, Jr. I'm presuming there was not a dev@ vote yet by the Abdera community itself? If not, could you please call that vote ASAP in parallel with the general@ vote? Monday evening is not to late to put this on the board agenda. There was already a vote on the abdera private list with more than 50% of the developers voting +1 and none voting -1. If you're really concerned that it's not on the dev list I can restart the vote there, but it seems awfully futile. The point is that yes, we hold votes (discussions) about people on private lists, so it was certainly appropriate to decide the initial composition on that list. But it is still for the dev@ list to sanity check the decision by the powers-that-be... that ensures I have no issues if you wish to 'seed' the vote with the list of ipmc members who have already voted in the affirmative, to spare them the trouble of re-voting. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Abdera Graduation to TLP
William A. Rowe, Jr. wrote: Garrett Rooney wrote: On Thu, Nov 13, 2008 at 10:37 PM, William A. Rowe, Jr. I'm presuming there was not a dev@ vote yet by the Abdera community itself? If not, could you please call that vote ASAP in parallel with the general@ vote? Monday evening is not to late to put this on the board agenda. There was already a vote on the abdera private list with more than 50% of the developers voting +1 and none voting -1. If you're really concerned that it's not on the dev list I can restart the vote there, but it seems awfully futile. The point is that yes, we hold votes (discussions) about people on private lists, so it was certainly appropriate to decide the initial composition on that list. But it is still for the dev@ list to sanity check the decision by the powers-that-be... that ensures Blasted fat fingers... ... that ensures the project is sufficiently connected to its community. I have no issues if you wish to 'seed' the vote with the list of ipmc members who have already voted in the affirmative, to spare them the trouble of re-voting. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Abdera Graduation to TLP
On Thu, Nov 13, 2008 at 10:54 PM, William A. Rowe, Jr. [EMAIL PROTECTED] wrote: Garrett Rooney wrote: On Thu, Nov 13, 2008 at 10:37 PM, William A. Rowe, Jr. I'm presuming there was not a dev@ vote yet by the Abdera community itself? If not, could you please call that vote ASAP in parallel with the general@ vote? Monday evening is not to late to put this on the board agenda. There was already a vote on the abdera private list with more than 50% of the developers voting +1 and none voting -1. If you're really concerned that it's not on the dev list I can restart the vote there, but it seems awfully futile. The point is that yes, we hold votes (discussions) about people on private lists, so it was certainly appropriate to decide the initial composition on that list. But it is still for the dev@ list to sanity check the decision by the powers-that-be... that ensures I have no issues if you wish to 'seed' the vote with the list of ipmc members who have already voted in the affirmative, to spare them the trouble of re-voting. Fine. Whatever. I've started yet another vote, this time on [EMAIL PROTECTED] For the curious, this is now the 4th vote or vote-like thread I've started about this graduation in the past week. You'll understand if I'm getting a bit sick of it, especially when all we're doing is following procedure for procedure's sake. -garrett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [VOTE] Accept Stonehenge into the Incubator
+1 Drew From: Paul Fremantle [EMAIL PROTECTED] Sent: Thursday, November 13, 2008 9:41 AM To: general@incubator.apache.org Subject: [VOTE] Accept Stonehenge into the Incubator The Stonehenge proposal has been around for discussion for a while, and we now have a wide set of contributors and mentors, so I'd like to call a vote. I know there are some other potential mentors and or contributors still considering getting involved, but the normal Apache process of course allows that at any time. The proposal is here: http://wiki.apache.org/incubator/StonehengeProposal And also included at the end: Please vote +1 to accept, or -1 with reasons to not accept as a podling. Paul StonehengeProposal Project Stonehenge Abstract Stonehenge is a set of example applications for Service Oriented Architecture that spans languages and platforms and demonstrates best practise and interoperability. Proposal The aim of the Stonehenge project is to develop a set of sample applications to demonstrate seamless interoperability across multiple underlying platform technologies by using currently defined W3C and OASIS standard protocols. We are proposing this incubator project because we believe that a project that includes a set of sample applications, with multiple language and framework implementations will become a useful and important part of the SOA landscape. It will: * illustrate and develop best practice for interoperable applications that communicate via distributed protocols, * demonstrate interoperability between platforms, * provide sample code upon which SOA developers can build, * help identify interoperability issues and their solutions, and * build confidence in cross-platform deployment of SOA technologies. We believe that pursuit of these objectives at Apache has a number of significant benefits: 1. Attractiveness of Apache to the wide range of vendors and customers willing to participate in the conception, development, and implementation of new scenarios. 2. A well-established, neutral forum and process for architectural design and implementation. 3. The flexibility of the Apache License to allow users to leverage Stonehenge without onerous conditions. Initially WSO2 will contribute an application called StockTrader, which is currently implemented in various languages based on Axis2/Java and Axis2/C including Java, PHP, Ruby, Perl, Python, and Spring. This will form the first of several applications which will be built in this incubator podling. In addition, we will invite contributions of other stock trader applications, including the Microsoft StockTrader sample found at [WWW] http://msdn.microsoft.com/en-us/netframework/bb499684.aspx. We also invite contributions from any other organization who has similar applications or technologies. Interoperability between the WSO2 StockTrader 2.0 application and the Microsoft StockTrader 2.0 has already been demonstrated and we expect to demonstrate wider interoperability. Going beyond StockTrader, we expect to develop additional applications that demonstrate SOA principles in an open and collaborative manner within the Stonehenge community. Current Status The development to date of the StockTrader application has successfully shown the benefits of cross-platform interoperability and have provided a useful example to developers on those platforms. However, the StockTrader application as currently implemented has limitations, including a limited repertoire of technologies (e.g. focusing primarily on WS-Security), and a limited number of implementation platforms (Axis2/Java, Axis2/C). We expect that this podling would expand the scope of this effort to a wider set of implementation platforms (including but not limited to Apache technologies such as Apache CXF) as well as bring in a wider, more diverse community of participants. Meritocracy One of the core aims of the Stonehenge proposal is to encourage meritocracy and contribution. One core aim in coming to Apache is to use the well-defined governance model that Apache has and to encourage the developers of frameworks to get involved and contribute implementations of the core components. A good proportion of the project participants are experienced Apache contributors and totally understand the Apache meritocracy approach. Everyone involved see that as being crucial to the success of this project. Core Developers The core developers are all listed in the initial committers list later in this proposal. Alignment The project already uses core libraries from the [WWW] Apache WS project including [WWW] Apache Axis2/Java, [WWW] Rampart and [WWW] Sandesha2. In addition, the PHP, Perl, and Python versions use the [WWW] Apache Axis2/C libraries. We hope to develop versions that utilize at least the [WWW] Apache CXF and [WWW] Apache Qpid projects in the future. For build we intend to use
Re: [PROPOSAL] Stonehenge
William A. Rowe, Jr. wrote: Robert Burrell Donkin wrote: 4. running continuous integration on shore may require licenses. it's important that contributors understand this and don't just start diving in. it may be better to start off shore. As a US based Deleware 501(c)3 that wouldn't protect us. Plus even off shore there are IP protections and legal requirements to use licensed software! Promoting piracy is not a good thing .. but I don't think that's what Robert was saying at all! As far as continuous integration solutions, I believe we can work with the companies to ensure sufficient (gratis) licenses to do so on the ASF infrastructure. +1. Sanjiva. -- Sanjiva Weerawarana, Ph.D. Founder Director; Lanka Software Foundation; http://www.opensource.lk/ Founder, Chairman CEO; WSO2, Inc.; http://www.wso2.com/ Member; Apache Software Foundation; http://www.apache.org/ Visiting Lecturer; University of Moratuwa; http://www.cse.mrt.ac.lk/ Blog: http://sanjiva.weerawarana.org/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Accept Stonehenge into the Incubator
William A. Rowe, Jr. wrote: Just two concerns... The project already uses core libraries from the Apache WS project including Apache Axis2/Java, Rampart and Sandesha2. In addition, the PHP, Perl, and Python versions use the Apache Axis2/C libraries. We hope to develop versions that utilize at least the Apache CXF and Apache Qpid projects in the future. For build we intend to use Apache Maven. Is it anticipated this will graduate into the WS TLP? If so, has WS voted to sponsor the project into incubation? I think its unlikely to be going into the WS TLP as this project is not at all biased towards code from the WS TLP (such as axis2). My expectation is that this will be a good TLP candidate but we're far from that discussion yet! Sanjiva. -- Sanjiva Weerawarana, Ph.D. Founder Director; Lanka Software Foundation; http://www.opensource.lk/ Founder, Chairman CEO; WSO2, Inc.; http://www.wso2.com/ Member; Apache Software Foundation; http://www.apache.org/ Visiting Lecturer; University of Moratuwa; http://www.cse.mrt.ac.lk/ Blog: http://sanjiva.weerawarana.org/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Accept Stonehenge into the Incubator
On Thu, Nov 13, 2008 at 9:41 AM, Paul Fremantle [EMAIL PROTECTED] wrote: The Stonehenge proposal has been around for discussion for a while, and we now have a wide set of contributors and mentors, so I'd like to call a vote. I know there are some other potential mentors and or contributors still considering getting involved, but the normal Apache process of course allows that at any time. The proposal is here: http://wiki.apache.org/incubator/StonehengeProposal And also included at the end: Please vote +1 to accept, or -1 with reasons to not accept as a podling. +1 Matthieu Paul
