I volunteer to help with the documentation effort. I'm also willing to draft the docs for the new grokproject.<br><br>Thanks,<br><br>Carlos de la Guardia<br>
<br>
Great!<br><br><div class="gmail_quote">On Fri, Nov 28, 2008 at 10:08 AM, Martijn Faassen <span dir="ltr"><<a href="mailto:faassen@startifact.com">faassen@startifact.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi there,<br>
<br>
I think we should consider calling the next release of Grok Grok 1.0. I<br>
would like to put us through an alpha and beta phase however, for two<br>
reasons:<br>
<br>
* we have a number of potentially disruptive changes we'd like to get<br>
some feedback on before we release.<br>
<br>
* 1.0 pre-releases for 1.0 are good marketing. We should announce these<br>
loudly to get people to think about Grok.<br>
<br>
The bigger changes I'm aware of are:<br>
<br>
* new grokproject that uses paster and WSGI. This is done, but needs to<br>
be tested heavily. Existing documentation needs to be modified and we<br>
need 'best practices' documentation that describe how you'd actually use<br>
all the WSGI goodness in your application. This change is by far the<br>
biggest one to land in a 1.0 release. Opinions on how to manage this?<br>
<br>
* grokcore.viewlet extraction - the extraction is done but the core<br>
isn't modified yet, correct? Sylvain, what's the status of that work?<br>
<br>
* refactoring grokcore.view to support improved view inheritance. JW and<br>
I have been working on this.<br>
<br>
I propose the following release plan:<br>
<br>
monday december 15: Grok 1.0 alpha<br>
<br>
Features: all of the above. Documentation doesn't need to be ideal yet<br>
for WSGI, but basic tutorial and dev notes should have been adjusted.<br>
<br>
wednesday january 7: Grok 1.0 beta<br>
<br>
Features: improved documentation, bugfixes based on issue tracker and<br>
alpha feedback.<br>
<br>
wednesday january 21: Grok 1.0rc1 release<br>
<br>
Features: documentation on <a href="http://grok.zope.org" target="_blank">grok.zope.org</a> is up to date with 1.0 stuff.<br>
This will be identical to the release if we can get away with it.<br>
<br>
wednesday january 28: Grok 1.0 release<br>
<br>
Hopefully practically identical to rc1.<br>
<br>
We will then continue with Grok 1.x development - things that I want to<br>
publish soon is megrok.rdb and the hurry.resource javascript/css<br>
resource handling framework.<br>
<br>
We need volunteers in various roles:<br>
<br>
* release manager. I'm hoping JW will step up again in this role.<br>
<br>
* documentation release manager: I'd like a separate role where someone<br>
prepares the documentation on <a href="http://grok.zope.org" target="_blank">grok.zope.org</a> and grok/trunk/doc for the<br>
release. This would be mostly a documentation editing role.<br>
<br>
* bug manager. I'm hoping someone will step up who watches the mailing<br>
list, irc, and makes sure we have bug reports in launchpad, and then<br>
shepherds the developers to actually do something about the bugs so we<br>
can close them.<br>
<br>
* PR lead: It'd be great if we had someone to write press releases and<br>
send them to various places.<br>
<br>
I volunteer in the role of General Nag during the release process to<br>
make sure everything stays on track. :)<br>
<br>
Feedback? Opinions? Changes to the release plan?<br>
<br>
Some inside information for those who read as far as this: a small group<br>
is also going to gather in late january at my place to consider larger<br>
low-level changes that I'll dub "Grok 2.0". We'll do our best to see<br>
about introducing these changes gradually in Grok 1.x releases instead,<br>
though, but the idea is to open up the floor for some radical rethinking<br>
of some low-level bits to make the insides of Zope 3 and Grok simpler<br>
and easier to understand. Less firmly planned is that we're also hoping<br>
to gather in a bigger sprint sometime next year.<br>
<br>
Regards,<br>
<br>
Martijn<br>
<br>
_______________________________________________<br>
Grok-dev mailing list<br>
<a href="mailto:Grok-dev@zope.org">Grok-dev@zope.org</a><br>
<a href="http://mail.zope.org/mailman/listinfo/grok-dev" target="_blank">http://mail.zope.org/mailman/listinfo/grok-dev</a><br>
</blockquote></div><br>