Project governance and roadmap

[k8hertweck]

Basic questions for governance:

• create GOVERNANCE.md and link from README (and index?)
• who is leading this project? GitHub usernames for core team, including specific roles (who responds to PRs?)
• how are decisions made regarding new feature development and accepting PRs?

Basic roadmap (add to README, and perhaps also index?):

• project status: still in active development? in maintenance mode?
• what things are top priority for new features?

[k8hertweck]

Additional information that may be useful is available here: https://chanzuckerberg.github.io/open-science/code/os-projects#governance

[k8hertweck]

I think the ggplot2 governance pretty closely replicates what this project would like to have (with "core contributors" in ggplot2 replaced by "maintainers"). Some additional details from the Carpentries' maintainers responsibilities would help clarify what maintainers would need to do.

[ergonyc]

@k8hertweck great resources. I will reformat cribbing on the ggplot2 docs and start to tick off the checks

[ergonyc]

Note that the GOVERNANCE_draft.md changes were accidently pushed to the main-dev branch... They should be correctly merged with the main branch to make considering their adoption more straightforward. (pr #188)

[ergonyc]

Everyone: please check out the GOVERNANCE.md [draft (https://github.com/ndcn/omicser/blob/main/GOVERNENCE_draft.md)

Need to:

• add all contributors / maintainers handles to documents

Note that ROADMAP updates remain incomplete