All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philip Balister <philip@balister.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Usage of groups
Date: Thu, 19 Feb 2009 17:35:54 -0500	[thread overview]
Message-ID: <499DDECA.2070304@balister.org> (raw)
In-Reply-To: <be7a9f3d0902161502y3e5ca44biac0b9acc4ff7b6ba@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1169 bytes --]

Otavio Salvador wrote:
> Hello folks,
> 
> I've contacted PatchWork people and asked for details how to make it
> properly fit our needs. Bellow goes the answer they gave me.
> 
>>> The OpenEmbedded project started to use PatchWork to allow us to
>>> better track the patches that come to us. It has been working fine
>>> except that we're not finding how to add groups to make easier the
>>> permission setting for users and like.
> 
>> The built-in 'groups' system doesn't affect any of the permissions on
>> patchwork at the moment. To allow a user to alter patches, they need to
>> be a 'maintainer' of the project that the patch belongs to.
> 
>> To make a use a maintainer, just open their UserProfile page in the
>> admin interface, and select the appropriate 'maintainer groups'.

OK, I've decrypted this message :) and managed to set up Khem's account 
so he can change patch state.

I'm thinking that people with commit access should be given maintainer 
status so they can mark patches as needed? How does that sound? If you 
have submitted a patch, can you change the state at the moment? Could 
someone check?

Thanks,

Philip

[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3303 bytes --]

      reply	other threads:[~2009-02-19 22:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87ocx2rq7w.fsf@neumann.lab.ossystems.com.br>
     [not found] ` <200902170936.57379.jk@ozlabs.org>
2009-02-16 23:02   ` Usage of groups Otavio Salvador
2009-02-19 22:35     ` Philip Balister [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=499DDECA.2070304@balister.org \
    --to=philip@balister.org \
    --cc=openembedded-devel@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.