Re: Plone 4.0 Documentation Updates

Israel Saeta Pérez <[email protected]>
Newsgroups gmane.comp.web.zope.plone.documentation
Message-ID <[email protected]>
2009/10/7 Eric Steele wrote:

>
> On Oct 2, 2009, at 8:10 AM, Israel Saeta Pérez wrote:
>
>> Hi Eric!
>>
>> Thank you very very much for your kind help proposals. :)
>>
>> The document listing all the PLIPs and their current state
>> [http://bit.ly/plips ] will be very helpful for sure. We will distribute
>> the
>> approved PLIPs among the current documentation editors and then each
>> editor
>> will manage to find out what do we need to update and contact the
>> implementers to ask for help to write the updates and new documentation.
>>
>> Should we create separate tickets in trac to track the documentation for
>> each PLIP or can we reuse the current PLIPs tickets?
>>
>
> I think I'd rather create new documentation tickets that reference the
> original PLIP ticket, purely for roadmap purposes. Though I may change my
> mind on that once Alex and I have a chance to finish the PSC migration. Feel
> free to talk me out of that.
>
>
Isn't documentation part of the roadmap for 4.0? ;)  Anyhow, I'm open to
create new tickets for documentation if this helps with the organization of
tasks.


> We should have a full list of inclusions by the end of the day tomorrow.
> I'll keep you posted.
>

Thanks!

=)

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference

_______________________________________________
Plone-docs mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/plone-docs
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.