[Grok-dev] Grok-doc Request for assistance

[Tim Cook]

Hi Souheil,

Thanks for this information.  I have a question though.

Is this the tutorial that you are talking about?
https://blueprints.launchpad.net/grok/+spec/doc-permissions

Would you care to have it assigned to you (as well as possibly Kevin)
since you are both familiar with these issues?

Thanks,
Tim


On Sun, 2009-07-05 at 12:31 +0100, Souheil CHELFOUH wrote:
> Hi there, Grokkers
> 
> During the sprint in Birmingham, Kevin Gill and myself worked on the
> permissions in Grok.
> Therefore, I'm sorry to announce that a part of the security doc is no
> longer "ok".
> 
> Grok 1.0 will have a permission fallback meaning that, if you don't
> explicitly define a "require" on your view,
> a default permission will be assigned : grok.View
> 
> In a basic grokproject and in Grok itself, we assigned grok.View
> permission to zope.Anybody. BUT, the doc should reflect that,
> 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.
> 
> You can get more information in :
> https://bugs.launchpad.net/grok/+bug/389386
> 
> 2009/7/2 Sebastian Ware <sebastian at urbantalk.se>
>         Hi all!
>         
>         CURRENT GOAL: Review and edit existing community documentation
>         to
>         prepare it for the Grok 1.0 release.
>         
>         Please help us with reviewing of community documentation. To
>         grab a
>         document, post the link and your Launchpad Id on [grok-doc]
>         (subscribe: http://mail.zope.org/mailman/listinfo/grok-doc)
>         
>         The following documents have recently been edited by the
>         grok-doc
>         team. Are they ok for 1.0?
>         
>         
>         https://blueprints.launchpad.net/grok/+spec/doc-implementing-search
>         
>           https://blueprints.launchpad.net/grok/+spec/doc-permissions
>         
>         The following documents need to be reviewed, are they ok for
>         1.0?
>         
>         
>         https://blueprints.launchpad.net/grok/+spec/doc-using-virtualenv-for-a-clean-grok-installation
>         
>         
>         https://blueprints.launchpad.net/grok/+spec/doc-install-on-ms-windows
>         
>         
>         https://blueprints.launchpad.net/grok/+spec/doc-a-grok-centric-explanation-of-adaptation
>         
>         NOTE: If you review a document and find that it needs editing,
>         make a
>         note on the "whiteboard" of the blueprint and post a message
>         on grok-
>         doc. You don't have to commit to doing the edits yourself.
>         
>         There are more documents pending review at:
>         
>           https://blueprints.launchpad.net/grok?searchtext=doc-
>         
>         more info on the review process here:
>         
>           https://blueprints.launchpad.net/grok/+spec/grok-docs-review
>         
>         Mvh Sebastian
>         
>         
>         _______________________________________________
>         Grok-dev mailing list
>         Grok-dev at zope.org
>         http://mail.zope.org/mailman/listinfo/grok-dev
> 
> _______________________________________________
> Grok-dev mailing list
> Grok-dev at zope.org
> http://mail.zope.org/mailman/listinfo/grok-dev
-- 
Timothy Cook, MSc
Health Informatics Research & Development Services
LinkedIn Profile:http://www.linkedin.com/in/timothywaynecook 
Skype ID == timothy.cook 
**************************************************************
*You may get my Public GPG key from  popular keyservers or   *
*from this link http://timothywayne.cook.googlepages.com/home*
**************************************************************
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part
Url : http://mail.zope.org/pipermail/grok-dev/attachments/20090705/53bfeed6/attachment.bin