[DISCUSSION] Hama Proposal
Dear Incubator PMC, I've updated the Hama project proposal. Please review/update as needed and report back any concerns. http://wiki.apache.org/incubator/HamaProposal Hama has a strong relationship with the hadoop, hbase and mahout project, so i discussed about become a sub-project of these project for a long time with the each community. However, The sub-project was beset with difficulties. Hence the list of committers, etc. And now we all agree that the Hama should aim to general purpose rathen than it becomes a specified piece in something. http://www.nabble.com/-jira--Created%3A-%28MAHOUT-16%29-Hama-contrib-package-for-the-mahout-to15998717.html https://issues.apache.org/jira/browse/HADOOP-2878 If you think this will make a good ASF project, please encourage our team members to create the world's largest matrix computational framework. Thanks. B. Regards, Edward yoon @ NHN, corp. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Apache CXF resolution feedback....
On Friday 14 March 2008, Daniel Kulp wrote: I've updated the text of the resolution (see below) based on the comments and discussion. Thanks to everyone for the help making it clearer. Are there ANY other questions or concerns about the resolution, about the CXF project in general, etc that anyone would like resolved/discussed/answered before calling the vote? Well, this has sat for 4 days without any furthur comments or questions, thus, I'll assume we're good to go. Thanks for all the feedback! Dan == Establish the Apache CXF project WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project, to be known as Apache CXF Project, related to a framework for creating, deploying, and consuming services based on SOA design principles for distribution at no charge to the public. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC) is hereby established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache CXF PMC be and hereby is charged with the creation and maintenance of Apache CXF; and be it further RESOLVED, that the office of Vice President, Apache CXF 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 CXF PMC, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache CXF PMC; and be it further RESOLVED, that the persons listed immediately below be and hereby are appointed to serve as the initial members of the Apache CXF PMC: * Ulhas Bhole [EMAIL PROTECTED] * Sean O'Callaghan [EMAIL PROTECTED] * Dan Diephouse [EMAIL PROTECTED] * Freeman Yue Fang [EMAIL PROTECTED] * Jarek Gawor [EMAIL PROTECTED] * Jeff Genender [EMAIL PROTECTED] * Eoghan Glynn [EMAIL PROTECTED] * Jim Jagielski [EMAIL PROTECTED] * Willem Ning Jiang [EMAIL PROTECTED] * Eric Johnson [EMAIL PROTECTED] * Peter Jones [EMAIL PROTECTED] * Daniel Kulp [EMAIL PROTECTED] * Bozhong Lin [EMAIL PROTECTED] * Jervis Liu [EMAIL PROTECTED] * Jim Ma [EMAIL PROTECTED] * James Maode Mao [EMAIL PROTECTED] * Benson Margulies [EMAIL PROTECTED] * Glen Mazza [EMAIL PROTECTED] * Guillaume Nodet [EMAIL PROTECTED] * Ajay Paibir [EMAIL PROTECTED] NOW, THEREFORE, BE IT FURTHER RESOLVED, that Daniel Kulp be appointed to the office of Vice President, Apache CXF, 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 Apache CXF Project be and hereby is tasked with the migration and rationalization of the Apache Incubator CXF podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator CXF podling encumbered upon the Apache Incubator PMC are hereafter discharged. == -- J. Daniel Kulp Principal Engineer, IONA [EMAIL PROTECTED] http://www.dankulp.com/blog - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: KEYS file in distribution
On Mon, Mar 17, 2008 at 10:35 AM, Thilo Goetz [EMAIL PROTECTED] wrote: Hi, UIMA currently ships the KEYS file as part of its distributions. I found one other Apache project (Derby) that also does. The others that I checked, don't (random sample of what I had on my hard drive). I would assume that putting the KEYS file in the distribution is at best not necessary, and may be counterproductive, as it might lead people to use it. And of course you can't verify your distribution that way. So I'm thinking of removing the KEYS file from the distribution. Any compelling reasons to go one way or the other? source distributions should be identical to the contents of version control when the release is cut. if the KEYs file is present in the source that's cut, it should be left. if you're worried, add a note to the top of the file (it'll be ignored upon import). if the KEYs file is not present in version control, it should not be added to the source distribution. for binary distributions, it's best not to include the KEYs file - robert
Re: KEYS file in distribution
Robert Burrell Donkin wrote: On Mon, Mar 17, 2008 at 10:35 AM, Thilo Goetz [EMAIL PROTECTED] wrote: Hi, UIMA currently ships the KEYS file as part of its distributions. I found one other Apache project (Derby) that also does. The others that I checked, don't (random sample of what I had on my hard drive). I would assume that putting the KEYS file in the distribution is at best not necessary, and may be counterproductive, as it might lead people to use it. And of course you can't verify your distribution that way. So I'm thinking of removing the KEYS file from the distribution. Any compelling reasons to go one way or the other? source distributions should be identical to the contents of version control when the release is cut. if the KEYs file is present in the source that's cut, it should be left. if you're worried, add a note to the top of the file (it'll be ignored upon import). if the KEYs file is not present in version control, it should not be added to the source distribution. for binary distributions, it's best not to include the KEYs file - robert That makes sense. --Thilo - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[VOTE] Apache CXF Graduation as TLP
After 20 months in the incubator, 6 releases complete and 2 more on the way shortly, several new committers, and too much email traffic :-), the Apache CXF community (with support from our mentors) feels that we are ready to graduate to an official top level project at Apache as indicated by the community vote recorded at: http://www.nabble.com/-VOTE--Graduate-Apache-CXF-as-a-top-level-project-to15812722.html We would like the resolution attached to this email to be presented to the board for consideration at the next possible board meeting. For additional information, the CXF status file is here: http://incubator.apache.org/projects/cxf.html Thank you in advance for your time and consideration. [ ] +1 [ ] +0 [ ] -1 -- Dan (on behalf of the entire Apache CXF team and with permission from the CXF mentors to call this vote.) == Establish the Apache CXF project WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project, to be known as Apache CXF Project, related to a framework for creating, deploying, and consuming services based on SOA design principles for distribution at no charge to the public. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC) is hereby established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache CXF PMC be and hereby is charged with the creation and maintenance of Apache CXF; and be it further RESOLVED, that the office of Vice President, Apache CXF 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 CXF PMC, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache CXF PMC; and be it further RESOLVED, that the persons listed immediately below be and hereby are appointed to serve as the initial members of the Apache CXF PMC: * Ulhas Bhole [EMAIL PROTECTED] * Sean O'Callaghan [EMAIL PROTECTED] * Dan Diephouse [EMAIL PROTECTED] * Freeman Yue Fang [EMAIL PROTECTED] * Jarek Gawor [EMAIL PROTECTED] * Jeff Genender [EMAIL PROTECTED] * Eoghan Glynn [EMAIL PROTECTED] * Jim Jagielski [EMAIL PROTECTED] * Willem Ning Jiang [EMAIL PROTECTED] * Eric Johnson [EMAIL PROTECTED] * Peter Jones [EMAIL PROTECTED] * Daniel Kulp [EMAIL PROTECTED] * Bozhong Lin [EMAIL PROTECTED] * Jervis Liu [EMAIL PROTECTED] * Jim Ma [EMAIL PROTECTED] * James Maode Mao [EMAIL PROTECTED] * Benson Margulies [EMAIL PROTECTED] * Glen Mazza [EMAIL PROTECTED] * Guillaume Nodet [EMAIL PROTECTED] * Ajay Paibir [EMAIL PROTECTED] NOW, THEREFORE, BE IT FURTHER RESOLVED, that Daniel Kulp be appointed to the office of Vice President, Apache CXF, 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 Apache CXF Project be and hereby is tasked with the migration and rationalization of the Apache Incubator CXF podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator CXF 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] Apache CXF Graduation as TLP
On Tue, Mar 18, 2008 at 9:08 AM, Daniel Kulp [EMAIL PROTECTED] wrote: After 20 months in the incubator, 6 releases complete and 2 more on the way shortly, several new committers, and too much email traffic :-), the Apache CXF community (with support from our mentors) feels that we are ready to graduate to an official top level project at Apache as indicated by the community vote recorded at: http://www.nabble.com/-VOTE--Graduate-Apache-CXF-as-a-top-level-project-to15812722.html We would like the resolution attached to this email to be presented to the board for consideration at the next possible board meeting. For additional information, the CXF status file is here: http://incubator.apache.org/projects/cxf.html Thank you in advance for your time and consideration. [ ] +1 [ ] +0 [ ] -1 +1 Woot! 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/ Apache Geronimo - http://geronimo.apache.org/ Blog: http://bruceblog.org/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Apache CXF Graduation as TLP
what is the diversity? Carl. Davanum Srinivas wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 +1 from me! Bruce Snyder wrote: | On Tue, Mar 18, 2008 at 9:08 AM, Daniel Kulp [EMAIL PROTECTED] wrote: | After 20 months in the incubator, 6 releases complete and 2 more on the | way shortly, several new committers, and too much email traffic :-), the | Apache CXF community (with support from our mentors) feels that we are | ready to graduate to an official top level project at Apache as | indicated by the community vote recorded at: | http://www.nabble.com/-VOTE--Graduate-Apache-CXF-as-a-top-level-project-to15812722.html | | We would like the resolution attached to this email to be presented to | the board for consideration at the next possible board meeting. | | For additional information, the CXF status file is here: | http://incubator.apache.org/projects/cxf.html | | Thank you in advance for your time and consideration. | | [ ] +1 | [ ] +0 | [ ] -1 | | +1 | | Woot! | | Bruce -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Cygwin) iD8DBQFH3+ERgNg6eWEDv1kRAntlAJ0dGOaV3hL2JetKQZxQ2tB5JSdLggCfTV9T XO5US96T9bitGXnaqRo4l+c= =P/7h -END PGP SIGNATURE- - 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] Apache CXF Graduation as TLP
On Tuesday 18 March 2008, Carl Trieloff wrote: what is the diversity? Carl. This could have been asked as part of the resolution discussion instead of hijacking the vote, but Looking at participation in the dev lists: http://markmail.org/search/?q=cxf+type%3Adevelopment+date%3A200710-200803 The top 4 people are from 4 separate companies/entities. Likewise, if you spit out commit logs for the last 3 months, the top 4 committers include 4 different entities. dkulp bimargulies jliu (ex-IONA, independent now) gmazza Yes, there are a bunch of IONA folks (and ex-IONA folks) on the lists, but from an active participant standpoint, we have more than 3 independent parties that are activily participating in the community and providing significant contributions. FYI: that couldn't have been said 6 months ago. The community has come a long way. Dan Davanum Srinivas wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 +1 from me! Bruce Snyder wrote: | On Tue, Mar 18, 2008 at 9:08 AM, Daniel Kulp [EMAIL PROTECTED] wrote: | After 20 months in the incubator, 6 releases complete and 2 more on the | way shortly, several new committers, and too much email traffic : :-), the : | Apache CXF community (with support from our mentors) feels that | we are | ready to graduate to an official top level project at Apache as | indicated by the community vote recorded at: http://www.nabble.com/-VOTE--Graduate-Apache-CXF-as-a-top-level-proj ect-to15812722.html | We would like the resolution attached to this email to be presented to | the board for consideration at the next possible board meeting. | | For additional information, the CXF status file is here: | http://incubator.apache.org/projects/cxf.html | | Thank you in advance for your time and consideration. | | [ ] +1 | [ ] +0 | [ ] -1 | | +1 | | Woot! | | Bruce -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Cygwin) iD8DBQFH3+ERgNg6eWEDv1kRAntlAJ0dGOaV3hL2JetKQZxQ2tB5JSdLggCfTV9T XO5US96T9bitGXnaqRo4l+c= =P/7h -END PGP SIGNATURE- - 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] -- J. Daniel Kulp Principal Engineer, IONA [EMAIL PROTECTED] http://www.dankulp.com/blog signature.asc Description: This is a digitally signed message part.
Re: [DISCUSSION] Hama Proposal
On Mar 18, 2008, at 8:02 AM, edward yoon wrote: Dear Incubator PMC, I've updated the Hama project proposal. Please review/update as needed and report back any concerns. http://wiki.apache.org/incubator/HamaProposal Hama has a strong relationship with the hadoop, hbase and mahout project, so i discussed about become a sub-project of these project for a long time with the each community. However, The sub-project was beset with difficulties. What's the issue w/ Hadoop sub project (I already know the Mahout discussion)? Do you have a mail thread reference? I'm not trying to push anything on the Hadoop PMC, but this logically seems to fit there in my mind as a subproject, but I suppose it could be a TLP as well. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [DISCUSSION] Hama Proposal
This seems small enough in scope and so tied to Hadoop that it seems like it should either just be part of one of the hadoop sub-projects or at a maximum, a hadoop sub-project of it's own. I see you opened https://issues.apache.org/jira/browse/HADOOP-2878 what's the status of that? -Yonik On Tue, Mar 18, 2008 at 8:02 AM, edward yoon [EMAIL PROTECTED] wrote: Dear Incubator PMC, I've updated the Hama project proposal. Please review/update as needed and report back any concerns. http://wiki.apache.org/incubator/HamaProposal Hama has a strong relationship with the hadoop, hbase and mahout project, so i discussed about become a sub-project of these project for a long time with the each community. However, The sub-project was beset with difficulties. Hence the list of committers, etc. And now we all agree that the Hama should aim to general purpose rathen than it becomes a specified piece in something. http://www.nabble.com/-jira--Created%3A-%28MAHOUT-16%29-Hama-contrib-package-for-the-mahout-to15998717.html https://issues.apache.org/jira/browse/HADOOP-2878 If you think this will make a good ASF project, please encourage our team members to create the world's largest matrix computational framework. Thanks. B. Regards, Edward yoon @ NHN, corp. - 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] Apache CXF Graduation as TLP
On Tue, Mar 18, 2008 at 3:08 PM, Daniel Kulp [EMAIL PROTECTED] wrote: After 20 months in the incubator, 6 releases complete and 2 more on the way shortly, several new committers, and too much email traffic :-), the Apache CXF community (with support from our mentors) feels that we are ready to graduate to an official top level project at Apache as indicated by the community vote recorded at: http://www.nabble.com/-VOTE--Graduate-Apache-CXF-as-a-top-level-project-to15812722.html We would like the resolution attached to this email to be presented to the board for consideration at the next possible board meeting. For additional information, the CXF status file is here: http://incubator.apache.org/projects/cxf.html Thank you in advance for your time and consideration. [ ] +1 [ ] +0 [ ] -1 + 1 - robert
Re: [VOTE] Apache CXF Graduation as TLP
Daniel Kulp wrote: On Tuesday 18 March 2008, Carl Trieloff wrote: what is the diversity? Carl. This could have been asked as part of the resolution discussion instead of hijacking the vote, but was out last week - thanks for the info. Carl.
Re: [VOTE] Apache CXF Graduation as TLP
On Tuesday 18 March 2008, Carl Trieloff wrote: Daniel Kulp wrote: On Tuesday 18 March 2008, Carl Trieloff wrote: what is the diversity? Carl. This could have been asked as part of the resolution discussion instead of hijacking the vote, but was out last week - thanks for the info. Carl. No problem. Thanks for raising the question. :-) CXF has worked hard the last 6 months to get to the point we're at today. It's definitely been a good learning experience. -- J. Daniel Kulp Principal Engineer, IONA [EMAIL PROTECTED] http://www.dankulp.com/blog signature.asc Description: This is a digitally signed message part.
VOTE Netiquette [WAS Re: [VOTE] Apache CXF Graduation as TLP]
On Tue, Mar 18, 2008 at 5:39 PM, Carl Trieloff [EMAIL PROTECTED] wrote: Daniel Kulp wrote: On Tuesday 18 March 2008, Carl Trieloff wrote: what is the diversity? Carl. This could have been asked as part of the resolution discussion instead of hijacking the vote, but was out last week - thanks for the info. always good to ask but it's best to edit the subject and start another thread. VOTE threads are hard to tally especially long ones (as these ones typically are). it's best to move any discussion out from the VOTE thread into it's own thread. - robert
Re: [VOTE] Apache CXF Graduation as TLP
+1 Only 20 months huh - lightweights :) On 18/03/2008, Daniel Kulp [EMAIL PROTECTED] wrote: After 20 months in the incubator, 6 releases complete and 2 more on the way shortly, several new committers, and too much email traffic :-), the Apache CXF community (with support from our mentors) feels that we are ready to graduate to an official top level project at Apache as indicated by the community vote recorded at: http://www.nabble.com/-VOTE--Graduate-Apache-CXF-as-a-top-level-project-to15812722.html We would like the resolution attached to this email to be presented to the board for consideration at the next possible board meeting. For additional information, the CXF status file is here: http://incubator.apache.org/projects/cxf.html Thank you in advance for your time and consideration. [ ] +1 [ ] +0 [ ] -1 -- Dan (on behalf of the entire Apache CXF team and with permission from the CXF mentors to call this vote.) == Establish the Apache CXF project WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project, to be known as Apache CXF Project, related to a framework for creating, deploying, and consuming services based on SOA design principles for distribution at no charge to the public. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC) is hereby established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache CXF PMC be and hereby is charged with the creation and maintenance of Apache CXF; and be it further RESOLVED, that the office of Vice President, Apache CXF 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 CXF PMC, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache CXF PMC; and be it further RESOLVED, that the persons listed immediately below be and hereby are appointed to serve as the initial members of the Apache CXF PMC: * Ulhas Bhole [EMAIL PROTECTED] * Sean O'Callaghan [EMAIL PROTECTED] * Dan Diephouse [EMAIL PROTECTED] * Freeman Yue Fang [EMAIL PROTECTED] * Jarek Gawor [EMAIL PROTECTED] * Jeff Genender [EMAIL PROTECTED] * Eoghan Glynn [EMAIL PROTECTED] * Jim Jagielski [EMAIL PROTECTED] * Willem Ning Jiang [EMAIL PROTECTED] * Eric Johnson [EMAIL PROTECTED] * Peter Jones [EMAIL PROTECTED] * Daniel Kulp [EMAIL PROTECTED] * Bozhong Lin [EMAIL PROTECTED] * Jervis Liu [EMAIL PROTECTED] * Jim Ma [EMAIL PROTECTED] * James Maode Mao [EMAIL PROTECTED] * Benson Margulies [EMAIL PROTECTED] * Glen Mazza [EMAIL PROTECTED] * Guillaume Nodet [EMAIL PROTECTED] * Ajay Paibir [EMAIL PROTECTED] NOW, THEREFORE, BE IT FURTHER RESOLVED, that Daniel Kulp be appointed to the office of Vice President, Apache CXF, 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 Apache CXF Project be and hereby is tasked with the migration and rationalization of the Apache Incubator CXF podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator CXF podling encumbered upon the Apache Incubator PMC are hereafter discharged. == - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- James --- http://macstrac.blogspot.com/ Open Source Integration http://open.iona.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Apache CXF Graduation as TLP
+1 Martijn Dashorst - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Apache CXF Graduation as TLP
+1 Good job. Craig On Mar 18, 2008, at 8:08 AM, Daniel Kulp wrote: After 20 months in the incubator, 6 releases complete and 2 more on the way shortly, several new committers, and too much email traffic :-), the Apache CXF community (with support from our mentors) feels that we are ready to graduate to an official top level project at Apache as indicated by the community vote recorded at: http://www.nabble.com/-VOTE--Graduate-Apache-CXF-as-a-top-level-project-to15812722.html We would like the resolution attached to this email to be presented to the board for consideration at the next possible board meeting. For additional information, the CXF status file is here: http://incubator.apache.org/projects/cxf.html Thank you in advance for your time and consideration. [ ] +1 [ ] +0 [ ] -1 -- Dan (on behalf of the entire Apache CXF team and with permission from the CXF mentors to call this vote.) == Establish the Apache CXF project WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project, to be known as Apache CXF Project, related to a framework for creating, deploying, and consuming services based on SOA design principles for distribution at no charge to the public. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC) is hereby established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache CXF PMC be and hereby is charged with the creation and maintenance of Apache CXF; and be it further RESOLVED, that the office of Vice President, Apache CXF 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 CXF PMC, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache CXF PMC; and be it further RESOLVED, that the persons listed immediately below be and hereby are appointed to serve as the initial members of the Apache CXF PMC: * Ulhas Bhole [EMAIL PROTECTED] * Sean O'Callaghan [EMAIL PROTECTED] * Dan Diephouse [EMAIL PROTECTED] * Freeman Yue Fang [EMAIL PROTECTED] * Jarek Gawor [EMAIL PROTECTED] * Jeff Genender [EMAIL PROTECTED] * Eoghan Glynn [EMAIL PROTECTED] * Jim Jagielski [EMAIL PROTECTED] * Willem Ning Jiang [EMAIL PROTECTED] * Eric Johnson [EMAIL PROTECTED] * Peter Jones [EMAIL PROTECTED] * Daniel Kulp [EMAIL PROTECTED] * Bozhong Lin [EMAIL PROTECTED] * Jervis Liu [EMAIL PROTECTED] * Jim Ma [EMAIL PROTECTED] * James Maode Mao [EMAIL PROTECTED] * Benson Margulies [EMAIL PROTECTED] * Glen Mazza [EMAIL PROTECTED] * Guillaume Nodet [EMAIL PROTECTED] * Ajay Paibir [EMAIL PROTECTED] NOW, THEREFORE, BE IT FURTHER RESOLVED, that Daniel Kulp be appointed to the office of Vice President, Apache CXF, 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 Apache CXF Project be and hereby is tasked with the migration and rationalization of the Apache Incubator CXF podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator CXF podling encumbered upon the Apache Incubator PMC are hereafter discharged. == - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Craig Russell Architect, Sun Java Enterprise System http://java.sun.com/products/jdo 408 276-5638 mailto:[EMAIL PROTECTED] P.S. A good JDO? O, Gasp! smime.p7s Description: S/MIME cryptographic signature
Re: [VOTE] Apache CXF Graduation as TLP
On Mar 18, 2008, at 11:08 AM, Daniel Kulp wrote: After 20 months in the incubator, 6 releases complete and 2 more on the way shortly, several new committers, and too much email traffic :-), the Apache CXF community (with support from our mentors) feels that we are ready to graduate to an official top level project at Apache as indicated by the community vote recorded at: http://www.nabble.com/-VOTE--Graduate-Apache-CXF-as-a-top-level-project-to15812722.html We would like the resolution attached to this email to be presented to the board for consideration at the next possible board meeting. For additional information, the CXF status file is here: http://incubator.apache.org/projects/cxf.html Thank you in advance for your time and consideration. [ ] +1 [ ] +0 [ ] -1 +1 --kevan
Re: [VOTE] Apache CXF Graduation as TLP
+1 from me. Congratulations guys! Paul On Tue, Mar 18, 2008 at 7:05 PM, Kevan Miller [EMAIL PROTECTED] wrote: On Mar 18, 2008, at 11:08 AM, Daniel Kulp wrote: After 20 months in the incubator, 6 releases complete and 2 more on the way shortly, several new committers, and too much email traffic :-), the Apache CXF community (with support from our mentors) feels that we are ready to graduate to an official top level project at Apache as indicated by the community vote recorded at: http://www.nabble.com/-VOTE--Graduate-Apache-CXF-as-a-top-level-project-to15812722.html We would like the resolution attached to this email to be presented to the board for consideration at the next possible board meeting. For additional information, the CXF status file is here: http://incubator.apache.org/projects/cxf.html Thank you in advance for your time and consideration. [ ] +1 [ ] +0 [ ] -1 +1 --kevan -- Paul Fremantle Co-Founder and VP of Technical Sales, 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] Apache CXF Graduation as TLP
+1 Niall On Tue, Mar 18, 2008 at 3:08 PM, Daniel Kulp [EMAIL PROTECTED] wrote: After 20 months in the incubator, 6 releases complete and 2 more on the way shortly, several new committers, and too much email traffic :-), the Apache CXF community (with support from our mentors) feels that we are ready to graduate to an official top level project at Apache as indicated by the community vote recorded at: http://www.nabble.com/-VOTE--Graduate-Apache-CXF-as-a-top-level-project-to15812722.html We would like the resolution attached to this email to be presented to the board for consideration at the next possible board meeting. For additional information, the CXF status file is here: http://incubator.apache.org/projects/cxf.html Thank you in advance for your time and consideration. [ ] +1 [ ] +0 [ ] -1 -- Dan (on behalf of the entire Apache CXF team and with permission from the CXF mentors to call this vote.) == Establish the Apache CXF project WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project, to be known as Apache CXF Project, related to a framework for creating, deploying, and consuming services based on SOA design principles for distribution at no charge to the public. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC) is hereby established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache CXF PMC be and hereby is charged with the creation and maintenance of Apache CXF; and be it further RESOLVED, that the office of Vice President, Apache CXF 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 CXF PMC, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache CXF PMC; and be it further RESOLVED, that the persons listed immediately below be and hereby are appointed to serve as the initial members of the Apache CXF PMC: * Ulhas Bhole [EMAIL PROTECTED] * Sean O'Callaghan [EMAIL PROTECTED] * Dan Diephouse [EMAIL PROTECTED] * Freeman Yue Fang [EMAIL PROTECTED] * Jarek Gawor [EMAIL PROTECTED] * Jeff Genender [EMAIL PROTECTED] * Eoghan Glynn [EMAIL PROTECTED] * Jim Jagielski [EMAIL PROTECTED] * Willem Ning Jiang [EMAIL PROTECTED] * Eric Johnson [EMAIL PROTECTED] * Peter Jones [EMAIL PROTECTED] * Daniel Kulp [EMAIL PROTECTED] * Bozhong Lin [EMAIL PROTECTED] * Jervis Liu [EMAIL PROTECTED] * Jim Ma [EMAIL PROTECTED] * James Maode Mao [EMAIL PROTECTED] * Benson Margulies [EMAIL PROTECTED] * Glen Mazza [EMAIL PROTECTED] * Guillaume Nodet [EMAIL PROTECTED] * Ajay Paibir [EMAIL PROTECTED] NOW, THEREFORE, BE IT FURTHER RESOLVED, that Daniel Kulp be appointed to the office of Vice President, Apache CXF, 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 Apache CXF Project be and hereby is tasked with the migration and rationalization of the Apache Incubator CXF podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator CXF 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: KEYS file in distribution
On Tue, Mar 18, 2008 at 8:40 PM, Christopher Lenz [EMAIL PROTECTED] wrote: On 18.03.2008, at 15:50, Robert Burrell Donkin wrote: source distributions should be identical to the contents of version control when the release is cut. Where does this rule come from? it's not a rule: it's a tautology ;-) by definition, a source distribution consists of the contents of version control compressed into an archive. anything else is a binary distribution. I wonder because with CouchDB, source tarballs are created through the GNU-Autotools based build process, rather than being a raw `svn export` of the release tag. We don't keep the auto*-generated configure/make files in the repository (they are generated files after all), but do include them in source tarballs to limit build-time dependencies and make the build process easier for the user. I guess we could start checking in the generating build files into SVN if that's required. But maybe you can back that statement up a bit before we do so? lots of binary distributions at apache contain source. this makes them binary distributions containing source, not source distributions. it's fine to distribute something along those lines to help users who want to be able to build easily but it's not a source distribution. if it makes things easier for users who want to build artifacts themselves, that's greats. source distributions (svn exports) are aimed at developers so they can create accurate diffs and contribute patches, not users. they are also useful for downstream distributors who want to be able to accurately and selectively apply patches. these groups should be able to build in the same way committers do so they don't really need it easy. binary distributions are for users, source distributions for developers. - robert
Re: [VOTE] Apache CXF Graduation as TLP
On Tue, Mar 18, 2008 at 4:08 PM, Daniel Kulp [EMAIL PROTECTED] wrote: ... We would like the resolution attached to this email to be presented to the board for consideration at the next possible board meeting +1 -Bertrand - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: KEYS file in distribution
On 18.03.2008, at 22:06, Robert Burrell Donkin wrote: On Tue, Mar 18, 2008 at 8:40 PM, Christopher Lenz [EMAIL PROTECTED] wrote: I wonder because with CouchDB, source tarballs are created through the GNU-Autotools based build process, rather than being a raw `svn export` of the release tag. We don't keep the auto*-generated configure/make files in the repository (they are generated files after all), but do include them in source tarballs to limit build-time dependencies and make the build process easier for the user. I guess we could start checking in the generating build files into SVN if that's required. But maybe you can back that statement up a bit before we do so? lots of binary distributions at apache contain source. this makes them binary distributions containing source, not source distributions. Maybe I didn't explain properly… our previous (pre-incubation) source distributions did not contain any binaries, only source. The difference between the tarballs and a source control checkout is that the former has some generated build scripts. Looking into the HTTPD repos and comparing to the HTTPD source tarballs, they appear to be doing the same thing: there's a configure file in the source tarball, but not in the repos. In general I'd say this is common practice for any project based on Autotools. [snip] source distributions (svn exports) are aimed at developers so they can create accurate diffs and contribute patches, not users. they are also useful for downstream distributors who want to be able to accurately and selectively apply patches. these groups should be able to build in the same way committers do so they don't really need it easy. binary distributions are for users, source distributions for developers. The generated source tarballs don't in anyway prevent developers from providing good patches. They contain the source plus some build files pre-generated for convenience (which can be regenerated from the very same tarballs nonetheless). Also, again similar to HTTPD, the source tarball is actually the main distribution for users, too (except the Windows camp, which we don't support yet anyway). Cheers, -- Christopher Lenz cmlenz at gmx.de http://www.cmlenz.net/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: KEYS file in distribution
On 18/03/2008, Robert Burrell Donkin [EMAIL PROTECTED] wrote: On Tue, Mar 18, 2008 at 9:44 PM, Christopher Lenz [EMAIL PROTECTED] wrote: On 18.03.2008, at 22:06, Robert Burrell Donkin wrote: On Tue, Mar 18, 2008 at 8:40 PM, Christopher Lenz [EMAIL PROTECTED] wrote: I wonder because with CouchDB, source tarballs are created through the GNU-Autotools based build process, rather than being a raw `svn export` of the release tag. We don't keep the auto*-generated configure/make files in the repository (they are generated files after all), but do include them in source tarballs to limit build-time dependencies and make the build process easier for the user. I guess we could start checking in the generating build files into SVN if that's required. But maybe you can back that statement up a bit before we do so? lots of binary distributions at apache contain source. this makes them binary distributions containing source, not source distributions. Maybe I didn't explain properly… our previous (pre-incubation) source distributions did not contain any binaries, only source. The difference between the tarballs and a source control checkout is that the former has some generated build scripts. yes: you explained that quite well the first time any distribution containing stuff which isn't in subversion is by definition a binary distribution Is this documented anywhere? Looking into the HTTPD repos and comparing to the HTTPD source tarballs, they appear to be doing the same thing: there's a configure file in the source tarball, but not in the repos. In general I'd say this is common practice for any project based on Autotools. IMHO it's not worth getting into arguments about HTTPD current verses original/best practice yes, it's common practice but it's important to distinguish terminology from presentation. what a source distribution means is a direct export from subversion. it's fine to create a distribution containing generated stuff; call it what you will; recommend it to users who want to build from source. still counts as a binary as far as rules and whatnot go. And where are these rules defined? there is a slight possibility that fans of source distribution may complain if you don't issue a source distribution. IMHO if that's the case then that's the time to present your arguments. till then, it's just terminology. [snip] source distributions (svn exports) are aimed at developers so they can create accurate diffs and contribute patches, not users. they are also useful for downstream distributors who want to be able to accurately and selectively apply patches. these groups should be able to build in the same way committers do so they don't really need it easy. binary distributions are for users, source distributions for developers. The generated source tarballs don't in anyway prevent developers from providing good patches. They contain the source plus some build files pre-generated for convenience (which can be regenerated from the very same tarballs nonetheless). IMHO it's best to avoid getting into this kind of argument: it's just terminology Also, again similar to HTTPD, the source tarball is actually the main distribution for users, too (except the Windows camp, which we don't support yet anyway). that's fine - robert - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Qpid Status page, was Re: Graduation resolution feedback - Qpid as TLP
folks, I have updated the status page with the news items Carl posted. I also added Craig's name under mentors. It will take some time for it to get it synced. Regards, Rajith On Tue, Mar 18, 2008 at 2:13 PM, Carl Trieloff [EMAIL PROTECTED] wrote: Carl Trieloff wrote: Yoav Shapira wrote: No rush, I probably won't get to do it until Monday next week anyhow. Others are welcome to help as well, it's not all on your shoulders ;) Yoav We are also missing Criag as a mentor on our status page. Below I have started a list for news, please correct and add to the list. This is what I have dug out of the board reports so far. Carl Aug 06 - Acceptance into Incubator Sept 06 - Project setup Nov 06 - Creation of committer accounts Nov 06 - IP Clearance for code grant Jan 07 - New C++ build/ make system May 07 - Addition of new committers (7 by May) June 07 - Addition of .NET client June 07 - M1 release of Qpid July 07 - Addition of new committers (3 more by July) July 07 - Closing of legal questions on TCK passing all JMS TCK tests Oct 07 - M2 release of Qpid Nov 07 - Addition of new committers (2 more by Nov) Dec 07 - Moving of build system back to Ant Dec 07 - Set scope and dates for M2.1 Jan 08 - Vote of Qpid community to request graduation as TLP Feb 08 - Karma clean up, done by community process Updated, dates by looking at svn log. Carl. -- Regards, Rajith Attapattu Red Hat blog: http://rajith.2rlabs.com/
Re: Qpid Status page, was Re: Graduation resolution feedback - Qpid as TLP
Thanks Rajith, I guess we are then ready to start a vote. regards, Carl. Rajith Attapattu wrote: folks, I have updated the status page with the news items Carl posted. I also added Craig's name under mentors. It will take some time for it to get it synced. Regards, Rajith On Tue, Mar 18, 2008 at 2:13 PM, Carl Trieloff [EMAIL PROTECTED] wrote: Carl Trieloff wrote: Yoav Shapira wrote: No rush, I probably won't get to do it until Monday next week anyhow. Others are welcome to help as well, it's not all on your shoulders ;) Yoav We are also missing Criag as a mentor on our status page. Below I have started a list for news, please correct and add to the list. This is what I have dug out of the board reports so far. Carl Aug 06 - Acceptance into Incubator Sept 06 - Project setup Nov 06 - Creation of committer accounts Nov 06 - IP Clearance for code grant Jan 07 - New C++ build/ make system May 07 - Addition of new committers (7 by May) June 07 - Addition of .NET client June 07 - M1 release of Qpid July 07 - Addition of new committers (3 more by July) July 07 - Closing of legal questions on TCK passing all JMS TCK tests Oct 07 - M2 release of Qpid Nov 07 - Addition of new committers (2 more by Nov) Dec 07 - Moving of build system back to Ant Dec 07 - Set scope and dates for M2.1 Jan 08 - Vote of Qpid community to request graduation as TLP Feb 08 - Karma clean up, done by community process Updated, dates by looking at svn log. Carl.
