[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [cti] Re: [EXT] Re: [cti] Re: Notice of upcoming change to OASIS TC Open Repositories
|From:||"Bret Jordan" <Bret_Jordan@symantec.com>|
|To:||"Jason Keirstead" <Jason.Keirstead@ca.ibm.com>, firstname.lastname@example.org|
|Cc:||email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com|
|Date:||Fri, Nov 1, 2019 4:52 PM|
|Subject:||[EXTERNAL] [cti] Re: [EXT] Re: [cti] Re: Notice of upcoming change to OASIS TC Open Repositories|
----- Original message -----
From: Chet Ensign <firstname.lastname@example.org>
Sent by: <email@example.com>
To: OASIS CTI TC Discussion List <firstname.lastname@example.org>, TC OpenC2 <email@example.com>, firstname.lastname@example.org, DITA TC <email@example.com>, legalruleml <firstname.lastname@example.org>, email@example.com, firstname.lastname@example.org
Cc: Carol Geyer <email@example.com>, Jory Burson <firstname.lastname@example.org>, Scott McGrath <email@example.com>, Paul Knight <firstname.lastname@example.org>
Subject: [EXTERNAL] [cti] Re: Notice of upcoming change to OASIS TC Open Repositories
Date: Fri, Nov 1, 2019 4:13 PM
Hi everyone,After sending this alert yesterday, I received several statements of concern. I had sent a similar message over the summer and heard nothing so I thought this would not be controversial.Given that concerns have been raised though, I will hold on this action and look for a less invasive solution.Best regards,/chetOn Thu, Oct 31, 2019 at 5:46 PM Chet Ensign <email@example.com> wrote:Members of the copied TCs,
For some time, we have encountered confusion about OASIS Open Repositories (open source projects initiated by a Technical Committee) and Open Projects (open source projects independent of the OASIS TC Process but with a pathway to standardization). People inside of OASIS and out have told us that they get the two confused.
To address this, we are preparing to change the program name from "OASIS TC Open Repositories" to "OASIS TC Public Repositories." Because your TC has one or more open repos set up, we're writing to give you advance notice so that you can ask questions and look at whether this might affect your project.
The process of doing this will involve several changes. The biggest will be the change of the GitHub organization from https://github.com/oasis-open/ to .../oasis-tc-public-repos/. This will require my updating links on README files, etc. and recreating the original org and setting it to private so that it remains reserved for our use.
According to GitHub (https://help.github.com/en/github/setting-up-and-managing-organizations-and-teams/renaming-an-organization), it will automatically redirect references to the repositories. Web links to existing repositories will continue to work.
You can continue pushing your local repositories to old remote tracking URLs without updating. However, they recommend updating all existing remote repository URLs after changing the organization name.
Previous Git commits will also be correctly attributed to the correct users.
After the change, any references to the old organization name https://github.com/oasis-open/ will return a 404 error. I will be updating all of our documentation to point to the new organization. API requests that use the old organization's name will also return a 404 error. I don't know that anyone has set up any such APIs but if you have, please let me know.
I will also go through references to your Open Repos on your TC webpages and update them for you.
While the name change itself will be quick, the checking and updating will take me several days. I will send out a note to you all once that is completed.
Please let me know if you have any questions or concerns.----