Hi Mark, On Jan 4, 2007, at 3:04 AM, Mark Brouwer wrote:
Phil Steitz wrote:> And maybe I'm completely out of bounds here but I think that even some> form of issue planning (in what version to expect what) can be > beneficial as well, JIRA is great for that too. Yep. It is. But be careful to keep things as open and welcoming to volunteers. Rigid process is off-putting to some people.+1There is a balance here to be struck. The process that I outlined was for submissions by non-committers, which requires that patches be submitted and I think it is in general much better to have the patches attached to Jiratickets than to have them arrive in emails.I personally favor a uniform way of working between committers and non-committers, the only difference is that committers have checkin permissions, the ability to resolve issues in JIRA [1] and assuming we want all committers to be part of the PMC a binding vote if that turns out to be valuable. [1] as the ASF runs the Enterprise edition of JIRA I assume we can setup our own permission schemes, etc. for the project?
Yes, it is possible, although recently the permission schemes were mostly reset to the standard permission scheme, including river. Many projects had trivial (but not meaningless) differences among each other, and now most projects have the same permission scheme. Of course, all projects have different notification schemes that refer to their own aliases...
Also can somebody show me a good project where they use JIRA for submitting the patches by (non-)committers, I have the tendency to always pick the wrong ones for my samples.
I don't know how good it is, but JDO http://issues.apache.org/jira/ secure/BrowseProject.jspa?id=10630 encourages patches to be posted for review on the JIRA issue before being checked in. I don't have a good example of a patch posted by a non-committer, but see http:// issues.apache.org/jira/browse/JDO-445 for how it works in practice.
That's a great practice (discuss on list, summarize in ticket); but hard to get volunteers to do uniformly. Good examples tend to get followed, though;-)
Probably my biggest frustration with this is having significant discussion happening simultaneously on the JIRA issue and on the email aliases. What I try to do is to start the discussion on email until there is some consensus that "somebody ought to do something" at which point a JIRA is created, the email discussion is summarized as the starting description for the JIRA and the discussion continues on the JIRA.
But each community at Apache is encouraged to find their own working style.
Craig
In general they do ... :-) -- Mark
Craig Russell Architect, Sun Java Enterprise System http://java.sun.com/products/jdo 408 276-5638 mailto:[EMAIL PROTECTED] P.S. A good JDO? O, Gasp!
smime.p7s
Description: S/MIME cryptographic signature
