Re: Seeking a few word about your repos

Duncan:

For the record, I think the googlesheet should not be a googlesheet but that this info goes sowmewhere in github.

Another option would be a table on the IC-SC wiki page. If we do that I'd focus the content on the OASIS open repos and drop the historical stuff. That would also simplify editing rights. Really, I created the GSheet as a tool for myself to help wrap my head around what the TC had for repos. It doesn't need to be a long term tool, but I figured it made sense to encourage maintainers to help me keep it relevant.

As for maintaining it in Github, I guess that's another approach but to me it feels a little bit "hammer / nail". Are there advantages to that approach that I'm overlooking?

Dave

David P. Lemire, CISSP
  OpenC2 Technical Committee Executive Secretary
  OpenC2 Implementation Considerations SC Co-chair
  Contractor support to NSA
Email:  
Office: 301-575-5190 / Mobile: 240-938-9350

 

Duncan Sparrell

sFractal Consulting LLC

iPhone, iTypo, iApologize

-------- Original Message --------

Subject: RE: [openc2-imple] RE: [Non-DoD Source] RE: Seeking a few word

about your repos

From: "Brule, Joseph M" <>

Date: Thu, April 05, 2018 12:33 pm

To: 'Robin Cover' <>

Cc: "" <>, dave.lemire

<>, "Kemp, David P" <>,

Joshua_Brulé <>, Adam Bradbury <>,

Danny Martinez <>, "STAIR, MICHAEL A"

<>, "ESSING, BLAKE" <>,

"" <>

       
 
Robin, 
 
 
 
This is a case where I engaged mouth before putting my brain in gear.  DISREGARD, everything is fine on your end, it was a googlesheet….
 
 
 
From: Robin Cover <> 
 Sent: Thursday, April 5, 2018 12:27 PM
 To: Brule, Joseph M <>
 Cc: ; dave.lemire <>; Kemp, David P <>; Joshua_Brulé <>; Adam Bradbury <>; Danny Martinez <>; STAIR, MICHAEL A <>; ESSING, BLAKE <>; 
 Subject: Re: [openc2-imple] RE: [Non-DoD Source] RE: Seeking a few word about your repos
 
 
 
 
 
 
 
 
On Thu, Apr 5, 2018 at 11:08 AM, Brule, Joseph M <> wrote:
  
 
 
ALCON = ‘All Concerned’.  
 
 
 
I will shoot off an email to Robin, I am stunned that the maintainers of the repos do not have full access
 
 
  
 
 
 
 
 
OK, standing by... when I read "edit rights on repo sheet", I thought Duncan means edit rights to a Google Spreadsheet document, which (?) I don't manage, in this case
 
 
 
 
 
 
 
Additionally (for Dave, I guess, initially, as he is tracking and supporting the GitHub repositories): would there be opportunity to get some of the updated repo information you are collecting into the GitHub repository README files?  I recently send Danny a message about his posting to the SC [1]
 
 
 
 
 
 
 
Best wishes, all
 
 
 
 
 
 
 
- Robin
 
 
 
 
 
 
 
 
 
 
 
[1]  Danny, what would you think about adding your nine-item bullet list ( https://lists.oasis-open.org/archives/openc2-imple/201803/msg00017.html ) to the repository README in the section designed for expansions/clarifications? I think the list provide nice commentary that readers will appreciate
 
 
 
I could make the addition if you want to authorize it as purely clerical.
 
Thanks!
  
 Robin
 
README Section::  https://github.com/oasis-open/openc2-pub-sub-on-bsd#additions-to-statement-of-purpose: "Repository Maintainers may include here any clarifications,,"
 
Was written in C and developed on HardenedBSD
 It utilizes a sub//pub (zeroMQ) model for its communication fabric
 The project has 3 subparts, broadcast, edge, and orchestrator
 The broadcast is used to create OpenC2 messages
 The orchestrator is used to send the OpenC2 messages to the appropriate places
 The edge is used to receive and act upon OpenC2 messages
 The edge utilizes plugins to add functionality, current two exist allow, and deny
 The allow and deny plugins are structured to work with packet filter firewall
 The intent is to create edge plugins for any functionality required by the actuator
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
  
 
 
 
 
 
 
From:  <> 
 Sent: Thursday, April 5, 2018 11:15 AM
 To: dave.lemire <>; Kemp, David P <>; Joshua_Brulé <>; Adam Bradbury <>; Danny Martinez <>; STAIR, MICHAEL A <>; ESSING, BLAKE <>
 Cc: Brule, Joseph M <>; 
 Subject: [Non-DoD Source] RE: Seeking a few word about your repos
 
 
 
 
 
 
Dumb question: What is ALCON?
 
 
 
 
 
 
 
Yes I would like edit rights on repo sheet.
 
 
 
 
 
 
 
On Ocas sheet (I couldn't make change myself since no permission), please add another top level bullet at end:
 
 
 
- status
 
 
 
    + build to forum rc4 and had minor updates but is currently out of date
 
 
 
    + intent is to update to CSD03 now that CSD03 has complete thread
 
 
 
 
 
 
 
Duncan Sparrell
 
 
 
sFractal Consulting LLC
 
 
 
iPhone, iTypo, iApologize
 
 
 
 
 
  
 
-------- Original Message --------
 Subject: Re: Seeking a few word about your repos
 From: Dave Lemire <>
 Date: Tue, April 03, 2018 10:32 am
 To: Duncan <>, "Kemp, David P"
 <>, Joshua_Brulé <>, Adam
 Bradbury <>, Danny Martinez
 <>, "STAIR, MICHAEL A" <>,
 "ESSING, BLAKE" <>
 Cc: "Brule, Joseph M" <>,
 
 
 
ALCON:  I've drafted an informational briefing about our open repos for tomorrow's working call. You can find the GSlides file in the GDrive implementation folder:
 
 
https://docs.google.com/presentation/d/19zCwK2pXq0fJY3-xOos7L0YwkVcuMJNPsLc8Jsc9kgg/edit#slide=id.p4
 
 
 
 
 
 
 
Please take a few minutes to review / correct, especially if I've mis-characterized your repo.  :-)
 
 
 
 
 
 
 
Also, if you're a repo maintainer / SME, I'll be happy to give you editing rights on the repo status GSheet referenced in the briefing:
 
 
 
https://docs.google.com/spreadsheets/d/1iC7Hm3v_n3VrHjqixqRwVl11Bh2SYgwkUkE-3HaIhsE/edit#gid=0
 
 
 
 
 
 
 
Just let me know.
 
 
 
 
 
 
 
 
 
 
 
Note: I've left off the openc2-iacd repo, as JoeB advises it will never be populated. I need to send out a CFO to the TC for deleting it.
 
 
 
 
 
 
 
 
Dave
 
 
 
 
 
 
David P. Lemire, CISSP
   OpenC2 Technical Committee Executive Secretary
   OpenC2 Implementation Considerations SC Co-chair
   Contractor support to NSA
 Email:  
 Office: 301-575-5190 / Mobile: 240-938-9350
 
 
 
 
 
 
 
On Tue, Mar 20, 2018 at 9:09 AM, Dave Lemire <> wrote:
  
 
Folks:  
 
 
 
 
 
 
Each of you have your names associated with one or more of our open repos for OpenC2. I would like to "share the wealth" by giving the TC a presentation about our open source repos, and what they contain.  I'd very much appreciate it if each of you could give me a few bullets about the repos you're associated with and what's interesting / special / unique about them, and why other implementer of OpenC2 should seek them out.
 
 
 
 
 
 
For reference (or if you need a reminder why you got this email), I've got a repo status tracking list (Google Sheet) on the oasis-openc2 Google Drive at  https://docs.google.com/spreadsheets/d/1iC7Hm3v_n3VrHjqixqRwVl11Bh2SYgwkUkE-3HaIhsE/edit#gid=0
 
 
 
 
 
 
 
Thanks for your help.
 
 
 
 
 
 
 
 
Dave
 
 
 
 
 
 
David P. Lemire, CISSP
   OpenC2 Technical Committee Executive Secretary
   OpenC2 Implementation Considerations SC Co-chair
   Contractor support to NSA
 Email:  
 Office: 301-575-5190 / Mobile: 240-938-9350
 
 
 
  
 
 
 
 
  
 
  
 

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