Oh, I see. We need extra step to add somebody in the contributors list so that he/she can be picked up in the possible assignee list in the JIRA.
I noticed Lin Chen was able to assign issues to herself today. That makes sense because it looks like she would continuously work on the project (quite a few patches already). For new contributors, perhaps we would use the similar approach, say if he/she has already come up more than 3 patches, then we could ..., make sense? Regards, Kai -----Original Message----- From: Emmanuel Lécharny [mailto:[email protected]] Sent: Thursday, January 15, 2015 9:54 PM To: Apache Directory Developers List Subject: Re: [Kerby/Haox] About committing codes for contributors Le 15/01/15 14:39, Pierre Smits a écrit : > I believe all committers must be able to assign issues to themselves > and have the ability to augment (if needed) and close these issues > when resolved. So let me clarify some few things : We do have committers, people being voted in. Those who participate and which we consider as valuable contributors should be quickly made committers. We also have contributors : those who have not *yet* been voted in as committers, or people who just post one patch and never come back. In any case, from the JIRA POV, this distinction is irrelevant : the assigned roles - and the associated permissions - are driven by other criteria. Typically, in order to be able to assign an issue to yourself, you have to have the 'contributors' role, and this is something we have to do manually in JIRA (and only admin for the project can do that). Yes, I know, it's stupid... So please give me the list of contributors (with their JIRA name) so that I can add them to the 'contributors' role. Thanks !
