It's good to leverage JIRA, but everything that happens there should
be considered invisible for the most part and only reviewed on a
random and infrequent basis.
A good way to bring jira "discussion" back to the list is to follow up
on the list rather than posting more jira comments. Maybe by having
the first followup comment be a link to Nabble's "forum" view of the
list. Optionally, you can Cc [EMAIL PROTECTED] and include "[jira]
OPENEJB-XXX" anywhere in your subject line and your email will get
added as a jira comment.
For those looking to contribute, there are some good habits to put
into use. We use a permission scheme called "Interactive
Permissions." It's description has some good information:
Interactive Permissions
This permissions model differs from the Standard Permissions
model in that people in the Contributor role must interact with
the dev list to get to get issues assigned to them and issues
closed. This isn't a trust issue, more that there are a few
benefits.
1. Active contributors hitting the list to begin and end work
shows other people not yet active how to get involved.
2. Adds more "touch points" between Contributors and
Committers. It should be possible to "see" the active
contributors even if you are not watching the JIRA or SVN
notifications. It's also hoped that the practice of
announcing your intentions on the dev list will persist
even when the Contributor becomes a Committer.
3. Gives Committers the opportunity to help, mentor or
otherwise get the Contributor going in the right direction
before a task is started; potentially resulting in fewer
rejected patches, less waisted Contributor time, and more
collaborative development.
4. Overall brings more communication to the dev list before
all work is done and all decisions made giving more
potential to collaboration.
If you'd like to get added to the openejb-contributors JIRA group,
just ping the list with your JIRA id and someone will add you.
Happy coding!
-David
