milagro-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Brian Spector <>
Subject Re: Project status - time to retire?
Date Wed, 07 Nov 2018 21:02:01 GMT
Hello Giorgio,

I may have prematurely given you access before you had been voted on to get access to the
repo, I had assumed you had.

I need to take you off the committer repo until the vote is approved, which I will do now.
I will send another email requesting that you be given status as a committer.

This shouldn't be a big deal as you already have the ICLA on file with Apache.

Thanks for your patience.


On Nov 07, 2018, at 07:59 PM, Giorgio Zoppi <> wrote:

i have the ICLA signed and access to the Apache Milagro code as committer.
The first objective is to port to Apache the crypto library (AMLC) that it
is present in github. Just C library
without wrappers. After the release we can think to the Java wrapper (as
Apache is mainly a java shop), and than the python one.
Hey guys at miracl, do you have already a release tagged there? If yes, can
you provide me a GIT tag (ie. MILAGRO_0_9_0_ALPHA) from starting point,
The idea for the tag, it is a tag for which you are sure that the codebase
is stable to pass directly to the tests. Do you have a gtest suite? I see
just vector tests overthere.
So after you provide me a tag as starting point, I can pull push and we
freeze the codebase for testing.
Brian, Go, any other priorities? Justin for the moment we will release asap
the AMCL library. How can we handle the legalize? As soon we release the
community will grow.
Justin, Do we have any other actions to do? How about legalize? How much
can we stay as incubator?
Go can you commit part of your team or yourself for testing vectors and
especially EC part?

Best Regards,

Best Regards,


El vie., 12 oct. 2018 a las 15:34, Giorgio Zoppi (<>)

i signed the ICLA may years for Tuscany. How can i help to get rid of the
deadlock? Can i port the currenct miracle repository to Apache?
Best Regards,

El sáb., 22 sept. 2018 a las 0:54, Justin Mclean (<>) escribió:


> 4.

sorry try instead.


  • Unnamed multipart/alternative (inline, None, 0 bytes)
    • Unnamed multipart/related (inline, None, 0 bytes)
View raw message