[Grok-dev] Final touches for a 1.0 "proper"
sebastian at urbantalk.se
Wed Sep 30 06:23:28 EDT 2009
I have begun marking stuff as possibly outdated...
In the beginning of the document I inserted:
**Might be outdated!** This document hasn't been reviewed for
Grok 1.0 and may be outdated. If you would like to review the
document, please read this post_.
.. _post: https://mail.zope.org/pipermail/grok-doc/2009-July/000002.html
In the blueprint I put:
2009-09-30 == Marked as possibly outdated == /jhsware
On 29 sep 2009, at 16.50, Sebastian Ware wrote:
> If someone can tell me what the proper formating should look like (I
> am hopeless at ReST-formating) for text in a alertish-style box then
> I, Tim and Steve can mark docs as possibly outdated. I will be able to
> spend an hour on this tomorrow.
> We obviously need help after that from people who could review these
> docs properly. Anybody who would can help with reviewing, just post
> your LaunchpadID and grok.zope.org username on the [Grok-doc] mailing
> list with a note that you want to check docs for 1.0 compatibility.
> Mvh Sebastian
> On 29 sep 2009, at 16.20, Martijn Faassen wrote:
>> Sebastian Ware wrote:
>>> I believe we still have community documentation that isn't updated.
>>> The least we should do is clearly mark them as
>>> "This document hasn't been verified with Grok 1.0 and may be
>>> Preferably with an explanation on the community docs process and
>>> to the Grok-doc information.
>>> If we don't do this, it will reflect badly on the great work that
>>> been done. I would argue that this is a show stopper.
>> So how do we resolve this situation? I'm fine with people marking the
>> documentation this way, but you need to organize an effort to do so,
>> right? Who is going to organize this?
>> Grok-dev mailing list
>> Grok-dev at zope.org
> Grok-dev mailing list
> Grok-dev at zope.org
More information about the Grok-dev