From: "Jacopo Cappellato" <jacopo.cappell...@gmail.com>
> Hi all,
> 
> we all are aware of the problems affecting our content in Confluence but 
> before we discuss the next steps and evaluate different options and their 
> pros and cons, in my opinion it would make sense to aggregate all the 5 
> spaces into 2. This would give us a rather easy and actionable plan that 
> should improve the current situation (less spaces to administer etc...).
> 
> Currently we have the following Confluence spaces:
> 
> Public Wiki
> End-User Documentation
> Technical Documentation
> Requirements and Designs
> Project Administration
> 
> Because of a series of problems (lack of contributions and technical issues 
> with the Confluence instance offered by the ASF) the initial plan was not 
> very successful and we now have some spaces that are not used much and some 
> overlapping and confusion on the content of each.
> For this reason I am proposing the following change:
> 
> 1) copy the content from:
> 
> End-User Documentation
> Technical Documentation
> Requirements and Designs
> 
> to Public Wiki
> 
> 2) remove the spaces:
> 
> End-User Documentation
> Technical Documentation
> Requirements and Designs
> 
> 3) keep the Project Administration space as is for now (where write access is 
> granted only to committers): we could then consider the migration to the new 
> ASF CMS technology starting from this space (if possible); if we are happy 
> and it works well we could plan on migrating the static html files of our 
> site to it too as a second step.
> 
> The end result would be:
> 
> * OFBiz website: html pages or ASF CMS
> * Project Administration: Confluence space or ASF CMS
> * Public Wiki: Confluence space
> 
> What do you think?
> 
> Jacopo

The plans sounds good to me. I'm constantly  watching changes in wiki, so it's 
not an issue for me to get the non admin parts open. For the rest (ASF CMS) the 
future will tell...

Jacques

Reply via email to