GitHub Repositories #
Source: GitHub Repositories for OASIS TC Members’ Chartered Work. Approved July 29, 2016; effective August 1, 2016.
Overview #
OASIS maintains two separate GitHub organizations for different purposes. Staff administering Technical Committees or Open Projects need to understand which organization applies to the work at hand and the governance rules that apply in each.
For questions about repository setup or administration, contact TC Administration at tc-admin@oasis-open.org.
Two GitHub Organizations #
oasis-open — For open source licensed assets developed through OASIS Open Repositories and Open Projects.
oasis-tcs — For chartered work products developed by OASIS Technical Committees. This organization follows OASIS TC Process rules, IPR Policy, and related governance policies — in the same way as TC Wikis, SVN repositories, and JIRA trackers.
Key Differences #
| Aspect | oasis-open (Open Repos) | oasis-tcs (Chartered Work) |
|---|---|---|
| Contributors | Anyone globally | TC Members primarily |
| Governance | Contributor License Agreements | OASIS TC Process and IPR Policy |
| Public feedback | Limited | Full support via GitHub Issues |
| Outbound licensing | FOSS licenses | OASIS TC IPR Mode |
Repository Requests #
TC officers (Chair or Secretary) submit requests for new repositories through the TC Administration online form. One or more TC Members must be designated as initial Maintainers at the time of the request.
Maintainer Responsibilities #
Staff or TC Members serving as Maintainers are responsible for:
- Accepting and evaluating contributions
- Managing issues, milestones, and releases
- Merging pull requests and resolving conflicts
- Applying labels and managing repository activity
Regular TC Members serve as contributors without direct write access.
Required Repository Files #
Each repository includes default boilerplate files: README, CONTRIBUTING, and LICENSE. The CONTRIBUTING and LICENSE files must remain unaltered. README content may be adapted for project-specific goals.
Contributions and Public Participation #
Substantive contributions are expected from TC Members only. Non-members may provide feedback via GitHub Issues. All contributions follow the “OASIS Feedback License” terms. Public participation is welcomed through issue tracking and comments.