This GitHub public repository ( https://github.com/oasis-open/tab-documentation ) was created at the request of the OASIS Technical Advisory Board (TAB) under the OASIS TC Open Repository program to support development of open source resources as anticipated in the TAB Work Plan.
While this GitHub Repository activity remains associated with the TAB, its development priorities, leadership, intellectual property terms, participation rules, and other matters of governance are separate and distinct from the OASIS TC Process and from development practices governing Repositories for TC Members' Chartered Work.
All contributions made to this TC Open Repository are subject to open source license terms expressed in the Apache License v 2.0. That license was selected as the declared "Applicable License" when the TC Open Repository was created.
As documented in "Public Participation Invited", contributions to this OASIS TC Open Repository are invited from all parties, whether affiliated with OASIS or not. Participants must have a GitHub account, but no fees or OASIS membership obligations are required. Participation is expected to be consistent with the OASIS TC Open Repository Guidelines and Procedures, the open source LICENSE designated for this particular repository, and the requirement for an Individual Contributor License Agreement that governs intellectual property.
The purpose of this Technical Advisory Board (TAB) documentation project is to enable a broader community to provide input on the materials developed by the TAB for the benefit of the OASIS community.
The TAB itself is not formally an OASIS Technical Committee, but a Board chartered to provide technical advice to OASIS. The purpose of the OASIS Technical Advisory Board (TAB) "is to advise the OASIS Board of Directors, Staff, and Membership on matters related to the technical agenda of OASIS. The TAB focuses on improving the standards development process, improving the quality of OASIS Standards through the production of guidelines and educational materials, and advising on improvements to community and collaboration processes and technologies."
Repository Maintainers may include here any clarifications — any additional sections, subsections, and paragraphs that the Maintainer(s) wish to add as descriptive text, reflecting (sub-) project status, milestones, releases, modifications to statement of purpose, etc. The project Maintainers will create and maintain this content on behalf of the participants.
The Repository Maintainers are responsible for oversight of this project's community development activities, including evaluation of GitHub pull requests and preserving open source principles of openness and fairness. Maintainers are recognized and trusted experts who serve to implement community goals and consensus design preferences.
Initially, the associated TC members have designated one or more persons to serve as Maintainer(s); subsequently, participating community members may select additional or substitute Maintainers, per consensus agreements.
- Chet Ensign; GitHub ID: https://github.com/chet-ensign/; WWW: OASIS Open
- Stefan Hagen; GitHub ID: https://github.com/sdrees/ (Individual)
- Patrick Durusau; GitHub ID: https://github.com/pdurusau/ (Individual)
- Jacques Durand; GitHub ID: https://github.com/jdanrud/; WWW: Fujitsu North America
- Trey Darley; GitHub ID: https://github.com/treyka/; WWW: New Context
Questions or comments about this TC Open Repository's activities should be composed as GitHub issues or comments. If use of an issue/comment is not possible or appropriate, questions may be directed by email to the Maintainer(s) listed above. Please send general questions about TC Open Repository participation to OASIS Staff at firstname.lastname@example.org and any specific CLA-related questions to email@example.com.