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


Help: OASIS Mailing Lists Help | MarkMail Help

oslc-core message

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

Subject: Re: Question on migrating OSLC Core TC infrastructure to GitHub

Ok Chet, the OSLC Core TC voted today to approve the migration. How do we proceed? Would you setup the Core GitHub repo, with issues, wiki and project management enabled, and you would do the migration? Or do you need us to do the migration.

Jim Amsden, Senior Technical Staff Member
OSLC and Linked Lifecycle Data

From:        Chet Ensign <chet.ensign@oasis-open.org>
To:        Jim Amsden <jamsden@us.ibm.com>
Cc:        "OSLC Core TC (oslc-core@lists.oasis-open.org)" <oslc-core@lists.oasis-open.org>
Date:        10/17/2018 02:54 PM
Subject:        Re: Question on migrating OSLC Core TC infrastructure to GitHub

Jim, I don't see a problem here. Answers interspersed below... 

On Thu, Oct 11, 2018 at 11:18 AM Jim Amsden <jamsden@us.ibm.com> wrote:
We got some outside feedback that indicated some frustration with accessing OSLC Core information. We believe part of that frustration results from the separation of OSLC specification development activities at OASIS from ecosystem support for using OSLC at
open-services.net, and the ongoing, but incomplete effort to migrate open-services.netto a new infrastructure at http://oslc.co.

We also believe that it may be due to fragmented and loosely integrate infrastructure used by OSLC Core which is Subversion SCM, JIRA, MainMain Wiki, and Kavi document publishing.

The OSLC Core TC is managing four different OSLC specifications, one of which consists of seven parts. We have three new specifications that are in the process of getting ready for their initial public review. So we are looking at significant specification development effort for some time. In addition, many of the Core TC members are also members of the OSLC Domains TC which currently uses GitHub.

The OSLC Core TC would like to consider migrating to GitHub in order to use a single infrastructure for all OSLC specification development activities, to provide a simpler, more efficient set of specification lifecycle management capabilities for the TC members, and to improve the external user experience.

Is this feasible?

 I don't see why not. Other TCs are moving this way as well. OpenC2 for example. Take a look at their GitHub projects in https://github.com/oasis-tcs?utf8=%E2%9C%93&q=openc2&type=&language=

I assume that you mean migrating work product drafts, issues, and wiki there. I think it would be straightforward to do that. 

Is it something the TAB would recommend and support?

I think I can safely say yes, but I will bring it up on the next TAB call.  

Is it possible to migrate to GitHub for future specification development work, but maintain the existing Subversion SCM, JIRA, MainMain Wiki for historical purposes?

Yes, we would have to do it for exactly that reason. I have to look into whether or not I can lock them against future updates. The wiki we could put a header on with a pointer to GitHub. There may be a way to do something similar for JIRA. SVN I'd need to look into.  

Can a TC have more than one GitHub repository? The Core TC might wish to develop some of the specifications more independently (OSLC Query, Tracked Resource Sets, Configuration Management and Core for example)?

Yep. Again, OpenC2 is a good example. They have each of their work products being developed in separate TC GitHubs. 

So if you want to proceed that way, let me know. Happy to help you make the switch. 


Jim Amsden, Senior Technical Staff Member

OSLC and Linked Lifecycle Data




Chet Ensign
Chief Technical Community Steward
OASIS: Advancing open standards for the information society


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

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