[ 
https://issues.apache.org/jira/browse/COUCHDB-2350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14158897#comment-14158897
 ] 

Javier Candeira commented on COUCHDB-2350:
------------------------------------------

Thanks again for the promptness. Old wiki is not a priority. The sandbox wiki 
is not required:

a) most of the pages are already updated, and
b) for a small number of articles or while I'm not confident about the results, 
I can have have my script pipe its output to xclip, and do the actual 
confluence editing by hand.

> 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)

Reply via email to