OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

tosca message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [tosca] Managing TOSCA type profiles in github


Chris, one other question to answer. Assuming you do want to open a new repository, should it be an Open Repo like -test-assertions, or a TC GitHub?Â

The difference is that the Open Repo is an open-source project that anyone, OASIS member or not, can take part in. The TC GitHub is like any other TC resource - available only for the TC members. (Although, being another GitHub repo, the maintainer has to keep an eye on who's submitting pull requests, etc.) It sounds to me like you'll want this to be a TC GitHub since this is to be the single source of truth.Â

Best -Â

/chetÂ

On Tue, Jan 28, 2020 at 11:52 PM Chris Lauwers <lauwers@ubicity.com> wrote:

We agreed on Tuesday to start using github to keep master copies of TOSCA type profiles (such as the Simple Profile). These master copies would act as the âsingle source of truthâ from which other descriptions (such as type definitions in Word documents) could be automatically generated.

Â

We need to agree on some logistical issues before we can proceed:

Â

  1. We currently have one TOSCA github repository at https://github.com/oasis-open/tosca-test-assertions. I assume we donât want to reuse this repo for managing type profiles. Is there agreement we will create a new repository? If so, what should we name this repo?
  2. Weâll start with type definitions that are part of the Simple Profile. Which versions should we support? I assume we will want to manage Version 2.0 of the Simple Profile in this repository. What about Version 1.3? What about older versions?
  3. How do we manage the directory structure in this repository? I suggest we use multiple top-level directories, one for each profile. Underneath these directories, will we have subdirectories for different versions?
  4. How do we organize a type profile into YAML files? It seems to me we have different options:
    1. One YAML file for the entire profile
    2. One YAML file for each type of types (e.g. a datatypes.yaml, nodetypes.yaml, relationshiptypes.yaml, etc.)
    3. One YAML file for each individual type

Â

Other issues we need to discuss and agree on?

Â

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Â


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]