Restricting delegation user list per project?

Stephen Finucane stephen at that.guru
Thu May 11 11:17:39 AEST 2017


On Wed, 2017-05-10 at 17:21 -0700, Florian Fainelli wrote:
> On 05/10/2017 05:12 PM, Florian Fainelli wrote:
> > Hi Jeremy,
> > 
> > On 05/10/2017 05:02 PM, Jeremy Kerr wrote:
> > > Hi Florian,
> > > 
> > > > I maintain several projects on a custom patchwork instance, and
> > > > I have
> > > > not found a way to restrict the delegation list to just a
> > > > particular
> > > > list of users?
> > > > 
> > > > I have seen it done on patchwork.ozlabs.org, so I am curious
> > > > how this
> > > > was done?
> > > 
> > > The list should only include the maintainers for that project -
> > > is that
> > > not the case on your instance? If not, what do you get for the
> > > delegate
> > > list?
> > 
> > The list contains all users that have registered with my patchwork
> > instance.
> > 
> > > 
> > > Also, which version of patchwork do you have running there?
> > 
> > So this is patchwork v1.1.0 which is a bit old, the 1.1.0 release
> > notes
> > has this:
> > 
> > Delegation of patches to any registered Patchwork user (previously
> > one
> > had to be a registered maintainer).
> > 
> > is it possible that this was actually way more permissive than it
> > was
> > intended by default?
> 
> Is not e0fd7cd91a5fbe0a0077c46bea870ccd09c8920d ("Allow assigning of
> any user as delegate") that was included in v1.1.0 and v1.1.1, and
> reverted in v1.1.2 the source of what I am seeing?

Yup, that feature was flawed so it has been reverted for v2.0.0 and in
the v1.1.2 hotfix. If you can upgrade (or ask your instance admin to
upgrade) the instance to v1.1.2 or greater, this will resolve this
issue for you.

Stephen


More information about the Patchwork mailing list