[jira] Commented: (INCUBATOR-103) [IP-GRANT] PyLucene
[ https://issues.apache.org/jira/browse/INCUBATOR-103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12660166#action_12660166 ] Craig Russell commented on INCUBATOR-103: - I guess one question I have is, all of this required before acceptance? It was my understanding that these issues just need to be resolved before release, right? Grant, The requirements for notice and license files are after the code is accepted and before release. Craig [IP-GRANT] PyLucene --- Key: INCUBATOR-103 URL: https://issues.apache.org/jira/browse/INCUBATOR-103 Project: Incubator Issue Type: Bug Reporter: Andi Vajda Assignee: Grant Ingersoll This is an archive of PyLucene's HEAD revision (488): http://people.apache.org/~vajda/PyLucene-2.4.0-2-488.tar.bz2 http://people.apache.org/~vajda/PyLucene-2.4.0-2-488.tar.bz2.md5 The md5 hash was created with Mac OS X 10.5.5's /sbin/md5: md5 PyLucene-2.4.0-2-488.tar.bz2 PyLucene-2.4.0-2-488.tar.bz2.md5 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] Commented: (INCUBATOR-103) [IP-GRANT] PyLucene
[ https://issues.apache.org/jira/browse/INCUBATOR-103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12659978#action_12659978 ] Craig Russell commented on INCUBATOR-103: - The files can be integrated into the project any time after the grant is approved. Best practice these days is to take contributions without modifications and make the changes in the incubator to allow full transparency. The only thing wrong with the headers is that they contain the copyright notice. The copyrights should be removed from the individual files and put into the NOTICE and COPYRIGHT files. And the header without the copyright should be the verbatim notice as in the license directive. [IP-GRANT] PyLucene --- Key: INCUBATOR-103 URL: https://issues.apache.org/jira/browse/INCUBATOR-103 Project: Incubator Issue Type: Bug Reporter: Andi Vajda This is an archive of PyLucene's HEAD revision (488): http://people.apache.org/~vajda/PyLucene-2.4.0-2-488.tar.bz2 http://people.apache.org/~vajda/PyLucene-2.4.0-2-488.tar.bz2.md5 The md5 hash was created with Mac OS X 10.5.5's /sbin/md5: md5 PyLucene-2.4.0-2-488.tar.bz2 PyLucene-2.4.0-2-488.tar.bz2.md5 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] Commented: (INCUBATOR-103) [IP-GRANT] PyLucene
[ https://issues.apache.org/jira/browse/INCUBATOR-103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12660024#action_12660024 ] Craig Russell commented on INCUBATOR-103: - Sorry, I'm a little confused about the meaning of words here. What is currently at the top of every file in the PyLucene sources is what is recommended anyone using the Apache 2.0 license do and comes from the bottom of http://www.apache.org/licenses/LICENSE-2.0 under: APPENDIX: How to apply the Apache License to your work Right. This is how non-Apache code would use the Apache license. Are you saying that I should remove only the line that says Copyright (c) 2007-2008 Open Source Applications Foundation Yes. Actually move instead of remove because you're moving the copyright notice from each individual file to a common place in the repository. or that I should remove the entire header from all the source files and add it only to COPYRIGHT and NOTICE ? Leave the license in each file. Currently, I don't have either of these files. I only have that same header in a file called LICENSE. Assuming that you want to retain the copyright, you should move the copyright notice from each file and put it into the COPYRIGHT file in the svn repository. NOTICE is not needed (I was a bit eager there). Putting the standard Apache license text into the LICENSE file is fine. [IP-GRANT] PyLucene --- Key: INCUBATOR-103 URL: https://issues.apache.org/jira/browse/INCUBATOR-103 Project: Incubator Issue Type: Bug Reporter: Andi Vajda This is an archive of PyLucene's HEAD revision (488): http://people.apache.org/~vajda/PyLucene-2.4.0-2-488.tar.bz2 http://people.apache.org/~vajda/PyLucene-2.4.0-2-488.tar.bz2.md5 The md5 hash was created with Mac OS X 10.5.5's /sbin/md5: md5 PyLucene-2.4.0-2-488.tar.bz2 PyLucene-2.4.0-2-488.tar.bz2.md5 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] Commented: (INCUBATOR-103) [IP-GRANT] PyLucene
[ https://issues.apache.org/jira/browse/INCUBATOR-103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12660026#action_12660026 ] Craig Russell commented on INCUBATOR-103: - NOTICE is not needed (I was a bit eager there). Putting the standard Apache license text into the LICENSE file is fine. I stand corrected. The standard NOTICE file contains the fact that the work contains code developed at Apache, e.g.: This product includes software developed at The Apache Software Foundation (http://www.apache.org/). So, the svn repository and the distribution should contain COPYRIGHT, NOTICE, and LICENSE files. [IP-GRANT] PyLucene --- Key: INCUBATOR-103 URL: https://issues.apache.org/jira/browse/INCUBATOR-103 Project: Incubator Issue Type: Bug Reporter: Andi Vajda This is an archive of PyLucene's HEAD revision (488): http://people.apache.org/~vajda/PyLucene-2.4.0-2-488.tar.bz2 http://people.apache.org/~vajda/PyLucene-2.4.0-2-488.tar.bz2.md5 The md5 hash was created with Mac OS X 10.5.5's /sbin/md5: md5 PyLucene-2.4.0-2-488.tar.bz2 PyLucene-2.4.0-2-488.tar.bz2.md5 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] Commented: (INCUBATOR-93) Incubation_Policy.html#Acceptance+By+Incubator needs clarification: process depends on who is Sponsor
[ https://issues.apache.org/jira/browse/INCUBATOR-93?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12640372#action_12640372 ] Craig Russell commented on INCUBATOR-93: +1 on the patch content. Could you clean up the 80 character lines? Incubation_Policy.html#Acceptance+By+Incubator needs clarification: process depends on who is Sponsor - Key: INCUBATOR-93 URL: https://issues.apache.org/jira/browse/INCUBATOR-93 Project: Incubator Issue Type: Bug Components: policy Reporter: David Crossley Attachments: INCUBATOR-93.txt This section details the next step after a successful acceptance vote. It involves a special message to general@ and acknowledgment from IPMC and 72 hours wait. It seems that this is not being followed, rather just doing a vote summary. Does this section need review, or is this a necessary due-process type of thing? It should at least be clarified who can do this step. This arises because i am investigating why some projects are not commencing properly, e.g. adding to reporting roster and getting their status document started. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (INCUBATOR-93) Incubation_Policy.html#Acceptance+By+Incubator needs clarification: process depends on who is Sponsor
[ https://issues.apache.org/jira/browse/INCUBATOR-93?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12638174#action_12638174 ] Craig Russell commented on INCUBATOR-93: It would be great if you would write a patch to clarify this. Incubation_Policy.html#Acceptance+By+Incubator needs clarification: process depends on who is Sponsor - Key: INCUBATOR-93 URL: https://issues.apache.org/jira/browse/INCUBATOR-93 Project: Incubator Issue Type: Bug Components: policy Reporter: David Crossley This section details the next step after a successful acceptance vote. It involves a special message to general@ and acknowledgment from IPMC and 72 hours wait. It seems that this is not being followed, rather just doing a vote summary. Does this section need review, or is this a necessary due-process type of thing? It should at least be clarified who can do this step. This arises because i am investigating why some projects are not commencing properly, e.g. adding to reporting roster and getting their status document started. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (INCUBATOR-87) Submission of ICLAs and CCLAs for initial committers
[ https://issues.apache.org/jira/browse/INCUBATOR-87?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12635274#action_12635274 ] Craig Russell commented on INCUBATOR-87: According to the pdf in documents/iclas/rene-fernando-barraza.pdf the correct forwarding email address for Rene is [EMAIL PROTECTED], so that's the address to use for the root account request. Submission of ICLAs and CCLAs for initial committers Key: INCUBATOR-87 URL: https://issues.apache.org/jira/browse/INCUBATOR-87 Project: Incubator Issue Type: Sub-task Reporter: Niclas Hedhman All committers must file ICLAs and CCLAs with the ASF Secretary. By snail mail, fax or Signed Email/ -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (INCUBATOR-78) Unreliable report schedule and list of podlings
[ https://issues.apache.org/jira/browse/INCUBATOR-78?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12611251#action_12611251 ] Craig Russell commented on INCUBATOR-78: If we all agree that http://wiki.apache.org/incubator/ReportingSchedule is normative, basing the reminders on this page seems to be non-controversial. Let's *not* create yet another duplicate place to keep this information. And I'll repeat my earlier comment that a global reminder sent to each podling's dev list that refers to the above page would be fine pending implementation of a smarter reminder service. Unreliable report schedule and list of podlings --- Key: INCUBATOR-78 URL: https://issues.apache.org/jira/browse/INCUBATOR-78 Project: Incubator Issue Type: Bug Reporter: Bertrand Delacretaz As discussed in http://markmail.org/message/le55q754m4eypu7r it would be useful to generate the podlings report schedule and the list of projects on the http://incubator.apache.org/ automatically from a master file. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (INCUBATOR-78) Unreliable report schedule and list of podlings
[ https://issues.apache.org/jira/browse/INCUBATOR-78?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12611373#action_12611373 ] Craig Russell commented on INCUBATOR-78: Robert Burrell Donkin opined: I think using an algorithm to assign podlings to reporting months would be better than manual assignment. I'm mentoring a few projects and prefer that they all have the same reporting schedule, so for me, manual assignment is preferable. Unreliable report schedule and list of podlings --- Key: INCUBATOR-78 URL: https://issues.apache.org/jira/browse/INCUBATOR-78 Project: Incubator Issue Type: Bug Reporter: Bertrand Delacretaz As discussed in http://markmail.org/message/le55q754m4eypu7r it would be useful to generate the podlings report schedule and the list of projects on the http://incubator.apache.org/ automatically from a master file. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (INCUBATOR-72) Clarify release policy by removing binding from dev vote
[ https://issues.apache.org/jira/browse/INCUBATOR-72?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Craig Russell closed INCUBATOR-72. -- Resolution: Fixed svn commit -m INCUBATOR-72 Remove reference to PPMC binding votes site-author/incubation/Incubation_Policy.xml site-publish/incubation/Incubation_Policy.html Sendingsite-author/incubation/Incubation_Policy.xml Sendingsite-publish/incubation/Incubation_Policy.html Transmitting file data .. Committed revision 673789. people.apache.org% svn up Uincubation/Incubation_Policy.html Updated to revision 673789. Clarify release policy by removing binding from dev vote -- Key: INCUBATOR-72 URL: https://issues.apache.org/jira/browse/INCUBATOR-72 Project: Incubator Issue Type: Improvement Components: policy Reporter: Craig Russell Assignee: Craig Russell Priority: Minor Attachments: incubator-72.patch The policy for podling releases states Therefore, should a Podling decide it wishes to perform a release, the Podling SHALL hold a vote on the Podling's public -dev list. At least three +1 votes are required (see the Apache Voting Process page), and only the PPMC member votes are binding. If the majority of all votes is positive, then the Podling SHALL send a summary of that vote to the Incubator's general list and formally request the Incubator PMC approve such a release. Three +1 Incubator PMC votes are required. Below is an example showing how an incubating project managed this process: This has led to confusion, and I'd like to propose that the text be changed to remove the reference to PPMC votes, as follows: Therefore, should a Podling decide it wishes to perform a release, the Podling SHALL hold a vote on the Podling's public -dev list. At least three +1 votes are required (see the Apache Voting Process page). If the majority of all votes is positive, then the Podling SHALL send a summary of that vote to the Incubator's general list and formally request the Incubator PMC approve such a release. Three +1 Incubator PMC votes are required. Below is an example showing how an incubating project managed this process: Please see this email thread for additional background: http://mail-archives.apache.org/mod_mbox/incubator-general/200801.mbox/[EMAIL PROTECTED] -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (INCUBATOR-57) In the PPMC guide, clarify how to vote in a new committer
[ https://issues.apache.org/jira/browse/INCUBATOR-57?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Craig Russell closed INCUBATOR-57. -- Resolution: Fixed clr% svn commit -m INCUBATOR-57 again, clarify podling new committer process site-author/guides/ppmc.xml site-publish/guides/ppmc.html Sendingsite-author/guides/ppmc.xml Sendingsite-publish/guides/ppmc.html Transmitting file data .. Committed revision 672013. In the PPMC guide, clarify how to vote in a new committer - Key: INCUBATOR-57 URL: https://issues.apache.org/jira/browse/INCUBATOR-57 Project: Incubator Issue Type: Improvement Components: site Reporter: Craig Russell Assignee: Craig Russell Attachments: incubator-57.patch, incubator-57.patch, incubator-57.patch, incubator-57.patch, ppmc.html, ppmc.html, ppmc.html, ppmc.html, ppmc.xml, ppmc.xml, ppmc.xml There are two issues in this section. The first is the meaning of the term (P)PMC. I'd like to get rid of that term and replace it with PPMC or IPMC as appropriate. The second is how many votes are needed to vote in a new committer, and who should follow up to create the account. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Reopened: (INCUBATOR-57) In the PPMC guide, clarify how to vote in a new committer
[ https://issues.apache.org/jira/browse/INCUBATOR-57?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Craig Russell reopened INCUBATOR-57: A number of members have suggested changes to the process of voting in a new committer. In the PPMC guide, clarify how to vote in a new committer - Key: INCUBATOR-57 URL: https://issues.apache.org/jira/browse/INCUBATOR-57 Project: Incubator Issue Type: Improvement Components: site Reporter: Craig Russell Assignee: Craig Russell Attachments: incubator-57.patch, incubator-57.patch, incubator-57.patch, ppmc.html, ppmc.html, ppmc.html, ppmc.xml, ppmc.xml, smime.p7s There are two issues in this section. The first is the meaning of the term (P)PMC. I'd like to get rid of that term and replace it with PPMC or IPMC as appropriate. The second is how many votes are needed to vote in a new committer, and who should follow up to create the account. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (INCUBATOR-57) In the PPMC guide, clarify how to vote in a new committer
[ https://issues.apache.org/jira/browse/INCUBATOR-57?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Craig Russell updated INCUBATOR-57: --- Attachment: incubator-57.diff ppmc.html ppmc.xml In the PPMC guide, clarify how to vote in a new committer - Key: INCUBATOR-57 URL: https://issues.apache.org/jira/browse/INCUBATOR-57 Project: Incubator Issue Type: Improvement Components: site Reporter: Craig Russell Assignee: Craig Russell Attachments: incubator-57.diff, incubator-57.patch, incubator-57.patch, incubator-57.patch, ppmc.html, ppmc.html, ppmc.html, ppmc.html, ppmc.xml, ppmc.xml, ppmc.xml There are two issues in this section. The first is the meaning of the term (P)PMC. I'd like to get rid of that term and replace it with PPMC or IPMC as appropriate. The second is how many votes are needed to vote in a new committer, and who should follow up to create the account. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (INCUBATOR-57) In the PPMC guide, clarify how to vote in a new committer
[ https://issues.apache.org/jira/browse/INCUBATOR-57?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Craig Russell updated INCUBATOR-57: --- Attachment: (was: incubator-57.diff) In the PPMC guide, clarify how to vote in a new committer - Key: INCUBATOR-57 URL: https://issues.apache.org/jira/browse/INCUBATOR-57 Project: Incubator Issue Type: Improvement Components: site Reporter: Craig Russell Assignee: Craig Russell Attachments: incubator-57.patch, incubator-57.patch, incubator-57.patch, ppmc.html, ppmc.html, ppmc.html, ppmc.html, ppmc.xml, ppmc.xml, ppmc.xml There are two issues in this section. The first is the meaning of the term (P)PMC. I'd like to get rid of that term and replace it with PPMC or IPMC as appropriate. The second is how many votes are needed to vote in a new committer, and who should follow up to create the account. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (INCUBATOR-57) In the PPMC guide, clarify how to vote in a new committer
[ https://issues.apache.org/jira/browse/INCUBATOR-57?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Craig Russell updated INCUBATOR-57: --- Attachment: incubator-57.patch In the PPMC guide, clarify how to vote in a new committer - Key: INCUBATOR-57 URL: https://issues.apache.org/jira/browse/INCUBATOR-57 Project: Incubator Issue Type: Improvement Components: site Reporter: Craig Russell Assignee: Craig Russell Attachments: incubator-57.patch, incubator-57.patch, incubator-57.patch, incubator-57.patch, ppmc.html, ppmc.html, ppmc.html, ppmc.html, ppmc.xml, ppmc.xml, ppmc.xml There are two issues in this section. The first is the meaning of the term (P)PMC. I'd like to get rid of that term and replace it with PPMC or IPMC as appropriate. The second is how many votes are needed to vote in a new committer, and who should follow up to create the account. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (INCUBATOR-74) IP Clearance Template is rubbish
[ https://issues.apache.org/jira/browse/INCUBATOR-74?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12598051#action_12598051 ] Craig Russell commented on INCUBATOR-74: Three things that might be relevant in helping the PMC decide whether to accept the contribution, or more rubbish: I'd like to know if there is any connection between the contribution and an existing product (commercial or otherwise). I'd like to know if the contribution reads on any patents known to the contributor. The grant does address patents owned by the contributor, but it would still be good to know what they are and if there are any other patents that are known to the contributor. I'd like to know if the contribution is subject to export controls due to encryption technology. With regard to the suggested template http://incubator.apache.org/ip-clearance/httpd-mod_domain-clearance.html is there any reason that the files should not have http links to the svn repo where they reside? IP Clearance Template is rubbish Key: INCUBATOR-74 URL: https://issues.apache.org/jira/browse/INCUBATOR-74 Project: Incubator Issue Type: Bug Reporter: Robert Burrell Donkin Attachments: ip.diff http://mail-archives.apache.org/mod_mbox/incubator-general/200804.mbox/[EMAIL PROTECTED] -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (INCUBATOR-72) Clarify release policy by removing binding from dev vote
Clarify release policy by removing binding from dev vote -- Key: INCUBATOR-72 URL: https://issues.apache.org/jira/browse/INCUBATOR-72 Project: Incubator Issue Type: Improvement Components: policy Reporter: Craig Russell Assignee: Craig Russell Priority: Minor The policy for podling releases states Therefore, should a Podling decide it wishes to perform a release, the Podling SHALL hold a vote on the Podling's public -dev list. At least three +1 votes are required (see the Apache Voting Process page), and only the PPMC member votes are binding. If the majority of all votes is positive, then the Podling SHALL send a summary of that vote to the Incubator's general list and formally request the Incubator PMC approve such a release. Three +1 Incubator PMC votes are required. Below is an example showing how an incubating project managed this process: This has led to confusion, and I'd like to propose that the text be changed to remove the reference to PPMC votes, as follows: Therefore, should a Podling decide it wishes to perform a release, the Podling SHALL hold a vote on the Podling's public -dev list. At least three +1 votes are required (see the Apache Voting Process page). If the majority of all votes is positive, then the Podling SHALL send a summary of that vote to the Incubator's general list and formally request the Incubator PMC approve such a release. Three +1 Incubator PMC votes are required. Below is an example showing how an incubating project managed this process: Please see this email thread for additional background: http://mail-archives.apache.org/mod_mbox/incubator-general/200801.mbox/[EMAIL PROTECTED] -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (INCUBATOR-72) Clarify release policy by removing binding from dev vote
[ https://issues.apache.org/jira/browse/INCUBATOR-72?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Craig Russell updated INCUBATOR-72: --- Attachment: incubator-72.patch This patch removes the text and only the PPMC member votes are binding. Clarify release policy by removing binding from dev vote -- Key: INCUBATOR-72 URL: https://issues.apache.org/jira/browse/INCUBATOR-72 Project: Incubator Issue Type: Improvement Components: policy Reporter: Craig Russell Assignee: Craig Russell Priority: Minor Attachments: incubator-72.patch The policy for podling releases states Therefore, should a Podling decide it wishes to perform a release, the Podling SHALL hold a vote on the Podling's public -dev list. At least three +1 votes are required (see the Apache Voting Process page), and only the PPMC member votes are binding. If the majority of all votes is positive, then the Podling SHALL send a summary of that vote to the Incubator's general list and formally request the Incubator PMC approve such a release. Three +1 Incubator PMC votes are required. Below is an example showing how an incubating project managed this process: This has led to confusion, and I'd like to propose that the text be changed to remove the reference to PPMC votes, as follows: Therefore, should a Podling decide it wishes to perform a release, the Podling SHALL hold a vote on the Podling's public -dev list. At least three +1 votes are required (see the Apache Voting Process page). If the majority of all votes is positive, then the Podling SHALL send a summary of that vote to the Incubator's general list and formally request the Incubator PMC approve such a release. Three +1 Incubator PMC votes are required. Below is an example showing how an incubating project managed this process: Please see this email thread for additional background: http://mail-archives.apache.org/mod_mbox/incubator-general/200801.mbox/[EMAIL PROTECTED] -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (INCUBATOR-71) Allow podling committers with sufficient karma to set up their own infrastructure
[ https://issues.apache.org/jira/browse/INCUBATOR-71?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Craig Russell resolved INCUBATOR-71. Resolution: Won't Fix Allow podling committers with sufficient karma to set up their own infrastructure - Key: INCUBATOR-71 URL: https://issues.apache.org/jira/browse/INCUBATOR-71 Project: Incubator Issue Type: Improvement Components: policy Reporter: Craig Russell Assignee: Craig Russell Priority: Minor According to policy, Once a proposal has been accepted and the podling created a Mentor SHOULD initiate the creation of: mailing lists, repository, and jira project. If podling committers have sufficient karma, they should be allowed to set up the infrastructure themselves with oversight by the Mentors. Here's a patch to the .xml file: Index: site-author/incubation/Incubation_Policy.xml === --- site-author/incubation/Incubation_Policy.xml(revision 596486) +++ site-author/incubation/Incubation_Policy.xml(working copy) @@ -312,6 +312,11 @@ a href=http://www.apache.org/dev/#pmc;PMC/a notes. Also see the a href=../guides/pmc.htmlIncubator PMC Guide/a. /p + p + Some incubating projects will include committers who have karma + to perform the setup activities. These committers MAY set up the + project with oversight by the Mentors. + /p /section section id=Ongoing+Activities titleOngoing Activities/title -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (INCUBATOR-71) Allow podling committers with sufficient karma to set up their own infrastructure
Allow podling committers with sufficient karma to set up their own infrastructure - Key: INCUBATOR-71 URL: https://issues.apache.org/jira/browse/INCUBATOR-71 Project: Incubator Issue Type: Improvement Components: policy Reporter: Craig Russell Assignee: Craig Russell Priority: Minor According to policy, Once a proposal has been accepted and the podling created a Mentor SHOULD initiate the creation of: mailing lists, repository, and jira project. If podling committers have sufficient karma, they should be allowed to set up the infrastructure themselves with oversight by the Mentors. Here's a patch to the .xml file: Index: site-author/incubation/Incubation_Policy.xml === --- site-author/incubation/Incubation_Policy.xml(revision 596486) +++ site-author/incubation/Incubation_Policy.xml(working copy) @@ -312,6 +312,11 @@ a href=http://www.apache.org/dev/#pmc;PMC/a notes. Also see the a href=../guides/pmc.htmlIncubator PMC Guide/a. /p + p + Some incubating projects will include committers who have karma + to perform the setup activities. These committers MAY set up the + project with oversight by the Mentors. + /p /section section id=Ongoing+Activities titleOngoing Activities/title -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (INCUBATOR-62) [policy] State distribution directory
[ https://issues.apache.org/jira/browse/INCUBATOR-62?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12533170 ] Craig Russell commented on INCUBATOR-62: +1 for this patch. Craig [policy] State distribution directory - Key: INCUBATOR-62 URL: https://issues.apache.org/jira/browse/INCUBATOR-62 Project: Incubator Issue Type: Improvement Components: site Reporter: Robert Burrell Donkin Assignee: Robert Burrell Donkin Attachments: distribution(6).patch Infrastructure requires that all releases are distributed through www.apache.org/dist. We do not state this explicitly in policy. This has resulted in confusion over the right location for releases. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (INCUBATOR-57) In the PPMC guide, clarify how to vote in a new committer
[ https://issues.apache.org/jira/browse/INCUBATOR-57?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Craig Russell resolved INCUBATOR-57. Resolution: Fixed Assignee: Craig Russell svn commit -m INCUBATOR-57 clarify new committer procedures in ppmc guide site-author/guides/ppmc.xml site-publish/guides/ppmc.html Sendingsite-author/guides/ppmc.xml Sendingsite-publish/guides/ppmc.html Transmitting file data .. Committed revision 544900. In the PPMC guide, clarify how to vote in a new committer - Key: INCUBATOR-57 URL: https://issues.apache.org/jira/browse/INCUBATOR-57 Project: Incubator Issue Type: Improvement Components: site Reporter: Craig Russell Assignee: Craig Russell Attachments: incubator-57.patch, incubator-57.patch, incubator-57.patch, ppmc.html, ppmc.html, ppmc.html, ppmc.xml, ppmc.xml, smime.p7s There are two issues in this section. The first is the meaning of the term (P)PMC. I'd like to get rid of that term and replace it with PPMC or IPMC as appropriate. The second is how many votes are needed to vote in a new committer, and who should follow up to create the account. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (INCUBATOR-60) Mentor policy is inconsistent across documentation
[ https://issues.apache.org/jira/browse/INCUBATOR-60?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Craig Russell resolved INCUBATOR-60. Resolution: Fixed Assignee: Craig Russell (was: Robert Burrell Donkin) Feedback was incorporated from Martijn Dashorst, Upayavira, and Jim Jagielski. +1 votes were recorded from Yoav Shapira, Niclas Hedhman, Stefan Bodewig, Martijn Dashorst, Bill Rowe, Justin Erenkrantz, Martin Sebor, Dims, Ted Husted, and Jim Jagielski. svn commit -m INCUBATOR-60 clean up inconsistencies in definition of Mentor in policy, process, and roles Sendingsite-author/incubation/Incubation_Policy.xml Sendingsite-author/incubation/Process_Description.xml Sendingsite-author/incubation/Roles_and_Responsibilities.xml Sendingsite-publish/incubation/Incubation_Policy.html Sendingsite-publish/incubation/Process_Description.html Sendingsite-publish/incubation/Roles_and_Responsibilities.html Transmitting file data .. Committed revision 544000. Mentor policy is inconsistent across documentation -- Key: INCUBATOR-60 URL: https://issues.apache.org/jira/browse/INCUBATOR-60 Project: Incubator Issue Type: Improvement Components: site Reporter: Robert Burrell Donkin Assignee: Craig Russell Attachments: Incubation_Policy.html, Incubation_Policy.html, incubator-60.patch, incubator-60.patch, incubator-60.patch, Process_Description.html, Roles_and_Responsibilities.html The documentation on mentoring and mentor policy is inconsistent. Content is duplicated between documents. This needs to be cleaned up. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (INCUBATOR-60) Mentor policy is inconsistent across documentation
[ https://issues.apache.org/jira/browse/INCUBATOR-60?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Craig Russell closed INCUBATOR-60. -- Mentor policy is inconsistent across documentation -- Key: INCUBATOR-60 URL: https://issues.apache.org/jira/browse/INCUBATOR-60 Project: Incubator Issue Type: Improvement Components: site Reporter: Robert Burrell Donkin Assignee: Craig Russell Attachments: Incubation_Policy.html, Incubation_Policy.html, incubator-60.patch, incubator-60.patch, incubator-60.patch, Process_Description.html, Roles_and_Responsibilities.html The documentation on mentoring and mentor policy is inconsistent. Content is duplicated between documents. This needs to be cleaned up. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (INCUBATOR-57) In the PPMC guide, clarify how to vote in a new committer
[ https://issues.apache.org/jira/browse/INCUBATOR-57?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Craig Russell updated INCUBATOR-57: --- Attachment: smime.p7s incubator-57.patch ppmc.html And for those of you who read offline, I've attached the patch and resulting .html file to this message. Craig In the PPMC guide, clarify how to vote in a new committer - Key: INCUBATOR-57 URL: https://issues.apache.org/jira/browse/INCUBATOR-57 Project: Incubator Issue Type: Improvement Components: site Reporter: Craig Russell Attachments: incubator-57.patch, incubator-57.patch, ppmc.html, ppmc.html, ppmc.xml, smime.p7s There are two issues in this section. The first is the meaning of the term (P)PMC. I'd like to get rid of that term and replace it with PPMC or IPMC as appropriate. The second is how many votes are needed to vote in a new committer, and who should follow up to create the account. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (INCUBATOR-57) In the PPMC guide, clarify how to vote in a new committer
[ https://issues.apache.org/jira/browse/INCUBATOR-57?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Craig Russell updated INCUBATOR-57: --- Attachment: ppmc.html ppmc.xml incubator-57.patch I've made changes to the guides/ppmc.xml to get a document to review. Some parts might still be worded awkwardly, and I might not have captured the essence of the reviewer comments, so feedback is welcome. I've attached both the patch and the resulting guides/ppmc.html file for easy review. In the PPMC guide, clarify how to vote in a new committer - Key: INCUBATOR-57 URL: https://issues.apache.org/jira/browse/INCUBATOR-57 Project: Incubator Issue Type: Improvement Components: site Reporter: Craig Russell Attachments: incubator-57.patch, ppmc.html, ppmc.xml There are two issues in this section. The first is the meaning of the term (P)PMC. I'd like to get rid of that term and replace it with PPMC or IPMC as appropriate. The second is how many votes are needed to vote in a new committer, and who should follow up to create the account. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (INCUBATOR-60) Mentor policy is inconsistent across documentation
[ https://issues.apache.org/jira/browse/INCUBATOR-60?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Craig Russell updated INCUBATOR-60: --- Attachment: Incubation_Policy.html Updated to provide for a single Mentor. Mentor policy is inconsistent across documentation -- Key: INCUBATOR-60 URL: https://issues.apache.org/jira/browse/INCUBATOR-60 Project: Incubator Issue Type: Improvement Components: site Reporter: Robert Burrell Donkin Assigned To: Robert Burrell Donkin Attachments: Incubation_Policy.html, Incubation_Policy.html, incubator-60.patch, incubator-60.patch, Process_Description.html, Roles_and_Responsibilities.html The documentation on mentoring and mentor policy is inconsistent. Content is duplicated between documents. This needs to be cleaned up. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (INCUBATOR-60) Mentor policy is inconsistent across documentation
[ https://issues.apache.org/jira/browse/INCUBATOR-60?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Craig Russell updated INCUBATOR-60: --- Attachment: incubator-60.patch Mentor policy is inconsistent across documentation -- Key: INCUBATOR-60 URL: https://issues.apache.org/jira/browse/INCUBATOR-60 Project: Incubator Issue Type: Improvement Components: site Reporter: Robert Burrell Donkin Assigned To: Robert Burrell Donkin Attachments: Incubation_Policy.html, Incubation_Policy.html, incubator-60.patch, incubator-60.patch, incubator-60.patch, Process_Description.html, Roles_and_Responsibilities.html The documentation on mentoring and mentor policy is inconsistent. Content is duplicated between documents. This needs to be cleaned up. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (INCUBATOR-60) Mentor policy is inconsistent across documentation
[ https://issues.apache.org/jira/browse/INCUBATOR-60?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Craig Russell updated INCUBATOR-60: --- Attachment: incubator-60.patch This patch incorporates the comments made by Martijn and Upayavira. Mentor policy is inconsistent across documentation -- Key: INCUBATOR-60 URL: https://issues.apache.org/jira/browse/INCUBATOR-60 Project: Incubator Issue Type: Improvement Components: site Reporter: Robert Burrell Donkin Assigned To: Robert Burrell Donkin Attachments: incubator-60.patch, incubator-60.patch The documentation on mentoring and mentor policy is inconsistent. Content is duplicated between documents. This needs to be cleaned up. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (INCUBATOR-60) Mentor policy is inconsistent across documentation
[ https://issues.apache.org/jira/browse/INCUBATOR-60?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Craig Russell updated INCUBATOR-60: --- Attachment: Roles_and_Responsibilities.html Process_Description.html Incubation_Policy.html I've attached the resulting site-publish files to make it easier to review. Mentor policy is inconsistent across documentation -- Key: INCUBATOR-60 URL: https://issues.apache.org/jira/browse/INCUBATOR-60 Project: Incubator Issue Type: Improvement Components: site Reporter: Robert Burrell Donkin Assigned To: Robert Burrell Donkin Attachments: Incubation_Policy.html, incubator-60.patch, incubator-60.patch, Process_Description.html, Roles_and_Responsibilities.html The documentation on mentoring and mentor policy is inconsistent. Content is duplicated between documents. This needs to be cleaned up. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Assigned: (INCUBATOR-64) Graduation.xml revision 2 minor changes
[ https://issues.apache.org/jira/browse/INCUBATOR-64?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Craig Russell reassigned INCUBATOR-64: -- Assignee: Craig Russell Graduation.xml revision 2 minor changes --- Key: INCUBATOR-64 URL: https://issues.apache.org/jira/browse/INCUBATOR-64 Project: Incubator Issue Type: Improvement Components: site Reporter: Martijn Dashorst Assigned To: Craig Russell Attachments: graduation.diff Fixes for US english, minor spelling error, and added some post graduation tasks that typically get overlooked: - update pom.xml for mailing lists, repo and site - update 3rd party list archives for new mailing lists -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (INCUBATOR-64) Graduation.xml revision 2 minor changes
[ https://issues.apache.org/jira/browse/INCUBATOR-64?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Craig Russell resolved INCUBATOR-64. Resolution: Fixed svn commit -m INCUBATOR-64 minor typographical updates. Patch submitted by Martijn Dashorst Sendingsite-author/guides/graduation.xml Sendingsite-publish/guides/graduation.html Transmitting file data .. Committed revision 537711. Graduation.xml revision 2 minor changes --- Key: INCUBATOR-64 URL: https://issues.apache.org/jira/browse/INCUBATOR-64 Project: Incubator Issue Type: Improvement Components: site Reporter: Martijn Dashorst Assigned To: Craig Russell Attachments: graduation.diff Fixes for US english, minor spelling error, and added some post graduation tasks that typically get overlooked: - update pom.xml for mailing lists, repo and site - update 3rd party list archives for new mailing lists -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (INCUBATOR-63) Attempt to improve the graduation guide
[ https://issues.apache.org/jira/browse/INCUBATOR-63?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12493595 ] Craig Russell commented on INCUBATOR-63: Hi Martijn, Very nice. Just a few mostly typographical comments. Podlings do not need to actual publish a release to demonstrate that @@ -379,6 +274,12 @@ incubator project management committee/a is usually the simplest way to do this. s/actual/actually/ +The openness of your community is not only measured by the number of accepted contributors. +You will need to have open and respectful discussions on the open mailinglist(s). You need to +show that you can resolve technical conflict without destroying personal relationships. If +you can manage this, then you have shown to be a lively, active and successful community. s/mailinglists/mailing lists + Transfer the podling website + ol + li + Load the website into it's new home. s/it's/its a name=notes-on-hand-overOn The Hand Over/a /h3 div class=section-content -pTODO: content/p +pTODO: content. NOTE: is there any actual physical stuff happening with the hand over?/p s/Hand Over/Handover s/hand over/handover And no, the handover is composed of all virtual resources. + liSource + olli + codesvn move/code + the podling source tree + /li/ol + /li Let's add a few words about Communicate to all committers information on how to svn switch their workspaces. Craig Attempt to improve the graduation guide --- Key: INCUBATOR-63 URL: https://issues.apache.org/jira/browse/INCUBATOR-63 Project: Incubator Issue Type: Improvement Components: site Reporter: Martijn Dashorst Attachments: incubator-63.patch, incubator-graduation.xml.diff This patch contains a small contribution to remove a TODO in the community part of the graduation guide. I have moved the post graduation tasks (moving the resources to the new place inside the foundation's infrastructure) to the last part (thought it belonged there better, and reflects the contents list). The patch also contains a couple of fixes for spelling errors. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (INCUBATOR-53) Remove references to escalation from Incubation Policy
[ https://issues.apache.org/jira/browse/INCUBATOR-53?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Craig Russell closed INCUBATOR-53. -- Remove references to escalation from Incubation Policy Key: INCUBATOR-53 URL: https://issues.apache.org/jira/browse/INCUBATOR-53 Project: Incubator Issue Type: Improvement Components: site Reporter: Craig Russell Assigned To: Craig Russell Priority: Minor Attachments: escalate.patch, Incubation_Policy.html, incubator-53.patch, incubator-53.patch Currently, incubation policy refers to escalation, migration, and graduation when discussing graduation from the incubator to a TLP or a sub-project. This proposal standardizes on the terminology graduation to refer to this process. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (INCUBATOR-60) Mentor policy is inconsistent across documentation
[ https://issues.apache.org/jira/browse/INCUBATOR-60?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Craig Russell updated INCUBATOR-60: --- Attachment: incubator-60.patch Please review this patch. The patch changes three Incubator documents: policy, roles, and process. I've attached the patch that updates the site-author and site-publish directories. Some specific changes: It is now assumed that there is more than one Mentor, so Mentor is changed to plural throughout. The Mentor is not required to be an ASF Member, so the text was changed to require that a Mentor must be an Incubator PMC member not necessarily a Member. A Mentor must be an Incubator PMC member, but it's not automatic. The text was changed to remove automatic. References to http://apache.org/foundation/how-it-works.html have been added as links in the policy document. Mentor policy is inconsistent across documentation -- Key: INCUBATOR-60 URL: https://issues.apache.org/jira/browse/INCUBATOR-60 Project: Incubator Issue Type: Improvement Components: site Reporter: Robert Burrell Donkin Assigned To: Robert Burrell Donkin Attachments: incubator-60.patch The documentation on mentoring and mentor policy is inconsistent. Content is duplicated between documents. This needs to be cleaned up. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (INCUBATOR-59) ADFFACES renamed to Trinidad
[ https://issues.apache.org/jira/browse/INCUBATOR-59?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Craig Russell resolved INCUBATOR-59. Resolution: Fixed clr% svn commit -m INCUBATOR-59 Rename addfaces to trinidad Deleting site-author/projects/adffaces.xml Sendingsite-author/projects/index.xml Adding site-author/projects/trinidad.xml Sendingsite-author/stylesheets/project.xml Sendingsite-publish/faq.html Sendingsite-publish/guides/branding.html Sendingsite-publish/guides/chair.html Sendingsite-publish/guides/committer.html Sendingsite-publish/guides/entry.html Sendingsite-publish/guides/graduation.html Sendingsite-publish/guides/index.html Sendingsite-publish/guides/lists.html Sendingsite-publish/guides/participation.html Sendingsite-publish/guides/pmc.html Sendingsite-publish/guides/ppmc.html Sendingsite-publish/guides/projects.html Sendingsite-publish/guides/proposal.html Sendingsite-publish/guides/releasemanagement.html Sendingsite-publish/guides/sites.html Sendingsite-publish/guides/website.html Sendingsite-publish/incubation/Incubation_Policy.html Sendingsite-publish/incubation/Process_Description.html Sendingsite-publish/incubation/Roles_and_Responsibilities.html Sendingsite-publish/index.html Sendingsite-publish/ip-clearance/activemq.html Sendingsite-publish/ip-clearance/apr-jlibtool.html Sendingsite-publish/ip-clearance/derby-2134-contribution-tests-ibm.html Sendingsite-publish/ip-clearance/derby-2248-contribution-tests-ibm.html Sendingsite-publish/ip-clearance/directory-mitosis.html Sendingsite-publish/ip-clearance/directory-triplesec.html Sendingsite-publish/ip-clearance/geronimo-1016-ibm-daytrader.html Sendingsite-publish/ip-clearance/geronimo--trifork-initial.html Sendingsite-publish/ip-clearance/geronimo-1478-xbean.html Sendingsite-publish/ip-clearance/geronimo-2743-ibm-covalent-j2g.html Sendingsite-publish/ip-clearance/geronimo-762-ibm-console.html Sendingsite-publish/ip-clearance/geronimo-875-ibm-eclipse.html Sendingsite-publish/ip-clearance/geronimo-iiop.html Sending site-publish/ip-clearance/harmony-127-contribution-plugin-ibm.html Sending site-publish/ip-clearance/harmony-14-contribution-classlib-ibm.html Sending site-publish/ip-clearance/harmony-16-contribution-classlib-intel.html Sending site-publish/ip-clearance/harmony-3-ccontribution-jcvm-archie-cobbs.html Sending site-publish/ip-clearance/harmony-438-contribution-drlvm-intel.html Sending site-publish/ip-clearance/harmony-5-component-poc-david-tanzer.html Sendingsite-publish/ip-clearance/harmony-57-contribution-tests-ibm.html Sending site-publish/ip-clearance/harmony-6-contribution-jvm-daniel-lydick.html Sendingsite-publish/ip-clearance/harmony-88-contribution-tests-ibm.html Sendingsite-publish/ip-clearance/httpd-wombat.html Sendingsite-publish/ip-clearance/index.html Sendingsite-publish/ip-clearance/ip-clearance-template.html Sendingsite-publish/ip-clearance/jackrabbit-bundle-persistence.html Sendingsite-publish/ip-clearance/jakarta-cactus-tahchiev.html Sendingsite-publish/ip-clearance/jakarta-commons-composite-pool.html Sendingsite-publish/ip-clearance/jakarta-commons-csv.html Sendingsite-publish/ip-clearance/jakarta-commons-mantissa.html Sendingsite-publish/ip-clearance/myfaces-tobago.html Sendingsite-publish/ip-clearance/ode-1-sybase-bpe.html Sendingsite-publish/ip-clearance/ode-2-intalio-pxe.html Sendingsite-publish/ip-clearance/perl-apache_reload.html Sendingsite-publish/ip-clearance/portals-gluecode-jetspeed.html Sendingsite-publish/ip-clearance/servicemix.html Sending site-publish/ip-clearance/triplesoup-1-contribution-mod_sparql.html Sendingsite-publish/ip-clearance/triplesoup-2-contribution-libb.html Sendingsite-publish/ip-clearance/triplesoup-3-contribution-RDFStore.html Sending site-publish/ip-clearance/uima-255-contribution-cpp-framework-ibm.html Sendingsite-publish/ip-clearance/ws-jaxws.html Sendingsite-publish/ip-clearance/ws-sandesha.html Sendingsite-publish/ip-clearance/ws-wss4j.html Sending site-publish/ip-clearance/xmlgraphics-commons-postscript-dsc-parser.html Sendingsite-publish/ip-clearance/xmlgraphics-fop-afp-renderer.html Sendingsite-publish/learn/rules-for-revolutionaries.html Sendingsite-publish/learn/theapacheway.html Sendingsite-publish/official/mailing-lists.html Sendingsite-publish/official/resolution.html Sendingsite-publish/projects/abdera.html
[jira] Resolved: (INCUBATOR-53) Remove references to escalation from Incubation Policy
[ https://issues.apache.org/jira/browse/INCUBATOR-53?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Craig Russell resolved INCUBATOR-53. Resolution: Fixed The change has been committed to the incubator site repository. clr% svn commit -m INCUBATOR-53 Change escalate to graduate in policy document site-author/incubation/Incubation_Policy.xml site-publish/incubation/Incubation_Policy.html Sendingsite-author/incubation/Incubation_Policy.xml Sendingsite-publish/incubation/Incubation_Policy.html Transmitting file data .. Committed revision 530509. Remove references to escalation from Incubation Policy Key: INCUBATOR-53 URL: https://issues.apache.org/jira/browse/INCUBATOR-53 Project: Incubator Issue Type: Improvement Components: site Reporter: Craig Russell Assigned To: Craig Russell Priority: Minor Attachments: escalate.patch, Incubation_Policy.html, incubator-53.patch, incubator-53.patch Currently, incubation policy refers to escalation, migration, and graduation when discussing graduation from the incubator to a TLP or a sub-project. This proposal standardizes on the terminology graduation to refer to this process. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (INCUBATOR-59) ADFFACES renamed to Trinidad
[ https://issues.apache.org/jira/browse/INCUBATOR-59?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Craig Russell updated INCUBATOR-59: --- Attachment: incubator-59.patch ADFFACES renamed to Trinidad Key: INCUBATOR-59 URL: https://issues.apache.org/jira/browse/INCUBATOR-59 Project: Incubator Issue Type: Improvement Reporter: Matthias Weßendorf Attachments: incubator-59.patch, incubator-59.patch, rename_adffaces_to_trinidad.patch During the process of incubation, the formal name ADFFACES was changed to Trinidad. Please update the websites for that. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (INCUBATOR-53) Remove references to escalation from Incubation Policy
[ https://issues.apache.org/jira/browse/INCUBATOR-53?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Craig Russell updated INCUBATOR-53: --- Attachment: Incubation_Policy.html This attachment contains the formatted html from site-publish. There are broken links but the patch text is complete. Remove references to escalation from Incubation Policy Key: INCUBATOR-53 URL: https://issues.apache.org/jira/browse/INCUBATOR-53 Project: Incubator Issue Type: Improvement Components: site Reporter: Craig Russell Assigned To: Craig Russell Priority: Minor Attachments: escalate.patch, Incubation_Policy.html, incubator-53.patch, incubator-53.patch Currently, incubation policy refers to escalation, migration, and graduation when discussing graduation from the incubator to a TLP or a sub-project. This proposal standardizes on the terminology graduation to refer to this process. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (INCUBATOR-53) Remove references to escalation from Incubation Policy
[ https://issues.apache.org/jira/browse/INCUBATOR-53?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Craig Russell updated INCUBATOR-53: --- Attachment: incubator-53.patch Please review this patch. I've reverted migrate the svn repo to move the svn repo per Niclas Hedhman's comments (thanks for that). Still looking for one more vote to commit this change. Remove references to escalation from Incubation Policy Key: INCUBATOR-53 URL: https://issues.apache.org/jira/browse/INCUBATOR-53 Project: Incubator Issue Type: Improvement Components: site Reporter: Craig Russell Assigned To: Craig Russell Priority: Minor Attachments: escalate.patch, incubator-53.patch, incubator-53.patch Currently, incubation policy refers to escalation, migration, and graduation when discussing graduation from the incubator to a TLP or a sub-project. This proposal standardizes on the terminology graduation to refer to this process. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (INCUBATOR-53) Remove references to escalation from Incubation Policy
[ https://issues.apache.org/jira/browse/INCUBATOR-53?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12487002 ] Craig Russell commented on INCUBATOR-53: Would IPMC members please take a few minutes to review and vote on these proposed changes? Robert, thanks for voting. Thanks, Craig Remove references to escalation from Incubation Policy Key: INCUBATOR-53 URL: https://issues.apache.org/jira/browse/INCUBATOR-53 Project: Incubator Issue Type: Improvement Components: site Reporter: Craig Russell Assigned To: Craig Russell Priority: Minor Attachments: escalate.patch, incubator-53.patch Currently, incubation policy refers to escalation, migration, and graduation when discussing graduation from the incubator to a TLP or a sub-project. This proposal standardizes on the terminology graduation to refer to this process. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (INCUBATOR-56) Add process for voting a new PPMC member to guides/ppmc
[ https://issues.apache.org/jira/browse/INCUBATOR-56?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12479950 ] Craig Russell commented on INCUBATOR-56: svn commit -m INCUBATOR-56 Added guideline to add new PPMC member site-author/guides/ppmc.xml site-author/guides/ppmc-offer.txt site-publish/guides/ppmc.html site-publish/guides/ppmc-offer.txt Adding site-author/guides/ppmc-offer.txt Sendingsite-author/guides/ppmc.xml Adding site-publish/guides/ppmc-offer.txt Sendingsite-publish/guides/ppmc.html Transmitting file data Committed revision 517024. Add process for voting a new PPMC member to guides/ppmc --- Key: INCUBATOR-56 URL: https://issues.apache.org/jira/browse/INCUBATOR-56 Project: Incubator Issue Type: Improvement Components: policy Reporter: Craig Russell Assigned To: Craig Russell Priority: Minor Attachments: incubator-56.patch, incubator-56.patch, incubator-56.patch, incubator-56.patch The process to add a new PPMC member is proposed as an update to guides/ppmc. The process proposal includes sample email prototypes. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (INCUBATOR-56) Add process for voting a new PPMC member to guides/ppmc
[ https://issues.apache.org/jira/browse/INCUBATOR-56?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Craig Russell resolved INCUBATOR-56. Resolution: Fixed Add process for voting a new PPMC member to guides/ppmc --- Key: INCUBATOR-56 URL: https://issues.apache.org/jira/browse/INCUBATOR-56 Project: Incubator Issue Type: Improvement Components: policy Reporter: Craig Russell Assigned To: Craig Russell Priority: Minor Attachments: incubator-56.patch, incubator-56.patch, incubator-56.patch, incubator-56.patch The process to add a new PPMC member is proposed as an update to guides/ppmc. The process proposal includes sample email prototypes. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (INCUBATOR-56) Add process for voting a new PPMC member to guides/ppmc
[ https://issues.apache.org/jira/browse/INCUBATOR-56?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Craig Russell updated INCUBATOR-56: --- Attachment: incubator-56.patch One last change. I've added the recommendation to notify the IPMC that a VOTE for a new PPMC member is underway. Since this is a commit-then-review, I'll commit it if there are no comments by tomorrow. Add process for voting a new PPMC member to guides/ppmc --- Key: INCUBATOR-56 URL: https://issues.apache.org/jira/browse/INCUBATOR-56 Project: Incubator Issue Type: Improvement Components: policy Reporter: Craig Russell Assigned To: Craig Russell Priority: Minor Attachments: incubator-56.patch, incubator-56.patch, incubator-56.patch, incubator-56.patch The process to add a new PPMC member is proposed as an update to guides/ppmc. The process proposal includes sample email prototypes. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (INCUBATOR-57) In the PPMC guide, clarify how to vote in a new committer
In the PPMC guide, clarify how to vote in a new committer - Key: INCUBATOR-57 URL: https://issues.apache.org/jira/browse/INCUBATOR-57 Project: Incubator Issue Type: Improvement Components: site Reporter: Craig Russell There are two issues in this section. The first is the meaning of the term (P)PMC. I'd like to get rid of that term and replace it with PPMC or IPMC as appropriate. The second is how many votes are needed to vote in a new committer, and who should follow up to create the account. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (INCUBATOR-56) Add process for voting a new PPMC member to guides/ppmc
[ https://issues.apache.org/jira/browse/INCUBATOR-56?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Craig Russell updated INCUBATOR-56: --- Attachment: incubator-56.patch Please review this patch. I've split out the PPMC offer letter contents into a separate file. I've incorporated Jean's comments: Removed reference to notify the board of the new PPMC member. Removed request to subscribe new member to the private alias. Added requirement to update committers/board/incubator-info.txt. Please let me know if it's not ok to commit this. Add process for voting a new PPMC member to guides/ppmc --- Key: INCUBATOR-56 URL: https://issues.apache.org/jira/browse/INCUBATOR-56 Project: Incubator Issue Type: Improvement Components: policy Reporter: Craig Russell Assigned To: Craig Russell Priority: Minor Attachments: incubator-56.patch, incubator-56.patch The process to add a new PPMC member is proposed as an update to guides/ppmc. The process proposal includes sample email prototypes. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (INCUBATOR-56) Add process for voting a new PPMC member to guides/ppmc
Add process for voting a new PPMC member to guides/ppmc --- Key: INCUBATOR-56 URL: https://issues.apache.org/jira/browse/INCUBATOR-56 Project: Incubator Issue Type: Improvement Components: policy Reporter: Craig Russell Assigned To: Craig Russell Priority: Minor The process to add a new PPMC member is proposed as an update to guides/ppmc. The process proposal includes sample email prototypes. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (INCUBATOR-56) Add process for voting a new PPMC member to guides/ppmc
[ https://issues.apache.org/jira/browse/INCUBATOR-56?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Craig Russell updated INCUBATOR-56: --- Attachment: incubator-56.patch Please review this patch. It includes an update to the guides/ppmc for both site-author and site-publish. Add process for voting a new PPMC member to guides/ppmc --- Key: INCUBATOR-56 URL: https://issues.apache.org/jira/browse/INCUBATOR-56 Project: Incubator Issue Type: Improvement Components: policy Reporter: Craig Russell Assigned To: Craig Russell Priority: Minor Attachments: incubator-56.patch The process to add a new PPMC member is proposed as an update to guides/ppmc. The process proposal includes sample email prototypes. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (INCUBATOR-53) Remove references to escalation from Incubation Policy
[ https://issues.apache.org/jira/browse/INCUBATOR-53?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12473277 ] Craig Russell commented on INCUBATOR-53: I've committed changes to the two non-policy documents. svn commit -m INCUBATOR-53 Changed references from escalate to graduate site-author/incubation/Process_Description.xml site-author/incubation/Roles_and_Responsibilities.xml site-publish/incubation/Roles_and_Responsibilities.html site-publish/incubation/Process_Description.html Sendingsite-author/incubation/Process_Description.xml Sendingsite-author/incubation/Roles_and_Responsibilities.xml Sendingsite-publish/incubation/Process_Description.html Sendingsite-publish/incubation/Roles_and_Responsibilities.html Transmitting file data Committed revision 507768. Remove references to escalation from Incubation Policy Key: INCUBATOR-53 URL: https://issues.apache.org/jira/browse/INCUBATOR-53 Project: Incubator Issue Type: Improvement Components: site Reporter: Craig Russell Assigned To: Craig Russell Priority: Minor Attachments: escalate.patch Currently, incubation policy refers to escalation, migration, and graduation when discussing graduation from the incubator to a TLP or a sub-project. This proposal standardizes on the terminology graduation to refer to this process. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (INCUBATOR-53) Remove references to escalation from Incubation Policy
[ https://issues.apache.org/jira/browse/INCUBATOR-53?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Craig Russell updated INCUBATOR-53: --- Attachment: incubator-53.patch This patch applies to Incubation_Policy only. Remove references to escalation from Incubation Policy Key: INCUBATOR-53 URL: https://issues.apache.org/jira/browse/INCUBATOR-53 Project: Incubator Issue Type: Improvement Components: site Reporter: Craig Russell Assigned To: Craig Russell Priority: Minor Attachments: escalate.patch, incubator-53.patch Currently, incubation policy refers to escalation, migration, and graduation when discussing graduation from the incubator to a TLP or a sub-project. This proposal standardizes on the terminology graduation to refer to this process. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (INCUBATOR-55) Move Post Graduation Check List
[ https://issues.apache.org/jira/browse/INCUBATOR-55?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12473283 ] Craig Russell commented on INCUBATOR-55: I agree with this patch which removes process details from the policy document. Move Post Graduation Check List --- Key: INCUBATOR-55 URL: https://issues.apache.org/jira/browse/INCUBATOR-55 Project: Incubator Issue Type: Improvement Components: policy, site Reporter: Robert Burrell Donkin Assigned To: Robert Burrell Donkin Attachments: post-graduation.patch The policy document is RTC and should not mandate infrastructure process details which are liable to change. The material in the Post Graduation check list need not be policy and would find a better home in the graudation guide. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (INCUBATOR-44) [policy neutral] cut discursive material better handled in the guides
[ http://issues.apache.org/jira/browse/INCUBATOR-44?page=comments#action_12431303 ] Craig Russell commented on INCUBATOR-44: One of the issues I've noticed in incubation is that the incubating project often does not know who can help in what area. The trouble with the proposed patch is that it removes any clue as to who might be the usual party to request help. Maybe a better resolution would be to identify the responsible party for each of the tasks noted: Setting up the svn repo: The general requesting resources page says, New projects will need to ask for their SVN-space to be created. Send to [EMAIL PROTECTED] and Cc your PMC. Add an issue to Jira in the Subversion category. What it doesn't say is who usually does the request. Creation of mailing lists: The general requesting resources page says, Gather the required information about the new lists. This includes the precise name and domain, the email addresses of the people who will be moderators (ideally three+ and well spread). Send to [EMAIL PROTECTED] and Cc your PMC. Add an issue to Jira in the Mailing Lists category. Who would normally be expected to submit the request? There is no detail on how to add an issue to which jira. Maybe a direct reference to the correct jira would help here. [policy neutral] cut discursive material better handled in the guides - Key: INCUBATOR-44 URL: http://issues.apache.org/jira/browse/INCUBATOR-44 Project: Incubator Issue Type: Improvement Components: policy Reporter: Robert Burrell Donkin Assigned To: Robert Burrell Donkin Cuts non-policy discursive material that is better located in the guides. This change is intended to be policy neutral. Index: site-author/incubation/Incubation_Policy.xml === --- site-author/incubation/Incubation_Policy.xml(revision 437587) +++ site-author/incubation/Incubation_Policy.xml(working copy) @@ -285,21 +285,9 @@ liIncubator PMC mandating a helper Mentor/li /ul p - Your project's mentors are able to undertake many of the setup - tasks. See notes about how to - a href=http://www.apache.org/dev/reporting-issues.html;request project resources/a - such as new committer accounts and new mailing lists. - (Note that a committer account will not be created - a href=http://www.apache.org/dev/pmc.html#newcommitter;until the - Contributor License Agreement (CLA) has been recorded./a) -/p -p - Your project committers/PPMC members need to become familiar with - the a href=http://www.apache.org/dev/;ASF Infrastructure information/a - and in particular the - a href=http://www.apache.org/dev/#pmc;PMC/a notes. - Also see the a href=../guides/pmc.htmlIncubator PMC Guide/a. - /p + See a href=http://www.apache.org/dev/reporting-issues.html;how to/a + request project resources. + /p /section section id=Ongoing+Activities titleOngoing Activities/title Index: site-publish/incubation/Incubation_Policy.html === --- site-publish/incubation/Incubation_Policy.html (revision 437587) +++ site-publish/incubation/Incubation_Policy.html (working copy) @@ -376,21 +376,9 @@ liIncubator PMC mandating a helper Mentor/li /ul p - Your project's mentors are able to undertake many of the setup - tasks. See notes about how to - a href=http://www.apache.org/dev/reporting-issues.html;request project resources/a - such as new committer accounts and new mailing lists. - (Note that a committer account will not be created - a href=http://www.apache.org/dev/pmc.html#newcommitter;until the - Contributor License Agreement (CLA) has been recorded./a) -/p -p - Your project committers/PPMC members need to become familiar with - the a href=http://www.apache.org/dev/;ASF Infrastructure information/a - and in particular the - a href=http://www.apache.org/dev/#pmc;PMC/a notes. - Also see the a href=../guides/pmc.htmlIncubator PMC Guide/a. - /p + See a href=http://www.apache.org/dev/reporting-issues.html;how to/a + request project resources. + /p /div h3 a name=Ongoing+ActivitiesOngoing Activities/a -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information
[jira] Commented: (INCUBATOR-39) Policy neutral change to improve organisation
[ http://issues.apache.org/jira/browse/INCUBATOR-39?page=comments#action_12424683 ] Craig Russell commented on INCUBATOR-39: titleAcceptance By Incubator/title pUpon a successful result, the PMC Chair of the Sponsor SHOULD request the Incubator PMC take on the Candidate as a new Podling. The request, which should be sent to the Incubator PMC on the a href=howtoparticipate.html#Mailing+listsgeneral/a list, MUST contain the following information: This might be a side issue, but if the Sponsor does not request the Incubator PMC to accept the project, how can it incubate? So I'm thinking that the PMC Chair of the Sponsor MUST request the Incubator to accept the project. Policy neutral change to improve organisation - Key: INCUBATOR-39 URL: http://issues.apache.org/jira/browse/INCUBATOR-39 Project: Incubator Issue Type: Improvement Components: policy Reporter: Robert Burrell Donkin Assigned To: Robert Burrell Donkin This patch separates the process of acceptance from approval by the sponsor. The consistency of usage of terms is increased. Index: site-author/incubation/Incubation_Policy.xml === --- site-author/incubation/Incubation_Policy.xml(revision 425516) +++ site-author/incubation/Incubation_Policy.xml(working copy) @@ -28,8 +28,9 @@ lia href=#Entry+to+IncubationEntry to Incubation/a ul lia href=#ProposalProposal/a/li -lia href=#Acceptance+of+Proposal+by+SponsorAcceptance of Proposal +lia href=#Approval+of+Proposal+by+SponsorApproval of Proposal by Sponsor/a/li +lia href=#Acceptance+By+IncubatorAcceptance By Incubator/a/li lia href=#Creation+of+PodlingCreation of Podling/a/li /ul /li @@ -221,17 +222,20 @@ /strong /p /section - section id=Acceptance+of+Proposal+by+Sponsor -titleAcceptance of Proposal by Sponsor + section id=Approval+of+Proposal+by+Sponsor +titleApproval of Proposal by Sponsor /title -pThe decision to accept a project MUST be taken on a vote by the -Sponsor, in accordance with that Entity's charter. +pThe decision to approve the candidate proposal MUST be taken +on a vote by the Sponsor, in accordance with that Entity's charter. /p +/section + section id='Acceptance+By+Incubator' +titleAcceptance By Incubator/title pUpon a successful result, the PMC Chair of the Sponsor SHOULD request the Incubator PMC take on the Candidate as a new Podling. The request, which should be sent to the Incubator PMC on the a href=howtoparticipate.html#Mailing+listsgeneral/a list, -MUST contain the following information : +MUST contain the following information: /p ul lia reference to the results of the vote (so as to provide an audit -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (INCUBATOR-36) Removed discursive material repeated elsewhere from policy
[ http://issues.apache.org/jira/browse/INCUBATOR-36?page=comments#action_12422932 ] Craig Russell commented on INCUBATOR-36: Typo it's for its: + p +This role and it's responsibilities are discussed +a href='/incubator/Roles_and_Responsibilities.html#Sponsor'here/a. + /p should be + p +This role and its responsibilities are discussed +a href='/incubator/Roles_and_Responsibilities.html#Sponsor'here/a. + /p Removed discursive material repeated elsewhere from policy -- Key: INCUBATOR-36 URL: http://issues.apache.org/jira/browse/INCUBATOR-36 Project: Incubator Issue Type: Improvement Components: site Reporter: Robert Burrell Donkin Assigned To: Robert Burrell Donkin This patch remove quite a quantity of discursive material from policy which is already covered in roles. Index: site-author/incubation/Incubation_Policy.xml === --- site-author/incubation/Incubation_Policy.xml(revision 423542) +++ site-author/incubation/Incubation_Policy.xml(working copy) @@ -225,23 +225,13 @@ libe nominated for incubation by a member of the Apache Software Foundation (The Champion); and /li - libe approved by a Sponsor. + libe approved by a a href='#Sponsor'Sponsor/a. /li /ul pApproval by a Sponsor will generally occur only after a vote within the Entity, and will require that the Entity be convinced that the -Candidate is appropriate for Incubation. A Sponsor may be one of: +Candidate is appropriate for Incubation. /p -ul - lithe Board of the Apache Software Foundation; -/li - lia Top Level Project (TLP) within the Apache Software Foundation -(where the TLP considers the Candidate to be a suitable sub-project); -or -/li - lithe Incubator PMC. -/li -/ul pTo start this process, a Candidate SHOULD submit a proposal to a Sponsor. The Proposal SHOULD, at minimum, detail the following areas : /p @@ -891,33 +881,23 @@ section id=Sponsor titleSponsor /title -pThe Sponsor is the entity within the ASF that makes the determination -that a candidate would make a worthy addition to the ASF, and agrees -to take on the candidate in question (or in the case of the Incubator -PMC, assist it in finding a home) should it complete the incubation -process. +p +A Sponsor SHALL be either: /p -pA Sponsor will be one of: -/p ul - liThe Board of the Apache Software Foundation. In this case, it is -expected that the candidate would become a TLP on successful -completion of Incubation. + lithe Board of the Apache Software Foundation; /li - liA Top Level Project within the ASF. In this case, the project in -question has agreed that the candidate is a good fit for their -project, and will take on the candidate as a sub-project upon -successful completion of Incubation. + lia Top Level Project (TLP) within the Apache Software Foundation +(where the TLP considers the Candidate to be a suitable sub-project); +or /li - liThe Incubator PMC. In this case, the Incubator PMC agrees that the -project in question will make a good addition to the ASF, but there -is no clear owner of the candidate should it successfully complete -incubation. An incubation exit requirement for such candidates will -be the identification (and successfuly lobbying) of an owner entity -- either the board (and the candidate will be a TLP) or another -project. + lithe Incubator PMC. /li /ul +p +This role and it's responsibilities are discussed +a href='/incubator/Roles_and_Responsibilities.html#Sponsor'here/a. +/p /section section id=Mentor titleMentor Index: site-author/incubation/Roles_and_Responsibilities.xml === --- site-author/incubation/Roles_and_Responsibilities.xml (revision 423542) +++ site-author/incubation/Roles_and_Responsibilities.xml (working copy) @@ -151,7 +151,8 @@ section id=Sponsor titleSponsor /title -pThe Sponsor is the entity within the ASF that makes the determination +pThe Sponsor [a href='/incubation/Incubator_Policy.html#Sponsor'definition/a] +is the entity within the ASF that makes the determination that a candidate would make a worthy addition to the ASF, and agrees to take on the candidate in question (or in the case of the Incubator PMC, assist it in finding a home) should it complete the incubation -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of
[jira] Commented: (INCUBATOR-35) Move discursive material about PMC from policy to roles and responsibilities
[ http://issues.apache.org/jira/browse/INCUBATOR-35?page=comments#action_12422933 ] Craig Russell commented on INCUBATOR-35: This seems wrong: + pThe Project Management Committee is responsible to the Board for administering + the Incubator Project in the manner specified in the founding + a href='http://incubator.apache.org/official/resolution.html'gt;resolutionlt;/a. /p I think the gt;resolutionlt is actually supposed to be xml metadata, as: + pThe Project Management Committee is responsible to the Board for administering + the Incubator Project in the manner specified in the founding + a href='http://incubator.apache.org/official/resolution.html'resolution/a. /p Maybe this gets fixed during post-processing of the xml but it doesn't follow the pattern elsewhere in this document. Move discursive material about PMC from policy to roles and responsibilities Key: INCUBATOR-35 URL: http://issues.apache.org/jira/browse/INCUBATOR-35 Project: Incubator Issue Type: Improvement Components: site Reporter: Robert Burrell Donkin Assigned To: Robert Burrell Donkin Consolidate discursive material onto roles and responsibilities. Added cross links. Index: site-author/incubation/Incubation_Policy.xml === --- site-author/incubation/Incubation_Policy.xml(revision 423542) +++ site-author/incubation/Incubation_Policy.xml(working copy) @@ -833,38 +833,14 @@ section id=Incubator+Project+Management+Committee+%28PMC%29 titleIncubator Project Management Committee (PMC) /title -p(From the resolution that created the Incubator Project - see -http://incubator.apache.org/resolution.html) +pThe Project Management Committee is responsible to the Board for administering +the Incubator Project in the manner specified in the founding +a href='http://incubator.apache.org/official/resolution.html'resolution/a. /p -pThe Incubator PMC is responsible for : +p +The roles and responsibilities of the PMC are described and discussed +a href='Roles_and_Responsibilities.html#Incubator+Project+Management+Committee+%28PMC%29'here/a. /p -ul - liacceptance and oversight of candidate projects submitted or proposed -to become part of the Foundation; -/li - liproviding guidance and ensuring that sub-projects under it's purview -develop products according to the Foundation's philosophy and -guidelines for collaborative development; -/li - liproviding a repository for the storage of incubation history and -information; -/li - liassisting a Podling's Mentor in discharging her/his duties; -/li - liregularly evaluating projects under its purview for the purposes of -recommending to the Sponsor whether the project should: -/li - li style=list-style: none -ul - lisuccessfully exit incubation; -/li - licontinue to receive guidance and support within the Incubator; or -/li - libe terminated. -/li -/ul - /li -/ul /section section id=Chair+of+the+Incubator+PMC titleChair of the Incubator PMC Index: site-author/incubation/Roles_and_Responsibilities.xml === --- site-author/incubation/Roles_and_Responsibilities.xml (revision 423542) +++ site-author/incubation/Roles_and_Responsibilities.xml (working copy) @@ -23,11 +23,10 @@ section id=Incubator+Project+Management+Committee+%28PMC%29 titleIncubator Project Management Committee (PMC) /title -p(From the resolution that created the Incubator Project - see -http://incubator.apache.org/resolution.html) +pThe Incubator PMC +[a href='/incubation/Incubation_Policy.html#Incubator+Project+Management+Committee+%28PMC%29'definition/a] +is responsible for : /p -pThe Incubator PMC is responsible for : -/p ul liacceptance and oversight of candidate projects submitted or proposed to become part of the Foundation; -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (INCUBATOR-28) Add sample podling web site
Add sample podling web site --- Key: INCUBATOR-28 URL: http://issues.apache.org/jira/browse/INCUBATOR-28 Project: Incubator Issue Type: Improvement Components: site Reporter: Craig Russell Priority: Minor A sample web site for podlings is provided, with commonly needed web pages. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (INCUBATOR-26) Add a sample podling web site and a guide for how to use it
[ http://issues.apache.org/jira/browse/INCUBATOR-26?page=all ] Craig Russell updated INCUBATOR-26: --- Attachment: INCUBATOR-26.patch This is the working version of the guide to using the sample podling site. Add a sample podling web site and a guide for how to use it --- Key: INCUBATOR-26 URL: http://issues.apache.org/jira/browse/INCUBATOR-26 Project: Incubator Type: Improvement Components: site Reporter: Craig Russell Priority: Minor Attachments: INCUBATOR-26.patch To help podlings get up to speed, a sample web site is provided. It contains the site generation tool and sample web pages that can be edited to suit the podling. A description of the sample web site is provided for the site-author/guides area. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
