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: TOSCA git repo


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:

 

  1. Who inside OASIS needs to create the repo(s)
  2. What should we name the repo
  3. What type is license is appropriate?
  4. 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
  5. What is the process for reviewing and accepting pull requests? Who participates?
  6. How do we organize the repo? Different directories for different versions of the spec? Different directories for different functional areas?
  7. Etc.

 

Thanks,

 

Chris

 



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