[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [EXT] Re: [cti] Re: Notice of upcoming change to OASIS TC Open Repositories
I still do not see why we do not have organizational repos per TCs and have ALL of the repos assigned to that TC in that organization, public and official work. Having organizational repos would solve the problem at hand and also solve the permissions problems
we have.
Bret
From: cti@lists.oasis-open.org <cti@lists.oasis-open.org> on behalf of Jason Keirstead <Jason.Keirstead@ca.ibm.com>
Sent: Friday, November 1, 2019 1:42 PM To: chet.ensign@oasis-open.org <chet.ensign@oasis-open.org> Cc: carol.geyer@oasis-open.org <carol.geyer@oasis-open.org>; csaf@lists.oasis-open.org <csaf@lists.oasis-open.org>; cti@lists.oasis-open.org <cti@lists.oasis-open.org>; dita@lists.oasis-open.org <dita@lists.oasis-open.org>; jory.burson@oasis-open.org <jory.burson@oasis-open.org>; legaldocml@lists.oasis-open.org <legaldocml@lists.oasis-open.org>; legalruleml@lists.oasis-open.org <legalruleml@lists.oasis-open.org>; openc2@lists.oasis-open.org <openc2@lists.oasis-open.org>; paul.knight@oasis-open.org <paul.knight@oasis-open.org>; scott.mcgrath@oasis-open.org <scott.mcgrath@oasis-open.org>; tosca@lists.oasis-open.org <tosca@lists.oasis-open.org> Subject: [EXT] Re: [cti] Re: Notice of upcoming change to OASIS TC Open Repositories FWIW - we have gone through this process ourselves internally, and never bothered to update any links, references etc - the Github redirect works flawlessly. All existing clones & checkouts work flawlessly.
TC's don't *actually* have to do anything. If and when a TC bothers to update any links to use the new name, is up to your own schedule.
IE - I think the concern here is being a bit overblown.
In response to Allen's comment "why doesn't Open Projects change it's location" - that is not the issue here. The reason this change is being looked at is because of the large confusion between these two things
"OASIS-Open" projects - ie, Github projects under the oasis-open org. These projects just so happen to be TC Open Repos, but that is not the name of the org.
"OASIS Open Projects" - the thing, as an entity.
As you can see - the only solution really is to re-name one of them. It is a lot simpler to re-name a Github organization, than rename an entity that OASIS has spent a year building and branding.
-
Jason Keirstead Chief Architect - IBM Security Threat Management https://clicktime.symantec.com/35rqxWtpxuZWo53KSAnpCPk7Vc?u=www.ibm.com%2Fsecurity "Would you like me to give you a formula for success? It's quite simple, really. Double your rate of failure." - Thomas J. Watson ----- Original message ----- --------------------------------------------------------------------- To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail. Follow this link to all your TCs in OASIS at: https://clicktime.symantec.com/3T7XksXAtBvjUq4qRuKRhxJ7Vc?u=https%3A%2F%2Fwww.oasis-open.org%2Fapps%2Forg%2Fworkgroup%2Fportal%2Fmy_workgroups.php |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]