Re: [tosca] TOSCA git repo

[Chet Ensign <chet.ensign@oasis-open.org>]

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:

1. Who inside OASIS needs to create the repo(s)

Your always similing, ever accommodatingÂTC Administrator !

2. What should we name the repo

Your call.ÂÂ

2. 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.ÂÂ

2. 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.ÂÂ

2. 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.ÂÂ

2. How do we organize the repo? Different directories for different versions of the spec? Different directories for different functional areas?
3. 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Â