I support Milhail's proposal - the possibility to work directly with JIRA issuess looks attractive to me. Probably we should not allow to close JIRA issues to everyone - it can be done by the committer who integrated the patch. Let's let everyone to assign the issue to him/herself, set patch available status - everything that is needed for every day work with an issue.
Thank you, Pavel On 12/14/06, Mikhail Markov <[EMAIL PROTECTED]> wrote:
On 12/14/06, Alexey Petrenko <[EMAIL PROTECTED]> wrote: > > 2006/12/14, Mikhail Markov <[EMAIL PROTECTED]>: > > On 12/14/06, Alexey Petrenko <[EMAIL PROTECTED]> wrote: > > > > > > 1. How will we choose people to give "contributor" access to JIRA? > > This should be discussed here :-). One of the easiest possible solutions > is > > to automatically grant this access after particular number of posts to > dev > > list + actions with JIRAs. > As we all knows number of posts does not tell anything about the person :) Agree, but this could be an indicator for considering the person as a candidate for JIRA contributor > Another option is to use the same procedure as for granting committer > > status (but have less strict requirements). > OK > > > 2. As far as I understood the main point here is to give a possibility > > > for non-committers to assign bugs. So non-committers can search for > > > non-assigned bugs. Right? > > The main point is to quicker process JIRAs not requiring committing to > svn + > > some small things like > > "Patch available" > I see two solutions here: > 1. Ask bug creator to set this flag if he/she happy with the resolution. > 2. Let set this tag to everybody (if it is possible) > > I like first one more. I prefer the second one :-) We could make a separate thread on this. > "In progress" tags. > I think we can let to set this flag to everybody. > And this is probably a good idea! Agree (we could discuss this in the same separate thread as the above question. Thanks, Mikhail SY, Alexey >
