[Trac] Permission model proposal (and volunteer)

[Muness Alrubaie]

Solo,

The URL you mention,
http://dev.muness.textdriven.com/trac.cgi/wiki/tags is not a
sggestion, but a working implementation of tagging.

But I never considered using it for ACL.  I think this would be
doable, but the implementation is a macro only solution.  For using it
for ACL it would probably need to be more closely coupled with the
Trac wiki.

Muness

On 8/27/05, solo turn <soloturn at gmail.com> wrote:
> thanks for that proposal! if something like this would exist in trac,
> it would be a big step forward. there is just one thing i'd like to do
> differently:
> > Approach:
> >   2. Introduce a hierarchical naming scheme for content so that access
> >      controls can be applied on a per-file basis and/or a per-subproject
> >      basis.
> i'd prefer more a "label", "category", or "tag" structure, like gmail
> did it for mails, and mediawiki did it with wiki. there is an
> implementation suggestion
> http://dev.muness.textdriven.com/trac.cgi/wiki/tags
> 
> this would mean there could be access rights an a label, and one would
> have to define the right if multiple tags apply. i'm not sure if this
> is equivalent with having multiple paths to an object.
> 
> access control in general would allow to use a wiki/trac for e.g.
> production support and store passwords and certificate files, and i
> consider it very important for that reason.
> 
> -solo.
> _______________________________________________
> Trac mailing list
> Trac at lists.edgewall.com
> http://lists.edgewall.com/mailman/listinfo/trac
>