Hi there, Grokkers<br><br>During the sprint in Birmingham, Kevin Gill and myself worked on the permissions in Grok.<br>Therefore, I'm sorry to announce that a part of the security doc is no longer "ok".<br><br>
Grok 1.0 will have a permission fallback meaning that, if you don't 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 permission to zope.Anybody. BUT, the doc should reflect that,<br>
if the developer wants it, he can remove the grok.View permission to the zope.Anybody group. This is really different than using zope.Public.<br><br>You can get more information in : <a href="https://bugs.launchpad.net/grok/+bug/389386">https://bugs.launchpad.net/grok/+bug/389386</a><br>
<br><div class="gmail_quote">2009/7/2 Sebastian Ware <span dir="ltr"><<a href="mailto:sebastian@urbantalk.se">sebastian@urbantalk.se</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 all!<br>
<br>
CURRENT GOAL: Review and edit existing community documentation to<br>
prepare it for the Grok 1.0 release.<br>
<br>
Please help us with reviewing of community documentation. To 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 grok-doc<br>
team. Are they ok for 1.0?<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 1.0?<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>
<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>
<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, make a<br>
note on the "whiteboard" of the blueprint and post a message 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>
</blockquote></div><br>