Create a guide to be a good Shindig citizen
-------------------------------------------
Key: SHINDIG-261
URL: https://issues.apache.org/jira/browse/SHINDIG-261
Project: Shindig
Issue Type: Task
Components: Website
Reporter: Vincent Siveton
Priority: Minor
Like other ASF projects, Shindig project should define this kind of guide. Here
are some generic rules:
* Search the Wiki or Mail Lists
* Report errors in the code/documentation by submitting patches in Jira
* Respect developers conventions
* Suggest developer environment
Other ASF resources:
http://www.apache.org/dev/contrib-email-tips.html
Also, IMHO to improve the health of the Shindig project, I propose other
project rules, my 2 cents please comments :)
- forbid mail replies on a Jira issue on shindig-dev@ , always comments in
jira. Reasoning: traceability (see SHINDIG-237)
- make patch related to only one issue. Forbid unrelated codes for an issue.
Reasoning: traceability, decrease side effects (see SHINDIG-257)
- make small svn commits and one commit for one jira issue. Reasoning:
traceability, commit readingness
- using an unique commit message template. Reasoning: quality, tracking
informations (specially potential committers)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
