I don't mind at all<br>I will be able to work on it starting the 12th of July<br>Also, I can contribute with more reviews and tutorials. I subscribed today to the doc mailing list<br><br><div class="gmail_quote">2009/7/5 Tim Cook <span dir="ltr"><<a href="mailto:timothywayne.cook@gmail.com">timothywayne.cook@gmail.com</a>></span><br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Hi Souheil,<br>
<br>
Thanks for this information. I have a question though.<br>
<br>
Is this the tutorial that you are talking about?<br>
<div class="im"><a href="https://blueprints.launchpad.net/grok/+spec/doc-permissions" target="_blank">https://blueprints.launchpad.net/grok/+spec/doc-permissions</a><br>
<br>
</div>Would you care to have it assigned to you (as well as possibly Kevin)<br>
since you are both familiar with these issues?<br>
<br>
Thanks,<br>
Tim<br>
<div><div></div><div class="h5"><br>
<br>
On Sun, 2009-07-05 at 12:31 +0100, Souheil CHELFOUH wrote:<br>
> Hi there, Grokkers<br>
><br>
> During the sprint in Birmingham, Kevin Gill and myself worked on the<br>
> permissions in Grok.<br>
> Therefore, I'm sorry to announce that a part of the security doc is no<br>
> longer "ok".<br>
><br>
> Grok 1.0 will have a permission fallback meaning that, if you don't<br>
> explicitly define a "require" on your view,<br>
> a default permission will be assigned : grok.View<br>
><br>
> In a basic grokproject and in Grok itself, we assigned grok.View<br>
> permission to zope.Anybody. BUT, the doc should reflect that,<br>
> if the developer wants it, he can remove the grok.View permission to<br>
> the zope.Anybody group. This is really different than using<br>
> zope.Public.<br>
><br>
> You can get more information in :<br>
> <a href="https://bugs.launchpad.net/grok/+bug/389386" target="_blank">https://bugs.launchpad.net/grok/+bug/389386</a><br>
><br>
> 2009/7/2 Sebastian Ware <<a href="mailto:sebastian@urbantalk.se">sebastian@urbantalk.se</a>><br>
> Hi all!<br>
><br>
> CURRENT GOAL: Review and edit existing community documentation<br>
> to<br>
> prepare it for the Grok 1.0 release.<br>
><br>
> Please help us with reviewing of community documentation. To<br>
> grab a<br>
> document, post the link and your Launchpad Id on [grok-doc]<br>
> (subscribe: <a href="http://mail.zope.org/mailman/listinfo/grok-doc" target="_blank">http://mail.zope.org/mailman/listinfo/grok-doc</a>)<br>
><br>
> The following documents have recently been edited by the<br>
> grok-doc<br>
> team. Are they ok for 1.0?<br>
><br>
><br>
> <a href="https://blueprints.launchpad.net/grok/+spec/doc-implementing-search" target="_blank">https://blueprints.launchpad.net/grok/+spec/doc-implementing-search</a><br>
><br>
> <a href="https://blueprints.launchpad.net/grok/+spec/doc-permissions" target="_blank">https://blueprints.launchpad.net/grok/+spec/doc-permissions</a><br>
><br>
> The following documents need to be reviewed, are they ok for<br>
> 1.0?<br>
><br>
><br>
> <a href="https://blueprints.launchpad.net/grok/+spec/doc-using-virtualenv-for-a-clean-grok-installation" target="_blank">https://blueprints.launchpad.net/grok/+spec/doc-using-virtualenv-for-a-clean-grok-installation</a><br>
><br>
><br>
> <a href="https://blueprints.launchpad.net/grok/+spec/doc-install-on-ms-windows" target="_blank">https://blueprints.launchpad.net/grok/+spec/doc-install-on-ms-windows</a><br>
><br>
><br>
> <a href="https://blueprints.launchpad.net/grok/+spec/doc-a-grok-centric-explanation-of-adaptation" target="_blank">https://blueprints.launchpad.net/grok/+spec/doc-a-grok-centric-explanation-of-adaptation</a><br>
><br>
> NOTE: If you review a document and find that it needs editing,<br>
> make a<br>
> note on the "whiteboard" of the blueprint and post a message<br>
> on grok-<br>
> doc. You don't have to commit to doing the edits yourself.<br>
><br>
> There are more documents pending review at:<br>
><br>
> <a href="https://blueprints.launchpad.net/grok?searchtext=doc-" target="_blank">https://blueprints.launchpad.net/grok?searchtext=doc-</a><br>
><br>
> more info on the review process here:<br>
><br>
> <a href="https://blueprints.launchpad.net/grok/+spec/grok-docs-review" target="_blank">https://blueprints.launchpad.net/grok/+spec/grok-docs-review</a><br>
><br>
> Mvh Sebastian<br>
><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>
><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>
</div></div>--<br>
Timothy Cook, MSc<br>
Health Informatics Research & Development Services<br>
LinkedIn Profile:<a href="http://www.linkedin.com/in/timothywaynecook" target="_blank">http://www.linkedin.com/in/timothywaynecook</a><br>
Skype ID == timothy.cook<br>
**************************************************************<br>
*You may get my Public GPG key from popular keyservers or *<br>
*from this link <a href="http://timothywayne.cook.googlepages.com/home*" target="_blank">http://timothywayne.cook.googlepages.com/home*</a><br>
**************************************************************<br>
</blockquote></div><br>