Request an OASIS TC Open Repository project be created

["TC Administrator" <chet.ensign@oasis-open.org>]

Submitted on Monday, April 20, 2020 - 17:40
Submitted by user:
Submitted values are:

Your name: David Lemire
TC name: Open Command and Control (OpenC2)
TC email address: openc2@lists.oasis-open.org
GitHub repository name: lycan-elixir
Purpose statement:
Statement of Purpose for this OASIS TC Open Repository (openc2-lycan-elixir)
as
proposed and approved [bis] by the TC:

The purpose of this OASIS TC Open repository is to develop a collection of
applications and libraries, coded in Elixir, a language that runs on the BEAM
virtual machine, for the purpose of implementing OpenC2. Repository assets
will
demonstrate implementations of OpenC2 that run on BEAM to facilitate other
other
development efforts. [BEAM stands for Bogdan/BjÃrn's Erlang Abstract Machine
-rcc]

This openc2-lycan-elixir repository is managed as an open source effort in
accordance with the MIT open source license, initially under the leadership
and
Maintainer role of Duncan Sparrell (sFractal Consulting).

The OASIS OpenC2 Technical Committee was chartered to address matters as they
pertain to command and control of cyber defense technologies, and to maintain
a
library of prototype implementations, sample commands, polyglot
implementation
and other artifacts as they pertain to the command and control of cyber
defense
technologies. TC consensus was found to develop and maintain this library as
a
TC Open Repository. The OpenC2 TC has already initiated creation of
transformation (aka lycan) libraries for python, java, and other BEAM
languages.
Description: OASIS TC Open Repository: Developing a collection of
applications
and libraries, coded in Elixir, which runs on the BEAM virtual machine, for
the
purpose of implementing OpenC2
Open source license: MIT License
Maintainer(s): Duncan Sparrell, duncan@sfractal.com, sparrell, sFractal
Consulting
Approval link:
https://www.oasis-open.org/committees/document.php?document_id=67025&wg_abbrev=openc2
Notes: Approval motion didn't include a formal "purpose" statement. However,
since the underlying goal was to split content from the existing lycan-beam
repository to better fit with the way BEAM languages, specifically Elixir,
handle dependencies, we have re-used the lycan-beam purpose statement with
appropriate edits to focus on Elixir.


The results of this submission may be viewed at:
http://tools.oasis-open.org/issues/browse/TCADMIN