[VOTE] Release JCS 1.3
Hi folks, After much discussion on the JCS developer list, the first official release of JCS (version 1.3) after leaving the Turbine project is ready to vote on. You can find the created artifacts here: site: http://people.apache.org/~tv/jcs/ jars: http://people.apache.org/~tv/jcs/jar/ dist: http://people.apache.org/~tv/jcs/dist/ Now, shall we release JCS as it is published there? [ ] +1 Yes, JCS 1.3 should be released [ ] 0 I do not care [ ] -1 No (give reasons) Voting is subject to the rules described in http://jakarta.apache.org/site/management.html The deadline is Sat, June 1 2007, 12:00 CET Note that the Jakarta PMC has the final word on whether the release is published or not. Bye, Thomas - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release JCS 1.3
Thomas Vandahl wrote: Now, shall we release JCS as it is published there? [X] +1 Yes, JCS 1.3 should be released [ ] 0 I do not care [ ] -1 No (give reasons) Bye, Thomas. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release JCS 1.3
Sorry, but: -1 There should be NOTICE files in all the archives (jar, zip etc). The NOTICE file (found in SVN) needs to refer to Xerox - see jcs-1.3\src\aspect\Trace.aj No KEYS file to check the signatures - and could not find it in SVN. Sourcefiles: There should probably be AL2.0 headers in the .aj files (apart from Trace.aj) -0 Other problems: Website: The Changes report refers to CVS - this should really be SVN The JCoverage report should really open in a new window, as is done for Javadocs etc. The Checkstyle report is in German, ideally it should be in English. Project Team: both tv and jvanzyl are committers Sebb AT AO On 26/05/07, Thomas Vandahl [EMAIL PROTECTED] wrote: Hi folks, After much discussion on the JCS developer list, the first official release of JCS (version 1.3) after leaving the Turbine project is ready to vote on. You can find the created artifacts here: site: http://people.apache.org/~tv/jcs/ jars: http://people.apache.org/~tv/jcs/jar/ dist: http://people.apache.org/~tv/jcs/dist/ Now, shall we release JCS as it is published there? [ ] +1 Yes, JCS 1.3 should be released [ ] 0 I do not care [ ] -1 No (give reasons) Voting is subject to the rules described in http://jakarta.apache.org/site/management.html The deadline is Sat, June 1 2007, 12:00 CET Note that the Jakarta PMC has the final word on whether the release is published or not. Bye, Thomas - 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] Release JCS 1.3
sebb wrote: Sorry, but: -1 There should be NOTICE files in all the archives (jar, zip etc). The NOTICE file (found in SVN) needs to refer to Xerox - see jcs-1.3\src\aspect\Trace.aj No KEYS file to check the signatures - and could not find it in SVN. Sourcefiles: There should probably be AL2.0 headers in the .aj files (apart from Trace.aj) One should not do those things in a hurry. Sorry for this. I will rebuild the stuff and upload it again. -0 Other problems: Website: The Changes report refers to CVS - this should really be SVN Changed. The JCoverage report should really open in a new window, as is done for Javadocs etc. This is standard Maven stuff. How would you change that? The Checkstyle report is in German, ideally it should be in English. Fixed. Project Team: both tv and jvanzyl are committers Actually my contributions are very small, so I'm fine with the contributor status. Bye, Thomas. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release JCS 1.3
On 26/05/07, Thomas Vandahl [EMAIL PROTECTED] wrote: sebb wrote: Sorry, but: -1 There should be NOTICE files in all the archives (jar, zip etc). The NOTICE file (found in SVN) needs to refer to Xerox - see jcs-1.3\src\aspect\Trace.aj No KEYS file to check the signatures - and could not find it in SVN. Sourcefiles: There should probably be AL2.0 headers in the .aj files (apart from Trace.aj) One should not do those things in a hurry. Sorry for this. I will rebuild the stuff and upload it again. -0 Other problems: Website: The Changes report refers to CVS - this should really be SVN Changed. The JCoverage report should really open in a new window, as is done for Javadocs etc. This is standard Maven stuff. How would you change that? Sorry, no idea. The Checkstyle report is in German, ideally it should be in English. Fixed. Project Team: both tv and jvanzyl are committers Actually my contributions are very small, so I'm fine with the contributor status. But you _are_ still a committer... Also what about jvanzyl? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PROPOSAL] The future of Jakarta
On 5/25/07, Henri Yandell [EMAIL PROTECTED] wrote: 4) Goto code.google. Ack :( I wouldn't discount GoogleCode (or Java.net or SourceForge or CodeHaus). Right now, there's a GoogleCode site that I use everyday, and it's been utterly reliable. There's features I miss, but the UI is so convenient, I don't mind. We are not Borg, and not every software product need live under the ASF umbella. Jakarta2 - A flattened commons-like umbrella which in terms of change means a flattened dev@ list and svn changes. What I don't know is whether people are going to be demanding that the subsites look the same; ie) need to mavenize each project and adjust the site. The easiest way to deal with things will be to move the other subprojects into Commons and reestablish the Project. This is probably just an unfortunate turn of phrase, but we can't just move anyone anywhere. The Incubator PMC is not going to accept any code without volunteers to go with it. Likewise, we can't do anything about the subproject websites without volunteers to do that work too. But, as a PMC, we could ask infra@ to create a shared mailing lists to replace the others, and make karma adjustments. Here's my take-away from Henri's post. The Jakata PMC, as it stands today, could set a deadline for the remaining subprojects to make other hosting arrangements (TLP, Commons, Google). Otherwise, on a date certain, we would create single Jakarta Dev and User lists for all the remaining subprojects to share, and open karma to all the subprojects to all the Jakarta committers, in the style of the Commons. In other words, create a TLP, join the Commons, or become a commons. One other alternative would be for the active committers to those remaining subprojects to draft their own resolution proposal for creating a new Jakarta PMC, and boot the rest of us out. :) Though, if anyone wanted to make that happen, I'd suggest making it happen for the June board meeting, to coincide with the Commons proposal. -Ted. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release JCS 1.3
sebb wrote: On 26/05/07, Thomas Vandahl [EMAIL PROTECTED] wrote: sebb wrote: Project Team: both tv and jvanzyl are committers Actually my contributions are very small, so I'm fine with the contributor status. But you _are_ still a committer... Surely it is up to Thomas to decide how he wants to be listed? Also what about jvanzyl? So as a committer Jason is welcome to make this change. I don't see this as the responsibility of the release manager. Scott - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Commons moving to TLP
On 5/23/07, Niall Pemberton [EMAIL PROTECTED] wrote: Committ access and being a PMC memeber are 2 different things - its been mooted that we should carry over the current Jakarta commit list for Commons (which I'm in favour of) - but that would be for the PMC to decide if its formed. Retaining someones commit access is a passive thing which is OK - making someone responsibe for a new TLP needs their consent IMO. As to the point of active consent, did each and every individual listed on the proposed resolution either actively consent in an email message on an ASF list, or add their own name to the list? In other words, what was the source of the initial list of PMC members? If there was a thread behind this thread, we should incorporate it by reference. -Ted. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release JCS 1.3
sebb wrote: But you _are_ still a committer... Yes, but then, everybody else in Jakarta is also potentially a committer for JCS and we would not want to list them all. By, Thomas. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release JCS 1.3
On 26/05/07, Scott Eade [EMAIL PROTECTED] wrote: sebb wrote: On 26/05/07, Thomas Vandahl [EMAIL PROTECTED] wrote: sebb wrote: Project Team: both tv and jvanzyl are committers Actually my contributions are very small, so I'm fine with the contributor status. But you _are_ still a committer... Surely it is up to Thomas to decide how he wants to be listed? Also what about jvanzyl? So as a committer Jason is welcome to make this change. I don't see this as the responsibility of the release manager. OK, fine. The page does not entirely agree with the SVN history; it was not clear if that was deliberate or accidental. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release JCS 1.3
sebb wrote: Sorry, but: -1 There should be NOTICE files in all the archives (jar, zip etc). The NOTICE file (found in SVN) needs to refer to Xerox - see jcs-1.3\src\aspect\Trace.aj No KEYS file to check the signatures - and could not find it in SVN. Sourcefiles: There should probably be AL2.0 headers in the .aj files (apart from Trace.aj) -0 Other problems: Website: The Changes report refers to CVS - this should really be SVN The JCoverage report should really open in a new window, as is done for Javadocs etc. The Checkstyle report is in German, ideally it should be in English. All complaints have been fixed. The new versions are online. I beg for pardon again. I uploaded a copy of the KEYS file to both, the jar and the dist directory for your convenience. I'm not sure how to handle the Xerox copyright stuff. I included the whole text inside the NOTICE file for now. Don't know if that is appropriate. Would you please be so kind as to review again and vote again. Bye, Thomas. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Commons moving to TLP
Ted Husted wrote: As to the point of active consent, did each and every individual listed on the proposed resolution either actively consent in an email message on an ASF list, or add their own name to the list? Based on the Wiki history... http://wiki.apache.org/jakarta-commons/TLPResolution?action=info Rory Winston - was added by Daniel Savarese Torsten Curdt - was added as chair by Henri Yandell All others added themselves. hope that helps, Roland - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release JCS 1.3
On 26/05/07, Thomas Vandahl [EMAIL PROTECTED] wrote: sebb wrote: Sorry, but: -1 There should be NOTICE files in all the archives (jar, zip etc). The NOTICE file (found in SVN) needs to refer to Xerox - see jcs-1.3\src\aspect\Trace.aj No KEYS file to check the signatures - and could not find it in SVN. Sourcefiles: There should probably be AL2.0 headers in the .aj files (apart from Trace.aj) -0 Other problems: Website: The Changes report refers to CVS - this should really be SVN The JCoverage report should really open in a new window, as is done for Javadocs etc. The Checkstyle report is in German, ideally it should be in English. All complaints have been fixed. The new versions are online. I beg for pardon again. I uploaded a copy of the KEYS file to both, the jar and the dist directory for your convenience. I'm not sure how to handle the Xerox copyright stuff. I included the whole text inside the NOTICE file for now. Don't know if that is appropriate. I don't think so. The NOTICE is not supposed to contain the license. See: http://svn.apache.org/viewvc/httpd/httpd/trunk/ for an example. Would you please be so kind as to review again and vote again. Bye, Thomas. - 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] Commons moving to TLP
In message [EMAIL PROTECTED], Roland Weber writes: Rory Winston - was added by Daniel Savarese Torsten Curdt - was added as chair by Henri Yandell Rory voted for the proposal so I saved him the time and redundancy when I added myself after voting for the proposal. I assume Henri did the same for Torsten. daniel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Commons moving to TLP
IIRC Torsten had already added himself to the proposal, then after emails in which T. indicated his willingness to act as chair, Henri updated the wiki accordingly. -Matt --- Daniel F. Savarese [EMAIL PROTECTED] wrote: In message [EMAIL PROTECTED], Roland Weber writes: Rory Winston - was added by Daniel Savarese Torsten Curdt - was added as chair by Henri Yandell Rory voted for the proposal so I saved him the time and redundancy when I added myself after voting for the proposal. I assume Henri did the same for Torsten. daniel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Sucker-punch spam with award-winning protection. Try the free Yahoo! Mail Beta. http://advision.webevents.yahoo.com/mailbeta/features_spam.html - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PROPOSAL] The future of Jakarta
On 5/26/07, Ted Husted [EMAIL PROTECTED] wrote: On 5/25/07, Henri Yandell [EMAIL PROTECTED] wrote: 4) Goto code.google. Ack :( I wouldn't discount GoogleCode (or Java.net or SourceForge or CodeHaus). Right now, there's a GoogleCode site that I use everyday, and it's been utterly reliable. There's features I miss, but the UI is so convenient, I don't mind. We are not Borg, and not every software product need live under the ASF umbella. Ack in terms of driving a community away because it is unable to meet our arbitrary criteria. Jakarta2 - A flattened commons-like umbrella which in terms of change means a flattened dev@ list and svn changes. What I don't know is whether people are going to be demanding that the subsites look the same; ie) need to mavenize each project and adjust the site. The easiest way to deal with things will be to move the other subprojects into Commons and reestablish the Project. This is probably just an unfortunate turn of phrase, but we can't just move anyone anywhere. Yes we can, we just choose not to. Our PMC has a history of delegating the decision making to the subprojects, rather than making it for them; it's not a requirement. Still - I'm definitely presuming that that will continue. Subprojects need to be on board. The problem is when a subproject chooses option 5; do nothing. Is that a decision we're happy with. The Incubator PMC is not going to accept any code without volunteers to go with it. Things get really easy in that situation - we retire it just like Alexandria. We've not got any code without community currently. Likewise, we can't do anything about the subproject websites without volunteers to do that work too. We can volunteer. (I'll happily go in and change things :) ). But, as a PMC, we could ask infra@ to create a shared mailing lists to replace the others, and make karma adjustments. Here's my take-away from Henri's post. The Jakata PMC, as it stands today, could set a deadline for the remaining subprojects to make other hosting arrangements (TLP, Commons, Google). Otherwise, on a date certain, we would create single Jakarta Dev and User lists for all the remaining subprojects to share, and open karma to all the subprojects to all the Jakarta committers, in the style of the Commons. In other words, create a TLP, join the Commons, or become a commons. One other alternative would be for the active committers to those remaining subprojects to draft their own resolution proposal for creating a new Jakarta PMC, and boot the rest of us out. :) Though, if anyone wanted to make that happen, I'd suggest making it happen for the June board meeting, to coincide with the Commons proposal. Chiefly, we need to decide if we're sending the Commons proposal. The board learnt from the Shale/Struts proposal not to accept anything if the current PMC are not happy with the situation. Hen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Commons moving to TLP
Stephen Colebourne wrote: This seems a little overplanned in my mind ;) Allow a little more evolution. - Commons goes TLP. - Rules for Commons TLP become clear (one mailing list, one PMC, anyone commits in any component, anyone votes/reviews any release, comfortable social group) - Then invite communities from Jakarta to join if they wish (once the rules and expectations are clear) Simple. And community-up not top-down. +1 Phil - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
