dawn

Proposed Process for Community Bug Reporting & Patches

Discussion created by dawn on Sep 13, 2007
Latest reply on Oct 29, 2007 by Gaston Dombiak

As promised, I have been working on a process to better manage Community Bug Reporting & Patches for the Ignite Realtime Community.  Here's the proposed process - please post any feedback to this discussion. I'll finalize this and put it in a document sometime next week. I tried to keep it simple & easy, but with a specific escalation process that community members can use for any issues.

 

Filing Bugs

 

Process for Community Members

Check to see if the bug has already been filed in JIRA

If not, post a discussion with the tag "bug_report"

 

Responsibility

Dawn to maintain JIRA access rights

 

Project Responsibilities:  The people below should monitor their communities for items tagged with "bug_report" and respond to each thread with either the number of an issue in Jira or an explanation of why it is not a bug.

  • Openfire: Gato

  • Spark: Derek

  • IM Gateway: Jadestorm

  • Smack: Gato

  • XIFF: Derek

  • Asterix IM: srt

 

Escalation

If you do not see a response to your thread with either the number of an issue in Jira or an explanation of why it is not a bug within 7 days, send a private message to Dawn with a link to your original discussion thread.  Dawn will harass the owner above to respond.

 

-


 

Submitting Patches

 

Process

Community member: Sign the contributor agreement found at http://www.igniterealtime.org/ignite_contributor_agreement.pdf (for contributions by an individual) or http://www.igniterealtime.org/ignite_contributor_agreement_org.pdf (for contributions on behalf of an organization). Submit a discussion thread with a link to your patch and the tag "patch".

If accepted, owner (responsibilities below) will put it in Jira and then it will go into an appropriate release of the code.

If not accepted, owner will respond to the thread with an explanation.

 

Responsibility

 

The people below should monitor their communities for items tagged with "patch" and respond to each thread with either the number of an issue in Jira containing the patch or an explanation of why it was not accepted.

  • Openfire: Gato

  • Spark: Derek

  • IM Gateway: Jadestorm

  • Smack: Gato

  • XIFF: Derek

  • Asterix IM: srt

 

 

Escalation

If you do not see a response to your thread with either the number of an issue in Jira containing the patch or an explanation of why it was not accepted within 7 days, send a private message to Dawn with a link to your original discussion thread.  Dawn will harass the owner above to respond.

Outcomes