Refine policies for issues, PRs, branching - Githubissues

ld4l-labs / bibliotek-o

bibliotek-o: a BIBFRAME 2 Extension Ontology

Creative Commons Zero v1.0 Universal

9 stars 8 forks source link

Refine policies for issues, PRs, branching #31

Closed rjyounes closed 7 years ago

rjyounes commented 7 years ago

Currently defined in README but needs some clarification:

Difference in process for those with and without write access - is this just a matter of cloning vs forking the repo?
Creating a PR vs creating a feature branch
Suggestion from @darrenleeweber: "Create a PR against an issue with the proposed changes in it. Use labels or a title prefix to indicate that it is pending approval, e.g. [PENDING #xxx APPROVAL]. The branch used to create the PR can be checked out and used by tools to run reasoners etc. on it and also explore implications for conversions." This suggests the PR itself is merged to the remote / upstream repo, rather than creating a PR against develop and merging it directly there.
Pruning defunct branches. E.g., should a branch be deleted as soon as it is merged into develop?

rjyounes commented 7 years ago

Possibly useful references, again from @darrenleeweber:

For reference only, I’m not recommending anything in particular, only noting that this is a road that others have walked already and documented some helpful tips:

https://github.com/jamesaoverton/obo-tutorial/blob/master/docs/ontology-development.md
- they point, at the bottom, to interesting project: https://github.com/owlcollab/owltools
good use of a wiki: https://github.com/nmrML/nmrML/wiki
- has use-cases and contribution help: https://github.com/nmrML/nmrML/wiki/Contributing
vivo-isf also uses the wiki: https://github.com/openrif/vivo-isf-ontology/wiki

rjyounes commented 7 years ago

Completed