Re: [openc2-lang] Github for Glossary v2

> ... since Oasis doesn't use private githubs.

Many thanks, Duncan.

I think your suggestion for a GitHub repo to support Glossary development sounds great -- though I am not a key stakeholder.  The Staff POV is that TCs should be able to use as many GitHub repositories as they want/need, for whatever purposes, without requiring a lot of debate: live and let live.  Using separate "single-purpose" (project-related and topic-related) repos means that the issues, pull requests, labels, conversations, and comments (etc) are all related to the designated topic/project.  Other SSOs'SDOs have thus concluded that separate and distinct repos are generally a good way to build community, focus attention, and reduce notification noise... etc

Thanks also for clarifying that OASIS uses GitHub public repositories only for both offerings: (a) GitHub Repositories for TC Members' Chartered work, and (b) OASIS Open Repositories.

- Robin

[1] Subject: Using public GitHub repositories for dedicated TC work and for open source development

* Comparison: OASIS Open Repositories versus GitHub Repositories for TC Members' Chartered work

https://lists.oasis-open.org/archives/openc2/201706/msg00038.html

- https://github.com/oasis-tcs/

- https://github.com/oasis-open/

On Tue, Aug 8, 2017 at 10:59 AM,  <> wrote:

I'm using the semantically pedantic one and I realize I may cause some confusion so I'm resending this with hopefully better wording since Oasis doesn't use private githubs.

As editor
 of the glossary I was thinking of trying an experiment. Unless anyone 
objects I was going to convert the glossary to markup and use the OASIS TC github to keep track of changes and versioning.

Why am I doing this? Several reasons. One being just to get familiar with the TC OASIS github since I don't think we have anything else in the OpenC2 TC using it. We have the open source software going into the open OASIS githubs and I thought it would be worth knowing how to use the TC OASIS github as well. Another reason is I do think git is better at version control than google docs. Using github would provide a history of the changes and the comment field on the committs allow reasons and who approved to be included. I also think it will be easy for people to suggest changes (fork, pull, approve) with clear history of who proposed and who approved.

Using the glossary (ie not our highest priority effort) seemed like a good document to experiment with (plus I'm the editor so I'd have to do the work).

If there is no objection, I'd like the Language SC (owners of the Glossary) to agree and to propose this to the full TC at the August meeting. I believe it will take a TC vote to creat the Glossary github site.

Comments? Agree? Disagree?

Duncan Sparrell

sFractal Consulting LLC

iPhone, iTypo, iApologize

---------------------------------------------------------------------
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 

-- 

Robin Cover
OASIS, Director of Information Services
Editor, Cover Pages and XML Daily Newslink
Email: 
Staff bio: http://www.oasis-open.org/people/staff/robin-cover
Cover Pages: http://xml.coverpages.org/
Newsletter: http://xml.coverpages.org/newsletterArchive.html
Tel: +1 972-296-1783