TC Members,
As you make plans for version control, issues management, and Wiki pages, you may wish to consider the two facilities OASIS supports for the use of public GitHub repositories -- for dedicated TC work and for open source software development. This note supplements the references provided by Chet [5]; it displays a comparison of features for the two GitHub repository facilities. References and examples are listed for both.
Please understand that TC decisions to use these collaboration venues and others are not mutually exclusive: you may spin up multiple GitHub repositories of both kinds, and elect to use GitHub's integrated issues tracking and Wiki pages alongside the use of TC JIRA instance and a TC Moin Wiki.
Cheers,
- Robin Cover
------
Comparison: OASIS Open Repositories versus GitHub Repositories for TC Members' Chartered work
A. OASIS Open Repositories
- with references below [1] and examples [3]
a) anyone (OASIS member or not) may fully participate, including any OASIS TC Members; no fees or membership
b) input licensing governed by Individual Contributor License Agreement (CLA)
c) outbound licensing governed by FOSS (open source) license: BSD-3-Clause, Apache, CC-BY, Eclipse
d) development practices and process governed by Open Repository Guidelines and Procedures, not by TC Process
e) provides no direct support for public feedback to the sponsor TC itself
f) assets developed in the repository may be contributed to any OASIS TC (Work Products) by any TC Member, subject to comnpatible licensing
B. GitHub Repositories for TC Members Chartered work
- with references below [2] and examples [4]
a) substantive contributions expected only from TC member participants (substantive: "any contributions larger than a breadbasket")
b) input licensing governed by OASIS policies and agreements: IPR Patent Policy, IPR Mode, Copyright, Trademark
c) outbound licensing governed by OASIS policies for TCs, not by (OSI-approved) open source licenses
d) development practices and process governed by OASIS TC Process
e) support public feedback to the TC, similar to the TC comment list, via Issues, Comments, Conversations (rarely, pull requests)
f) assets developed in the repository are automatically/inherently part of official TC work, not requiring additional contribution
=========================================
[1] OASIS Open Repositories: References
========================================
OASIS Open Repositories: Overview
FAQ Document
Licenses
Guidelines
Individual CLA Form
===================================================================
[2] GitHub Repositories for TC Members' Chartered Work: References
===================================================================
OASIS TCs: GitHub Repositories for TC Members' Chartered Work
TC GitHub Repository: Documentation
c) TC GitHub Repository Request Form
========================================================================
[3] OASIS Open Repositories: Examples
========================================================================
dita-lightweight
"Schema files, tools and documentation related to the Lightweight DITA Subcommittee"
dita-rng-converter.
"Providing cross-platform tools for generating DITA-conforming DTD- and XSD-format versions of RELAX NG DITA grammars: document type shells, vocabulary modules, and constraint modules. It makes it as easy as possible to develop and maintain DITA grammars by allowing use of RELAX NG syntax.
tosca-test-assertions
"Manages TOSCA Simple Profile in YAML templates and definitions that can be used to test TOSCA compliance using metadata (primarily the OASIS Test Assertion Markup Language) that describes the test and the expected behavior of the TOSCA tool or orchestrator"
legaldocml-akomantoso
"Schema files, examples, exemplificative implementations and libraries, and documentation related to the LegalDocML TC and Akoma Ntoso schema"
cti-stix2-json-schemas
"Non-normative schemas and examples for STIX 2"
cti-documentation
"GitHub Pages site for STIX, CybOX, and TAXII"
cti-stix-validator
"Validator for STIX 2.0 JSON normative requirements and best practices"
cti-pattern-validator
"Validate patterns used to express CybOX content in STIX Indicators"
cti-stix-visualization
"Lightweight visualization for STIX 2.0 objects and relationships"
cti-cybox3-json-schemas
"Non-normative schemas and examples for CybOX 3"
cti-marking-prototype
"Prototype for processing granular data markings in STIX"
cti-stix-elevator
"Convert STIX 1.2 XML to STIX 2.0 JSON"
cti-pattern-matcher
"Match STIX content against STIX patterns"
========================================================================
[4] GitHub Repositories for TC Members' Chartered Work: examples
========================================================================
"Supporting version control for Work Product artifacts developed by members of the CSAF TC, including prose specifications and secondary artifacts like meeting minutes and productivity code"
"Tools for producing API descriptions for OData services that adhere to the OpenAPI Specification"
"Standard vocabularies for annotating OData services"
"Object Model for XLIFF Versions 2.0 and higher"
"JSON serialization of the XLIFF Abstract Object Model"
"Official repository for the source files for the written DITA specification "
"OASIS OSLC Domains TC: Repository providing version control, issues tracking, and GitHub Wiki pages to support development of Open Services for Lifecycle Collaboration (OSLC) resources by TC members"
"OASIS CTI TC: Provides issue tracking and wiki pages for the STIX 2.x Work Products, including: Part 1: STIX Core, Part 2: STIX Objects, Part 3: Cyber Observable Core, Part 4: Cyber Observable Objects, and Part 5: Patterning"
"OASIS LegalXML Electronic Court Filing TC: Supporting version control for ECF Version 5.0 UML models created with BOUML"
-----------
[5] List of useful OASIS resources for your TC
"Other facilities you can request include:
--
Robin Cover
OASIS, Director of Information Services