You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ofbiz.apache.org by Jacopo Cappellato <ja...@gmail.com> on 2012/11/20 09:52:17 UTC
Cleaning up the OFBiz Confluence spaces
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
Re: Cleaning up the OFBiz Confluence spaces
Posted by Olivier Heintz <ho...@nereide.biz>.
Le 20/11/2012 19:26, Jacques Le Roux a écrit :
> From: "Jacopo Cappellato" <ja...@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
Who is able to realize this plan ? or who has planned to realize it ?
Is it possible to help ?
Re: Cleaning up the OFBiz Confluence spaces
Posted by Jacques Le Roux <ja...@les7arts.com>.
From: "Jacopo Cappellato" <ja...@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
Re: Cleaning up the OFBiz Confluence spaces
Posted by Christian Geisert <ch...@isu-gmbh.de>.
Am 20.11.2012 09:52, schrieb Jacopo Cappellato:
> 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...).
[..]
> 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?
+100
Christian
Re: Cleaning up the OFBiz Confluence spaces
Posted by Paul Foxworthy <pa...@cohsoft.com.au>.
Hi Jacopo,
+1 for the consolidation.
Cheers
Paul Foxworthy
Jacopo Cappellato-3 wrote
> 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
-----
--
Coherent Software Australia Pty Ltd
http://www.coherentsoftware.com.au/
Bonsai ERP, the all-inclusive ERP system
http://www.bonsaierp.com.au/
--
View this message in context: http://ofbiz.135035.n4.nabble.com/Cleaning-up-the-OFBiz-Confluence-spaces-tp4637779p4637813.html
Sent from the OFBiz - Dev mailing list archive at Nabble.com.
Re: Cleaning up the OFBiz Confluence spaces
Posted by Ashish Vijaywargiya <vi...@gmail.com>.
+ 1
--
Ashish
On Tue, Nov 20, 2012 at 2:22 PM, Jacopo Cappellato <
jacopo.cappellato@gmail.com> wrote:
> 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
>
>
Re: Cleaning up the OFBiz Confluence spaces
Posted by Olivier Heintz <ho...@nereide.biz>.
Le 20/11/2012 09:52, Jacopo Cappellato a écrit :
> 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?
+1
I have done a merge of OFBiz website Documentation page with the
ofbiz-documentation-index wiki page, to have more visibility of what is
where.
I think that some wiki page should be migrated to ofbiz user help
integrated to ofbiz.
> Jacopo
>
>