Re: JIRA guidelines
Thanks for the info Bertrand. Cheers, Paul. On 23/04/2015 5:10 PM, Bertrand Delacretaz wrote: Hi, On Thu, Apr 23, 2015 at 2:32 AM, Paul King wrote: ...I noticed that one of our contributors was trying to assign (I believe) himself to an issue but didn't have permissions,... There are no Apache-wide guidelines on project-specific jira permissions, this project can define its own rules and configure (via INFRA issues if needed) whatever's appropriate. As long as that doesn't put the jira instance at risk. ...Also, do JIRA labels have any special significance within Apache?... In general no, with the exception of a few foundation-wide labels like "gsoc2015" which was used to collect proposals for this year's Google Summer of Code. If Groovy-specific labels are useful you might use a prefix like g. for them. -Bertrand --- This email has been checked for viruses by Avast antivirus software. http://www.avast.com
Re: JIRA guidelines
On Thu, Apr 23, 2015 at 2:32 AM, Paul King wrote: > ...Just wanting > to know if we should be changing our normal practice to align it more > closely with other projects?... BTW it's fine for an Apache project to operate independently of others for most things. http://community.apache.org/apache-way/apache-project-maturity-model.html tries to capture the elements that are common to all Apache projects, but apart from that most things can be done as the projects wants them to happen. -Bertrand
Re: JIRA guidelines
Hi, On Thu, Apr 23, 2015 at 2:32 AM, Paul King wrote: > ...I noticed that one of our contributors was trying to assign (I believe) > himself to an issue but didn't have permissions,... There are no Apache-wide guidelines on project-specific jira permissions, this project can define its own rules and configure (via INFRA issues if needed) whatever's appropriate. As long as that doesn't put the jira instance at risk. > ...Also, do JIRA labels have any special significance within Apache?... In general no, with the exception of a few foundation-wide labels like "gsoc2015" which was used to collect proposals for this year's Google Summer of Code. If Groovy-specific labels are useful you might use a prefix like g. for them. -Bertrand
