OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC

A couple of months ago, Tal made the following suggestion:   Let's create a git repository with all the YAML snippets from the spec. This would allow each of us to run them through our parsers and see if they are valid examples. We would then require that any new examples in the spec be committed to this repo. We can even do auto-testing (Travis?) to ensure this, even if it's just at the YAML level.   I continue to think that that is an excellent suggestion. As we’re starting for focus on editing the 2.0 specification, now may be a good time to get this started. I assume we can use the oasis github site. In fact, we already have a repo there:   https://github.com/oasis-open/tosca-test-assertions   If others think this is a good idea as well, then let’s please discuss how to get this started:   Who inside OASIS needs to create the repo(s) What should we name the repo What type is license is appropriate? Will the repo contain just the code snippets from the spec, or can it be used as a general-purpose collection of TOSCA samples contributed by TOSCA members What is the process for reviewing and accepting pull requests? Who participates? How do we organize the repo? Different directories for different versions of the spec? Different directories for different functional areas? Etc.   Thanks,   Chris  

Hi Chris - just saw this and figured I can save you some time. One question is do you want a TC GitHub (a closed TC resource only open to TC members) or an Open Repository (a TC-hosted open source project open to anyone, OASIS/TC member or not, so long as the sign the appropriate CLA)? The existing one you point to is an Open Repository. You can request a TC GitHub here -> https://www.oasis-open.org/resources/tc-admin-requests/request-a-tc-github-version-control-instance-be-created . You'll all need to agree on the repo name, the maintainers, a short description, and a purpose statement. You can request an Open Repo here -> https://www.oasis-open.org/resources/tc-admin-requests/open-repository-request . You'll need the same info plus your choice from the approved licenses and it will need to be approved by a resolution of the TC. On Wed, Jan 22, 2020 at 4:51 PM Chris Lauwers < lauwers@ubicity.com > wrote: Who inside OASIS needs to create the repo(s) Your always similing, ever accommodating TC Administrator ! What should we name the repo Your call. What type is license is appropriate? Your choices are BSD-3-Clause License, MIT License, Apache License v 2.0, CC-BY 2.0, CC-BY 4.0, or Eclipse Public License v 1.0. Personally I suggest Apache as it includes patent provisions but you may well have reason to go with one of the others. Will the repo contain just the code snippets from the spec, or can it be used as a general-purpose collection of TOSCA samples contributed by TOSCA members Either option above lets you do either or both. What is the process for reviewing and accepting pull requests? Who participates? You all should work that out with the maintainer(s). The pull request is the opportunity for broader review and discussion and it would be a good idea to work out your protocols before the work starts. We have a guide for maintainers here -> https://www.oasis-open.org/resources/open-repositories/maintainers-guide This may help. How do we organize the repo? Different directories for different versions of the spec? Different directories for different functional areas? Etc. Hope the above is helpful. /chet Thanks, Chris -- /chet ---------------- Chet Ensign Chief Technical Community Steward OASIS: Advancing open source & open standards for the information society http://www.oasis-open.org Mobile: +1 201-341-1393