Wow! Someone aready added the KSS tutorial that's awesome.<br><br><div class="gmail_quote">On Jan 6, 2008 8:11 AM, Kevin Teague <<a href="mailto:kevin@bud.ca">kevin@bud.ca</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">><br>> I'm already registered so feel free to add permissions.<br><br></div>I've created a new Group on the site called "Documentation". Anyone<br>with the Site Admin role can add people to this Group.
<br><br><a href="http://plone.grok.quintagroup.com/prefs_group_members?groupname=Documentation" target="_blank">http://plone.grok.quintagroup.com/prefs_group_members?groupname=Documentation</a><br><br>I've also just put everyone currently registered with the site in this
<br>group. Then I granted full access to just the /documentation/ section<br>of the web site (I assigned the Manager role as a Local Role at the<br>root of the PHC install). We might want to get a bit more fine-grained<br>
with permissions in the future, but that should be good enough for now.<br><br>You should be able to add, edit and publish a this doc as a How-To at:<br><br><a href="http://plone.grok.quintagroup.com/documentation/how-to" target="_blank">
http://plone.grok.quintagroup.com/documentation/how-to</a><br><br>(you should see an "add how-to" link in the top left - unless I've not<br>quite got the permissions loose-enough yet ...)<br><div class="Ih2E3d">
<br>><br>> Not being a technical writer, I just did the best I could to write<br>> something that would have helped me a lot. Also I'm not sure I made<br>> any attempt to conform to a grok-style of documentation.
<br>><br><br></div>The grok-style of documentation is to provide text that other people<br>might find helpful :)<br><br>ME GROK WANT DOCS!<br><br>We basically have wiki-style permissions on the docs at the moment.<br>Other Documentation people may make minor edits to existing text to
<br>correct obvious errors, typos, broken links, etc. If people want to<br>make larger expansions to an existing work, then it's polite to notify<br>the original author, and you should notify the original author first
<br>if you feel that taking on a larger reworking of the text that would<br>be beneficial.<br><div class="Ih2E3d"><br>><br>> Is it ok if people submit documentation under a creative commons<br>> license? It would seem to be ok to me.
<br>> What's a good attribution system to follow? Credits at the end with<br>> authors and smaller contributors listed? Maybe i"ll explore the<br>> creative commons website.<br><br></div>If you create a work you will be listed as it's primary author. It's
<br>also possible to edit this on the Properties tab for a document in the<br>Plone Help Center, as well as list additional contributors by name.<br><br>For a content licensing the default for Plone Help Center is "GNU Free
<br>Documentation License" but this is just a string which can be<br>configured globally for all content in the Plone Help Center. Since we<br>are pulling content such as the Grok Tutorial from the Zope SVN repo,<br>
are we required to give that a ZPL license? Or is a Creative Commons<br>license better? <a href="http://Plone.org" target="_blank">Plone.org</a> has the text "All content is copyright Plone<br>Foundation and the original contributors" so would similar wording
<br>with "Zope Foundation" apply?<br><div><div></div><div class="Wj3C7c">_______________________________________________<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></blockquote></div><br><br clear="all"><br>-- <br><br>-- Daniel