RE: [openc2-lang] Language Spec open issues

From GITHUB

So, our first change, shipped on July 17th, updates GitHub.com to redirect links that contain a deleted branch name to the corresponding link in the repository's default branch.

This change supports projects that have already moved. If you havenât moved yet, we recommend not moving right now, and waiting until later this year. Weâre investing in tools to make the renaming the default branch of an existing repository a seamless experience for both maintainers and contributors.

From: openc2-lang@lists.oasis-open.org <openc2-lang@lists.oasis-open.org> On Behalf Of duncan sfractal.com
Sent: Monday, August 17, 2020 4:42 PM
To: David Kemp <dk190a@gmail.com>; openc2-lang@lists.oasis-open.org
Cc: Lemire, Dave (HII-TSD) <david.lemire@hii-tsd.com>
Subject: Re: [openc2-lang] Language Spec open issues

Wrt getting legacy LS GitHub in sync with our new norms â this is a volunteer organization and relies on volunteers to do the work. Anybody â including yourself â can do the work. I donât think anyone can task another OASIS member to do the work. It is the editorâs job and Iâll confess It's not highest on my list(I already did it on some of the other artifacts). Iâm being a pain in the hope someone else would volunteer to be a co-editor and volunteer to do it.

Wrt JADN â please propose the wording change youâd like to the meeting notes.

Wrt JADN - Are the changes you mention to the working branch being done by PRâs being accepted after being agreed to by the Language SC? I donât recall any of these PRâs being discussed but maybe I missed it. If we havenât been reviewing, we might want to start following the process. The editor can make editorial changes willy nilly but even those should be pointed out to LSC, and substantive changes should be reviewed.

I donât mean to be snippy but my basement flooded yet again, while we were away and after we thought weâd fixed everything, so I had to drive back to VA and spend last several days talking to expensive contractors.

Duncan Sparrell

sFractal Consulting LLC

iPhone, iTypo, iApologize

I welcome VSRE emails. Learn more at http://vsre.info/

From: openc2-lang <openc2-lang@lists.oasis-open.org> on behalf of David Kemp <dk190a@gmail.com>
Date: Monday, August 17, 2020 at 4:24 PM
To: openc2-lang <openc2-lang@lists.oasis-open.org>
Cc: David Kemp <dk190a@gmail.com>, "Lemire, Dave (HII-TSD)" <david.lemire@hii-tsd.com>
Subject: [openc2-lang] Language Spec open issues

Hello Co-chairs,

We made good progress discussing open issues at the 3 August meeting https://meet.lucidmeetings.com/meeting/258343.

Under 3.2.2 Pull Requests, there are a number left over from before the release of CS01, with the question of whether they are OBE. In order to close them out I need to replace them with PRs against the current CS02 spec. May I request that you task the TC Secretary to update the LS repo to the current CS02 release.

Under 3.3 there's a question in the agenda about the JADN repo not being touched in 2 years. That refers to the master branch dating to creation of the repo. As noted at the meeting the working branch https://github.com/oasis-tcs/openc2-jadn/tree/working is regularly updated, so the meeting minutes should reflect that it is under active development and review and feedback is welcome.

Regards,

Dave

openc2-lang message