Hi all,
Seems like a good idea. I think that about maxes out the number of
topics which can be discussed at the code sprint ... that is if we also
want to write some actual code. :-P
Detailed agenda coming soon. I'll try to schedule things in such a way
that everyone can attend the discussions they're (as far as I can
gather) most interested in.
Best regards,
Hans
On 15/03/2011 14:00, Stefaan Vanbillemont wrote:
Developers,
I suggest that we discuss this around the code sprint table next week.
This is too complex material to discuss on the dev list.
Everybody ok with that approach?
Kind Regards,
Stefaan
Op 15/03/11 13:35, Systho schreef:
I would say that enforcing the narrowing of the right migh be an
option but shouldn't be the default one.
In general I agree that the 2 level rights in weblcms had lost me
when I tried to understand how the rights worked in Chamilo.
Systho
Le 15/03/2011 12:56, Ludwig Theunis a écrit :
Hi all
The idea to use one rights system seems logic.
Just the idea of allowing only narrowing the rights whenn you go
down tree will not work I think.
For a student the course itself is always (in most cases) Readonly,
the documents tool mostly is also readonly, the dropbox in the
documents module is not readonly, here the student will need write
rights to.
Greetings,
Ludwig
Currently the weblcms is using 2 right-systems
1) the global right system to set righs on tools and categories etc
2) a second right-system to set rights on publications
this prevents us from doing certain things we want to do there. (see
redmine for some of the issues)
it is also not a good idea to mix 2 different rights-systems in one
application I think.
I think we should use the chamilo rights system for everything
in the
weblcms.
This should be discussed asap, before everybody starts to try to
work
around this problem, complicating things even further.
to me it seems the best solution that you have one location tree
- course
- tool
- category
- publication
and allow the inheritance of the rights. It would also be best if we
could enforce that you can only narrow the rights when you go
down the
tree: If someone does not have view-rights on the course, tool or
category, it should not be possible to give him/here view-rights
on the
publication.
we particularly need this to "mimic" some of the tools in 1.8.x like
group-documents, studentpublications, teacher publications, ... with
categories in the documents and forum-tools that have certain
pre-set
rights.
Kind regards,
Nathalie
_______________________________________________
Dev mailing list
Dev@lists.chamilo.org <mailto:Dev@lists.chamilo.org>
http://lists.chamilo.org/listinfo/dev
_______________________________________________
Dev mailing list
Dev@lists.chamilo.org
http://lists.chamilo.org/listinfo/dev
_______________________________________________
Dev mailing list
Dev@lists.chamilo.org
http://lists.chamilo.org/listinfo/dev
_______________________________________________
Dev mailing list
Dev@lists.chamilo.org
http://lists.chamilo.org/listinfo/dev
_______________________________________________
Dev mailing list
Dev@lists.chamilo.org
http://lists.chamilo.org/listinfo/dev
