Re: [ubl-comment] Given that they are part of 2.2 (by reason of backward compatibility)

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

Hello Boris, 

Thank you for the comment. OASIS Technical Committees are welcome to use github for specification development if they so choose. Several TCs have done so. TCs can also use SVN if they wish. 

For the final approved work products however, OASIS needs a fixed, stable, immutable copy that we can store and point to in the future, confident that it will not have changed. Yes, of course, Github provides mechanisms for accomplishing this, however our docs.oasis-open.org server has for over a decade now been the reference point for authoritative publication of TC work. I don't want to cause confusion by starting to mix up locations. 

Best, 

/chet

On Thu, Sep 28, 2017 at 11:29 AM, Boris Kortiak <boris@tbsindustries.com> wrote:

Hi All,

 

Just a thought, with low confidence of relevance…

 

Has anyone looked into using something like a github¹ to maintain version control and information?

 

¹ Github see:

-          https://github.com/features

-          https://en.wikipedia.org/wiki/GitHub

-          https://www.youtube.com/user/github

 

 

--
Boris Kortiak
(UTC-5)
Main: tel: +1 215-535-6500   fax: +1 215-535-6505
Direct: tel: +1 215-695-3302 fax: +1 215-695-3371

en-US-5;pt-BR-4;es-US-3;uk-UA-2;ru-RU-1
http://www.tbsindustries.com

“Computer recycling Specialists”

/chet 
----------------
Chet Ensign
Director of Standards Development and TC Administration 
OASIS: Advancing open standards for the information society
http://www.oasis-open.org

Primary: +1 973-996-2298
Mobile: +1 201-341-1393