[ https://issues.apache.org/jira/browse/COUCHDB-2350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14158869#comment-14158869 ]
Joan Touzet commented on COUCHDB-2350: -------------------------------------- Hi Javier, I'm happy to grant you access, but please keep in mind that the *large bulk* of the old wiki has been converted to the official documentation. None of us want to see those pages mass imported in. You should make a point of checking docs.couchdb.org first, and if the information is contained there, simply obsolete the old page and have it redirect to the appropriate docs page. > Finish move of the wiki documentation; clean up references in docs.couchdb.org > ------------------------------------------------------------------------------ > > Key: COUCHDB-2350 > URL: https://issues.apache.org/jira/browse/COUCHDB-2350 > Project: CouchDB > Issue Type: Improvement > Security Level: public(Regular issues) > Components: Documentation, Website > Reporter: Javier Candeira > > It occurs to me that as a new inductee into the project I'm in a privileged > position to update and restructure the documentation as I take the project > in, and it would probably be a better first task than to go after individual > bugs. > This is how I'd go about working on restructuring the documentation: > - move the old wiki content to confluence and 301 all wiki.apache.org pages > to the new wiki. No new content added. > - track all links and references to old wiki in docs.couchdb.org, and rewrite > them to point at new wiki. Still no new content added. > - then I would start triaging documentation bugs. There are many tasks that > are better done by a newcomer, since we need to follow the documentation or > be confused by it. > This is what I'd need: > - To be added to the confluence wiki contributors list (username: candeira) > - To be added to the old wiki contributors list (username: JavierCandeira) > - Optionally, to have a test confluence wiki so I can test migrating the old > one to the new one via scripts without making public changes until bugs have > been ironed out. -- This message was sent by Atlassian JIRA (v6.3.4#6332)