CONTRIBUTING.md

Contributing

Awesome that you are reading this.

This GitHub follows the Contributor Covenant Code of Conduct.

Submitting use cases

New use cases are welcome.

You can do so by:

Which package to contribute to?

tracerer is part of the babette package suite, which consists out of five packages. Here is how to determine which package is best suited for your contribution:

If you want to contribute to the creation of BEAST2 XML input file, go to beautier.

If you want to contribute to how BEAST2 is run, go to beautier.

If you want to contribute regarding the BEAST2 package management, go to mauricer

If you want to contribute with an overarching idea, go to babette

If you want to contribute to how BEAST2 output is parsed, you are at the right spot :-)

Submitting code

Submitted code should follow these quality guidelines:

These are all checked by Travis CI when submitting a Pull Request.

Emails with code will not be accepted.

Submitting bugs

Awesome. These are your options:

Pull Requests should follow the same guidelines as 'Submitting code'.

Branching policy

git usage

To get started working on tracerer do:

git clone https://github.com/ropensci/tracerer

Development is done on the develop branch. To download and checkout the develop branch, first go into the tracerer folder (cd tracerer), then do:

git checkout develop

Then the workflow is the common git workflow:

git pull
git add --all :/
git commit -m "Did something awesome"
git push


richelbilderbeek/tracerer documentation built on Oct. 2, 2023, 7:32 a.m.