OASIS Common Security Advisory Framework (CSAF) TC

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 ---------------- Chet Ensign Chief Technical Community Steward OASIS: Advancing open source & open standards for the information society http://www.oasis-open.org Mobile: +1 201-341-1393

Hi Chet, What's the schedule for this? Since we've giving the Tech Talk about our plug fest on Tuesday, I may need to make some adjustments in our slides. Dave David Lemire, CISSP Systems Engineer HII Mission Driven Innovative Solutions (HII-MDIS) formerly G2, Inc. Technical Solutions Division 302 Sentinel Drive Annapolis Junction, MD 20701 Email: dave.lemire@g2-inc.com Work: 301-575-5190 Mobile: 240-938-9350 On Thu, Oct 31, 2019 at 5:47 PM Chet Ensign < chet.ensign@oasis-open.org > 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. -- /chet ---------------- Chet Ensign Chief Technical Community Steward OASIS: Advancing open source & open standards for the information society http://www.oasis-open.org Mobile: +1 201-341-1393

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, /chet On Thu, Oct 31, 2019 at 5:46 PM Chet Ensign < chet.ensign@oasis-open.org > 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. -- /chet ---------------- Chet Ensign Chief Technical Community Steward OASIS: Advancing open source & open standards for the information society http://www.oasis-open.org Mobile: +1 201-341-1393 -- /chet ---------------- Chet Ensign Chief Technical Community Steward OASIS: Advancing open source & open standards for the information society http://www.oasis-open.org Mobile: +1 201-341-1393

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, /chet On Thu, Oct 31, 2019 at 5:46 PM Chet Ensign < chet.ensign@oasis-open.org > 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. -- /chet ---------------- Chet Ensign Chief Technical Community Steward OASIS: Advancing open source & open standards for the information society http://www.oasis-open.org Mobile: +1 201-341-1393 -- /chet ---------------- Chet Ensign Chief Technical Community Steward OASIS: Advancing open source & open standards for the information society http://www.oasis-open.org Mobile: +1 201-341-1393

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, /chet On Thu, Oct 31, 2019 at 5:46 PM Chet Ensign < chet.ensign@oasis-open.org > 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. -- /chet ---------------- Chet Ensign Chief Technical Community Steward OASIS: Advancing open source & open standards for the information society http://www.oasis-open.org Mobile: +1 201-341-1393 -- /chet ---------------- Chet Ensign Chief Technical Community Steward OASIS: Advancing open source & open standards for the information society http://www.oasis-open.org Mobile: +1 201-341-1393

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, /chet On Thu, Oct 31, 2019 at 5:46 PM Chet Ensign < chet.ensign@oasis-open.org > 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. -- /chet ---------------- Chet Ensign Chief Technical Community Steward OASIS: Advancing open source & open standards for the information society http://www.oasis-open.org Mobile: +1 201-341-1393 -- /chet ---------------- Chet Ensign Chief Technical Community Steward OASIS: Advancing open source & open standards for the information society http://www.oasis-open.org Mobile: +1 201-341-1393

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, /chet On Thu, Oct 31, 2019 at 5:46 PM Chet Ensign < chet.ensign@oasis-open.org > 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. -- /chet ---------------- Chet Ensign Chief Technical Community Steward OASIS: Advancing open source & open standards for the information society http://www.oasis-open.org Mobile: +1 201-341-1393 -- /chet ---------------- Chet Ensign Chief Technical Community Steward OASIS: Advancing open source & open standards for the information society http://www.oasis-open.org Mobile: +1 201-341-1393

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 www.ibm.com/security 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 ----- From: Chet Ensign <chet.ensign@oasis-open.org> Sent by: <cti@lists.oasis-open.org> To: 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: [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,    /chet   On Thu, Oct 31, 2019 at 5:46 PM Chet Ensign < chet.ensign@oasis-open.org > 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.   -- /chet  ---------------- Chet Ensign Chief Technical Community Steward OASIS: Advancing open source & open standards for the information society http://www.oasis-open.org Mobile: +1 201-341-1393      -- /chet  ---------------- Chet Ensign Chief Technical Community Steward OASIS: Advancing open source & open standards for the information society http://www.oasis-open.org Mobile: +1 201-341-1393   

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 ----- From: Chet Ensign <chet.ensign@oasis-open.org> Sent by: <cti@lists.oasis-open.org> To: 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: [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,    /chet   On Thu, Oct 31, 2019 at 5:46 PM Chet Ensign < chet.ensign@oasis-open.org > 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.   -- /chet  ---------------- Chet Ensign Chief Technical Community Steward OASIS: Advancing open source & open standards for the information society http://www.oasis-open.org Mobile: +1 201-341-1393      -- /chet  ---------------- Chet Ensign Chief Technical Community Steward OASIS: Advancing open source & open standards for the information society http://www.oasis-open.org Mobile: +1 201-341-1393    --------------------------------------------------------------------- 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

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 ----- From: Chet Ensign <chet.ensign@oasis-open.org> Sent by: <cti@lists.oasis-open.org> To: 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: [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,    /chet   On Thu, Oct 31, 2019 at 5:46 PM Chet Ensign < chet.ensign@oasis-open.org > 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.   -- /chet  ---------------- Chet Ensign Chief Technical Community Steward OASIS: Advancing open source & open standards for the information society http://www.oasis-open.org Mobile: +1 201-341-1393      -- /chet  ---------------- Chet Ensign Chief Technical Community Steward OASIS: Advancing open source & open standards for the information society http://www.oasis-open.org Mobile: +1 201-341-1393    --------------------------------------------------------------------- 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

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 ----- From: Chet Ensign <chet.ensign@oasis-open.org> Sent by: <cti@lists.oasis-open.org> To: 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: [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,    /chet   On Thu, Oct 31, 2019 at 5:46 PM Chet Ensign < chet.ensign@oasis-open.org > 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.   -- /chet  ---------------- Chet Ensign Chief Technical Community Steward OASIS: Advancing open source & open standards for the information society http://www.oasis-open.org Mobile: +1 201-341-1393      -- /chet  ---------------- Chet Ensign Chief Technical Community Steward OASIS: Advancing open source & open standards for the information society http://www.oasis-open.org Mobile: +1 201-341-1393    --------------------------------------------------------------------- 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

That would create a much larger burden on OASIS staff though. Bret Jordan --- [EXTERNAL] [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>, chet.ensign@oasis-open.org Cc: carol.geyer@oasis-open.org, csaf@lists.oasis-open.org, cti@lists.oasis-open.org, dita@lists.oasis-open.org, jory.burson@oasis-open.org, legaldocml@lists.oasis-open.org, legalruleml@lists.oasis-open.org, openc2@lists.oasis-open.org, paul.knight@oasis-open.org, scott.mcgrath@oasis-open.org, tosca@lists.oasis-open.org 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 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 ----- From: Chet Ensign <chet.ensign@oasis-open.org> Sent by: <cti@lists.oasis-open.org> To: 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: [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,    /chet   On Thu, Oct 31, 2019 at 5:46 PM Chet Ensign < chet.ensign@oasis-open.org > 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.   -- /chet  ---------------- Chet Ensign Chief Technical Community Steward OASIS: Advancing open source & open standards for the information society http://www.oasis-open.org Mobile: +1 201-341-1393      -- /chet  ---------------- Chet Ensign Chief Technical Community Steward OASIS: Advancing open source & open standards for the information society http://www.oasis-open.org Mobile: +1 201-341-1393    --------------------------------------------------------------------- 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

And with all due respect, Jason you have completely totally missed the point that the organisation's DNS name is and remains oasis-open.org . That is the beginning and end of the argument. It also happens to be the actual organisation name if you want to check those details too. The organisation is not "oasis" and never has been. We may use that as shorthand in various ways - but "OASIS OPEN" is the organisation's legal name - also noted in the Bylaws. That also by itself should be the beginning and end of the argument too. If oasis-open-projects.org is considered confusing compared to oasis-open.org (which is the logical conclusion from your claim of major confusion) then it should have been completely named differently - and - as it is the newer name then it is the one that should be changed. This has nothing to do with GitHub itself - the organisations within GitHub should simply match the organisation DNS usage (as they normally do). You are trying to fix an issue in the wrong place - if the issue is truely one that is causing significant confusion then the oasis-open-projects organisation needs to the changed. That same "confusion" is inherent in the domain names - and the "open" in oasis-open was never about open source so attempting to redefine an existing established usage isn't sensible. Tim. On Fri, 1 Nov. 2019, 8:43 pm Jason Keirstead, < Jason.Keirstead@ca.ibm.com > wrote: 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 www.ibm.com/security "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 ----- From: Chet Ensign < chet.ensign@oasis-open.org > Sent by: < cti@lists.oasis-open.org > To: 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: [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, /chet On Thu, Oct 31, 2019 at 5:46 PM Chet Ensign < chet.ensign@oasis-open.org > 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. -- /chet ---------------- Chet Ensign Chief Technical Community Steward OASIS: Advancing open source & open standards for the information society http://www.oasis-open.org Mobile: +1 201-341-1393 -- /chet ---------------- Chet Ensign Chief Technical Community Steward OASIS: Advancing open source & open standards for the information society http://www.oasis-open.org Mobile: +1 201-341-1393 --------------------------------------------------------------------- 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://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php

Maybe I wasn't clear. The proposal was not about oasis-open.org . It was just the GitHub organization. On Fri, Nov 1, 2019 at 4:44 PM Tim Hudson < tjh@cryptsoft.com > wrote: And with all due respect, Jason you have completely totally missed the point that the organisation's DNS name is and remains oasis-open.org . That is the beginning and end of the argument. It also happens to be the actual organisation name if you want to check those details too. The organisation is not "oasis" and never has been. We may use that as shorthand in various ways - but "OASIS OPEN" is the organisation's legal name - also noted in the Bylaws. That also by itself should be the beginning and end of the argument too. If oasis-open-projects.org is considered confusing compared to oasis-open.org (which is the logical conclusion from your claim of major confusion) then it should have been completely named differently - and - as it is the newer name then it is the one that should be changed. This has nothing to do with GitHub itself - the organisations within GitHub should simply match the organisation DNS usage (as they normally do). You are trying to fix an issue in the wrong place - if the issue is truely one that is causing significant confusion then the oasis-open-projects organisation needs to the changed. That same "confusion" is inherent in the domain names - and the "open" in oasis-open was never about open source so attempting to redefine an existing established usage isn't sensible. Tim. On Fri, 1 Nov. 2019, 8:43 pm Jason Keirstead, < Jason.Keirstead@ca.ibm.com > wrote: 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 www.ibm.com/security "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 ----- From: Chet Ensign < chet.ensign@oasis-open.org > Sent by: < cti@lists.oasis-open.org > To: 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: [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, /chet On Thu, Oct 31, 2019 at 5:46 PM Chet Ensign < chet.ensign@oasis-open.org > 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. -- /chet ---------------- Chet Ensign Chief Technical Community Steward OASIS: Advancing open source & open standards for the information society http://www.oasis-open.org Mobile: +1 201-341-1393 -- /chet ---------------- Chet Ensign Chief Technical Community Steward OASIS: Advancing open source & open standards for the information society http://www.oasis-open.org Mobile: +1 201-341-1393 --------------------------------------------------------------------- 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://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php -- /chet ---------------- Chet Ensign Chief Technical Community Steward OASIS: Advancing open source & open standards for the information society http://www.oasis-open.org Mobile: +1 201-341-1393

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, /chet On Thu, Oct 31, 2019 at 5:46 PM Chet Ensign < chet.ensign@oasis-open.org > 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. -- /chet ---------------- Chet Ensign Chief Technical Community Steward OASIS: Advancing open source & open standards for the information society http://www.oasis-open.org Mobile: +1 201-341-1393 -- /chet ---------------- Chet Ensign Chief Technical Community Steward OASIS: Advancing open source & open standards for the information society http://www.oasis-open.org Mobile: +1 201-341-1393

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, /chet On Thu, Oct 31, 2019 at 5:46 PM Chet Ensign < chet.ensign@oasis-open.org > 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. -- /chet ---------------- Chet Ensign Chief Technical Community Steward OASIS: Advancing open source & open standards for the information society http://www.oasis-open.org Mobile: +1 201-341-1393 -- /chet ---------------- Chet Ensign Chief Technical Community Steward OASIS: Advancing open source & open standards for the information society http://www.oasis-open.org Mobile: +1 201-341-1393