Project Participation Protocols

Project Participation Protocols

  Back to Project Home

  This is a list of general rules of conduct and processes for participation in the SonATA project.
 

  1. Please, no flaming in the forums or anywhere else.
  2. Collaborate and disuss issues with other participants BEFORE working on any issue.
  3. To participate in code changes, please follow these general guidelines:
    • Avoid performing work which will result in it not being accepted into the project. To avoid this, view all the issues in our issue tracker at http://issues.setiquest.org/projects/sonata/issues?query_id=7. Offer to help with an already existing issue, or create an issue of your own. If you create an issue of your own please try to get a consensus that your issue is worth doing. If people generally agree, start working on the issue, informing the community what you are doing.
    • Allow and welcome others to help you and offer advice if you are working on an issue. The more people involved addressing an issue, the more likely the result will be accepted into the source code base.
  4. To participate in issues involving the source code:
    • Create an account on GitHub if you do not already have one.
    • Perform a Fork of the setiQuest/SonATA project
    • "git clone" the forked project onto your local computer. Make whatever changes you going to make. Make sure to follow any project/source code quidelines.
    • When you are ready to have your changes accepted into the project issue a "pull request" to the setiQuest/SonATA project, along with details of the changes, preferable referencing the issues.setiquest.org issue number for reference.
    • Please do not take it personally if your work is not accepted into the setiQuest/SonATA project. Following the suggestions mentioned in this topic will reduce the risk of your work not being accepted.