[haiku-web] Re: Community Documentation Collaboration (Was: Add Comunity Project)
- From: "Jorge G. Mare" <koki@xxxxxxxxxxxxx>
- To: haiku-web@xxxxxxxxxxxxx
- Date: Wed, 15 Apr 2009 09:50:07 -0700
Hi Matt.
Matt Madia wrote:
> You have to keep in mind, that I do not know all of the drupal lingo
> The best way I can explain myself would be with an analogy....
> i obviously don't know the correct term for "new types of nodes", so
> mentally substitute it when reading and then eventually tell me the
> name. :)
>
> ok, you have authenticated users. then you have the additive
> permissions (from Urias's idea) that are granted to each user.
>
> on the other side, you have individual pages.
> then those "new types of nodes" would classify which additive
> permission is needed. I'm not sure what level of granularity is
> needed to define those "new types of nodes", eg, blog, forum
> postings, news article, how-to guide. or something more coarse
> grained : "grant everyone write access", "grant only super editors
> write access", "grant normal editors write access".
>
> In my mind, it's perfectly reasonable to offer at least two different
> levels of editor access. Think about it... there are certainly some
> sections of the website that should not be editable by any person
> capable of registering an account. The "new types of nodes" is what
> is used to identify the required-editor-permissions on either a type
> of content like blogs or possibly individual pages.
>
First, please see my reply to Urias here...
//www.freelists.org/post/haiku-web/Community-Documentation-Collaboration-Was-Add-Comunity-Project,17
...where the content types are explained. If I understand you correctly,
what you are asking for is already possible. You just need to define
roles and permissions as needed.
>> Sorry, but I don't see the bigger picture here.
>>
> It's all about damage control. Just like how most forum and blog
> software have restrictions on who can post a comment in order to
> prevent spam, our website should have some restrictions as to who can
> edit what.
>
> Yes, i understand that the diff+revision modules will enable us to
> revert any bad/malicious/incorrect content. But placing some sensible
> restrictions would reduce the need for someone to intervene.
>
Ditto (as in "this is already possible, and you just need to define
roles and permissions as needed). The diff module is both a safeguard
(just in case) and a very convenient tool to manage revisions.
Cheers,
Jorge
-----------------------------------------------------------------------
haiku-web@xxxxxxxxxxxxx - Haiku Web & Developer Support Discussion List
Other related posts:
