Documentation on best practises for contributing #43
Labels
documentation
Improvements or additions to documentation
enhancement
New feature or request
future
Feature that may be implemented in the future, left as a reference.
Documentation for contributions to RUBIX
For the first public release we should probably have a little section that describes the best practises in software development and how we envision people to contribute to RUBIX. I.e. we should describe the workflow we adopted. First write an issue, then create branch and implement the feature, write tests and ask for pull request. This might help new developers to adopt to our workflow.
Of course, this is not really an urgent item and needs to be in place only for public release.
@MaHaWo @nashmit could you provide some boiler plate text for how you set up the GitHub project and what the SSC recommends in this case?
The text was updated successfully, but these errors were encountered: