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

 


Help: OASIS Mailing Lists Help | MarkMail Help

openc2 message

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


Subject: Re: [openc2] Groups - Resolution to create openc2-lycan-beam, an open source repository for erlang/elixir uploaded


My bad. I read the email, but didn't follow the link to the document. Apologies.

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

On Thu, Mar 8, 2018 at 1:17 PM, <duncan@sfractal.com> wrote:
Did I upload the wrong document? Doesn't it say
"The initial maintainer of the openc2-lycan-beam repository shall be
Duncan Sparrell(sFractal Consulting)."
as the last sentence of the resolution?

Note the words in the email are just the box you fill out when you
submit a document. The document
(https://www.oasis-open.org/apps/org/workgroup/openc2/download.php/62672/a%20resolution%20to%20create%20an%20open%20repository%20for%20lycan-beam.pdf)
is the resolution I would like considered at the next TC meeting. I was
putting it on the website and publishing it now so it was available
prior to the meeting. My hope is we could just do a call for objections
at the TC meeting and not have to do an eballot and save a few weeks.


Duncan Sparrell
sFractal Consulting LLC
iPhone, iTypo, iApologize



-------- Original Message --------
Subject: Re: [openc2] Groups - Resolution to create openc2-lycan-beam,
an open source repository for erlang/elixir uploaded
From: Dave Lemire <dave.lemire@g2-inc.com>
Date: Thu, March 08, 2018 12:45 pm
To: Robin Cover <robin@oasis-open.org>
Cc: Duncan Sparrell <duncan@sfractal.com>, OASIS OpenC2 TC Discussion
List <openc2@lists.oasis-open.org>

Duncan: the language we used in August establishing the initial set of
open source repos was a little more structured (which I don't care so
much about) and identified an individual as the "initial maintainer"
(which I think we can't neglect).  Are you putting yourself forward as
the initial maintainer of the proposed lycan-beam repo?

If you want to find that initial language, here's a link to the email in
the TC archive:
https://www.oasis-open.org/apps/org/workgroup/openc2/email/archives/201708/msg00013.html


Dave


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



On Thu, Mar 8, 2018 at 11:20 AM, Robin Cover <robin@oasis-open.org>
wrote:
Duncan (and TC)

I have forwarded a copy of the repo proposal to Staff to see if we can
expand the list of open source licenses supporting OASIS TC Open
Repositoriees


The MIT licence is a great (permissive) license -- in my view -- and is
a clear favorite for many open source projects hosted as GitHub public
repositories


https://opensource.guide/legal/#which-open-source-license-is-appropriate-for-my-project

https://choosealicense.com/licenses/mit/



In 2015 (update?) MIT was the top choice
https://blog.github.com/2015-03-09-open-source-license-usage-on-github-com/



In any case: OASIS has a standing agreement to " periodically review
other widely-used free and open source licenses for inclusion in the
list [of supported licenses
for TC Open Repositories

 The TC creating a TC Open Repository will select its Applicable License
from among the following list: BSD-3-Clause License (which shall apply
if the TC makes no license selection in its approval action); Apache
License v 2.0; CC-BY 2.0; CC-BY 4.0; Eclipse Public License v 1.0.
(OASIS periodically will review other widely-used free and open source
licenses for inclusion in this list by amending these procedures.)



See:
https://www.oasis-open.org/policies-guidelines/open-repositories#licensingRules


Current licenses:


https://www.oasis-open.org/resources/open-repositories/licenses






I'll let you know.


- Robin

On Thu, Mar 8, 2018 at 9:38 AM, Duncan Sparrell <duncan@sfractal.com>
wrote:
 Submitter's message
 I propose an open source repo be established for the erlang/elixir
languages similar to the recently passed repo's for java and python. If
no one objects, I would propose this repo be established by passing the
attached motion at the next TC meeting (ie we would not need an
e-ballot).
 -- Mr. Duncan Sparrell    Document Name: Resolution to create
openc2-lycan-beam, an open source repository for erlang/elixir
  Description
 The openc2-lycan-beam repository contains a collection of applications
and
 libraries, coded in languages that run on the BEAM virtual machine (eg
 erlang, elixir), for the purposes of implementing OpenC2.
 Download Latest Revision
 Public Download Link
  Submitter: Mr. Duncan Sparrell
 Group: OASIS Open Command and Control (OpenC2) TC
 Folder: Documents
 Date submitted: 2018-03-08 07:38:36









--
Robin Cover
OASIS, Director of Information Services
Editor, Cover Pages and XML Daily Newslink
Email: robin@oasis-open.org
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



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