Re: Plone 3.3 documentation update timeline

Israel Saeta Pérez <[email protected]>
Newsgroups gmane.comp.web.zope.plone.documentation
Message-ID <[email protected]>
On Fri, Feb 20, 2009 at 9:51 PM, JoAnna Springsteen wrote:
> I am making sure all the tickets are assigned to at least someone. I
> think they can be documented with in the next two weeks but the
> assignees need to make sure they get done.
>
> Donna- I've reassigned a couple to you. Please work with the PLIP
> owners to find out the details you need to document the PLIPS. Of
> course, we are all here to help.
>
> I have one PLIP that needs someone to work on it- ticket 7664, it's to
> document PLIP 149.  If someone could grab this, that would be great.

I would say that documenting the 3.3 plips has higher priority now
than documenting older ones.

Although this looks rather counter-intuitive, I feel 3.3 ones are more
feasible now. Moreover, I think they will constitute a good test of
whether or not we are in good shape to bind the documentation to the
development process, i.e. if we can document changes before (or very
shortly after) the new Plone version that includes these changes is
released.

IMHO, if we can't do that, Plone documentation is condemned to stay
out-of-date forever and ever.

> For those that just need to be reviewed, please find a SME (the plip
> owner or person who made the most commits?) and have that person read
> your doc and verify technical details. If you need help tracking
> someone down, let me know and I will work with Wichert to find that
> person.
>
> Doc team- this is a  *critical* deadline for us to meet. We will be
> letting the framework team down if we do not reach our goal of
> documenting these plips. If everyone could chip in, that will help us
> complete this task. If you would like to help, please email the list,
> catch me online or email me off the list. I will find something for
> you to do!

Potential contributors: please keep in mind you don't have to be a
Plone master to do your bit. If you don't feel confident about writing
documentation, you can always review others' work, look for poorly
documented tasks, etc.

--israel

------------------------------------------------------------------------------
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
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.