[jira] [Commented] (INCUBATOR-100) document the process for a podling that has decided to go to dormant status
[ https://issues.apache.org/jira/browse/INCUBATOR-100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13050185#comment-13050185 ] David Crossley commented on INCUBATOR-100: -- Permanent links to some discussion: Re: TripleSoup going into dormant mode http://s.apache.org/d2s Re: process for going Dormant/Retired http://s.apache.org/oN document the process for a podling that has decided to go to dormant status --- Key: INCUBATOR-100 URL: https://issues.apache.org/jira/browse/INCUBATOR-100 Project: Incubator Issue Type: Task Components: site Reporter: David Crossley Document the process. Some steps were thoughtfully provided by Leo and Matthieu for TripleSoup: Re: TripleSoup going into dormant mode http://markmail.org/message/kavm65g65x55wqr5 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Issue Comment Edited] (INCUBATOR-100) document the process for a podling that has decided to go to dormant status
[ https://issues.apache.org/jira/browse/INCUBATOR-100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13050185#comment-13050185 ] David Crossley edited comment on INCUBATOR-100 at 6/16/11 3:40 AM: --- Permanent links to some discussion: Re: TripleSoup going into dormant mode Re: how to close down / put into dormant mode an incubator project / podling http://s.apache.org/d2s Re: process for going Dormant/Retired http://s.apache.org/oN Re: Bluesky status and plans http://s.apache.org/NLL was (Author: crossley): Permanent links to some discussion: Re: TripleSoup going into dormant mode http://s.apache.org/d2s Re: process for going Dormant/Retired http://s.apache.org/oN document the process for a podling that has decided to go to dormant status --- Key: INCUBATOR-100 URL: https://issues.apache.org/jira/browse/INCUBATOR-100 Project: Incubator Issue Type: Task Components: site Reporter: David Crossley Document the process. Some steps were thoughtfully provided by Leo and Matthieu for TripleSoup: Re: TripleSoup going into dormant mode http://markmail.org/message/kavm65g65x55wqr5 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] Commented: (INCUBATOR-108) Incubator navigation still includes Subversion and Cassandra TLPs
[ https://issues.apache.org/jira/browse/INCUBATOR-108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12870923#action_12870923 ] David Crossley commented on INCUBATOR-108: -- These projects need to tidy up after themselves. Cassandra is also still listed as needing to report. Clutch tries to give them some assistance with the post-graduation steps: http://incubator.apache.org/clutch.html#h-Graduate Incubator navigation still includes Subversion and Cassandra TLPs - Key: INCUBATOR-108 URL: https://issues.apache.org/jira/browse/INCUBATOR-108 Project: Incubator Issue Type: Bug Components: site Reporter: Sebb Incubator navigation still includes links to the podlings Subversion and Cassandra, however these are now TLPs, so it's a bit confusing to still have them listed as podlings -- 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-27) Overhaul the Check Trademark process
[ https://issues.apache.org/jira/browse/INCUBATOR-27?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12655428#action_12655428 ] David Crossley commented on INCUBATOR-27: - See the new document: http://www.apache.org/dev/project-names.html Choosing names for ASF projects Overhaul the Check Trademark process -- Key: INCUBATOR-27 URL: https://issues.apache.org/jira/browse/INCUBATOR-27 Project: Incubator Issue Type: Task Reporter: Matthias Weßendorf Lot's of incubator pages point to nameprotect DOT com for checking the podling name against a registered trademark. For some reasons this is *impossible*. That trademark search engine charges USD for a *research* I needs to be checked, howto handle this ? -Create an Apache account on that page ? -Using United States Patent and Trademark Office website ? See also http://wiki.apache.org/incubator/Trademarks -- 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-100) document the process for a podling that has decided to go to dormant status
document the process for a podling that has decided to go to dormant status --- Key: INCUBATOR-100 URL: https://issues.apache.org/jira/browse/INCUBATOR-100 Project: Incubator Issue Type: Task Components: site Reporter: David Crossley Document the process. Some steps were thoughtfully provided by Leo and Matthieu for TripleSoup: Re: TripleSoup going into dormant mode http://markmail.org/message/kavm65g65x55wqr5 -- 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-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:all-tabpanel ] David Crossley closed INCUBATOR-93. --- Resolution: Fixed The Vote was a successful result. One person voted here, the others on general@ list. [Vote] [Policy] clarify podling acceptance: INCUBATOR-93Link to this message http://markmail.org/message/w5e2j6fyavwom7bm Patch is now applied. 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] Closed: (INCUBATOR-95) Release guidelines contain incorrect permissions, url for distributing release
[ https://issues.apache.org/jira/browse/INCUBATOR-95?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Crossley closed INCUBATOR-95. --- Resolution: Fixed I applied your patch, thanks. According to http://incubator.apache.org/guides/website.html the first paragraph of Edit the content explains that any podling committer can edit these documents. So no need to wait to fix any docs inaccuracies. The policy documents are review-then-commit, otherwise go ahead. Release guidelines contain incorrect permissions, url for distributing release -- Key: INCUBATOR-95 URL: https://issues.apache.org/jira/browse/INCUBATOR-95 Project: Incubator Issue Type: Bug Components: site Reporter: Aidan Skinner Attachments: INCUBATOR-95.patch, INCUBATOR-95.patch The chmod command in the release pages is wrong and knackers stuff. The directory in the checklist is also incorrect. In addition, the suggested permission scheme leaves all incubator artifacts writable by a group of around 500 people, which is unfortunate. -- 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=12640831#action_12640831 ] David Crossley commented on INCUBATOR-78: - Today i added a tool called clutch which addresses some of this need. See r705975. See the notice to the general mailing list: Re: new tool clutch assist oversight of all podlings http://markmail.org/message/yy6cb2gokk5p2ur7 and the website at http://incubator.apache.org/clutch.html 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 Assignee: David Crossley 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] Assigned: (INCUBATOR-78) Unreliable report schedule and list of podlings
[ https://issues.apache.org/jira/browse/INCUBATOR-78?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Crossley reassigned INCUBATOR-78: --- Assignee: (was: David Crossley) 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] Assigned: (INCUBATOR-78) Unreliable report schedule and list of podlings
[ https://issues.apache.org/jira/browse/INCUBATOR-78?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Crossley reassigned INCUBATOR-78: --- Assignee: David Crossley 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 Assignee: David Crossley 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=12639257#action_12639257 ] David Crossley commented on INCUBATOR-78: - We can parse the generated table Currently in incubation at http://incubator.apache.org/projects/ which has most of the information that we need. However, this is still not reliable because we need to know which projects were accepted. Often they miss the first two steps: adding their status to that table, and adding themselves to the reporting schedule Wiki page: http://wiki.apache.org/incubator/ReportingSchedule See some more discussion at: Re: up-to-date list of projects in incubation http://markmail.org/message/qxemvfbsljdwbflj If their mentors don't add to the reporting schedule soon after acceptance, then another IPMC member needs to jump in to do it. Then we can parse that wiki ReportingSchedule and correlate with the projects index. Less maintenance of source data, and alerts to missing status info pages. 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] Updated: (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:all-tabpanel ] David Crossley updated INCUBATOR-93: Attachment: INCUBATOR-93.txt See the attached patch: In Incubation_Policy.xml ... * Add sentence to distinguish between IPMC being the sponsor or a TLP. * Move the Acceptance of Mentors paragraph to its own sub-section. In Process_Description.xml ... * Add an Introduction section at beginning to remind to read other documents which also explain the process. * Add words to distinguish between IPMC being the sponsor or a TLP. 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] Closed: (INCUBATOR-79) Update guide: releasing-eclipse-update-site to correct some inaccuracies
[ https://issues.apache.org/jira/browse/INCUBATOR-79?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Crossley closed INCUBATOR-79. --- Resolution: Fixed Thanks, patch applied. This should not have waited, AFAIK you could have done it immediately. Only the Policy documents need an IPMC review. Update guide: releasing-eclipse-update-site to correct some inaccuracies Key: INCUBATOR-79 URL: https://issues.apache.org/jira/browse/INCUBATOR-79 Project: Incubator Issue Type: Improvement Reporter: Marshall Schor Priority: Minor Attachments: patch.txt Found some inaccuracies in the guide while building an eclipse update site: the location of the urlDigest needs to point to the directory containing the digest.zip, not the digest.zip itself. Add info on using relative urls, as well. -- 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 or be followed
[ https://issues.apache.org/jira/browse/INCUBATOR-93?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12638161#action_12638161 ] David Crossley commented on INCUBATOR-93: - One issue seems to be that these documents do to not differentiate between the Sponsor being some other existing PMC or the Sponsor being the Incubator PMC (on behalf of the board). When read from the former point-of-view, they make more sense than the latter. Craig summed it up: ...If the Sponsor is *not* the incubator, then the paragraph you cited applies. If the Sponsor *is* the incubator, nothing else is required. Bill's words earlier in that thread are useful: http://mail-archives.apache.org/mod_mbox/incubator-general/200810.mbox/[EMAIL PROTECTED] In another thread Jukka summed it up: No ACK needed, as it was the Incubator PMC itself who just voted. From those words we should be able to add an introductory paragraph in those sections to remind. Incubation_Policy.html#Acceptance+By+Incubator needs clarification or be followed - 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] Updated: (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:all-tabpanel ] David Crossley updated INCUBATOR-93: Summary: Incubation_Policy.html#Acceptance+By+Incubator needs clarification: process depends on who is Sponsor (was: Incubation_Policy.html#Acceptance+By+Incubator needs clarification or be followed) 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-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=12638185#action_12638185 ] David Crossley commented on INCUBATOR-93: - ROTFL, you fisherman, you. Yeah i will try next week. 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-93) Incubation_Policy.html#Acceptance+By+Incubator needs clarification or be followed
[ https://issues.apache.org/jira/browse/INCUBATOR-93?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12636275#action_12636275 ] David Crossley commented on INCUBATOR-93: - The main reference is: http://incubator.apache.org/incubation/Incubation_Policy.html#Acceptance+By+Incubator and another source of confusion is: http://incubator.apache.org/incubation/Process_Description.html#Acceptance Incubation_Policy.html#Acceptance+By+Incubator needs clarification or be followed - 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] Created: (INCUBATOR-93) Incubation_Policy.html#Acceptance+By+Incubator needs clarification or be followed
Incubation_Policy.html#Acceptance+By+Incubator needs clarification or be followed - 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] Closed: (INCUBATOR-11) 'exitting' on Incubation_Policy.html
[ http://issues.apache.org/jira/browse/INCUBATOR-11?page=all ] David Crossley closed INCUBATOR-11: --- Resolution: Fixed Patch applied, thanks. 'exitting' on Incubation_Policy.html Key: INCUBATOR-11 URL: http://issues.apache.org/jira/browse/INCUBATOR-11 Project: Incubator Type: Bug Reporter: David N. Welton Priority: Trivial Attachments: Incubation_Policy.html.diff http://incubator.apache.org/incubation/Incubation_Policy.html Spelling mistake: Exitting - Exiting -- 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-12) Process_Description.html navigation improvement
[ http://issues.apache.org/jira/browse/INCUBATOR-12?page=comments#action_12362703 ] David Crossley commented on INCUBATOR-12: - Thanks anyway, Gavin. However that is not the correct patch. The Learn area is a special part of the Incubator website that was to create ASF-wide documentation. It has not been attended to. There is docs at the top-level www.apache.org that i will link to. I think that DavidW is also referring to the difficulty in finding the info about the Incubator mailing lists. Process_Description.html navigation improvement --- Key: INCUBATOR-12 URL: http://issues.apache.org/jira/browse/INCUBATOR-12 Project: Incubator Type: Improvement Reporter: David N. Welton Priority: Minor Attachments: Process_Description.html.diff http://incubator.apache.org/incubation/Process_Description.html mentions a mailing lists section of this site, yet provides no link, and it is not at all obvious from the left-hand navigation where that might reside. A link should be provided. Thanks, Dave -- 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-12) Process_Description.html navigation improvement
[ http://issues.apache.org/jira/browse/INCUBATOR-12?page=comments#action_12362707 ] David Crossley commented on INCUBATOR-12: - Still not happy with it, but svn r368950 improves the discovery of relevant mailing lists. The document was referring to a yet-to-be-written section of that Process_Description doc. Dunno, so referred to howtoparticipate.html instead. The other aspect of this issue is that the left-hand navigation needs improvement in general. So still open. Also the issue title shows that the whole document needs review to ensure that all links are correct and up-to-date, e.g. some point to a very old ASF Wiki. Process_Description.html navigation improvement --- Key: INCUBATOR-12 URL: http://issues.apache.org/jira/browse/INCUBATOR-12 Project: Incubator Type: Improvement Reporter: David N. Welton Priority: Minor Attachments: Process_Description.html.diff http://incubator.apache.org/incubation/Process_Description.html mentions a mailing lists section of this site, yet provides no link, and it is not at all obvious from the left-hand navigation where that might reside. A link should be provided. Thanks, Dave -- 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-7) STATUS file out of date, confusing
[ http://issues.apache.org/jira/browse/INCUBATOR-7?page=comments#action_12358446 ] David Crossley commented on INCUBATOR-7: Thanks Martin, i clarified those requirements for the project status files. Not quite the same as your suggested patch. The issue is still open because the general problem remains. STATUS file out of date, confusing -- Key: INCUBATOR-7 URL: http://issues.apache.org/jira/browse/INCUBATOR-7 Project: Incubator Type: Bug Environment: all Reporter: Martin Sebor The STATUS file (http://svn.apache.org/repos/asf/incubator/public/trunk/STATUS) posted to general@incubator.apache.org once a week is out of date and confusing. See this thread for details: http://mail-archives.apache.org/mod_mbox/incubator-general/200511.mbox/[EMAIL PROTECTED] A tentative patch for the problems pointed out in the post above is here: http://mail-archives.apache.org/mod_mbox/incubator-general/200511.mbox/[EMAIL PROTECTED] In addition, in his response (below) to this thread, David Crossley identifies two specific issues that should be addressed: http://mail-archives.apache.org/mod_mbox/incubator-general/200511.mbox/[EMAIL PROTECTED] -- 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-5) status file requirement unclear
[ http://issues.apache.org/jira/browse/INCUBATOR-5?page=comments#action_12358447 ] David Crossley commented on INCUBATOR-5: There was a comment from Noel in one of those threads to say that there is only one status file for each project and that is the documents at http://incubator.apache.org/projects/ Anyway, i patched the Incubation_Policy.html to clarify that. status file requirement unclear --- Key: INCUBATOR-5 URL: http://issues.apache.org/jira/browse/INCUBATOR-5 Project: Incubator Type: Improvement Environment: all Reporter: Martin Sebor The Incubation Policy mentions two requirements for a status file: http://incubator.apache.org/incubation/Incubation_Policy.html#Ongoing+Activities%0D http://incubator.apache.org/incubation/Incubation_Policy.html#Use+of+Apache+Resources While all podlings have a status Web page, none appears to provide a STATUS file in the expected location, even though the latter is mentioned more prominently in the policy and reiterated in the weekly Incubator status report -- see below: http://mail-archives.apache.org/mod_mbox/incubator-general/200507.mbox/[EMAIL PROTECTED] It's not clear which of these two files is actually required. This is a request to clarify the policy on this question. -- 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]
