You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@milagro.apache.org by "John D. Ament" <jo...@apache.org> on 2018/01/30 04:05:58 UTC
[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/e6a5db6fab6c61156c2101aae003ed576ddb0e77f3bb2c037b405131@%3Cdev.milagro.apache.org%3E
Re: [DISCUSS] Retire Milagro
Posted by "John D. Ament" <jo...@apache.org>.
Hello,
And how are you planning to create those repositories?
What about the board reports that have not been received in months?
John
On 2018/02/09 16:31:11, Kealan Mccusker <ke...@miracl.com> wrote:
> Hi Giorgio
>
> It was designed for the internet of things but we are now using it in many
> settings.
> It is a very easy to understand, side channel resistant library that is
> provided in
> common dev languages.
>
> What we would like to do, as stated above, is create a number of repos for
> the
> language versions;
>
> milagro-crypto-c
> milagro-crypto-js
> milagro-crypto-java
> milagro-crypto-go
>
> Please read the pdf included which has an introduction to the library.
>
> Regards
>
> Kealan
>
>
>
>
>
> [image: MIRACL Logo]
> <http://www.miracl.com/?utm_campaign=Email%20Signature&utm_source=email&utm_content=email_miracl_logo>
> *Try MIRACL Trust® in Five Minutes*
> *Download Guide*
> <http://www.miracl.com/try-miracl-trust-in-5-minutes?utm_campaign=Email%20Signature&utm_source=email&utm_content=email_download_guide>
> | *Read FAQs*
> <http://www.miracl.com/faqs-miracl-trust?utm_campaign=Email%20Signature&utm_source=email&utm_content=email_read_faqs>
>
>
>
>
>
> On Fri, Feb 9, 2018 at 3:06 PM, Giorgio Zoppi <gi...@gmail.com>
> wrote:
>
> > Again which is the target of miracle? How does differentiate this from
> > OpenSSL or Botan for example?
> >
> >
> > 2018-02-09 5:23 GMT+01:00 Go Yamamoto <ya...@lab.ntt.co.jp>:
> >
> > > 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.zoppi@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 <si...@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" <ya...@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.zoppi@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.zoppi@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 <johndament@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
> > > > <si...@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" <jo...@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"
> > > > >> > <ya...@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:johndament@apache.org]
> > > > >> > > Sent: Tuesday, January 30, 2018 1:06 PM
> > > > >> > > To: dev@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
> > > > >> > >
> > > > >> > >
> > > > >> > >
> > > > >> >
> > > > >> >
> > > > >>
> > > > >
> > > > >
> > > >
> > > >
> > > >
> > > >
> > >
> > >
> > >
> >
>
Re: [DISCUSS] Retire Milagro
Posted by Kealan Mccusker <ke...@miracl.com>.
Hi Giorgio
It was designed for the internet of things but we are now using it in many
settings.
It is a very easy to understand, side channel resistant library that is
provided in
common dev languages.
What we would like to do, as stated above, is create a number of repos for
the
language versions;
milagro-crypto-c
milagro-crypto-js
milagro-crypto-java
milagro-crypto-go
Please read the pdf included which has an introduction to the library.
Regards
Kealan
[image: MIRACL Logo]
<http://www.miracl.com/?utm_campaign=Email%20Signature&utm_source=email&utm_content=email_miracl_logo>
*Try MIRACL Trust® in Five Minutes*
*Download Guide*
<http://www.miracl.com/try-miracl-trust-in-5-minutes?utm_campaign=Email%20Signature&utm_source=email&utm_content=email_download_guide>
| *Read FAQs*
<http://www.miracl.com/faqs-miracl-trust?utm_campaign=Email%20Signature&utm_source=email&utm_content=email_read_faqs>
On Fri, Feb 9, 2018 at 3:06 PM, Giorgio Zoppi <gi...@gmail.com>
wrote:
> Again which is the target of miracle? How does differentiate this from
> OpenSSL or Botan for example?
>
>
> 2018-02-09 5:23 GMT+01:00 Go Yamamoto <ya...@lab.ntt.co.jp>:
>
> > 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.zoppi@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 <si...@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" <ya...@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.zoppi@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.zoppi@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 <johndament@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
> > > <si...@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" <jo...@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"
> > > >> > <ya...@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:johndament@apache.org]
> > > >> > > Sent: Tuesday, January 30, 2018 1:06 PM
> > > >> > > To: dev@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
> > > >> > >
> > > >> > >
> > > >> > >
> > > >> >
> > > >> >
> > > >>
> > > >
> > > >
> > >
> > >
> > >
> > >
> >
> >
> >
>
Re: [DISCUSS] Retire Milagro
Posted by Giorgio Zoppi <gi...@gmail.com>.
Again which is the target of miracle? How does differentiate this from
OpenSSL or Botan for example?
2018-02-09 5:23 GMT+01:00 Go Yamamoto <ya...@lab.ntt.co.jp>:
> 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.zoppi@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 <si...@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" <ya...@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.zoppi@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 <gi...@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 <jo...@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
> > <si...@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" <jo...@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"
> > >> > <ya...@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:johndament@apache.org]
> > >> > > Sent: Tuesday, January 30, 2018 1:06 PM
> > >> > > To: dev@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
> > >> > >
> > >> > >
> > >> > >
> > >> >
> > >> >
> > >>
> > >
> > >
> >
> >
> >
> >
>
>
>
RE: [DISCUSS] Retire Milagro
Posted by Go Yamamoto <ya...@lab.ntt.co.jp>.
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.zoppi@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 <si...@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" <ya...@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.zoppi@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 <gi...@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 <jo...@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
> <si...@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" <jo...@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"
> >> > <ya...@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:johndament@apache.org]
> >> > > Sent: Tuesday, January 30, 2018 1:06 PM
> >> > > To: dev@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
> >> > >
> >> > >
> >> > >
> >> >
> >> >
> >>
> >
> >
>
>
>
>
Re: RE: [DISCUSS] Retire Milagro
Posted by Giorgio Zoppi <gi...@gmail.com>.
Can be used milagro with react native? I mean the autentication.
2018-03-12 10:13 GMT+01:00 Go Yamamoto <ya...@lab.ntt.co.jp>:
> Thank you for guidance. Sorry, I was somewhat confused.
>
> "We" means NTT in this context.
>
> I understand Milagro project has some difficulty in releasing code at the
> official repository.
> https://github.com/apache/incubator-milagro
>
> The reason is not clear for me, however, if a new official repository
> resolves the issue, then I think it is a good idea to install it.
>
> For that purpose NTT is willing to work in managements.
>
> Regards,
> Go Yamamoto
>
> -----Original Message-----
> From: John D. Ament [mailto:johndament@apache.org]
> Sent: Sunday, March 11, 2018 10:34 PM
> To: dev@milagro.apache.org
> Subject: Re: RE: [DISCUSS] Retire Milagro
>
>
>
> On 2018/03/08 05:20:41, "Go Yamamoto" <ya...@lab.ntt.co.jp> wrote:
> > Hi
> >
> > Who is taking care of management tasks right now?
> > We would like to request the official repository to release our code.
> > If nobody is working for the task, we will take it over.
>
> Who is "we" in this case?
> http://git.apache.org/ shows 11 repositories for Milagro.
>
> >
> > Regards,
> > Go Yamamoto
> >
> > -----Original Message-----
> > From: Nikolai Stoilov [mailto:nikolai.stoilov@miracl.com]
> > Sent: Tuesday, February 20, 2018 1:51 AM
> > To: dev@milagro.incubator.apache.org
> > Subject: Re: [DISCUSS] Retire Milagro
> >
> > Hi Go,
> >
> > Regarding management, I can show someone from your side how to fill in
> the
> monthly reports which are required for the project.
> >
> > Nikolai
> >
> > On Mon, Feb 19, 2018 at 6:24 PM Giorgio Zoppi
> > <gi...@gmail.com>
> > wrote:
> >
> > > Ok,
> > > just to be proactive, schedule some tickets when you have a plan and
> > > i will able to do a couple of jiras at week,
> > >
> > > 2018-02-19 17:15 GMT+01:00 Go Yamamoto <ya...@lab.ntt.co.jp>:
> > >
> > > > Thanks, Giorgio.
> > > >
> > > > All, let's start planning release the crypto library first.
> > > > I think we can simply start official repository that mirrors
> > > > current crypto code at Miracl's, and then we declare that it is
> > > > the master of the project.
> > > > After that, Miracl's team will pull-request to contribute the
> > > advancements
> > > > at the local repo.
> > > >
> > > > We can start right now.
> > > > Who is managing the official repo right now?
> > > >
> > > > Go
> > > >
> > > > -----Original Message-----
> > > > From: Giorgio Zoppi [mailto:giorgio.zoppi@gmail.com]
> > > > Sent: Tuesday, February 20, 2018 1:00 AM
> > > > To: dev@milagro.incubator.apache.org
> > > > Subject: Re: [DISCUSS] Retire Milagro
> > > >
> > > > If it goes as planner i canhelp and build and test code. Porting
> > > > some
> > > code
> > > > to c++ for the server part.
> > > >
> > > > 2018-02-19 16:53 GMT+01:00 Go Yamamoto <ya...@lab.ntt.co.jp>:
> > > >
> > > > > 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.go@lab.ntt.co.jp]
> > > > > Sent: Friday, February 09, 2018 1:24 PM
> > > > > To: 'dev@milagro.incubator.apache.org'
> > > > > <de...@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.zoppi@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
> <si...@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" <ya...@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.zoppi@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.zoppi@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 <
> > > johndament@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
> > > > > > <si...@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"
> > > > > > <jo...@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"
> > > > > > >> > <ya...@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:johndament@apache.org
> ]
> > > > > > >> > > Sent: Tuesday, January 30, 2018 1:06 PM
> > > > > > >> > > To: dev@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
> > > > > > >> > >
> > > > > > >> > >
> > > > > > >> > >
> > > > > > >> >
> > > > > > >> >
> > > > > > >>
> > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > > >
> > > >
> > > >
> > > >
> > >
> > --
> > Nikolai Stoilov
> > NOC/Support Team Lead
> > MIRACL
> >
> >
> >
>
>
>
RE: RE: [DISCUSS] Retire Milagro
Posted by Go Yamamoto <ya...@lab.ntt.co.jp>.
Thank you for guidance. Sorry, I was somewhat confused.
"We" means NTT in this context.
I understand Milagro project has some difficulty in releasing code at the
official repository.
https://github.com/apache/incubator-milagro
The reason is not clear for me, however, if a new official repository
resolves the issue, then I think it is a good idea to install it.
For that purpose NTT is willing to work in managements.
Regards,
Go Yamamoto
-----Original Message-----
From: John D. Ament [mailto:johndament@apache.org]
Sent: Sunday, March 11, 2018 10:34 PM
To: dev@milagro.apache.org
Subject: Re: RE: [DISCUSS] Retire Milagro
On 2018/03/08 05:20:41, "Go Yamamoto" <ya...@lab.ntt.co.jp> wrote:
> Hi
>
> Who is taking care of management tasks right now?
> We would like to request the official repository to release our code.
> If nobody is working for the task, we will take it over.
Who is "we" in this case?
http://git.apache.org/ shows 11 repositories for Milagro.
>
> Regards,
> Go Yamamoto
>
> -----Original Message-----
> From: Nikolai Stoilov [mailto:nikolai.stoilov@miracl.com]
> Sent: Tuesday, February 20, 2018 1:51 AM
> To: dev@milagro.incubator.apache.org
> Subject: Re: [DISCUSS] Retire Milagro
>
> Hi Go,
>
> Regarding management, I can show someone from your side how to fill in the
monthly reports which are required for the project.
>
> Nikolai
>
> On Mon, Feb 19, 2018 at 6:24 PM Giorgio Zoppi
> <gi...@gmail.com>
> wrote:
>
> > Ok,
> > just to be proactive, schedule some tickets when you have a plan and
> > i will able to do a couple of jiras at week,
> >
> > 2018-02-19 17:15 GMT+01:00 Go Yamamoto <ya...@lab.ntt.co.jp>:
> >
> > > Thanks, Giorgio.
> > >
> > > All, let's start planning release the crypto library first.
> > > I think we can simply start official repository that mirrors
> > > current crypto code at Miracl's, and then we declare that it is
> > > the master of the project.
> > > After that, Miracl's team will pull-request to contribute the
> > advancements
> > > at the local repo.
> > >
> > > We can start right now.
> > > Who is managing the official repo right now?
> > >
> > > Go
> > >
> > > -----Original Message-----
> > > From: Giorgio Zoppi [mailto:giorgio.zoppi@gmail.com]
> > > Sent: Tuesday, February 20, 2018 1:00 AM
> > > To: dev@milagro.incubator.apache.org
> > > Subject: Re: [DISCUSS] Retire Milagro
> > >
> > > If it goes as planner i canhelp and build and test code. Porting
> > > some
> > code
> > > to c++ for the server part.
> > >
> > > 2018-02-19 16:53 GMT+01:00 Go Yamamoto <ya...@lab.ntt.co.jp>:
> > >
> > > > 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.go@lab.ntt.co.jp]
> > > > Sent: Friday, February 09, 2018 1:24 PM
> > > > To: 'dev@milagro.incubator.apache.org'
> > > > <de...@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.zoppi@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
<si...@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" <ya...@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.zoppi@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.zoppi@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 <
> > johndament@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
> > > > > <si...@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"
> > > > > <jo...@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"
> > > > > >> > <ya...@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:johndament@apache.org]
> > > > > >> > > Sent: Tuesday, January 30, 2018 1:06 PM
> > > > > >> > > To: dev@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
> > > > > >> > >
> > > > > >> > >
> > > > > >> > >
> > > > > >> >
> > > > > >> >
> > > > > >>
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > >
> > > >
> > > >
> > >
> > >
> > >
> >
> --
> Nikolai Stoilov
> NOC/Support Team Lead
> MIRACL
>
>
>
Re: RE: [DISCUSS] Retire Milagro
Posted by "John D. Ament" <jo...@apache.org>.
On 2018/03/08 05:20:41, "Go Yamamoto" <ya...@lab.ntt.co.jp> wrote:
> Hi
>
> Who is taking care of management tasks right now?
> We would like to request the official repository to release our code.
> If nobody is working for the task, we will take it over.
Who is "we" in this case?
http://git.apache.org/ shows 11 repositories for Milagro.
>
> Regards,
> Go Yamamoto
>
> -----Original Message-----
> From: Nikolai Stoilov [mailto:nikolai.stoilov@miracl.com]
> Sent: Tuesday, February 20, 2018 1:51 AM
> To: dev@milagro.incubator.apache.org
> Subject: Re: [DISCUSS] Retire Milagro
>
> Hi Go,
>
> Regarding management, I can show someone from your side how to fill in the monthly reports which are required for the project.
>
> Nikolai
>
> On Mon, Feb 19, 2018 at 6:24 PM Giorgio Zoppi <gi...@gmail.com>
> wrote:
>
> > Ok,
> > just to be proactive, schedule some tickets when you have a plan and i
> > will able to do a couple of jiras at week,
> >
> > 2018-02-19 17:15 GMT+01:00 Go Yamamoto <ya...@lab.ntt.co.jp>:
> >
> > > Thanks, Giorgio.
> > >
> > > All, let's start planning release the crypto library first.
> > > I think we can simply start official repository that mirrors current
> > > crypto code at Miracl's, and then we declare that it is the master
> > > of the project.
> > > After that, Miracl's team will pull-request to contribute the
> > advancements
> > > at the local repo.
> > >
> > > We can start right now.
> > > Who is managing the official repo right now?
> > >
> > > Go
> > >
> > > -----Original Message-----
> > > From: Giorgio Zoppi [mailto:giorgio.zoppi@gmail.com]
> > > Sent: Tuesday, February 20, 2018 1:00 AM
> > > To: dev@milagro.incubator.apache.org
> > > Subject: Re: [DISCUSS] Retire Milagro
> > >
> > > If it goes as planner i canhelp and build and test code. Porting
> > > some
> > code
> > > to c++ for the server part.
> > >
> > > 2018-02-19 16:53 GMT+01:00 Go Yamamoto <ya...@lab.ntt.co.jp>:
> > >
> > > > 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.go@lab.ntt.co.jp]
> > > > Sent: Friday, February 09, 2018 1:24 PM
> > > > To: 'dev@milagro.incubator.apache.org'
> > > > <de...@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.zoppi@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 <si...@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" <ya...@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.zoppi@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.zoppi@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 <
> > johndament@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
> > > > > <si...@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"
> > > > > <jo...@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"
> > > > > >> > <ya...@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:johndament@apache.org]
> > > > > >> > > Sent: Tuesday, January 30, 2018 1:06 PM
> > > > > >> > > To: dev@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
> > > > > >> > >
> > > > > >> > >
> > > > > >> > >
> > > > > >> >
> > > > > >> >
> > > > > >>
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > >
> > > >
> > > >
> > >
> > >
> > >
> >
> --
> Nikolai Stoilov
> NOC/Support Team Lead
> MIRACL
>
>
>
RE: [DISCUSS] Retire Milagro
Posted by Go Yamamoto <ya...@lab.ntt.co.jp>.
Hi
Who is taking care of management tasks right now?
We would like to request the official repository to release our code.
If nobody is working for the task, we will take it over.
Regards,
Go Yamamoto
-----Original Message-----
From: Nikolai Stoilov [mailto:nikolai.stoilov@miracl.com]
Sent: Tuesday, February 20, 2018 1:51 AM
To: dev@milagro.incubator.apache.org
Subject: Re: [DISCUSS] Retire Milagro
Hi Go,
Regarding management, I can show someone from your side how to fill in the monthly reports which are required for the project.
Nikolai
On Mon, Feb 19, 2018 at 6:24 PM Giorgio Zoppi <gi...@gmail.com>
wrote:
> Ok,
> just to be proactive, schedule some tickets when you have a plan and i
> will able to do a couple of jiras at week,
>
> 2018-02-19 17:15 GMT+01:00 Go Yamamoto <ya...@lab.ntt.co.jp>:
>
> > Thanks, Giorgio.
> >
> > All, let's start planning release the crypto library first.
> > I think we can simply start official repository that mirrors current
> > crypto code at Miracl's, and then we declare that it is the master
> > of the project.
> > After that, Miracl's team will pull-request to contribute the
> advancements
> > at the local repo.
> >
> > We can start right now.
> > Who is managing the official repo right now?
> >
> > Go
> >
> > -----Original Message-----
> > From: Giorgio Zoppi [mailto:giorgio.zoppi@gmail.com]
> > Sent: Tuesday, February 20, 2018 1:00 AM
> > To: dev@milagro.incubator.apache.org
> > Subject: Re: [DISCUSS] Retire Milagro
> >
> > If it goes as planner i canhelp and build and test code. Porting
> > some
> code
> > to c++ for the server part.
> >
> > 2018-02-19 16:53 GMT+01:00 Go Yamamoto <ya...@lab.ntt.co.jp>:
> >
> > > 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.go@lab.ntt.co.jp]
> > > Sent: Friday, February 09, 2018 1:24 PM
> > > To: 'dev@milagro.incubator.apache.org'
> > > <de...@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.zoppi@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 <si...@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" <ya...@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.zoppi@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.zoppi@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 <
> johndament@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
> > > > <si...@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"
> > > > <jo...@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"
> > > > >> > <ya...@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:johndament@apache.org]
> > > > >> > > Sent: Tuesday, January 30, 2018 1:06 PM
> > > > >> > > To: dev@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
> > > > >> > >
> > > > >> > >
> > > > >> > >
> > > > >> >
> > > > >> >
> > > > >>
> > > > >
> > > > >
> > > >
> > > >
> > > >
> > > >
> > >
> > >
> > >
> >
> >
> >
>
--
Nikolai Stoilov
NOC/Support Team Lead
MIRACL
Re: [DISCUSS] Retire Milagro
Posted by Nikolai Stoilov <ni...@miracl.com>.
Hi Go,
Regarding management, I can show someone from your side how to fill in the
monthly reports which are required for the project.
Nikolai
On Mon, Feb 19, 2018 at 6:24 PM Giorgio Zoppi <gi...@gmail.com>
wrote:
> Ok,
> just to be proactive, schedule some tickets when you have a plan and i will
> able to do a couple of jiras at week,
>
> 2018-02-19 17:15 GMT+01:00 Go Yamamoto <ya...@lab.ntt.co.jp>:
>
> > Thanks, Giorgio.
> >
> > All, let's start planning release the crypto library first.
> > I think we can simply start official repository that mirrors current
> > crypto code at Miracl's, and then we declare that it is the master of the
> > project.
> > After that, Miracl's team will pull-request to contribute the
> advancements
> > at the local repo.
> >
> > We can start right now.
> > Who is managing the official repo right now?
> >
> > Go
> >
> > -----Original Message-----
> > From: Giorgio Zoppi [mailto:giorgio.zoppi@gmail.com]
> > Sent: Tuesday, February 20, 2018 1:00 AM
> > To: dev@milagro.incubator.apache.org
> > Subject: Re: [DISCUSS] Retire Milagro
> >
> > If it goes as planner i canhelp and build and test code. Porting some
> code
> > to c++ for the server part.
> >
> > 2018-02-19 16:53 GMT+01:00 Go Yamamoto <ya...@lab.ntt.co.jp>:
> >
> > > 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.go@lab.ntt.co.jp]
> > > Sent: Friday, February 09, 2018 1:24 PM
> > > To: 'dev@milagro.incubator.apache.org'
> > > <de...@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.zoppi@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 <si...@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" <ya...@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.zoppi@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.zoppi@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 <
> johndament@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
> > > > <si...@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" <jo...@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"
> > > > >> > <ya...@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:johndament@apache.org]
> > > > >> > > Sent: Tuesday, January 30, 2018 1:06 PM
> > > > >> > > To: dev@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
> > > > >> > >
> > > > >> > >
> > > > >> > >
> > > > >> >
> > > > >> >
> > > > >>
> > > > >
> > > > >
> > > >
> > > >
> > > >
> > > >
> > >
> > >
> > >
> >
> >
> >
>
--
Nikolai Stoilov
NOC/Support Team Lead
MIRACL
Re: [DISCUSS] Retire Milagro
Posted by Giorgio Zoppi <gi...@gmail.com>.
Ok,
just to be proactive, schedule some tickets when you have a plan and i will
able to do a couple of jiras at week,
2018-02-19 17:15 GMT+01:00 Go Yamamoto <ya...@lab.ntt.co.jp>:
> Thanks, Giorgio.
>
> All, let's start planning release the crypto library first.
> I think we can simply start official repository that mirrors current
> crypto code at Miracl's, and then we declare that it is the master of the
> project.
> After that, Miracl's team will pull-request to contribute the advancements
> at the local repo.
>
> We can start right now.
> Who is managing the official repo right now?
>
> Go
>
> -----Original Message-----
> From: Giorgio Zoppi [mailto:giorgio.zoppi@gmail.com]
> Sent: Tuesday, February 20, 2018 1:00 AM
> To: dev@milagro.incubator.apache.org
> Subject: Re: [DISCUSS] Retire Milagro
>
> If it goes as planner i canhelp and build and test code. Porting some code
> to c++ for the server part.
>
> 2018-02-19 16:53 GMT+01:00 Go Yamamoto <ya...@lab.ntt.co.jp>:
>
> > 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.go@lab.ntt.co.jp]
> > Sent: Friday, February 09, 2018 1:24 PM
> > To: 'dev@milagro.incubator.apache.org'
> > <de...@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.zoppi@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 <si...@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" <ya...@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.zoppi@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.zoppi@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 <johndament@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
> > > <si...@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" <jo...@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"
> > > >> > <ya...@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:johndament@apache.org]
> > > >> > > Sent: Tuesday, January 30, 2018 1:06 PM
> > > >> > > To: dev@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
> > > >> > >
> > > >> > >
> > > >> > >
> > > >> >
> > > >> >
> > > >>
> > > >
> > > >
> > >
> > >
> > >
> > >
> >
> >
> >
>
>
>
RE: [DISCUSS] Retire Milagro
Posted by Go Yamamoto <ya...@lab.ntt.co.jp>.
Thanks, Giorgio.
All, let's start planning release the crypto library first.
I think we can simply start official repository that mirrors current crypto code at Miracl's, and then we declare that it is the master of the project.
After that, Miracl's team will pull-request to contribute the advancements at the local repo.
We can start right now.
Who is managing the official repo right now?
Go
-----Original Message-----
From: Giorgio Zoppi [mailto:giorgio.zoppi@gmail.com]
Sent: Tuesday, February 20, 2018 1:00 AM
To: dev@milagro.incubator.apache.org
Subject: Re: [DISCUSS] Retire Milagro
If it goes as planner i canhelp and build and test code. Porting some code to c++ for the server part.
2018-02-19 16:53 GMT+01:00 Go Yamamoto <ya...@lab.ntt.co.jp>:
> 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.go@lab.ntt.co.jp]
> Sent: Friday, February 09, 2018 1:24 PM
> To: 'dev@milagro.incubator.apache.org'
> <de...@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.zoppi@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 <si...@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" <ya...@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.zoppi@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 <gi...@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 <jo...@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
> > <si...@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" <jo...@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"
> > >> > <ya...@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:johndament@apache.org]
> > >> > > Sent: Tuesday, January 30, 2018 1:06 PM
> > >> > > To: dev@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
> > >> > >
> > >> > >
> > >> > >
> > >> >
> > >> >
> > >>
> > >
> > >
> >
> >
> >
> >
>
>
>
Re: [DISCUSS] Retire Milagro
Posted by Giorgio Zoppi <gi...@gmail.com>.
If it goes as planner i canhelp and build and test code. Porting some code
to c++ for the server part.
2018-02-19 16:53 GMT+01:00 Go Yamamoto <ya...@lab.ntt.co.jp>:
> 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.go@lab.ntt.co.jp]
> Sent: Friday, February 09, 2018 1:24 PM
> To: 'dev@milagro.incubator.apache.org' <de...@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.zoppi@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 <si...@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" <ya...@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.zoppi@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 <gi...@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 <jo...@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
> > <si...@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" <jo...@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"
> > >> > <ya...@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:johndament@apache.org]
> > >> > > Sent: Tuesday, January 30, 2018 1:06 PM
> > >> > > To: dev@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
> > >> > >
> > >> > >
> > >> > >
> > >> >
> > >> >
> > >>
> > >
> > >
> >
> >
> >
> >
>
>
>
RE: [DISCUSS] Retire Milagro
Posted by Go Yamamoto <ya...@lab.ntt.co.jp>.
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.go@lab.ntt.co.jp]
Sent: Friday, February 09, 2018 1:24 PM
To: 'dev@milagro.incubator.apache.org' <de...@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.zoppi@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 <si...@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" <ya...@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.zoppi@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 <gi...@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 <jo...@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
> <si...@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" <jo...@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"
> >> > <ya...@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:johndament@apache.org]
> >> > > Sent: Tuesday, January 30, 2018 1:06 PM
> >> > > To: dev@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
> >> > >
> >> > >
> >> > >
> >> >
> >> >
> >>
> >
> >
>
>
>
>
Re: [DISCUSS] Retire Milagro
Posted by Giorgio Zoppi <gi...@gmail.com>.
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 <si...@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" <ya...@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.zoppi@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 <gi...@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 <jo...@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 <si...@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" <jo...@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"
> >> > <ya...@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:johndament@apache.org]
> >> > > Sent: Tuesday, January 30, 2018 1:06 PM
> >> > > To: dev@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
> >> > >
> >> > >
> >> > >
> >> >
> >> >
> >>
> >
> >
>
>
>
>
Re: [DISCUSS] Retire Milagro
Posted by Simeon Aladjem <si...@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" <ya...@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.zoppi@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 <gi...@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 <jo...@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 <si...@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" <jo...@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"
>> > <ya...@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:johndament@apache.org]
>> > > Sent: Tuesday, January 30, 2018 1:06 PM
>> > > To: dev@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
>> > >
>> > >
>> > >
>> >
>> >
>>
>
>
RE: [DISCUSS] Retire Milagro
Posted by Go Yamamoto <ya...@lab.ntt.co.jp>.
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.zoppi@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 <gi...@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 <jo...@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 <si...@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" <jo...@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"
>> > <ya...@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:johndament@apache.org]
>> > > Sent: Tuesday, January 30, 2018 1:06 PM
>> > > To: dev@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
>> > >
>> > >
>> > >
>> >
>> >
>>
>
>
Re: [DISCUSS] Retire Milagro
Posted by Giorgio Zoppi <gi...@gmail.com>.
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 <gi...@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 <jo...@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 <si...@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" <jo...@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" <ya...@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:johndament@apache.org]
>> > > Sent: Tuesday, January 30, 2018 1:06 PM
>> > > To: dev@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
>> > >
>> > >
>> > >
>> >
>> >
>>
>
>
Re: [DISCUSS] Retire Milagro
Posted by Giorgio Zoppi <gi...@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 <jo...@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 <si...@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" <jo...@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" <ya...@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:johndament@apache.org]
> > > Sent: Tuesday, January 30, 2018 1:06 PM
> > > To: dev@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/
> e6a5db6fab6c61156c2101aae003ed576ddb0e77f3bb2c037b405131@%
> 3Cdev.milagro.apache.org%3E
> > >
> > >
> > >
> >
> >
>
Re: [DISCUSS] Retire Milagro
Posted by "John D. Ament" <jo...@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 <si...@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" <jo...@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" <ya...@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:johndament@apache.org]
> > Sent: Tuesday, January 30, 2018 1:06 PM
> > To: dev@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/e6a5db6fab6c61156c2101aae003ed576ddb0e77f3bb2c037b405131@%3Cdev.milagro.apache.org%3E
> >
> >
> >
>
>
Re: [DISCUSS] Retire Milagro
Posted by Simeon Aladjem <si...@miracl.com>.
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" <jo...@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" <ya...@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:johndament@apache.org]
> Sent: Tuesday, January 30, 2018 1:06 PM
> To: dev@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/e6a5db6fab6c61156c2101aae003ed576ddb0e77f3bb2c037b405131@%3Cdev.milagro.apache.org%3E
>
>
>
Re: RE: [DISCUSS] Retire Milagro
Posted by "John D. Ament" <jo...@apache.org>.
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" <ya...@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:johndament@apache.org]
> Sent: Tuesday, January 30, 2018 1:06 PM
> To: dev@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/e6a5db6fab6c61156c2101aae003ed576ddb0e77f3bb2c037b405131@%3Cdev.milagro.apache.org%3E
>
>
>
RE: [DISCUSS] Retire Milagro
Posted by Go Yamamoto <ya...@lab.ntt.co.jp>.
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:johndament@apache.org]
Sent: Tuesday, January 30, 2018 1:06 PM
To: dev@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/e6a5db6fab6c61156c2101aae003ed576ddb0e77f3bb2c037b405131@%3Cdev.milagro.apache.org%3E