Board Report - MAY 2016

[Tomasz Matecki <to...@miracl.com>]

===============

Milagro



Distributed Cryptography;

M-Pin protocol for Identity and Trust



Milagro has been incubating since 2015-12-21.



Three most important issues to address in the move towards graduation:

1.    Release the 1.0 version with new tools and features included (one of the key features is stand alone DTA instance)

2.    Integration with other ASF projects

3.    Engage the Apache community

4.    First public independent DTA



Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of?

n/a



How has the community developed since the last report?

After successful launch during the ApacheCon North America in Vancouver, Milagro get the enthusiast – our first compiler Nicola Hedman, who did his first deployment during Day 3 of the conference. Since then Milagro community is growing slowly. Milagro is looking forward to get a release in Q3 2016. Project is getting popular while more and more developers are concerned about the security.
The Chief Cryptographer for ntti3 labs, Go Yamamoto, is speaking at Apache Con Tokyo in a few weeks about Apache Milagro with the intent of generating participation in the project.


How has the project developed since the last report?

Miracl repos was updated:

Milagro TLS:

	-       updated doxyfile to output code API,

 Milagro Crypto libraries was refactored:


	-       New project repo that contains only C source code, and the language wrapper (Python), all unnecessary code has been removed.

	-       The structure of directory organization was changed to reflect a common standard model.

	-       Documentation was updated and extended – both the README and the source code documentation.

	-       The building files (cmake) were adapted to support the VERSION file, and Windows cross compilation in Linux

	-       Script was added that builds and test this several versions of this library in a Docker container

	-       Travis CI configuration file was added – so every pull request or code change is automatically build and test in Travis CI, including the Windows versions

	-       The testing (through CI and Docker) has been extended to cover both Linux and Windows in both 32bit and 64bit versions.

	-       Automatic test source coverage reports

	-       Fix dozens of compilations warnings

	-       Unused variables were removed from the code to to fix warnings

	-       The source code was formatted – using the standard format

	-       Fixed files permissions





Date of last release:

N/A



When were the last committers or PMC members elected?

Initial Committers only.







Signed-off-by:







  [ ](milagro) Sterling Hughes



  [ ](milagro) Jan Willem Janssen



  [ ](milagro) Nick Kew






Shepherd/Mentor notes:











Tomasz Matecki
Technical Product Manager

T: +44 (0) 20 3389 8190
M: +44 (0) 7947 725 062

MIRACL
81 Rivington Street
London UK, EC2A 3AY
Registered in England and Wales 7017635

https://www.miracl.com

This email message is for the sole use of the intended recipient(s)
and may contain confidential and privileged information which is
protected from disclosure.

 Any unauthorized review, use, disclosure or distribution by any means
is prohibited. If you are not the intended recipient, please contact
the sender by reply email and destroy all copies of the original
message.

Re: Board Report - MAY 2016

[Nick Kew <ni...@apache.org>]

On Wed, 6 Jul 2016 17:17:55 +0100
Tomasz Matecki <to...@miracl.com> wrote:

> ===============

Thanks Tom.  I already filled in the report, but I can use
some of this to update what I wrote.

> Three most important issues to address in the move towards graduation:
> 
> 1.    Release the 1.0 version with new tools and features included
> (one of the key features is stand alone DTA instance)

Release is a target, though we don't need any detail.

> 2.    Integration with other ASF projects
> 
> 3.    Engage the Apache community
> 
> 4.    First public independent DTA

2 and 4 are good project goals, but I don't think they're
really relevant to graduation.

On the other hand, we do need to sort out apparent confusion
about Milagro work taking place outside apache, and not visible
at apache.


> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> aware of?

I've mentioned the semi-detached docs site milagro.io.
I don't think it's a problem provided we treat it as a
community (as opposed to corporate) resource, but best
to be on-record.

> How has the community developed since the last report?

Too much detail, but I can use some of that to improve what
I've written.  Not sure what Tokyo conference you mean?

> How has the project developed since the last report?
> 
> Miracl repos was updated:

Repos dropped in to apache, but work appears to
have taken place outside it.  It seems we need to sort
out the question of what belongs in Milagro vs other
work Miracl is doing.

Are there now Miracl public repos at github that are
(intentionally) separate from Milagro?

(And again, too much detail).

-- 
Nick Kew