Re: permission matrix plugin

Hi

Just a little note before I (finally) leave :)

I basically agree with Hannes, I just wouldn't spent too much time on
the GUI part :)

As we will have some discussions next January where Flux should head to
(and where it should be improved) and one of those things is a more
coherent GUI, I wouldn't try to do fancy stuff there now. Later, no
problem :)

For the rest, I have nothing to add to hannes. And yes, it's better to
concentrate on the "normal" plugins like collection and xhtml/static
pages, than on the blog plugin and all those. They are the "p=FCnktchen
auf dem i"

greetings

chregu

On 6.12.2007 20:01 Uhr, Hannes Gassert wrote:
> Hi Pierre, hi all
> =

> Thanks for your great/big posting. I'm not qualified to give you any
> definitive answers, but what I guess is the following:
> =

>> the first problem is, that the "blog-back-blog" permission does not
>>  exist (c.f. [2], i guess "blog-back-post" could be the one we are
>>  looking for here).
> =

> Yes. Just a trivial bug, methinks.
> =

>> the second problem might be more complicated to solve, and it might
>>  also be the reason why the "permission matrix plugin" paradigm
>> isn't a good one.
> =

> I think the paradigm is a good one, I quite like the ACL-ish approach,
> although I think what you refer to as "group id" should also be able
> to contain just a user id.
> Question here: what is the behavior for the cases where I'm in
> different groups with possibly contradicting rules?
> =

>> the collection path is hardcoded to '/blog/'. i haven't looked at
>> the blog plugin internals, nor have i compared this with the
>> behavior of other plugins... but the "permission matrix plugin"
>> would expect a collection path here, in order to know which blog is
>>  referenced.
> =

> Having multiple blogs inside one Flux CMS instance is a rather..
> obscure/undocumented feature (setting a blogid and then ..), so if you
> want to deal with the "which blog"  issue then you might want to look
> into that. I'd say taking out the  hardcoded collection path is a good
> idea.
> Question here: what happens when I rename/move some collection? Do the
> permissions reflect that change automatically?
> =

>> so here are the questions that burn on my tongue: is a permission
>> model, based on the path / user group / permission triplet
>> realistic in the flux cms?
> =

> Yes. What else? The class Unix groups approach?
> =

>> will there be many problems like the once i cited?
> =

> There will be a bunch, but I suggest you first concentrate on making
> the thing work with a coherent (beautiful?) UI for ordinary
> collections and care about the special cases (files/gallery/blog ..
> just guessing) afterwards?
> =

>> what do you think about it?
> =

> I think I'd love to see a cool UI for that thing! :-)
> =

> Keep up the good work, kind regards to Fribourg,
> Hannes
> =


-- =

Liip AG // Schoeneggstrasse 5 // CH-8004 Zurich
Tel +41 44 240 56 70 // Mobile +41 76 561 88 60
www.liip.ch // blog.liip.ch // GnuPG 0x5CE1DECB
-- =

bitflux-cms mailing list
[email protected]
http://lists.bitflux.ch/cgi-bin/listinfo/bitflux-cms