All, We again request to discuss renewing the roadmap and to start the official repository to share the codes we have worked for years. Kelean, what do you think is blocking this obvious task?
If this project needs help in management, we are willing to participate. Regards, Go Yamamto -----Original Message----- From: Go Yamamoto [mailto:yamamoto...@lab.ntt.co.jp] Sent: Friday, February 09, 2018 1:24 PM To: 'dev@milagro.incubator.apache.org' <dev@milagro.incubator.apache.org> Subject: RE: [DISCUSS] Retire Milagro Simeon, please tell us whatever you need. I think it is obvious that the leadership team is responsible to present a roadmap. I will be always willing to participate or to help. Go -----Original Message----- From: Giorgio Zoppi [mailto:giorgio.zo...@gmail.com] Sent: Thursday, February 08, 2018 8:01 PM To: dev@milagro.incubator.apache.org Subject: Re: [DISCUSS] Retire Milagro If there is a clear roadmap. You can decide to assign some tickets to me and i will help. 2018-02-07 10:13 GMT+01:00 Simeon Aladjem <simeon.alad...@miracl.com>: > Hello, > > Sorry for being out of pocket for a while and not being able to > participate in the discussion. > > Re the repositories reorganization - it hasn't been really clear how > this needs to be done from a procedural stand point. > None of the contributors have the permissions to manipulate the > project repositories, and AFAIK, only the project mentors can do that, > but what needs to be done in order for this to happen, hasn't been clear. > This was one of our pain points along the way. > > Re the roadmap - as I already mentioned, MIRACL didn't have resources > to lead the project, but the question is - in a community like this, > who is responsible to craft a roadmap? > The discussed direction is to focus the project on the crypto library, > with which MIRACL and NTT agree, and I guess if/when NTT take the > leading role on the project, they can propose a roadmap. > > We also have a more developed version of the crypto, with full > unit-test coverage, which we can merge to the project when we > figure-out the repositories issue. > > Kind Regards, > Simeon Aladjem > > On 5/2/18, 6:49, "Go Yamamoto" <yamamoto...@lab.ntt.co.jp> wrote: > > We have been talking with Simeon and Kealan about the roadmap. > We think it will make sense if we release the crypto library > first, and then the authentication server/clients second. What do we > need to authorize the plan? > > So far the code in the library looks mature and we have found no > problems in actual use in our engineering activities. > It could be better to work for test codes more before the crypto > library released since the current code does not seem to cover > sub-normal cases necessarily. > It does not mean I think the improvements on test codes are > required for the first release, they will at least help further > development activities. > > BTW, our repository contains a lot of possible contributions on > test codes. > I believe the code will help users and developers if they are merged. > > Regards, > Go Yamamoto > > -----Original Message----- > From: Giorgio Zoppi [mailto:giorgio.zo...@gmail.com] > Sent: Wednesday, January 31, 2018 6:29 AM > To: dev@milagro.incubator.apache.org > Subject: Re: [DISCUSS] Retire Milagro > > BTW, > do you have a roadmap? Do you want to support hardware as well? IS > there a todo list of things? When do you plan next release? > > 2018-01-30 22:26 GMT+01:00 Giorgio Zoppi <giorgio.zo...@gmail.com>: > > > Hello everybody, > > is there any way to save just the crypto library inside Apache? The > > server doenst make sense, there is no valuable code. > > The crypto library including mpin protocol can be used from other > > projects. Currently there is no community. > > > > > > 2018-01-30 22:12 GMT+01:00 John D. Ament <johndam...@apache.org>: > > > >> Simeon, > >> > >> In order for that to happen, someone would need to make sure Go > >> Yamamoto has write access to the repositories. I'm not sure > that has happened. > >> > >> John > >> > >> On 2018/01/30 14:49:07, Simeon Aladjem > <simeon.alad...@miracl.com> > wrote: > >> > Hi all, > >> > > >> > As a part of MIRACL, I feel that I have to provide our perspective > >> > on > >> the project. > >> > > >> > First of all, we did disengage with the idea to move the Milagro > >> > Crypto > >> code elsewhere. > >> > All the code under the Milagro project refers to the crypto > >> > repository > >> that is under Apache, so https://github.com/milagro-crypto doesn't > >> directly affect the project at the current. > >> > > >> > It does contain a more developed version of the original Milagro > >> > Crypto > >> code, which will eventually find its way to the project, > >> > but in order for this to happen we will need some repository > >> reorganization, which was communicated in the past, to the best > of my > >> memory. > >> > > >> > MIRACL is committed to continue and contribute to the Milagro > >> > Crypto > >> code, but we were unable to play the leading role in the project for > >> the last year or so. > >> > For this reason, it was proposed that NTT and Go Yamamoto > will take > >> > on > >> the leadership over the project going forward. > >> > > >> > I hope that it clarifies some points, and will help on getting the > >> project out of the mud and to start moving it forward. > >> > > >> > Kind Regards, > >> > Simeon Aladjem > >> > > >> > On 30/1/18, 15:54, "John D.Ament" <johndam...@apache.org> wrote: > >> > > >> > Hi Yamamoto > >> > > >> > I believe you're hitting the problem right on the head. The > >> project was originally founded with a donation from MIRACL. You can > >> see that code changes continually go to > >> https://github.com/milagro-crypto but no changes to Apache > hosted git repositories. > >> > > >> > I understand your frustration, but the implications I am > seeing > >> > are > >> that MIRACL has no interest in working on code within the podling. > >> > > >> > John > >> > > >> > On 2018/01/30 05:17:42, "Go Yamamoto" > >> > <yamamoto...@lab.ntt.co.jp> > >> wrote: > >> > > Hi John, > >> > > > >> > > NTT is currently using Milagro as a crypto library. > >> > Retirement > >> of Milagro causes impact on our business, so I would like to ask for > >> discussion what can we do for supporting Milagro. > >> > > > >> > > As I mentioned last time, we have code that is ready to > commit. > >> > > Our repositories have been updated since then. > >> > > However, the way to commit the code to Apache repository is > >> > not > >> clear for us. > >> > > As far as I recognize it is because the code from MIRACL is > >> > not > >> placed on the Apache repository. > >> > > Since MIRACL's code also have been updated continuously, it > >> > seems > >> this management problem blocks starting the project for years. > >> > > > >> > > I think we can discuss whether NTT team can take over the > >> management of the Apache repository to resolve the problem. > >> > > > >> > > Kind regards, > >> > > Go Yamamoto > >> > > > >> > > > >> > > > >> > > -----Original Message----- > >> > > From: John D. Ament [mailto:johndam...@apache.org] > >> > > Sent: Tuesday, January 30, 2018 1:06 PM > >> > > To: d...@milagro.apache.org > >> > > Subject: [DISCUSS] Retire Milagro > >> > > > >> > > Hi All, > >> > > > >> > > Mid last year [1] I reached out to the project about > retirement. > >> At that point, some community members stepped up to help out > the project. > >> However, I don't believe its been enough. > >> > > > >> > > Since that has occurred: > >> > > - Milagro has missed reporting periods. This has included > >> multiple requests for a report by me. > >> > > - Requests for a special report clarifying the move of > source > >> code away from the ASF managed repos on github have been unanswered. > >> > > - On list activity has dropped to nearly nothing. > >> > > - Very little commit activity; most of your repositories > have > >> > not > >> been updated since we last spoke. > >> > > > >> > > At this point, I believe its clear that Milagro should > retire. > >> > > > >> > > [1]: > >> > > https://lists.apache.org/thread.html/ > e6a5db6fab6c61156c2101a > >> ae003ed576ddb0e77f3bb2c037b405131@%3Cdev.milagro.apache.org%3E > >> > > > >> > > > >> > > > >> > > >> > > >> > > > > > > > >
