RE: [VOTE] James as an official Apache project
Hi, I haven't forgotten this, but have been sidetracked by real-life issues(!) So, to summarise, the results of the voting were in favour of the proposal That we should prepare a proposal for submission to the board, that James be elevated to a top level Apache project. as follows: Binding votes: +1 Serge Knystautas Danny Angus Peter Goldstein Noel Bergman Charles Bennet +0 None -0 None -1 None Commiters who did not vote, or are inactive: Harmeet Bedi Darrell De Boer Peter Donald Paul Hammant Brendan Burns James Duncan Davidson Jon Scott Stevens Votes of support from the community: +1 Stephen McConnell Brad Walker Scott Sanders Steve Short Alan Gerhard Leo Simons David Jenkins Jason Webb Dave Richardson Serge Sozonoff Chris Means -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: [VOTE] James as an official Apache project
On Thu, 21 Nov 2002 19:52, Danny Angus wrote: Hi, I haven't forgotten this, but have been sidetracked by real-life issues(!) So, to summarise, the results of the voting were in favour of the proposal That we should prepare a proposal for submission to the board, that James be elevated to a top level Apache project. as follows: My very late +1 Binding votes: +1 Serge Knystautas Danny Angus Peter Goldstein Noel Bergman Charles Bennet Darrell DeBoer +0 None -0 None -1 None Commiters who did not vote, or are inactive: Harmeet Bedi Darrell De Boer Peter Donald Paul Hammant Brendan Burns James Duncan Davidson Jon Scott Stevens Votes of support from the community: +1 Stephen McConnell Brad Walker Scott Sanders Steve Short Alan Gerhard Leo Simons David Jenkins Jason Webb Dave Richardson Serge Sozonoff Chris Means -- ciao, Daz -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: [VOTE] James as an official Apache project
Danny, No worries. Thinking about it the other day, I figured that we'd get onto this in December after we shipped v2.1. It is nice of Stephen McConnell to offer his assistance, having just participated in Avalon's successful promotion. I propose Serge to have the honor of being the initial PMC Chairman, and all Committers as the initial PMC, unless they wish to demure. Please note: next week is Thanksgiving in the USA. It is most likely that a number of us will probably be off-line for extended periods. --- Noel -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: [VOTE] James as an official Apache project
All, I propose Serge to have the honor of being the initial PMC Chairman, and all Committers as the initial PMC, unless they wish to demure. +1 --Peter -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: [VOTE] James as an official Apache project
- Original Message - From: Noel J. Bergman [EMAIL PROTECTED] I propose Serge to have the honor of being the initial PMC Chairman. +1. Harmeet -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: [VOTE] James as an official Apache project
+1 I suggest (like Noel) that the inital PMC is all committers. Charles Danny Angus wrote: All, Now that we've had a chance to digest whats meant by a top level project, I'll subject you to my opinion, which I've held back so far. Basically I'm in favour of proposing james as an apache top level project (tlp), I'm prepared to take the lead on our proposal, and here's why: James has a small yet mature community, we seldom seek recourse to the jakarta PMC, and equally seldom are we scrutinised by them. We are not the most active project, and I feel that this sometimes causes James to be disregarded. Likewise, apart from Avalon, we have few direct ties with other jakarta projects, and little in common apart from the language/platform and culture (but the culture is Apache) The tlp issue is more about management than web-site and mail addresses, I don't believe that james.apache.org will bring many benefits, but I do think that normalising our managerial relationship with Jakarta by becoming a sibling rather than a child, and taking official control of all the issues we currently inherit and interpret from Jakarta would benefit James. The James PMC would be responsible to The Board. I do believe that Jakarta is becoming too big to function as a single project, that community and culture become diluted as you descend the heirarchy and that one solution is for mature projects leave the nest. Of course other projects are free to make their own choices but as James consists primarily of the server which is an end-user product I feel that top level project status, emphasisng its purpose rather then its technology, would suit it well. The proposals being discussed on reorg community include the notion of federated projects, James, with the approval of the Jakarta PMC, could continue to be associated with Jakarta, I would like to think that we wouldn't be leaving Jakarta, just growing up. I also know that James would continue to rely on Jakarta for code, insight and cool thinking, but we don't need to be a Jakarta sub-project for that. It would also give us the opportunity, as Serge mentioned, to better promote our sub-projects, theres Mailet, and mailets, and there are the beginings of full blown mailet applications. So.. we've had time to examine the issues, lets vote.. Should we prepare a proposal for submission to the board, that James be elevated to a top level project? [ ] +1 I think it's a good idea [ ] +0 I'll accept the majority decision, stop bothering me [ ] -0 I have reservations [ ] -1, I don't think its a good idea d. -- To unsubscribe, e-mail: mailto:james-dev-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:james-dev-help;jakarta.apache.org -- To unsubscribe, e-mail: mailto:james-dev-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:james-dev-help;jakarta.apache.org
RE: [VOTE] James as an official Apache project
+1 (if I'm not too late) -- Jason -- To unsubscribe, e-mail: mailto:james-dev-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:james-dev-help;jakarta.apache.org
RE: [VOTE] James as an official Apache project
Jason, No not too late, I'll give this one a week, and possibly prod some of the commiters who are innactive in James but active elsewhere in Jakarta. A yes vote now, while not being a vote to actually submit a proposal, (we should probably have a lazy vote on the proposal before we submit it) represents the biggest shift in James PM since I-dont-know-when, its adoption by java.apache or the inception of Jakarta probably. We really don't want people to misunderstand our motives, or misconstrue our opinions about Jakarta, and I would feel most confident about going ahead with this if we can get a full turnout and no -1's Even then there's no guarantee we'd be accepted. d. -Original Message- From: Jason Webb [mailto:jw;inovem.com] Sent: 31 October 2002 09:39 To: 'James Developers List' Subject: RE: [VOTE] James as an official Apache project +1 (if I'm not too late) -- Jason -- To unsubscribe, e-mail: mailto:james-dev-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:james-dev-help;jakarta.apache.org -- To unsubscribe, e-mail: mailto:james-dev-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:james-dev-help;jakarta.apache.org
[VOTE] James as an official Apache project
All, Now that we've had a chance to digest whats meant by a top level project, I'll subject you to my opinion, which I've held back so far. Basically I'm in favour of proposing james as an apache top level project (tlp), I'm prepared to take the lead on our proposal, and here's why: James has a small yet mature community, we seldom seek recourse to the jakarta PMC, and equally seldom are we scrutinised by them. We are not the most active project, and I feel that this sometimes causes James to be disregarded. Likewise, apart from Avalon, we have few direct ties with other jakarta projects, and little in common apart from the language/platform and culture (but the culture is Apache) The tlp issue is more about management than web-site and mail addresses, I don't believe that james.apache.org will bring many benefits, but I do think that normalising our managerial relationship with Jakarta by becoming a sibling rather than a child, and taking official control of all the issues we currently inherit and interpret from Jakarta would benefit James. The James PMC would be responsible to The Board. I do believe that Jakarta is becoming too big to function as a single project, that community and culture become diluted as you descend the heirarchy and that one solution is for mature projects leave the nest. Of course other projects are free to make their own choices but as James consists primarily of the server which is an end-user product I feel that top level project status, emphasisng its purpose rather then its technology, would suit it well. The proposals being discussed on reorg community include the notion of federated projects, James, with the approval of the Jakarta PMC, could continue to be associated with Jakarta, I would like to think that we wouldn't be leaving Jakarta, just growing up. I also know that James would continue to rely on Jakarta for code, insight and cool thinking, but we don't need to be a Jakarta sub-project for that. It would also give us the opportunity, as Serge mentioned, to better promote our sub-projects, theres Mailet, and mailets, and there are the beginings of full blown mailet applications. So.. we've had time to examine the issues, lets vote.. Should we prepare a proposal for submission to the board, that James be elevated to a top level project? [ ] +1 I think it's a good idea [ ] +0 I'll accept the majority decision, stop bothering me [ ] -0 I have reservations [ ] -1, I don't think its a good idea d. -- To unsubscribe, e-mail: mailto:james-dev-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:james-dev-help;jakarta.apache.org
RE: [VOTE] James as an official Apache project
Should we prepare a proposal for submission to the board, that James be elevated to a top level project? [ ] +1 I think it's a good idea [ ] +0 I'll accept the majority decision, stop bothering me [ ] -0 I have reservations [ ] -1, I don't think its a good idea My non-binding +1. I think a mailets sub-project space should be included in that proposal. Scott -- To unsubscribe, e-mail: mailto:james-dev-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:james-dev-help;jakarta.apache.org
RE: [VOTE] James as an official Apache project
PS... Theres a tradition of people voting who's vote may not count, do that please because I'd really like to hear from the whole community, not just the commiters. d. -- To unsubscribe, e-mail: mailto:james-dev-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:james-dev-help;jakarta.apache.org
Re: [VOTE] James as an official Apache project
Danny Angus wrote: All, Now that we've had a chance to digest whats meant by a top level project, I'll subject you to my opinion, which I've held back so far. Basically I'm in favour of proposing james as an apache top level project (tlp), I'm prepared to take the lead on our proposal, and here's why: James has a small yet mature community, we seldom seek recourse to the jakarta PMC, and equally seldom are we scrutinised by them. We are not the most active project, and I feel that this sometimes causes James to be disregarded. Likewise, apart from Avalon, we have few direct ties with other jakarta projects, and little in common apart from the language/platform and culture (but the culture is Apache) The tlp issue is more about management than web-site and mail addresses, I don't believe that james.apache.org will bring many benefits, but I do think that normalising our managerial relationship with Jakarta by becoming a sibling rather than a child, and taking official control of all the issues we currently inherit and interpret from Jakarta would benefit James. The James PMC would be responsible to The Board. I do believe that Jakarta is becoming too big to function as a single project, that community and culture become diluted as you descend the heirarchy and that one solution is for mature projects leave the nest. Of course other projects are free to make their own choices but as James consists primarily of the server which is an end-user product I feel that top level project status, emphasisng its purpose rather then its technology, would suit it well. The proposals being discussed on reorg community include the notion of federated projects, James, with the approval of the Jakarta PMC, could continue to be associated with Jakarta, I would like to think that we wouldn't be leaving Jakarta, just growing up. I also know that James would continue to rely on Jakarta for code, insight and cool thinking, but we don't need to be a Jakarta sub-project for that. It would also give us the opportunity, as Serge mentioned, to better promote our sub-projects, theres Mailet, and mailets, and there are the beginings of full blown mailet applications. So.. we've had time to examine the issues, lets vote.. Should we prepare a proposal for submission to the board, that James be elevated to a top level project? [ ] +1 I think it's a good idea [ ] +0 I'll accept the majority decision, stop bothering me [ ] -0 I have reservations [ ] -1, I don't think its a good idea +1 Cheers, Steve. -- Stephen J. McConnell OSM SARL digital products for a global economy mailto:mcconnell;osm.net http://www.osm.net -- To unsubscribe, e-mail: mailto:james-dev-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:james-dev-help;jakarta.apache.org
RE: [VOTE] James as an official Apache project
+1 without a doubt -Original Message- From: Danny Angus [mailto:danny;apache.org] Sent: Wednesday, October 30, 2002 12:56 PM To: James Developers List Subject: RE: [VOTE] James as an official Apache project PS... Theres a tradition of people voting who's vote may not count, do that please because I'd really like to hear from the whole community, not just the commiters. d. -- To unsubscribe, e-mail: mailto:james-dev-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:james-dev-help;jakarta.apache.org -- To unsubscribe, e-mail: mailto:james-dev-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:james-dev-help;jakarta.apache.org
RE: [VOTE] James as an official Apache project
+1. -Original Message- From: Danny Angus [mailto:danny;apache.org] Sent: Wednesday, October 30, 2002 9:47 AM To: James Developers List Subject: [VOTE] James as an official Apache project All, Now that we've had a chance to digest whats meant by a top level project, I'll subject you to my opinion, which I've held back so far. Basically I'm in favour of proposing james as an apache top level project (tlp), I'm prepared to take the lead on our proposal, and here's why: James has a small yet mature community, we seldom seek recourse to the jakarta PMC, and equally seldom are we scrutinised by them. We are not the most active project, and I feel that this sometimes causes James to be disregarded. Likewise, apart from Avalon, we have few direct ties with other jakarta projects, and little in common apart from the language/platform and culture (but the culture is Apache) The tlp issue is more about management than web-site and mail addresses, I don't believe that james.apache.org will bring many benefits, but I do think that normalising our managerial relationship with Jakarta by becoming a sibling rather than a child, and taking official control of all the issues we currently inherit and interpret from Jakarta would benefit James. The James PMC would be responsible to The Board. I do believe that Jakarta is becoming too big to function as a single project, that community and culture become diluted as you descend the heirarchy and that one solution is for mature projects leave the nest. Of course other projects are free to make their own choices but as James consists primarily of the server which is an end-user product I feel that top level project status, emphasisng its purpose rather then its technology, would suit it well. The proposals being discussed on reorg community include the notion of federated projects, James, with the approval of the Jakarta PMC, could continue to be associated with Jakarta, I would like to think that we wouldn't be leaving Jakarta, just growing up. I also know that James would continue to rely on Jakarta for code, insight and cool thinking, but we don't need to be a Jakarta sub-project for that. It would also give us the opportunity, as Serge mentioned, to better promote our sub-projects, theres Mailet, and mailets, and there are the beginings of full blown mailet applications. So.. we've had time to examine the issues, lets vote.. Should we prepare a proposal for submission to the board, that James be elevated to a top level project? [ ] +1 I think it's a good idea [ ] +0 I'll accept the majority decision, stop bothering me [ ] -0 I have reservations [ ] -1, I don't think its a good idea d. -- To unsubscribe, e-mail: mailto:james-dev- [EMAIL PROTECTED] For additional commands, e-mail: mailto:james-dev- [EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:james-dev-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:james-dev-help;jakarta.apache.org
RE: [VOTE] James as an official Apache project
+1 (Non-committer) -Original Message- From: Danny Angus [mailto:danny;apache.org] Sent: Wednesday, October 30, 2002 9:47 AM To: James Developers List Subject: [VOTE] James as an official Apache project All, Now that we've had a chance to digest whats meant by a top level project, I'll subject you to my opinion, which I've held back so far. Basically I'm in favour of proposing james as an apache top level project (tlp), I'm prepared to take the lead on our proposal, and here's why: James has a small yet mature community, we seldom seek recourse to the jakarta PMC, and equally seldom are we scrutinised by them. We are not the most active project, and I feel that this sometimes causes James to be disregarded. Likewise, apart from Avalon, we have few direct ties with other jakarta projects, and little in common apart from the language/platform and culture (but the culture is Apache) The tlp issue is more about management than web-site and mail addresses, I don't believe that james.apache.org will bring many benefits, but I do think that normalising our managerial relationship with Jakarta by becoming a sibling rather than a child, and taking official control of all the issues we currently inherit and interpret from Jakarta would benefit James. The James PMC would be responsible to The Board. I do believe that Jakarta is becoming too big to function as a single project, that community and culture become diluted as you descend the heirarchy and that one solution is for mature projects leave the nest. Of course other projects are free to make their own choices but as James consists primarily of the server which is an end-user product I feel that top level project status, emphasisng its purpose rather then its technology, would suit it well. The proposals being discussed on reorg community include the notion of federated projects, James, with the approval of the Jakarta PMC, could continue to be associated with Jakarta, I would like to think that we wouldn't be leaving Jakarta, just growing up. I also know that James would continue to rely on Jakarta for code, insight and cool thinking, but we don't need to be a Jakarta sub-project for that. It would also give us the opportunity, as Serge mentioned, to better promote our sub-projects, theres Mailet, and mailets, and there are the beginings of full blown mailet applications. So.. we've had time to examine the issues, lets vote.. Should we prepare a proposal for submission to the board, that James be elevated to a top level project? [ ] +1 I think it's a good idea [ ] +0 I'll accept the majority decision, stop bothering me [ ] -0 I have reservations [ ] -1, I don't think its a good idea d. -- To unsubscribe, e-mail: mailto:james-dev- [EMAIL PROTECTED] For additional commands, e-mail: mailto:james-dev-help;jakarta.apache.org -- To unsubscribe, e-mail: mailto:james-dev-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:james-dev-help;jakarta.apache.org
RE: [VOTE] James as an official Apache project
Danny, Do you want to adopt the Cocoon project's proposal that the (initial) PMC be made from all Committers who want on, or do you have other thoughts? --- Noel -- To unsubscribe, e-mail: mailto:james-dev-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:james-dev-help;jakarta.apache.org
Re: [VOTE] James as an official Apache project
my un-official vote is a +1 with following in mind The tlp issue is more about management than web-site and mail addresses I firmly believe that James will benefit with the resources a tlp brings alan -- This EMail Was brought to you by WebMail A Netwin Web Based EMail Client http://netwinsite.com/webmail/tag.htm -- To unsubscribe, e-mail: mailto:james-dev-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:james-dev-help;jakarta.apache.org
Re: [VOTE] James as an official Apache project
On Wed, 2002-10-30 at 18:46, Danny Angus wrote: Should we prepare a proposal for submission to the board, that James be elevated to a top level project? [X] +1 I think it's a good idea [ ] +0 I'll accept the majority decision, stop bothering me [ ] -0 I have reservations [ ] -1, I don't think its a good idea non-binding :) cheers, Leo Simons -- To unsubscribe, e-mail: mailto:james-dev-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:james-dev-help;jakarta.apache.org
Re: [VOTE] James as an official Apache project
+1 Here -- To unsubscribe, e-mail: mailto:james-dev-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:james-dev-help;jakarta.apache.org
