Re: [VOTE] Accept Stonehenge into the Incubator
On Fri, Nov 14, 2008 at 3:49 AM, William A. Rowe, Jr. [EMAIL PROTECTED] wrote: Just two concerns... Is it anticipated this will graduate into the WS TLP? If so, has WS voted to sponsor the project into incubation? We would like to leave this open during the initial graduation. I think this might aim for TLP in order to maintain neutrality across different frameworks such as Axis, Axis2 and CXF. I presume n==6, could you update the wiki? Done. Thanks for picking this up. Paul -- Paul Fremantle Co-Founder and CTO, WSO2 Apache Synapse PMC Chair OASIS WS-RX TC Co-chair blog: http://pzf.fremantle.org [EMAIL PROTECTED] Oxygenating the Web Service Platform, www.wso2.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release Apache UIMACPP-2.2.2-incubating
+1 - Sam Ruby On Thu, Oct 16, 2008 at 9:53 AM, Rodent of Unusual Size [EMAIL PROTECTED] wrote: +1 -- #kenP-)} Ken Coar, Sanagendamgagwedweinini http://Ken.Coar.Org/ Author, developer, opinionist http://Apache-Server.Com/ Millennium hand and shrimp! - 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 Dan On Thursday 13 November 2008 12:41:56 pm 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
Re: [VOTE] Accept Stonehenge into the Incubator
+1 Thank you! Deepal +1 Dan On Thursday 13 November 2008 12:41:56 pm 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.
Re: [VOTE] Accept Stonehenge into the Incubator
On Thursday 13 November 2008 10:49:02 pm 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? As Paul and Sanjiva kind of mentioned, this really doesn't need to be decided now.We DID talk about this a bit when we were working on the proposal and really didn't have a good answer right now. The goal of the project is to NOT be tied to Axis2 and the other WebServices project stuff.. Axis2 will be one implementation. .NET another. CXF another.Hopefully we'll get others as well. Maybe Metro, Spring WebServices, Oracle/BEA, etc.Thus, tying it directly to the axis2 stuff would be a disservice to Stonehenge and what it's trying to achieve. That's actually part of how the project would like to diversify and grow. Bring in implementations (and committers) for other toolkits. THAT said, there are talks to pull Axis out TLP with WebServices being the common stuff. If/when that happens, then it MIGHT make more sense to put it there. But that depends on events outside the Stonehenge project and isn't really something we wanted to depend on at proposal time. Thus, the decision was made to not put that tie in right now. That is something that can be resolved when the project is closer to graduation. Besides, don't you think the WS project is big enough already? :-) -- Daniel Kulp [EMAIL PROTECTED] http://dankulp.com/blog - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Accept Stonehenge into the Incubator
Paul Fremantle wrote: On Fri, Nov 14, 2008 at 3:49 AM, William A. Rowe, Jr. [EMAIL PROTECTED] wrote: Just two concerns... Is it anticipated this will graduate into the WS TLP? If so, has WS voted to sponsor the project into incubation? We would like to leave this open during the initial graduation. I think this might aim for TLP in order to maintain neutrality across different frameworks such as Axis, Axis2 and CXF. Thanks to all who answered, you've clarified things quite a bit. This was mostly to if this isn't an end-run around the WS PMC, which it most obviously is not. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[RESULT] [VOTE] Qpid Graduation - for top level
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. Binding - names listed at: http://incubator.apache.org/whoweare.html (8 +1 binding) Niall Pemberton [EMAIL PROTECTED] Martijn Dashorst [EMAIL PROTECTED] Bertrand Delacretaz [EMAIL PROTECTED] Jim Jagielski [EMAIL PROTECTED] Craig L Russell [EMAIL PROTECTED] Yoav Shapira [EMAIL PROTECTED] Paul Fremantle [EMAIL PROTECTED] Ant Elder [EMAIL PROTECTED] (2 +1 non-binding) Daniel Kulp [EMAIL PROTECTED] Luciano Resende [EMAIL PROTECTED] no (0 or -1 votes) Many thanks to all those involved and that voted on the community vote etc... I will now pass the resolution onto the board. Carl. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Accept Stonehenge into the Incubator
+1 Craig On Nov 13, 2008, at 9:41 AM, 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 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
