Skip to content

Documentation on best practises for contributing #43

@TobiBu

Description

@TobiBu

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?

Metadata

Metadata

Assignees

No one assigned

    Labels

    documentationImprovements or additions to documentationenhancementNew feature or requestfutureFeature that may be implemented in the future, left as a reference.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions