on 1/19/00 10:58 AM, Bernie Hoeneisen <[EMAIL PROTECTED]> wrote:
> I had a look on Turbine. I try to be as close as possible
> to Turbine with my implementation of the access rights.
GREAT!
> I thought the following roles make sense. The BASIC idea of these roles
> are in braces ():
>
> - root (all permissions)
> - admin (most of the permissions)
> - trusted_user (permissions to add and modify)
> - authenticated_user (only permissions to add)
> - guest (cannot neither modify nor add)
>
> Anyway, is not that important to fix these roles now, since Turbine
> provides a flexible handling of the roules. I plan to make this five
> roles as defaults in the installation.
>
> Comments?
+1
> This topic is a bit tricky. We have to find a tradeoff between
> flexibility and easyness in the configuration.
> I mean: Should the access rights (add, modify, ...) for every layer
> (project, faq, topic, question, answer) be seperately configurable?
> Or is it sufficiant to have these access rights for either
> all layers or none?
I think that they should be separate. The reason is that someone may want to
give people the ability to add Q&A, but not necessarily add a new Project.
> I suggest to keep this as simple as possible, to only to have
> permissions for all or none of the layers. Objections?
I'm fine with that, because you are doing the work, but I personally would
rather see them be separate. It is up to you. ;-)
> Thus I plan to implement the following permissions into the existing
> Jyve code (elem stands for elements). The changes will go to the actions
> and the screens classes.
>
> - add_jyve_elem (project, faq, topic, question and answer)
> - modify_jyve_elem (dito)
>
> For the realease feature (admin has to release elements first)
> - see_unreleased_jyve_elem (e.g. only for admin)
> - release_jyve_elem (for admin)
> - add_unreleased_jyve_elem (e.g. for auth. user)
> - modify_my_own_unreleased_jyve_elem (e.g. for auth user)
The only thing that I would change here is to take out the _jyve_ in the
string.
Also, it would be easy to just add something like this:
add_project_elem
add_faq_elem
add_topic_elem
...
> (Besides this also the turbine User Administration permissions will be
> implemented to jyve (add_user, modify_user, ...).)
Correct.
> Makes sense? Did I forget about anything? Please comment!
Perfect sense. Go for it! Be careful not to make to many changes right now
though because Jonas asked for a code freeze. I know that your changes would
probably conflict with his so, you might wait until he is done.
-jon
--
Come to the first official Apache Software Foundation
Conference! <http://ApacheCon.Com/>
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html>
Problems?: [EMAIL PROTECTED]
