plan for collective.developermanual

Hi,

I'm not sure where we're going in making a decision but there doesn't  
seem to be too much variation in options so I'm going to go out on a  
limb and propose a plan. Unless someone violently disagrees I'll start  
implementing it.

1. Someone gives me plone.org manual area access

2. I upload collective.developermanual to http://plone.org/documentation/manual/plone3/developer-manual 
  and delete the kb version.

3. I convert http://plone.org/documentation/manual/developer-manual  
into reST and check into the collective. We create two branches called  
plone3 and plone4. I setup nightly uploading script to sync both to  
plone.org.

4. Mikko and Israel sit down and discuss chapter headings that take  
the best of both manuals (and anyone else who wants to of course).  
They raise some tickets about merging the two manuals.

5. Run a tuneup day maybe to help get the work done to do the merge

6. Turn off the old manual so only one exists on the manuals section

7. Publize it to the dev team and product developers lists. Give  
examples on how existing code documetnation can be included or how and  
where to edit new content for the manual

8. If after a few months the manual isn't awesome we re-evaluate.


---
Dylan Jay, Plone Solutions Manager
www.pretaweb.com
tel:+61299552830
mob:+61421477460
skype:dylan_jay


------------------------------------------------------------------------------
The Planet: dedicated and managed hosting, cloud storage, colocation
Stay online with enterprise data centers and the best network in the business
Choose flexible plans and management services without long-term contracts
Personal 24x7 support from experience hosting pros just a phone call away.
http://p.sf.net/sfu/theplanet-com