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 2017/11/06 13:07:18 UTC
Re: RE: State of Milagro
Hi,
Sorry, I don't fully understand your response.
Where do you want this project to go? I know from an IPMC standpoint, I'm concerned that you moved development away from the ASF.
John
On 2017-10-29 08:29, "Go Yamamoto" <ya...@lab.ntt.co.jp> wrote:
> Hi,
>
> I am wondering why this project does not go. We have a set of MFA server/client and an ID-based crypt library that actually work fine. We have been working for the code and are willing to donate the code. It sounds like a quite unreasonable story.
>
> I think we should start from releasing the library part and fix the API for the library.
> What is the blocker? Should we restart the project?
>
> Regards,
> Go Yamamoto
>
>
>
>
>
>
> -----Original Message-----
> From: John D. Ament [mailto:johndament@apache.org]
> Sent: Sunday, October 29, 2017 7:35 PM
> To: dev@milagro.apache.org
> Subject: State of Milagro
>
> Hi All,
>
> Last month, as noted in email, your board report was removed due to questions being raised and lack of mentor sign off.
>
> The IPMC looks for a response from you considering the questions raised by Dave Fisher, in addition your mentors must sign off on your report explicitly. You cannot add their sign off.
>
> John
>
>
>
Re: State of Milagro
Posted by Nikolai Stoilov <ni...@miracl.com>.
I added the report to the wiki.
Thanks,
Nikolai
On Thu, Nov 9, 2017 at 9:25 AM Nikolai Stoilov <ni...@miracl.com>
wrote:
> I'll submit a report later today.
>
> On Thu, Nov 9, 2017 at 1:20 AM John D. Ament <jo...@apache.org>
> wrote:
>
>> Ok, thanks for clarifying those items.
>>
>> The reason I was originally stopping by was due to lack of report. Any
>> update on a report?
>>
>> John
>>
>> On 2017-11-08 03:19, Simeon Aladjem <si...@miracl.com> wrote:
>> > The issue was that newest crypto code was initially published under
>> https://github.com/milagro-crypto/milagro-crypto-c, but it will be moved
>> to https://github.com/apache.
>> >
>> > Simeon
>> >
>> > On 8/11/17, 04:47, "John D. Ament" <jo...@apache.org> wrote:
>> >
>> >
>> >
>> > On 2017-11-07 05:18, Simeon Aladjem <si...@miracl.com>
>> wrote:
>> > > No, exactly the opposite!
>> > > The issue that shacked the ground is not present anymore, so the
>> project can continue as it should.
>> > > Any proposed change will be raised for a vote.
>> >
>> > Which issue are you referring to?
>> >
>> > >
>> > > Thanks,
>> > > Simeon Aladjem
>> > >
>> > > On 7/11/17, 12:10, "Giorgio Zoppi" <gi...@gmail.com>
>> wrote:
>> > >
>> > > Hello everybody,
>> > > this means that it is not an apache.org project anymore?
>> > > BR,
>> > > Giorgio
>> > >
>> > > <
>> https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail
>> >
>> > > Libre
>> > > de virus. www.avast.com
>> > > <
>> https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail
>> >
>> > > <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>> > >
>> > > 2017-11-07 9:42 GMT+01:00 Simeon Aladjem <
>> simeon.aladjem@miracl.com>:
>> > >
>> > > > Hello,
>> > > >
>> > > > To the best of my understanding, the current problem with
>> the project is
>> > > > the hinted move of the milagro-crypto repository to a
>> different GitHub
>> > > > organization.
>> > > > I think that won't be a problem anymore, since the
>> intention to make this
>> > > > move was suspended.
>> > > >
>> > > > Together with that, we do want to contribute a new crypto
>> code, which
>> > > > doesn't fit into the current repository, as it presents a
>> missive change
>> > > > from the current one.
>> > > > We intend to propose in the near future few changes in the
>> project
>> > > > code-base and repositories.
>> > > >
>> > > > Best,
>> > > > Simeon Aladjem
>> > > > MIRACL
>> > > >
>> > > > On 6/11/17, 15:07, "John D. Ament" <
>> johndament@apache.org> wrote:
>> > > >
>> > > > Hi,
>> > > >
>> > > > Sorry, I don't fully understand your response.
>> > > >
>> > > > Where do you want this project to go? I know from an
>> IPMC standpoint,
>> > > > I'm concerned that you moved development away from the ASF.
>> > > >
>> > > > John
>> > > >
>> > > > On 2017-10-29 08:29, "Go Yamamoto" <
>> yamamoto.go@lab.ntt.co.jp> wrote:
>> > > > > Hi,
>> > > > >
>> > > > > I am wondering why this project does not go. We have
>> a set of MFA
>> > > > server/client and an ID-based crypt library that actually
>> work fine. We
>> > > > have been working for the code and are willing to donate
>> the code. It
>> > > > sounds like a quite unreasonable story.
>> > > > >
>> > > > > I think we should start from releasing the library
>> part and fix the
>> > > > API for the library.
>> > > > > What is the blocker? Should we restart the project?
>> > > > >
>> > > > > Regards,
>> > > > > Go Yamamoto
>> > > > >
>> > > > >
>> > > > >
>> > > > >
>> > > > >
>> > > > >
>> > > > > -----Original Message-----
>> > > > > From: John D. Ament [mailto:johndament@apache.org]
>> > > > > Sent: Sunday, October 29, 2017 7:35 PM
>> > > > > To: dev@milagro.apache.org
>> > > > > Subject: State of Milagro
>> > > > >
>> > > > > Hi All,
>> > > > >
>> > > > > Last month, as noted in email, your board report was
>> removed due to
>> > > > questions being raised and lack of mentor sign off.
>> > > > >
>> > > > > The IPMC looks for a response from you considering
>> the questions
>> > > > raised by Dave Fisher, in addition your mentors must sign
>> off on your
>> > > > report explicitly. You cannot add their sign off.
>> > > > >
>> > > > > John
>> > > > >
>> > > > >
>> > > > >
>> > > >
>> > > >
>> > >
>> > >
>> >
>> >
>>
> --
> Nikolai Stoilov
> NOC/Support Team Lead
> MIRACL
>
--
Nikolai Stoilov
NOC/Support Team Lead
MIRACL
Re: State of Milagro
Posted by Nikolai Stoilov <ni...@miracl.com>.
I'll submit a report later today.
On Thu, Nov 9, 2017 at 1:20 AM John D. Ament <jo...@apache.org> wrote:
> Ok, thanks for clarifying those items.
>
> The reason I was originally stopping by was due to lack of report. Any
> update on a report?
>
> John
>
> On 2017-11-08 03:19, Simeon Aladjem <si...@miracl.com> wrote:
> > The issue was that newest crypto code was initially published under
> https://github.com/milagro-crypto/milagro-crypto-c, but it will be moved
> to https://github.com/apache.
> >
> > Simeon
> >
> > On 8/11/17, 04:47, "John D. Ament" <jo...@apache.org> wrote:
> >
> >
> >
> > On 2017-11-07 05:18, Simeon Aladjem <si...@miracl.com>
> wrote:
> > > No, exactly the opposite!
> > > The issue that shacked the ground is not present anymore, so the
> project can continue as it should.
> > > Any proposed change will be raised for a vote.
> >
> > Which issue are you referring to?
> >
> > >
> > > Thanks,
> > > Simeon Aladjem
> > >
> > > On 7/11/17, 12:10, "Giorgio Zoppi" <gi...@gmail.com>
> wrote:
> > >
> > > Hello everybody,
> > > this means that it is not an apache.org project anymore?
> > > BR,
> > > Giorgio
> > >
> > > <
> https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail
> >
> > > Libre
> > > de virus. www.avast.com
> > > <
> https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail
> >
> > > <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
> > >
> > > 2017-11-07 9:42 GMT+01:00 Simeon Aladjem <
> simeon.aladjem@miracl.com>:
> > >
> > > > Hello,
> > > >
> > > > To the best of my understanding, the current problem with
> the project is
> > > > the hinted move of the milagro-crypto repository to a
> different GitHub
> > > > organization.
> > > > I think that won't be a problem anymore, since the intention
> to make this
> > > > move was suspended.
> > > >
> > > > Together with that, we do want to contribute a new crypto
> code, which
> > > > doesn't fit into the current repository, as it presents a
> missive change
> > > > from the current one.
> > > > We intend to propose in the near future few changes in the
> project
> > > > code-base and repositories.
> > > >
> > > > Best,
> > > > Simeon Aladjem
> > > > MIRACL
> > > >
> > > > On 6/11/17, 15:07, "John D. Ament" <jo...@apache.org>
> wrote:
> > > >
> > > > Hi,
> > > >
> > > > Sorry, I don't fully understand your response.
> > > >
> > > > Where do you want this project to go? I know from an
> IPMC standpoint,
> > > > I'm concerned that you moved development away from the ASF.
> > > >
> > > > John
> > > >
> > > > On 2017-10-29 08:29, "Go Yamamoto" <
> yamamoto.go@lab.ntt.co.jp> wrote:
> > > > > Hi,
> > > > >
> > > > > I am wondering why this project does not go. We have
> a set of MFA
> > > > server/client and an ID-based crypt library that actually
> work fine. We
> > > > have been working for the code and are willing to donate the
> code. It
> > > > sounds like a quite unreasonable story.
> > > > >
> > > > > I think we should start from releasing the library
> part and fix the
> > > > API for the library.
> > > > > What is the blocker? Should we restart the project?
> > > > >
> > > > > Regards,
> > > > > Go Yamamoto
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > -----Original Message-----
> > > > > From: John D. Ament [mailto:johndament@apache.org]
> > > > > Sent: Sunday, October 29, 2017 7:35 PM
> > > > > To: dev@milagro.apache.org
> > > > > Subject: State of Milagro
> > > > >
> > > > > Hi All,
> > > > >
> > > > > Last month, as noted in email, your board report was
> removed due to
> > > > questions being raised and lack of mentor sign off.
> > > > >
> > > > > The IPMC looks for a response from you considering the
> questions
> > > > raised by Dave Fisher, in addition your mentors must sign
> off on your
> > > > report explicitly. You cannot add their sign off.
> > > > >
> > > > > John
> > > > >
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
--
Nikolai Stoilov
NOC/Support Team Lead
MIRACL
Re: State of Milagro
Posted by "John D. Ament" <jo...@apache.org>.
Ok, thanks for clarifying those items.
The reason I was originally stopping by was due to lack of report. Any update on a report?
John
On 2017-11-08 03:19, Simeon Aladjem <si...@miracl.com> wrote:
> The issue was that newest crypto code was initially published under https://github.com/milagro-crypto/milagro-crypto-c, but it will be moved to https://github.com/apache.
>
> Simeon
>
> On 8/11/17, 04:47, "John D. Ament" <jo...@apache.org> wrote:
>
>
>
> On 2017-11-07 05:18, Simeon Aladjem <si...@miracl.com> wrote:
> > No, exactly the opposite!
> > The issue that shacked the ground is not present anymore, so the project can continue as it should.
> > Any proposed change will be raised for a vote.
>
> Which issue are you referring to?
>
> >
> > Thanks,
> > Simeon Aladjem
> >
> > On 7/11/17, 12:10, "Giorgio Zoppi" <gi...@gmail.com> wrote:
> >
> > Hello everybody,
> > this means that it is not an apache.org project anymore?
> > BR,
> > Giorgio
> >
> > <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
> > Libre
> > de virus. www.avast.com
> > <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
> > <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
> >
> > 2017-11-07 9:42 GMT+01:00 Simeon Aladjem <si...@miracl.com>:
> >
> > > Hello,
> > >
> > > To the best of my understanding, the current problem with the project is
> > > the hinted move of the milagro-crypto repository to a different GitHub
> > > organization.
> > > I think that won't be a problem anymore, since the intention to make this
> > > move was suspended.
> > >
> > > Together with that, we do want to contribute a new crypto code, which
> > > doesn't fit into the current repository, as it presents a missive change
> > > from the current one.
> > > We intend to propose in the near future few changes in the project
> > > code-base and repositories.
> > >
> > > Best,
> > > Simeon Aladjem
> > > MIRACL
> > >
> > > On 6/11/17, 15:07, "John D. Ament" <jo...@apache.org> wrote:
> > >
> > > Hi,
> > >
> > > Sorry, I don't fully understand your response.
> > >
> > > Where do you want this project to go? I know from an IPMC standpoint,
> > > I'm concerned that you moved development away from the ASF.
> > >
> > > John
> > >
> > > On 2017-10-29 08:29, "Go Yamamoto" <ya...@lab.ntt.co.jp> wrote:
> > > > Hi,
> > > >
> > > > I am wondering why this project does not go. We have a set of MFA
> > > server/client and an ID-based crypt library that actually work fine. We
> > > have been working for the code and are willing to donate the code. It
> > > sounds like a quite unreasonable story.
> > > >
> > > > I think we should start from releasing the library part and fix the
> > > API for the library.
> > > > What is the blocker? Should we restart the project?
> > > >
> > > > Regards,
> > > > Go Yamamoto
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > -----Original Message-----
> > > > From: John D. Ament [mailto:johndament@apache.org]
> > > > Sent: Sunday, October 29, 2017 7:35 PM
> > > > To: dev@milagro.apache.org
> > > > Subject: State of Milagro
> > > >
> > > > Hi All,
> > > >
> > > > Last month, as noted in email, your board report was removed due to
> > > questions being raised and lack of mentor sign off.
> > > >
> > > > The IPMC looks for a response from you considering the questions
> > > raised by Dave Fisher, in addition your mentors must sign off on your
> > > report explicitly. You cannot add their sign off.
> > > >
> > > > John
> > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>
Re: State of Milagro
Posted by Simeon Aladjem <si...@miracl.com>.
The issue was that newest crypto code was initially published under https://github.com/milagro-crypto/milagro-crypto-c, but it will be moved to https://github.com/apache.
Simeon
On 8/11/17, 04:47, "John D. Ament" <jo...@apache.org> wrote:
On 2017-11-07 05:18, Simeon Aladjem <si...@miracl.com> wrote:
> No, exactly the opposite!
> The issue that shacked the ground is not present anymore, so the project can continue as it should.
> Any proposed change will be raised for a vote.
Which issue are you referring to?
>
> Thanks,
> Simeon Aladjem
>
> On 7/11/17, 12:10, "Giorgio Zoppi" <gi...@gmail.com> wrote:
>
> Hello everybody,
> this means that it is not an apache.org project anymore?
> BR,
> Giorgio
>
> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
> Libre
> de virus. www.avast.com
> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>
> 2017-11-07 9:42 GMT+01:00 Simeon Aladjem <si...@miracl.com>:
>
> > Hello,
> >
> > To the best of my understanding, the current problem with the project is
> > the hinted move of the milagro-crypto repository to a different GitHub
> > organization.
> > I think that won't be a problem anymore, since the intention to make this
> > move was suspended.
> >
> > Together with that, we do want to contribute a new crypto code, which
> > doesn't fit into the current repository, as it presents a missive change
> > from the current one.
> > We intend to propose in the near future few changes in the project
> > code-base and repositories.
> >
> > Best,
> > Simeon Aladjem
> > MIRACL
> >
> > On 6/11/17, 15:07, "John D. Ament" <jo...@apache.org> wrote:
> >
> > Hi,
> >
> > Sorry, I don't fully understand your response.
> >
> > Where do you want this project to go? I know from an IPMC standpoint,
> > I'm concerned that you moved development away from the ASF.
> >
> > John
> >
> > On 2017-10-29 08:29, "Go Yamamoto" <ya...@lab.ntt.co.jp> wrote:
> > > Hi,
> > >
> > > I am wondering why this project does not go. We have a set of MFA
> > server/client and an ID-based crypt library that actually work fine. We
> > have been working for the code and are willing to donate the code. It
> > sounds like a quite unreasonable story.
> > >
> > > I think we should start from releasing the library part and fix the
> > API for the library.
> > > What is the blocker? Should we restart the project?
> > >
> > > Regards,
> > > Go Yamamoto
> > >
> > >
> > >
> > >
> > >
> > >
> > > -----Original Message-----
> > > From: John D. Ament [mailto:johndament@apache.org]
> > > Sent: Sunday, October 29, 2017 7:35 PM
> > > To: dev@milagro.apache.org
> > > Subject: State of Milagro
> > >
> > > Hi All,
> > >
> > > Last month, as noted in email, your board report was removed due to
> > questions being raised and lack of mentor sign off.
> > >
> > > The IPMC looks for a response from you considering the questions
> > raised by Dave Fisher, in addition your mentors must sign off on your
> > report explicitly. You cannot add their sign off.
> > >
> > > John
> > >
> > >
> > >
> >
> >
>
>
Re: State of Milagro
Posted by "John D. Ament" <jo...@apache.org>.
On 2017-11-07 05:18, Simeon Aladjem <si...@miracl.com> wrote:
> No, exactly the opposite!
> The issue that shacked the ground is not present anymore, so the project can continue as it should.
> Any proposed change will be raised for a vote.
Which issue are you referring to?
>
> Thanks,
> Simeon Aladjem
>
> On 7/11/17, 12:10, "Giorgio Zoppi" <gi...@gmail.com> wrote:
>
> Hello everybody,
> this means that it is not an apache.org project anymore?
> BR,
> Giorgio
>
> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
> Libre
> de virus. www.avast.com
> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>
> 2017-11-07 9:42 GMT+01:00 Simeon Aladjem <si...@miracl.com>:
>
> > Hello,
> >
> > To the best of my understanding, the current problem with the project is
> > the hinted move of the milagro-crypto repository to a different GitHub
> > organization.
> > I think that won't be a problem anymore, since the intention to make this
> > move was suspended.
> >
> > Together with that, we do want to contribute a new crypto code, which
> > doesn't fit into the current repository, as it presents a missive change
> > from the current one.
> > We intend to propose in the near future few changes in the project
> > code-base and repositories.
> >
> > Best,
> > Simeon Aladjem
> > MIRACL
> >
> > On 6/11/17, 15:07, "John D. Ament" <jo...@apache.org> wrote:
> >
> > Hi,
> >
> > Sorry, I don't fully understand your response.
> >
> > Where do you want this project to go? I know from an IPMC standpoint,
> > I'm concerned that you moved development away from the ASF.
> >
> > John
> >
> > On 2017-10-29 08:29, "Go Yamamoto" <ya...@lab.ntt.co.jp> wrote:
> > > Hi,
> > >
> > > I am wondering why this project does not go. We have a set of MFA
> > server/client and an ID-based crypt library that actually work fine. We
> > have been working for the code and are willing to donate the code. It
> > sounds like a quite unreasonable story.
> > >
> > > I think we should start from releasing the library part and fix the
> > API for the library.
> > > What is the blocker? Should we restart the project?
> > >
> > > Regards,
> > > Go Yamamoto
> > >
> > >
> > >
> > >
> > >
> > >
> > > -----Original Message-----
> > > From: John D. Ament [mailto:johndament@apache.org]
> > > Sent: Sunday, October 29, 2017 7:35 PM
> > > To: dev@milagro.apache.org
> > > Subject: State of Milagro
> > >
> > > Hi All,
> > >
> > > Last month, as noted in email, your board report was removed due to
> > questions being raised and lack of mentor sign off.
> > >
> > > The IPMC looks for a response from you considering the questions
> > raised by Dave Fisher, in addition your mentors must sign off on your
> > report explicitly. You cannot add their sign off.
> > >
> > > John
> > >
> > >
> > >
> >
> >
>
>
Re: State of Milagro
Posted by Simeon Aladjem <si...@miracl.com>.
No, exactly the opposite!
The issue that shacked the ground is not present anymore, so the project can continue as it should.
Any proposed change will be raised for a vote.
Thanks,
Simeon Aladjem
On 7/11/17, 12:10, "Giorgio Zoppi" <gi...@gmail.com> wrote:
Hello everybody,
this means that it is not an apache.org project anymore?
BR,
Giorgio
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
Libre
de virus. www.avast.com
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
2017-11-07 9:42 GMT+01:00 Simeon Aladjem <si...@miracl.com>:
> Hello,
>
> To the best of my understanding, the current problem with the project is
> the hinted move of the milagro-crypto repository to a different GitHub
> organization.
> I think that won't be a problem anymore, since the intention to make this
> move was suspended.
>
> Together with that, we do want to contribute a new crypto code, which
> doesn't fit into the current repository, as it presents a missive change
> from the current one.
> We intend to propose in the near future few changes in the project
> code-base and repositories.
>
> Best,
> Simeon Aladjem
> MIRACL
>
> On 6/11/17, 15:07, "John D. Ament" <jo...@apache.org> wrote:
>
> Hi,
>
> Sorry, I don't fully understand your response.
>
> Where do you want this project to go? I know from an IPMC standpoint,
> I'm concerned that you moved development away from the ASF.
>
> John
>
> On 2017-10-29 08:29, "Go Yamamoto" <ya...@lab.ntt.co.jp> wrote:
> > Hi,
> >
> > I am wondering why this project does not go. We have a set of MFA
> server/client and an ID-based crypt library that actually work fine. We
> have been working for the code and are willing to donate the code. It
> sounds like a quite unreasonable story.
> >
> > I think we should start from releasing the library part and fix the
> API for the library.
> > What is the blocker? Should we restart the project?
> >
> > Regards,
> > Go Yamamoto
> >
> >
> >
> >
> >
> >
> > -----Original Message-----
> > From: John D. Ament [mailto:johndament@apache.org]
> > Sent: Sunday, October 29, 2017 7:35 PM
> > To: dev@milagro.apache.org
> > Subject: State of Milagro
> >
> > Hi All,
> >
> > Last month, as noted in email, your board report was removed due to
> questions being raised and lack of mentor sign off.
> >
> > The IPMC looks for a response from you considering the questions
> raised by Dave Fisher, in addition your mentors must sign off on your
> report explicitly. You cannot add their sign off.
> >
> > John
> >
> >
> >
>
>
Re: State of Milagro
Posted by Giorgio Zoppi <gi...@gmail.com>.
Hello everybody,
this means that it is not an apache.org project anymore?
BR,
Giorgio
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
Libre
de virus. www.avast.com
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
2017-11-07 9:42 GMT+01:00 Simeon Aladjem <si...@miracl.com>:
> Hello,
>
> To the best of my understanding, the current problem with the project is
> the hinted move of the milagro-crypto repository to a different GitHub
> organization.
> I think that won't be a problem anymore, since the intention to make this
> move was suspended.
>
> Together with that, we do want to contribute a new crypto code, which
> doesn't fit into the current repository, as it presents a missive change
> from the current one.
> We intend to propose in the near future few changes in the project
> code-base and repositories.
>
> Best,
> Simeon Aladjem
> MIRACL
>
> On 6/11/17, 15:07, "John D. Ament" <jo...@apache.org> wrote:
>
> Hi,
>
> Sorry, I don't fully understand your response.
>
> Where do you want this project to go? I know from an IPMC standpoint,
> I'm concerned that you moved development away from the ASF.
>
> John
>
> On 2017-10-29 08:29, "Go Yamamoto" <ya...@lab.ntt.co.jp> wrote:
> > Hi,
> >
> > I am wondering why this project does not go. We have a set of MFA
> server/client and an ID-based crypt library that actually work fine. We
> have been working for the code and are willing to donate the code. It
> sounds like a quite unreasonable story.
> >
> > I think we should start from releasing the library part and fix the
> API for the library.
> > What is the blocker? Should we restart the project?
> >
> > Regards,
> > Go Yamamoto
> >
> >
> >
> >
> >
> >
> > -----Original Message-----
> > From: John D. Ament [mailto:johndament@apache.org]
> > Sent: Sunday, October 29, 2017 7:35 PM
> > To: dev@milagro.apache.org
> > Subject: State of Milagro
> >
> > Hi All,
> >
> > Last month, as noted in email, your board report was removed due to
> questions being raised and lack of mentor sign off.
> >
> > The IPMC looks for a response from you considering the questions
> raised by Dave Fisher, in addition your mentors must sign off on your
> report explicitly. You cannot add their sign off.
> >
> > John
> >
> >
> >
>
>
Re: State of Milagro
Posted by Simeon Aladjem <si...@miracl.com>.
Hello,
To the best of my understanding, the current problem with the project is the hinted move of the milagro-crypto repository to a different GitHub organization.
I think that won't be a problem anymore, since the intention to make this move was suspended.
Together with that, we do want to contribute a new crypto code, which doesn't fit into the current repository, as it presents a missive change from the current one.
We intend to propose in the near future few changes in the project code-base and repositories.
Best,
Simeon Aladjem
MIRACL
On 6/11/17, 15:07, "John D. Ament" <jo...@apache.org> wrote:
Hi,
Sorry, I don't fully understand your response.
Where do you want this project to go? I know from an IPMC standpoint, I'm concerned that you moved development away from the ASF.
John
On 2017-10-29 08:29, "Go Yamamoto" <ya...@lab.ntt.co.jp> wrote:
> Hi,
>
> I am wondering why this project does not go. We have a set of MFA server/client and an ID-based crypt library that actually work fine. We have been working for the code and are willing to donate the code. It sounds like a quite unreasonable story.
>
> I think we should start from releasing the library part and fix the API for the library.
> What is the blocker? Should we restart the project?
>
> Regards,
> Go Yamamoto
>
>
>
>
>
>
> -----Original Message-----
> From: John D. Ament [mailto:johndament@apache.org]
> Sent: Sunday, October 29, 2017 7:35 PM
> To: dev@milagro.apache.org
> Subject: State of Milagro
>
> Hi All,
>
> Last month, as noted in email, your board report was removed due to questions being raised and lack of mentor sign off.
>
> The IPMC looks for a response from you considering the questions raised by Dave Fisher, in addition your mentors must sign off on your report explicitly. You cannot add their sign off.
>
> John
>
>
>