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


Help: OASIS Mailing Lists Help | MarkMail Help

openc2-lang message

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

Subject: Re: [openc2-lang] Language Spec open issues

Wrt not stepping on editorâs toes:

I am now the only editor again as both Jason and Drew have left, and Iâd happily welcome the help.


Wrt asking Dave â

as long as you are asking him as his customer, not because heâs the secretary, that would be great.


Wrt âdeleting branch issueâ â

we can leave âmasterâ for now. I think Daveâs issue is, correctly, that our current copy is not up to date with what we approved. We can do that wo changing names or deleting.


Wrt Pull Requests â

ideally they should be reviewed by someone but more importantly normative changes shouldnât be merged until approved at an LSC meeting. Editorial and non-substantive changes you can approve but then report at meeting what happened since last meeting. Approving PRâs is highest priority at the LSC meetings and should always be first on the agenda. Eg it was 2.1/2.2 on 3-Aug mtg. Apologies if it was my fault for not noticing any open PRâs on JADN to bring up for approval.


Duncan Sparrell

sFractal Consulting LLC

iPhone, iTypo, iApologize

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



From: David Kemp <dk190a@gmail.com>
Date: Monday, August 17, 2020 at 7:22 PM
To: Toby Considine <Toby.Considine@unc.edu>
Cc: "duncan@sfractal.com" <duncan@sfractal.com>, openc2-lang <openc2-lang@lists.oasis-open.org>, "Lemire, Dave (HII-TSD)" <david.lemire@hii-tsd.com>
Subject: Re: [openc2-lang] Language Spec open issues


We can change branch names whenever GitHub has an easy process.  I just want to get CS02 into the repo so I can start updating old PRs and making new ones.


On Mon, Aug 17, 2020 at 6:13 PM Considine, Toby <Toby.Considine@unc.edu> wrote:

If you think that this new social requirement is a burning issue which makes risking broken links tolerable and you want to fix all the back-links by hand, go ahead.

I note that Github cites numerous problems and recommends waiting.


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