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


Help: OASIS Mailing Lists Help | MarkMail Help

cti message

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

Subject: Re: [cti] RE: [EXT] [cti] Re: [csaf] Notice of upcoming change to OASIS TC Open Repositories

The GitHub organisation name should remain as is - matching the domain name of the organisation as a whole.Â

I.e. oasis-open.org has repositories at github.com/oasis-open/ and oasis-open-projects.org at github.com/oasis-open-projects.

There is no confusion in that sense at all (given the domain name usage) as this is what is meant to happen. Further, making any changes in this area would only add confusion given the domain name usage and the standard GitHub naming schemes that are used.

Changes that impact members (like this one) should only be made after open consultation using the normal OASIS TC processes to get feedback on impacts. This clearly has *not* happened.

OASIS is a member driven organisation - and absent an open member vote about such things, these sorts of changes simply should not be happening.


On Fri, 1 Nov. 2019, 4:08 pm Lenk, Chris, <clenk@mitre.org> wrote:

I concur with Allanâs comments. Itâs nice that links to the repositories will redirect, but it sounds like a lot of work with potential for additional confusion, for only marginal benefit.


If we must change the name of the GitHub organization, my vote would be the more succinct âoasis-reposâ.


Thank you,

Chris Lenk


From: cti@lists.oasis-open.org <cti@lists.oasis-open.org> On Behalf Of Allan Thomson
Sent: Thursday, October 31, 2019 6:34 PM
To: Chet Ensign <chet.ensign@oasis-open.org>; OASIS CTI TC Discussion List <cti@lists.oasis-open.org>; TC OpenC2 <openc2@lists.oasis-open.org>; csaf@lists.oasis-open.org; DITA TC <dita@lists.oasis-open.org>; legalruleml <legalruleml@lists.oasis-open.org>; legaldocml@lists.oasis-open.org; tosca@lists.oasis-open.org
Cc: Carol Geyer <carol.geyer@oasis-open.org>; Jory Burson <jory.burson@oasis-open.org>; Scott McGrath <scott.mcgrath@oasis-open.org>; Paul Knight <paul.knight@oasis-open.org>
Subject: [EXT] [cti] Re: [csaf] Notice of upcoming change to OASIS TC Open Repositories


Chet â may I ask why existing TC work has to change vs the new thing not changing what itâs called? i.e. why arenât the open projects not renaming their work given that its presumably smaller/less people impacted by it.


Seems like OASIS have made this decision without consulting the majority that are impacted by this change.


Secondly, I donât see how changing the word from open to public makes it any less confusing. Were any of the TCâs consulted on this naming change?


Finally, if OASIS must keep with this change path why isnât the name just âTC Repositoriesâ. Whether a repo is open/public outside of the TC is then just a permission setting on github which is exactly what it was designed to do.







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.




Chet Ensign

Chief Technical Community Steward
OASIS: Advancing open source & open standards for the information society

Mobile: +1 201-341-1393Â

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