Hi Rex (and all)
Some additional documentation is available online for the
use of GitHub repositories by TC members (for official TC
work). We also support "OASIS Open Repositories" for public
participation in work loosely associated with a TC (but not
under TC control).
"GitHub Repositories for OASIS TC Members' Chartered Work"
In particular, note
a) The GitHub repositories for TCs are considered venues
for spinup by TCs (not by individual Subcommittees), but a TC
can write a Description and Purpose Statement that matches the
scope for a particular Subcommitee, and/or subset of
b) We endeavor to provide write access for those who want
and need to make commits to these GitHub repositories, but
there's a special role for Maintainers (designated persons)
that works better than giving blanket write privs to everyone
in a TC. See excerpt below.
Please feel free to contact me with questions on any
details that may arise in your discussions
- Robin Cover
When a TC makes request for creation of a GitHub repository,
one or more TC Members must be designated to serve as initial
Maintainer(s) — sometimes also called "Committer(s)".
Additional or substitute Maintainers may be designated at any
time from among qualified TC Members.
All TC members may "contribute" substantive content, as
well as provide input via GitHub Issues, comments, GitHub
conversations, Wiki edits (etc), but they do not have full
Maintainer responsibilities, described below. A regular TC
Member can be a "contributor" in the GitHub defined
sense: "contributor is someone who has contributed to
a project by having a pull request merged but does not have
collaborator [ viz, direct write] access."
A Maintainer, much like a prose specification editor, holds
the pen and has direct write access to the GitHub "code"
repository. A Maintainer accepts input from all TC members,
evaluating it for incorporation into revised content. TC
member input is expected in the form of GitHub
Issues/Comments, GitHub conversations, pull requests, but
might also be taken from the TC discussion list, or from TC
Maintainer thus serves in an editorial capacity by
having responsibility for assigning and closing issues,
creating and associating milestones, creating releases,
designating a default branch, creating and applying labels,
initiating conversations on pull requests, merging and
closing pull requests, assigning evaluation of a pull
request, resolving merge conflicts, etc. The Maintainers may
also monitor repository activity to help ensure that
substantive contributions are made only by TC Members or by
parties who agree to the terms of the OASIS
Feedback License, as explained in the repository's