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 <[email protected]> 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" <[email protected]> wrote:
> 
>     
>     
>     On 2017-11-07 05:18, Simeon Aladjem <[email protected]> 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" <[email protected]> 
> 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 
> <[email protected]>:
>     >     
>     >     > 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" <[email protected]> 
> 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" 
> <[email protected]> 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:[email protected]]
>     >     >     > Sent: Sunday, October 29, 2017 7:35 PM
>     >     >     > To: [email protected]
>     >     >     > 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
>     >     >     >
>     >     >     >
>     >     >     >
>     >     >
>     >     >
>     >     
>     > 
>     
> 

Reply via email to