Re: State of documentation area reorg and tasks ?

Dylan Jay wrote:
> On 15/01/2010, at 11:12 PM, Kamon Ayeva wrote:
> 
>> Hi everybody,
>>
>> I can invest some time this week-end and next week to help on ongoing
>> documentation tasks.
>> Since I've seen http://dev.plone.org/plone/ticket/9928, can someone
>> please give me a picture of the current state of the developers
>> manual, and how it affects tickets that I was assigned to
>> (Archetypes-related).
>> I can do my best to work on and close my old tickets.

Just do anything Archetypes-related you need to do in
http://plone.org/documentation/manual/developer-manual/archetypes


>> Or suggest more priority tickets where help is needed ?

Just look at https://dev.plone.org/plone/report/25 and choose what you 
feel more comfortable with.

Plone 4 plips-related can be easy and quick to fix sometimes, and we 
certainly need them to get done in a near future:
http://bit.ly/9304FG


> Since no one else seems to have replied I'll say what I know. Hope I'm  
> not stepping on anyones toes.
> 
> There's two potential developer manuals (or starts of the final manual)
> 
> http://plone.org/documentation/manual/developer-manual
> 
> and
> 
> http://plonemanual.twinapex.fi/ (which is sourced out of the  
> collective and generated by sphinx).
> 
> 
> Obviously we need one manual that lives on plone.org but I don't think  
> it's clear yet which one this will be but if we have both being  
> published on plone.org then we can make that choice. The sooner we do  
> the sooner we know where to merge all the content into.

The approach I'm currently proposing is to leave both; 
collective.developermanual as part of the KnowledgeBase, where 
everywhere can contribute snippets of code freely, and the developer 
manual in the manuals area of plone.org for more organized and 
quality-controlled stuff. If we feel in the future that one of them is 
not working, we can reconsider this.

-- israel


------------------------------------------------------------------------------
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for Conference
attendees to learn about information security's most important issues through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev