Re: plan for collective.developermanual

On 14/04/2010, at 2:18 AM, Alex Clark wrote:

> Hi Dylan,
>
> I may be missing something, but this sounds like moving in the wrong
> direction to me. I'm pushing for "less code" on PloneOrg,

no new code. It's an offline converversion that can happen on another  
server if need be and then uploaded via xmlrpc nightly.


> because it's not being managed properly IMO (too much
> code outside core, too few active maintainers).
>
> However I think c.developermanual is a great idea and I personally  
> just
> want to read it, so I have created (based on trunk):
>
>    http://collective-docs.plone.org/
>
> I'm calling this an "experiment" to see if anyone else finds it  
> useful.

Might just confuse the issue since the best place for the manual is  
integrated into the manual section of plone.org. There is already a  
mirror at http://plonemanual.twinapex.fi. Having another temporary  
verison might lead to more future dead links.

>
> If not, or if I have stepped on any toes, or if it confuses people let
> me know and I'll remove it.
>
> Alex
>
> On 2010-02-03, Dylan Jay <dylan-Q+/Sk2sTzaxWk0Htik3J/[email protected]> wrote:
>> 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
>
>
> -- 
> Alex Clark · http://aclark.net
> Author of Plone 3.3 Site Administration · http://aclark.net/plone-site-admin
>
>
> ------------------------------------------------------------------------------
> Download Intel&#174; Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> Plone-docs mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/plone-docs


------------------------------------------------------------------------------
Download Intel&#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev