[
https://issues.apache.org/jira/browse/INCUBATOR-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16784653#comment-16784653
]
David Fisher commented on INCUBATOR-231:
----------------------------------------
I am not sure if I agree on moving everything to git. I think that the parts
that are foundation records should remain in SVN.
Records would be:
# /content/podlings.xml (or whatever the successor to that would be.)
# /content/(podlings or projects)/(project).(xml or yml) (or whatever we
determine is the source of record for podling status.)
# /content/ip-clearance/
I think that we should reach out to Whimsy team to help with UI for updating
these records once we determine the final format.
Processes should certainly move:
# Clutch update scripts which do the following.
** Build pickle file of podling status
** Create data for various pages in the Incubator Site.
** Create data for emailed status and reporting process.
# Reporting scripts
** Email reminders.
** Monthly Report Template updated for Confluence.
** New: Email podling dev sites their "Clutch view monthly"
# New pages
** Podling status page (includes a version for retired and graduated podlings.)
** Podling listing page with current, graduated and retired podlings.
** Clutch page with status of current podlings. Status should reflect the
steps on podling has accomplished on their way towards graduation. Perhaps code
is shared with Whimsy.
** IP Clearance page.
# New scripts
** Create podling status files and clutch entry.
** Retire podling to update status and clutch.
** Graduate podling to update status and clutch.
** Memorialize podling LDAP and Mentors in status when graduating or retiring.
Before we proceed in a small incremental way with this large undertaking we
need to determine what format we wish to use for podling status. Choices
include:
# XML.
# YML.
# Doap / RDF.
Goals for these changes should be to:
# Better serve podlings by making status and expectations part of the workflow.
# Better serve mentors by easing their tasks to limit the amount of Incubator
redcap and semisecret records they need to learn.
# Better streamline the process so that a podling's transition to TLP is eased.
> Cleanup Git-generated Incubator website
> ---------------------------------------
>
> Key: INCUBATOR-231
> URL: https://issues.apache.org/jira/browse/INCUBATOR-231
> Project: Incubator
> Issue Type: Task
> Reporter: Bertrand Delacretaz
> Priority: Major
>
> [http://incubator.apache.org/] is generated from
> [https://github.com/apache/incubator] but a few things (clutch, project
> pages) are still maintained under
> [http://svn.apache.org/repos/asf/incubator/public/trunk/]
> We should cleanup and unify for consistency, and there's a number of folders
> in svn that are not used anymore. Everything should move to Git to avoid
> confusion.
> Also, a lot of the projects information in the XML files found under
> [http://svn.apache.org/repos/asf/incubator/public/trunk/content/projects/] is
> duplicated in other places, LDAP, podlings websites etc - it would be good to
> clean that up and simplify those pages to adapt to our current workflows,
> while preserving history where it makes sense.
> There are also YAML files with yet more duplicated information at
> [http://svn.apache.org/repos/asf/incubator/public/trunk/content/podlings/] ,
> not sure if that's used or useful.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
