Enhancements to mangeability of patches

[simo]

On Thu, 2012-10-25 at 11:39 +0800, Jeremy Kerr wrote:
> Hi Simo,
> 
> > I recently installed patchwork and we are testing it for 3 separate
> > upstream projects. I have the need to make it a bit more flexible in the
> > way users can be configured to access and change patches status yet not
> > give them actual admin rights as I do not want to let users from one
> > group worry about mistakenly touch other groups patches.
> 
> I'm a little confused - isn't this how things are already?
> 
> If you assign a user as a 'maintainer' of a project (ie, through the 
> UserProfile admin), then they have privileges to update patches for only 
> that project. Note that this isn't the same as making someone an admin 
> through the 'User' and 'Group' interfaces.
> 
> Or were you thinking something else?

I was just clueless I guess.
I will test out the maintainer thing.

> > Also, bonus question, are you planning on making patchwork django 1.4
> > friendly ?
> 
> A few folks (myself included) are running on django 1.4. You'll need a 
> fairly recent checkout though, I've only recently merged the 1.4 branch 
> into master.

Cloned just a few hours ago and I had the issues mentioned.
(Using python-django-1.4.2-1.fc18)

Simo.

-- 
Simo Sorce
Samba Team GPL Compliance Officer <simo at samba.org>
Principal Software Engineer at Red Hat, Inc. <simo at redhat.com>