Hi Ric,

This feature request is quite common, and it's tracked here: 
https://code.djangoproject.com/ticket/8936

A few people talked to me since I wrote the GSoC project description linked in 
comment #5, but I don't think anyone is actively working on this.

Since we deprecated databrowse, the problem is much simpler than what I 
described. It's probably still more complicated than what a patch can handle.

If you want to work on this ticket, I suggest to:
a) read the contributing guide in the docs (if you haven't yet),
b) review related discussions on this mailing list, and search for related 
tickets in Trac,
c) post a more detailed proposal here,
d) fork the bitbucket or github mirror and work on your clone,
e) track your progress by commenting on the ticket or on the mailing list.

Be aware that this isn't an easy ticket — you may prefer to start with smaller 
issues and tackle this when you're more at ease with our development process.

Best regards,

-- 
Aymeric Augustin.


On 16 nov. 2011, at 17:47, Ric wrote:

> i've been thinking about a new django admin feature, that could be
> backward implemented
> 
> it's about adding a view permission for models
> 
> so we can have
> 
> 1.change_permission
> 2.delete_permission
> 3.add_permission
> and
> 4.view_permission
> 
> in the changelist_view view_permission allow user to see the
> changelist, but user still need a change_permission to use the
> list_editable.
> in the change_view, having a view_permission allow to see the object,
> but the method get_read_only_fields returns all the fields.
> 
> in every case a POST request raise a PermissionDenied if the user do
> not have a change_permission, but allows GET request if user got a
> view_permission
> 
> view_permission could be added on the next syncdb...
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Django developers" group.
> To post to this group, send email to django-developers@googlegroups.com.
> To unsubscribe from this group, send email to 
> django-developers+unsubscr...@googlegroups.com.
> For more options, visit this group at 
> http://groups.google.com/group/django-developers?hl=en.
> 

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Reply via email to