These documents explain the principles of operational processes when working on open-source software in the DataSHIELD community. They help everyone understand how different tasks should be carried out to ensure people can work together more consistently.
The guidelines are based on best practice and are designed to:
- improve the quality of the software
- make things easier for the people maintaining the software
- help larger groups work together effectively
- make it easier for new contributors to get started
Becca Wilson
Theertha Kariyathan
Olly Butters
Stuart Wheater
Florian Schwarz
Demetris Avraam
Roberto Villegar-Diaz
Hayley Jones
- contributions of code/fixes policy
- Github branch management policy
- master branch, release branch, bug fix branch, feature branch.
- process for creating next release is not defined
- attributions and authorship
- issues policy
- citation of packages policy
- copyright policy
- disclosure issues policy
- contributions.md - only one of 60 datashield packages has a contributions policy.
- testing and test coverage policy
- documentation policy
- test data policy/statement
- roadmap communication
- CRAN policy
- DataSHIELD R code style