obook
obook copied to clipboard
EPIC: add more high level guidelines for working collaboratively
I am creating an epic issue here that spans not only the OBook but also other adjacent guides that may want to reference the obook even if the content being collaborated on is not an ontology per se
- [ ] Keep GitHub PRs small and atomic, don't mix concerns; commit early, commit often
- https://github.com/OBOAcademy/obook/pull/458
- https://github.com/linkml/linkml-project-cookiecutter/pull/77
- https://github.com/knocean/practises/#git-and-github
- https://berkeleybop.github.io/best_practice/
- https://codeinthehole.com/tips/advanced-pull-request-crafting/
- https://www.perplexity.ai/search/What-are-some-goG_JHHPSOqanNU5d0jtrw?s=c
- [ ] Social aspects of working collaboratively on an ontology or semantic artefact
- how are decisions made? votes on PRs? Zoom meetings? Consensus? Lead semantic engineer? Lead content developer?
cc @turbomam @sierra-moxon
See also
- https://github.com/linkml/linkml/issues/1744