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


Hi Chris, all,

 

With regard to Arturoâs question in the same thread, I think that we need to also cover the âSimple Profileâ by all the TOSCA rules. Otherwise, they might not be usable in the same contexts. This does not mean that other profiles need to follow this, but since the âSimple Profileâ is under the OASIS TOSCA maintenance, we should ensure that is covered exactly by the same rules as the specification.

 

BR/C

 

From: <tosca@lists.oasis-open.org> on behalf of Chet Ensign <chet.ensign@oasis-open.org>
Date: Thursday, 30 January 2020 at 15:36
To: Chris Lauwers <lauwers@ubicity.com>
Cc: Tal Liron <tliron@redhat.com>, "tosca@lists.oasis-open.org" <tosca@lists.oasis-open.org>
Subject: Re: [tosca] Managing TOSCA type profiles in github

 

Hi Chris - Yes. The specification must be on a TC-only platform. - /chet

 

On Thu, Jan 30, 2020 at 12:58 AM Chris Lauwers <lauwers@ubicity.com> wrote:

I think we need a middle ground here:

 

  • Since the Simple Profile types will no longer be part of the TOSCA âstandardâ, it is OK for that profile to managed in an open repository
  • However, the specification itself (including the examples in that specification) must comply with the OASIS IPR rules, and as a result can only be managed in a closed repo IMHO

 

Chet, does that sound correct to you?

 

Thanks,

 

Chris

 

 

From: Tal Liron <tliron@redhat.com>
Sent: Wednesday, January 29, 2020 11:46 AM
To: Chet Ensign <chet.ensign@oasis-open.org>
Cc: Chris Lauwers <lauwers@ubicity.com>; tosca@lists.oasis-open.org
Subject: Re: [tosca] Managing TOSCA type profiles in github

 

On Wed, Jan 29, 2020 at 1:36 PM Chet Ensign <chet.ensign@oasis-open.org> wrote:

Hey Tal, I am with you on "open." However, the nuance here is that the work in an Open Repo is *not* official TC work covered under the OASIS IPR Policy.

 

I think that matches with our intent -- at least at this point we are not thinking of these repos as official specification, rather as a tool to help us collaborate on the work towards the specification. The Word document will be the official source of truth. But maybe Chris has other thoughts?


 

--


/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]