[jira] [Comment Edited] (MILAGRO-21) Redefine our development scope

[Go Yamamoto (JIRA)]

[ 
https://issues.apache.org/jira/browse/MILAGRO-21?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16680815#comment-16680815
 ] 

Go Yamamoto edited comment on MILAGRO-21 at 11/9/18 4:11 AM:
-

The link fixed.  Previously linked to example.com for an unknown reason.  
Please copy and past the link text if a similar problem occurs again.

I think the crypto library is ready to release first.
However the process is not clear for me.  
Do we need some legal clearance?


was (Author: go):
The link fixed.  Previously linked to example.com for unknown reason.  Please 
cut and past the link text if a similar problem occurs again.

I think we can release the crypto library part first.
The process is not clear for me.  
Do we need some legal clearance?

> Redefine our development scope
> --
>
> Key: MILAGRO-21
> URL: https://issues.apache.org/jira/browse/MILAGRO-21
> Project: Milagro
>  Issue Type: Task
>    Reporter: Go Yamamoto
>Priority: Major
>
> {color:#00}The current roadmap suggests releasing the crypto library part 
> (AMCL) first.{color}
> {color:#00}[https://wiki.apache.org/incubator/MilagroRescueRoadmap]{color}
> {color:#00}Let's discuss the scope or an reboot plan for our 
> project.{color}
>  
> {color:#00}I think an OSS library for elliptic curve crypto with pairing 
> is precious and essential.{color}
> {color:#00}Moreover, ASF will be one of the safest place to develop 
> crypto library from the viewpoint of problems among intellectual property 
> rights.{color}
> {color:#00}The library is the basis of everything we have developed in 
> this project, so we can start from releasing it.{color}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MILAGRO-21) Redefine our development scope

[Go Yamamoto (JIRA)]

[ 
https://issues.apache.org/jira/browse/MILAGRO-21?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16680815#comment-16680815
 ] 

Go Yamamoto commented on MILAGRO-21:


The link fixed.  Previously linked to example.com for unknown reason.  Please 
cut and past the link text if a similar problem occurs again.

I think we can release the crypto library part first.
The process is not clear for me.  
Do we need some legal clearance?

> Redefine our development scope
> --
>
> Key: MILAGRO-21
> URL: https://issues.apache.org/jira/browse/MILAGRO-21
> Project: Milagro
>  Issue Type: Task
>    Reporter: Go Yamamoto
>Priority: Major
>
> {color:#00}The current roadmap suggests releasing the crypto library part 
> (AMCL) first.{color}
> {color:#00}[https://wiki.apache.org/incubator/MilagroRescueRoadmap]{color}
> {color:#00}Let's discuss the scope or an reboot plan for our 
> project.{color}
>  
> {color:#00}I think an OSS library for elliptic curve crypto with pairing 
> is precious and essential.{color}
> {color:#00}Moreover, ASF will be one of the safest place to develop 
> crypto library from the viewpoint of problems among intellectual property 
> rights.{color}
> {color:#00}The library is the basis of everything we have developed in 
> this project, so we can start from releasing it.{color}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (MILAGRO-21) Redefine our development scope

[Go Yamamoto (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MILAGRO-21?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Go Yamamoto updated MILAGRO-21:
---
Description: 
{color:#00}The current roadmap suggests releasing the crypto library part 
(AMCL) first.{color}

{color:#00}[https://wiki.apache.org/incubator/MilagroRescueRoadmap|http://example.com/]{color}

{color:#00}Let's discuss the scope or an reboot plan for our project.{color}

 

{color:#00}I think an OSS library for elliptic curve crypto with pairing is 
precious and essential.{color}

{color:#00}Moreover, ASF will be one of the safest place to develop crypto 
library from the viewpoint of problems among intellectual property 
rights.{color}

{color:#00}The library is the basis of everything we have developed in this 
project, so we can start from releasing it.{color}

  was:
{color:#00}The current roadmap suggests releasing the crypto library part 
(AMCL) first.{color}

{color:#00}[https://wiki.apache.org/incubator/MilagroRescueRoadmap|http://example.com/]{color}

{color:#00}[[https://wiki.apache.org/incubator/MilagroRescueRoadmap|http://example.com/]|[https://wiki.apache.org/incubator/MilagroRescueRoadmap|http://example.com/]]{color}

{color:#00}Let's discuss the scope or an reboot plan for our project.{color}

 

{color:#00}I think an OSS library for elliptic curve crypto with pairing is 
precious and essential.{color}

{color:#00}Moreover, ASF will be one of the safest place to develop crypto 
library from the viewpoint of problems among intellectual property 
rights.{color}

{color:#00}The library is the basis of everything we have developed in this 
project, so we can start from releasing it.{color}


> Redefine our development scope
> --
>
> Key: MILAGRO-21
> URL: https://issues.apache.org/jira/browse/MILAGRO-21
> Project: Milagro
>  Issue Type: Task
>    Reporter: Go Yamamoto
>Priority: Major
>
> {color:#00}The current roadmap suggests releasing the crypto library part 
> (AMCL) first.{color}
> {color:#00}[https://wiki.apache.org/incubator/MilagroRescueRoadmap|http://example.com/]{color}
> {color:#00}Let's discuss the scope or an reboot plan for our 
> project.{color}
>  
> {color:#00}I think an OSS library for elliptic curve crypto with pairing 
> is precious and essential.{color}
> {color:#00}Moreover, ASF will be one of the safest place to develop 
> crypto library from the viewpoint of problems among intellectual property 
> rights.{color}
> {color:#00}The library is the basis of everything we have developed in 
> this project, so we can start from releasing it.{color}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (MILAGRO-21) Redefine our development scope

[Go Yamamoto (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MILAGRO-21?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Go Yamamoto updated MILAGRO-21:
---
Description: 
{color:#00}The current roadmap suggests releasing the crypto library part 
(AMCL) first.{color}

{color:#00}[https://wiki.apache.org/incubator/MilagroRescueRoadmap]{color}

{color:#00}Let's discuss the scope or an reboot plan for our project.{color}

 

{color:#00}I think an OSS library for elliptic curve crypto with pairing is 
precious and essential.{color}

{color:#00}Moreover, ASF will be one of the safest place to develop crypto 
library from the viewpoint of problems among intellectual property 
rights.{color}

{color:#00}The library is the basis of everything we have developed in this 
project, so we can start from releasing it.{color}

  was:
{color:#00}The current roadmap suggests releasing the crypto library part 
(AMCL) first.{color}

{color:#00}[https://wiki.apache.org/incubator/MilagroRescueRoadmap|http://example.com/]{color}

{color:#00}Let's discuss the scope or an reboot plan for our project.{color}

 

{color:#00}I think an OSS library for elliptic curve crypto with pairing is 
precious and essential.{color}

{color:#00}Moreover, ASF will be one of the safest place to develop crypto 
library from the viewpoint of problems among intellectual property 
rights.{color}

{color:#00}The library is the basis of everything we have developed in this 
project, so we can start from releasing it.{color}


> Redefine our development scope
> --
>
> Key: MILAGRO-21
> URL: https://issues.apache.org/jira/browse/MILAGRO-21
> Project: Milagro
>  Issue Type: Task
>    Reporter: Go Yamamoto
>Priority: Major
>
> {color:#00}The current roadmap suggests releasing the crypto library part 
> (AMCL) first.{color}
> {color:#00}[https://wiki.apache.org/incubator/MilagroRescueRoadmap]{color}
> {color:#00}Let's discuss the scope or an reboot plan for our 
> project.{color}
>  
> {color:#00}I think an OSS library for elliptic curve crypto with pairing 
> is precious and essential.{color}
> {color:#00}Moreover, ASF will be one of the safest place to develop 
> crypto library from the viewpoint of problems among intellectual property 
> rights.{color}
> {color:#00}The library is the basis of everything we have developed in 
> this project, so we can start from releasing it.{color}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (MILAGRO-21) Redefine our development scope

[Go Yamamoto (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MILAGRO-21?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Go Yamamoto updated MILAGRO-21:
---
Description: 
{color:#00}The current roadmap suggests releasing the crypto library part 
(AMCL) first.{color}

{color:#00}[https://wiki.apache.org/incubator/MilagroRescueRoadmap|http://example.com/]{color}

{color:#00}[[https://wiki.apache.org/incubator/MilagroRescueRoadmap|http://example.com/]|[https://wiki.apache.org/incubator/MilagroRescueRoadmap|http://example.com/]]{color}

{color:#00}Let's discuss the scope or an reboot plan for our project.{color}

 

{color:#00}I think an OSS library for elliptic curve crypto with pairing is 
precious and essential.{color}

{color:#00}Moreover, ASF will be one of the safest place to develop crypto 
library from the viewpoint of problems among intellectual property 
rights.{color}

{color:#00}The library is the basis of everything we have developed in this 
project, so we can start from releasing it.{color}

  was:
{color:#00}The current roadmap suggests releasing the crypto library part 
(AMCL) first.{color}

{color:#00}[https://wiki.apache.org/incubator/MilagroRescueRoadmap|http://example.com/]]{color}

[[https://wiki.apache.org/incubator/MilagroRescueRoadmap|http://example.com/]|[https://wiki.apache.org/incubator/MilagroRescueRoadmap|http://example.com/]]

{color:#00}Let's discuss the scope or an reboot plan for our project.{color}

 

{color:#00}I think an OSS library for elliptic curve crypto with pairing is 
precious and essential.{color}

{color:#00}Moreover, ASF will be one of the safest place to develop crypto 
library from the viewpoint of problems among intellectual property 
rights.{color}

{color:#00}The library is the basis of everything we have developed in this 
project, so we can start from releasing it.{color}


> Redefine our development scope
> --
>
> Key: MILAGRO-21
> URL: https://issues.apache.org/jira/browse/MILAGRO-21
> Project: Milagro
>  Issue Type: Task
>    Reporter: Go Yamamoto
>Priority: Major
>
> {color:#00}The current roadmap suggests releasing the crypto library part 
> (AMCL) first.{color}
> {color:#00}[https://wiki.apache.org/incubator/MilagroRescueRoadmap|http://example.com/]{color}
> {color:#00}[[https://wiki.apache.org/incubator/MilagroRescueRoadmap|http://example.com/]|[https://wiki.apache.org/incubator/MilagroRescueRoadmap|http://example.com/]]{color}
> {color:#00}Let's discuss the scope or an reboot plan for our 
> project.{color}
>  
> {color:#00}I think an OSS library for elliptic curve crypto with pairing 
> is precious and essential.{color}
> {color:#00}Moreover, ASF will be one of the safest place to develop 
> crypto library from the viewpoint of problems among intellectual property 
> rights.{color}
> {color:#00}The library is the basis of everything we have developed in 
> this project, so we can start from releasing it.{color}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (MILAGRO-21) Redefine our development scope

[Go Yamamoto (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MILAGRO-21?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Go Yamamoto updated MILAGRO-21:
---
Description: 
{color:#00}The current roadmap suggests releasing the crypto library part 
(AMCL) first.{color}

{color:#00}[https://wiki.apache.org/incubator/MilagroRescueRoadmap|http://example.com/]]{color}

[[https://wiki.apache.org/incubator/MilagroRescueRoadmap|http://example.com/]|[https://wiki.apache.org/incubator/MilagroRescueRoadmap|http://example.com/]]

{color:#00}Let's discuss the scope or an reboot plan for our project.{color}

 

{color:#00}I think an OSS library for elliptic curve crypto with pairing is 
precious and essential.{color}

{color:#00}Moreover, ASF will be one of the safest place to develop crypto 
library from the viewpoint of problems among intellectual property 
rights.{color}

{color:#00}The library is the basis of everything we have developed in this 
project, so we can start from releasing it.{color}

  was:
{color:#00}The current roadmap suggests releasing the crypto library part 
(AMCL) first.{color}

{color:#00}[https://wiki.apache.org/incubator/MilagroRescueRoadmap|http://example.com/]{color}

 

{color:#00}Let's discuss the scope or an reboot plan for our project.{color}

 

{color:#00}I think an OSS library for elliptic curve crypto with pairing is 
precious and essential.{color}

{color:#00}Moreover, ASF will be one of the safest place to develop crypto 
library from the viewpoint of problems among intellectual property 
rights.{color}

{color:#00}The library is the basis of everything we have developed in this 
project, so we can start from releasing it.{color}


> Redefine our development scope
> --
>
> Key: MILAGRO-21
> URL: https://issues.apache.org/jira/browse/MILAGRO-21
> Project: Milagro
>  Issue Type: Task
>    Reporter: Go Yamamoto
>Priority: Major
>
> {color:#00}The current roadmap suggests releasing the crypto library part 
> (AMCL) first.{color}
> {color:#00}[https://wiki.apache.org/incubator/MilagroRescueRoadmap|http://example.com/]]{color}
> [[https://wiki.apache.org/incubator/MilagroRescueRoadmap|http://example.com/]|[https://wiki.apache.org/incubator/MilagroRescueRoadmap|http://example.com/]]
> {color:#00}Let's discuss the scope or an reboot plan for our 
> project.{color}
>  
> {color:#00}I think an OSS library for elliptic curve crypto with pairing 
> is precious and essential.{color}
> {color:#00}Moreover, ASF will be one of the safest place to develop 
> crypto library from the viewpoint of problems among intellectual property 
> rights.{color}
> {color:#00}The library is the basis of everything we have developed in 
> this project, so we can start from releasing it.{color}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (MILAGRO-21) Redefine our development scope

[Go Yamamoto (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MILAGRO-21?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Go Yamamoto updated MILAGRO-21:
---
Description: 
{color:#00}The current roadmap suggests releasing the crypto library part 
(AMCL) first.{color}

{color:#00}[https://wiki.apache.org/incubator/MilagroRescueRoadmap|http://example.com/]{color}

 

{color:#00}Let's discuss the scope or an reboot plan for our project.{color}

 

{color:#00}I think an OSS library for elliptic curve crypto with pairing is 
precious and essential.{color}

{color:#00}Moreover, ASF will be one of the safest place to develop crypto 
library from the viewpoint of problems among intellectual property 
rights.{color}

{color:#00}The library is the basis of everything we have developed in this 
project, so we can start from releasing it.{color}

  was:
{color:#00}The current roadmap suggests releasing the crypto library part 
(AMCL) first.{color}

{color:#00}[[https://wiki.apache.org/incubator/MilagroRescueRoadmap|http://example.com/]]{color}

 

{color:#00}Let's discuss the scope or an reboot plan for our project.{color}

 

{color:#00}I think an OSS library for elliptic curve crypto with pairing is 
precious and essential.{color}

{color:#00}Moreover, ASF will be one of the safest place to develop crypto 
library from the viewpoint of problems among intellectual property 
rights.{color}

{color:#00}The library is the basis of everything we have developed in this 
project, so we can start from releasing it.{color}


> Redefine our development scope
> --
>
> Key: MILAGRO-21
> URL: https://issues.apache.org/jira/browse/MILAGRO-21
> Project: Milagro
>  Issue Type: Task
>    Reporter: Go Yamamoto
>Priority: Major
>
> {color:#00}The current roadmap suggests releasing the crypto library part 
> (AMCL) first.{color}
> {color:#00}[https://wiki.apache.org/incubator/MilagroRescueRoadmap|http://example.com/]{color}
>  
> {color:#00}Let's discuss the scope or an reboot plan for our 
> project.{color}
>  
> {color:#00}I think an OSS library for elliptic curve crypto with pairing 
> is precious and essential.{color}
> {color:#00}Moreover, ASF will be one of the safest place to develop 
> crypto library from the viewpoint of problems among intellectual property 
> rights.{color}
> {color:#00}The library is the basis of everything we have developed in 
> this project, so we can start from releasing it.{color}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (MILAGRO-21) Redefine our development scope

[Go Yamamoto (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MILAGRO-21?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Go Yamamoto updated MILAGRO-21:
---
Description: 
{color:#00}The current roadmap suggests releasing the crypto library part 
(AMCL) first.{color}

{color:#00}[[https://wiki.apache.org/incubator/MilagroRescueRoadmap|http://example.com/]
 []|http://example.com/]{color}

 

{color:#00}Let's discuss the scope or an reboot plan for our project.{color}

 

{color:#00}I think an OSS library for elliptic curve crypto with pairing is 
precious and essential.{color}

{color:#00}Moreover, ASF will be one of the safest place to develop crypto 
library from the viewpoint of problems among intellectual property 
rights.{color}

{color:#00}The library is the basis of everything we have developed in this 
project, so we can start from releasing it.{color}

  was:
{color:#00}The current roadmap suggests releasing the crypto library part 
(AMCL) first.{color}

{color:#00}[https://wiki.apache.org/incubator/MilagroRescueRoadmap|http://example.com/]{color}

 

{color:#00}Let's discuss the scope or an reboot plan for our project.{color}

 

{color:#00}I think an OSS library for elliptic curve crypto with pairing is 
precious and essential.{color}

{color:#00}Moreover, ASF will be one of the safest place to develop crypto 
library from the viewpoint of problems among intellectual property 
rights.{color}

{color:#00}The library is the basis of everything we have developed in this 
project, so we can start from releasing it.{color}


> Redefine our development scope
> --
>
> Key: MILAGRO-21
> URL: https://issues.apache.org/jira/browse/MILAGRO-21
> Project: Milagro
>  Issue Type: Task
>    Reporter: Go Yamamoto
>Priority: Major
>
> {color:#00}The current roadmap suggests releasing the crypto library part 
> (AMCL) first.{color}
> {color:#00}[[https://wiki.apache.org/incubator/MilagroRescueRoadmap|http://example.com/]
>  []|http://example.com/]{color}
>  
> {color:#00}Let's discuss the scope or an reboot plan for our 
> project.{color}
>  
> {color:#00}I think an OSS library for elliptic curve crypto with pairing 
> is precious and essential.{color}
> {color:#00}Moreover, ASF will be one of the safest place to develop 
> crypto library from the viewpoint of problems among intellectual property 
> rights.{color}
> {color:#00}The library is the basis of everything we have developed in 
> this project, so we can start from releasing it.{color}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (MILAGRO-21) Redefine our development scope

[Go Yamamoto (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MILAGRO-21?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Go Yamamoto updated MILAGRO-21:
---
Description: 
{color:#00}The current roadmap suggests releasing the crypto library part 
(AMCL) first.{color}

{color:#00}[[https://wiki.apache.org/incubator/MilagroRescueRoadmap|http://example.com/]]{color}

 

{color:#00}Let's discuss the scope or an reboot plan for our project.{color}

 

{color:#00}I think an OSS library for elliptic curve crypto with pairing is 
precious and essential.{color}

{color:#00}Moreover, ASF will be one of the safest place to develop crypto 
library from the viewpoint of problems among intellectual property 
rights.{color}

{color:#00}The library is the basis of everything we have developed in this 
project, so we can start from releasing it.{color}

  was:
{color:#00}The current roadmap suggests releasing the crypto library part 
(AMCL) first.{color}

{color:#00}[[https://wiki.apache.org/incubator/MilagroRescueRoadmap|http://example.com/]
 []|http://example.com/]{color}

 

{color:#00}Let's discuss the scope or an reboot plan for our project.{color}

 

{color:#00}I think an OSS library for elliptic curve crypto with pairing is 
precious and essential.{color}

{color:#00}Moreover, ASF will be one of the safest place to develop crypto 
library from the viewpoint of problems among intellectual property 
rights.{color}

{color:#00}The library is the basis of everything we have developed in this 
project, so we can start from releasing it.{color}


> Redefine our development scope
> --
>
> Key: MILAGRO-21
> URL: https://issues.apache.org/jira/browse/MILAGRO-21
> Project: Milagro
>  Issue Type: Task
>    Reporter: Go Yamamoto
>Priority: Major
>
> {color:#00}The current roadmap suggests releasing the crypto library part 
> (AMCL) first.{color}
> {color:#00}[[https://wiki.apache.org/incubator/MilagroRescueRoadmap|http://example.com/]]{color}
>  
> {color:#00}Let's discuss the scope or an reboot plan for our 
> project.{color}
>  
> {color:#00}I think an OSS library for elliptic curve crypto with pairing 
> is precious and essential.{color}
> {color:#00}Moreover, ASF will be one of the safest place to develop 
> crypto library from the viewpoint of problems among intellectual property 
> rights.{color}
> {color:#00}The library is the basis of everything we have developed in 
> this project, so we can start from releasing it.{color}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: Project status - time to retire?

[Go Yamamoto]

Please ignore the difference of the colors by lines in my previous message if 
you are receiving in rich text format.
It happened by an accident because I am working in an unfamiliar environment.

Go
> On Sep 21, 2018, at 22:29, Go Yamamoto  wrote:
> 
> Hi Justin,
> 
> Thank you for the information.   
> I am glad that we are finding clue to get the same page.
> 
> (A) Access right issue
> Many committers have not signed the ICLA, and it blocks the access.  
> OK, it is a new knowledge to me.
> 
> Is the ICLA issue shared among PPMCs?
> Is somebody working to resolve the issue?
> I  think we should have recored the issue at project JIRA.
> 
> 
> (B) PPMC membership
> Justin thought I am a part of PPMC, but I have never imagined of it.
> This kind of gaps should never be happened in project management.
> 
> As far as I can find I have signed up as a committer.
> What is the process that authorize PPMC membership? 
> 
> 
> (C) Podling report
> I will be glad to submit podling reports.
> Justin, could you please guide me how to access previous reports and 
> discussions?
> Unfortunately I have never in the communication that prepares previous ones.  
>   
> 
> 
> Regards,
> Go Yamamoto
> 
> 
>> On Sep 21, 2018, at 18:24, Justin Mclean  wrote:
>> 
>> Hi,
>> 
>> Sorry if two similar email show up, but I think my first may of been lost.
>> 
>> Re the "access issue" I've look at you roster and the initial 
>> committers/PPMC list and it seems that 11 people didn't sign ICLAs, without 
>> an ICLA you cannot get access. Of the 5 who did (including yourself) I added 
>> them to the roster. Why this hadn't been done I've no idea as it's a simple 
>> process, so I'm not sure who you have been talking to to sort out these 
>> access issues. You can find the current roster here. [1] You did realise 
>> that you are actually part of the PPMC?
>> 
>> Thanks,
>> Justin
>> 
>> 1. https://whimsy.apache.org/roster/ppmc/milagro
> 

RE: RE: Project status - time to retire?

[Go Yamamoto]

Hi Justin,

We know the reports are missing, and that is why we have been requesting for 
help.
Our PMCs are contributed mainly by Miracl, and they say they have an external 
reason and will need time to decide continuing the contribution.

What is the blocker for ASF to help us to add PMC members?

Regards,
Go Yamamoto


-Original Message-
From: Justin Mclean [mailto:jmcl...@apache.org] 
Sent: Friday, September 14, 2018 11:04 PM
To: d...@milagro.apache.org
Subject: Re: RE: Project status - time to retire?

Hi,

Retire doesn't mean the project no longer exists, it can continue to live on 
somewhere (e.g GitHub), just not at the ASF. That's OK the ASF is not for 
everyone and a different way of operating as an open source project may be 
better for you.

The facts as I see them: You have missed multiple board reports in a row and 
repeated requests to submit one have been ignored. Your last submitted board 
report was in November 2017 [1] as far as I can tell, please correct me if I'm 
mistaken. Anyone can write the board report, even if your PPMC is missing.

It is a requirement that the reports are submitted quarterly, if you miss one 
(which is OK) they need to be submitted in the next month, so by my rough 
calculations that makes 10 months in a row this project has not reported. There 
is little to no email on this mailing list and it seems that any activity that 
is taking place external to the repos hosted at the ASF. 

Does anyone disagree with the above?

Given all this can someone tell me what benefit it will the project gain from 
continuing to be in the Apache incubator?

I'm sorry but I don't see that people are ready to jump in and help out here or 
they would of done that. I'm also sorry that you don't support the idea of 
retirement, but if there is no project oversight by the PPMC and activity is 
happening elsewhere then I can't see how project can continue in the Apache 
incubator. Currently I can't see how this project could graduate as a TLP 
Apache project without a lot of work.

If any of the mentors of this project disagree with anything I've said above 
please speak up, as you know this project far better than I.

Thanks,
Justin
V.P. Incubator

1. https://whimsy.apache.org/board/minutes/Milagro.html

Request for review

[Go Yamamoto]

Hi Nick and all,

 

Katsu has submitted the pull request on our repositories on GitHub.

https://github.com/apache/incubator-milagro

https://github.com/apache/incubator-milagro-crypto

 

We would like to commit this version of the crypto library as a release
candidate for the step.

Please check it and response how this project should review the pull
request.

 

Regards,

Go Yamamoto

 

Introducing a member from NTT

[Go Yamamoto]

Hi Team,

 

Let me introduce Katsuhiro Hirata from NTT group.

He have been working for the code for years internally, and I would like to
connect him directly with this loop.

 

We (participants from NTT) are working for identifying problems in producing
single golden version of AMCL library to resolve an issue in our JIRA.

He will have some points to discuss with this list.

 

Regards,

Go Yamamoto

 

 

RE: Milagro Rescue Roadmap

[Go Yamamoto]

Hi Nick and all,

The current roadmap suggests rescuing this project by releasing the crypto
library part (AMCL) first.
It is because the library is the basis of everything we have developed in
this project, and I believe it is an useful fundamental software.
Please share your concerns and issues if any.

I have created some issues from the roadmap at the project JIRA.
https://issues.apache.org/jira/projects/MILAGRO/issues/
https://wiki.apache.org/incubator/MilagroRescueRoadmap
Anyone who want to join the conversation can create your account at the ASF
JIRA by following "Sign up" link at Login.

Nick, please comment me if we have any problems in using this ASF JIRA as
the project JIRA.

We (people from NTT) have been collaborating with people from Miracl as
initial committers, and we recognize Miracl asked us to take over some tasks
for managing this project.
Our engineer team is ready to work on the code for re-scoping as long as it
is done by edits or minor modifications over existing code.

Regards,
Go Yamamoto

-Original Message-----
From: Go Yamamoto [mailto:g...@apache.org] 
Sent: Wednesday, May 09, 2018 12:33 AM
To: dev@milagro.incubator.apache.org
Subject: Re: Milagro Rescue Roadmap

Hi team,

I have updated the Milagro rescue wiki.  
Please feel free to comment the change.

I think we can start Step 1 immediately.
Nick, can you point someone who decide the project JIRA?

For Step 2, we will need to discuss the scope of the initial code at the
project repo.

I propose to start from the AMCL library, the crypto library for elliptic
curve operations with pairings.
It is the essential part that delivers unique value from this development
loop with crypto specialists. 

I think this minimal scope will also help our management easier because it
is unlikely to be influenced by business environments of participants.

Regards,
Go Yamamoto

[jira] [Updated] (MILAGRO-21) Redefine our development scope

[Go Yamamoto (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MILAGRO-21?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Go Yamamoto updated MILAGRO-21:
---
Description: 
{color:#00}The current roadmap suggests releasing the crypto library part 
(AMCL) first.{color}

{color:#00}[https://wiki.apache.org/incubator/MilagroRescueRoadmap|http://example.com/]{color}

 

{color:#00}Let's discuss the scope or an reboot plan for our project.{color}

 

{color:#00}I think an OSS library for elliptic curve crypto with pairing is 
precious and essential.{color}

{color:#00}Moreover, ASF will be one of the safest place to develop crypto 
library from the viewpoint of problems among intellectual property 
rights.{color}

{color:#00}The library is the basis of everything we have developed in this 
project, so we can start from releasing it.{color}

  was:
{color:#00}The current roadmap suggests releasing the crypto library part 
(AMCL) first.{color}

{color:#00}[https://wiki.apache.org/incubator/MilagroRescueRoadmap|http://example.com]{color}

 

{color:#00}Let's discuss the scope or an reboot plan for our project.{color}

 

{color:#00}I think an OSS library for elliptic curve crypto with pairing is 
precious and essential.{color}

{color:#00}Moreover, ASF will be one of the safest place to develop crypto 
library from the viewpoint of problems among intellectual property 
rights.{color}

{color:#00}The library is the basis of everything we developped in this 
project, so we can start from releasing it.{color}


> Redefine our development scope
> --
>
> Key: MILAGRO-21
> URL: https://issues.apache.org/jira/browse/MILAGRO-21
> Project: Milagro
>  Issue Type: Task
>    Reporter: Go Yamamoto
>Priority: Major
>
> {color:#00}The current roadmap suggests releasing the crypto library part 
> (AMCL) first.{color}
> {color:#00}[https://wiki.apache.org/incubator/MilagroRescueRoadmap|http://example.com/]{color}
>  
> {color:#00}Let's discuss the scope or an reboot plan for our 
> project.{color}
>  
> {color:#00}I think an OSS library for elliptic curve crypto with pairing 
> is precious and essential.{color}
> {color:#00}Moreover, ASF will be one of the safest place to develop 
> crypto library from the viewpoint of problems among intellectual property 
> rights.{color}
> {color:#00}The library is the basis of everything we have developed in 
> this project, so we can start from releasing it.{color}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (MILAGRO-21) Redefine our development scope

[Go Yamamoto (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MILAGRO-21?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Go Yamamoto updated MILAGRO-21:
---
Summary: Redefine our development scope  (was: Redefie our development 
scope)

> Redefine our development scope
> --
>
> Key: MILAGRO-21
> URL: https://issues.apache.org/jira/browse/MILAGRO-21
> Project: Milagro
>  Issue Type: Task
>    Reporter: Go Yamamoto
>Priority: Major
>
> {color:#00}The current roadmap suggests releasing the crypto library part 
> (AMCL) first.{color}
> {color:#00}[https://wiki.apache.org/incubator/MilagroRescueRoadmap|http://example.com]{color}
>  
> {color:#00}Let's discuss the scope or an reboot plan for our 
> project.{color}
>  
> {color:#00}I think an OSS library for elliptic curve crypto with pairing 
> is precious and essential.{color}
> {color:#00}Moreover, ASF will be one of the safest place to develop 
> crypto library from the viewpoint of problems among intellectual property 
> rights.{color}
> {color:#00}The library is the basis of everything we developped in this 
> project, so we can start from releasing it.{color}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (MILAGRO-21) Redefie our development scope

[Go Yamamoto (JIRA)]

Go Yamamoto created MILAGRO-21:
--

 Summary: Redefie our development scope
 Key: MILAGRO-21
 URL: https://issues.apache.org/jira/browse/MILAGRO-21
 Project: Milagro
  Issue Type: Task
Reporter: Go Yamamoto


{color:#00}The current roadmap suggests releasing the crypto library part 
(AMCL) first.{color}

{color:#00}[https://wiki.apache.org/incubator/MilagroRescueRoadmap|http://example.com]{color}

 

{color:#00}Let's discuss the scope or an reboot plan for our project.{color}

 

{color:#00}I think an OSS library for elliptic curve crypto with pairing is 
precious and essential.{color}

{color:#00}Moreover, ASF will be one of the safest place to develop crypto 
library from the viewpoint of problems among intellectual property 
rights.{color}

{color:#00}The library is the basis of everything we developped in this 
project, so we can start from releasing it.{color}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (MILAGRO-20) Review Recovery Roadmap

[Go Yamamoto (JIRA)]

Go Yamamoto created MILAGRO-20:
--

 Summary: Review Recovery Roadmap
 Key: MILAGRO-20
 URL: https://issues.apache.org/jira/browse/MILAGRO-20
 Project: Milagro
  Issue Type: Task
Reporter: Go Yamamoto


Milagro project needs actions for recovery.

The draft of the roadmap is here.

{color:#00}https://wiki.apache.org/incubator/MilagroRescueRoadmap{color}

 

Please comment anything you concern.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

RE: Milagro Rescue Roadmap

[Go Yamamoto]

Hi Nick,

Could you please give PMCs and initial committers write access to the Wiki
page?
https://wiki.apache.org/incubator/MilagroRescueRoadmap
I will update the wiki page to add our proposals.

The first problem to solve is lack of write access permissions for
committers at document sites and repositories.
We need write access to contribute ether it is documents or codes.

Regards,
Go Yamamoto





-Original Message-
From: Go Yamamoto [mailto:yamamoto...@lab.ntt.co.jp]
Sent: Saturday, April 21, 2018 3:34 AM
To: dev@milagro.incubator.apache.org
Subject: RE: Milagro Rescue Roadmap

Hi Nick and team,

Thank you for clarifying the problem.   I think we can discuss by agreeing
criteria that define what is work in Apache and what is donation.

In my opinion the difference is in the place where the ticket/review
processes are held.   The works at Apache will be a bunch of codes that
resolves tickets at Apache and that are reviewed and accepted by the Apache
project community.   All the other works can be thought as donations.

The codes in various milagro* repose are technically matured to work as the
MFA product as described in the project proposal as far as the engineers in
NTT play with them, and I suppose so is in Miracl too.  That is why no
significant changes are happening in recent months.   However it is obvious
that we need a lot of works to develop it as a matured open source software
that is widely used and is accepted as a fundamental software.

To start the works at Apache, I propose an immediate action list.
(1)　Prepare Milagro JIRA
　　a.If we can user https://issues.apache.org/jira/projects/MILAGRO/,
then provision accounts for committers and announce it as the project JIRA.
(2)　Prepare write access rights to committers at the official repository
(3)　Bind Milagro JIRA with the official repository at GitHub
(4)　Commit selected codes from various milagro* repos and accept as
donation.
　　a.　We need to discuss a roadmap to accept codes.
(5) Ticket problems at Milagro JIRA for further developments.

I propose to use Milagro JIRA not only for ticketing problems in the
development but in the management processes.  For example, I am an initial
committer of this project but I do not have a write access to the official
repository at GitHub, so it blocks for NTT to join the editorial works at
the official repository.   If we have JIRA, I can place a ticket that says
“I need write-access” and we can discuss how to resolve it.

Regards,
Go Yamamoto

-Original Message-
From: Nick Kew [mailto:n...@apache.org]
Sent: Thursday, April 19, 2018 11:28 PM
To: dev@milagro.incubator.apache.org
Subject: Re: Milagro Rescue Roadmap

On Tue, 17 Apr 2018 19:46:36 +0900
"Go Yamamoto" <yamamoto...@lab.ntt.co.jp> wrote:

> Hi Milagro team,
>
> We need to talk to update the wiki page.

Indeed.

> I have a question, what is our definition of "place elsewhere"?
>
> Because of the nature of the pull-request driven workflow, the code is
> updated at each participant's fork repository first.
> Does anybody think it is developed in a place elsewhere than Apache
> for this situation?

The issue isn't that individual developers work in their own forks from time
to time.  Or even most of the time.  That's fine.
What's not fine is that great swathes of work happen elsewhere and appear as
a big code dump!  That's a donation, and the idea of incubation is that we
*start* with a donation and work in the open thereafter!

The issue is that nothing seems to be happening at all at apache.
The last commit that does anything (and that just fixing a URL) was on
October 17th.  And nothing before that since 2016, when we thought activity
was initial project setup!
Meanwhile, as John pointed out, development seems to be happening
elsewhere: various milagro* repos at github.  The bundle John cited as an
example:
https://git1-us-west.apache.org/repos/asf?p=incubator-milagro-mfa-server.git
;a=log
looks to me like a lot more than a developer's working branch!


> If yes, then is it a problem to solve in managing this project?

It's a roadmap we want right now.  Why is nothing happening at Apache?  Does
the project really want to work at Apache (bearing in mind, working
elsewhere and dumping code to Apache is not a solution)?  Are all the team
on board?

I'm looking to you (everyone@milagro) to think through how work can migrate
to apache, and commit to migrating.  Then flesh out that roadmap!

Note that on the infrastructure side, we can do more now than when Milagro
first entered incubation.  I think gitbox is likely to feature in the
roadmap, if folks will use it!

--
Nick Kew

RE: Milagro Rescue Roadmap

[Go Yamamoto]

Hi Nick and team,

Thank you for clarifying the problem.   I think we can discuss by agreeing
criteria that define what is work in Apache and what is donation.

In my opinion the difference is in the place where the ticket/review
processes are held.   The works at Apache will be a bunch of codes that
resolves tickets at Apache and that are reviewed and accepted by the Apache
project community.   All the other works can be thought as donations.

The codes in various milagro* repose are technically matured to work as the
MFA product as described in the project proposal as far as the engineers in
NTT play with them, and I suppose so is in Miracl too.  That is why no
significant changes are happening in recent months.   However it is obvious
that we need a lot of works to develop it as a matured open source software
that is widely used and is accepted as a fundamental software.

To start the works at Apache, I propose an immediate action list.
(1)　Prepare Milagro JIRA
　　a.If we can user https://issues.apache.org/jira/projects/MILAGRO/,
then provision accounts for committers and announce it as the project JIRA.
(2)　Prepare write access rights to committers at the official repository
(3)　Bind Milagro JIRA with the official repository at GitHub
(4)　Commit selected codes from various milagro* repos and accept as
donation.
　　a.　We need to discuss a roadmap to accept codes.
(5) Ticket problems at Milagro JIRA for further developments.

I propose to use Milagro JIRA not only for ticketing problems in the
development but in the management processes.  For example, I am an initial
committer of this project but I do not have a write access to the official
repository at GitHub, so it blocks for NTT to join the editorial works at
the official repository.   If we have JIRA, I can place a ticket that says
“I need write-access” and we can discuss how to resolve it.

Regards,
Go Yamamoto

-Original Message-
From: Nick Kew [mailto:n...@apache.org]
Sent: Thursday, April 19, 2018 11:28 PM
To: dev@milagro.incubator.apache.org
Subject: Re: Milagro Rescue Roadmap

On Tue, 17 Apr 2018 19:46:36 +0900
"Go Yamamoto" <yamamoto...@lab.ntt.co.jp> wrote:

> Hi Milagro team,
>
> We need to talk to update the wiki page.

Indeed.

> I have a question, what is our definition of "place elsewhere"?
>
> Because of the nature of the pull-request driven workflow, the code is
> updated at each participant's fork repository first.
> Does anybody think it is developed in a place elsewhere than Apache
> for this situation?

The issue isn't that individual developers work in their own forks from time
to time.  Or even most of the time.  That's fine.
What's not fine is that great swathes of work happen elsewhere and appear as
a big code dump!  That's a donation, and the idea of incubation is that we
*start* with a donation and work in the open thereafter!

The issue is that nothing seems to be happening at all at apache.
The last commit that does anything (and that just fixing a URL) was on
October 17th.  And nothing before that since 2016, when we thought activity
was initial project setup!
Meanwhile, as John pointed out, development seems to be happening
elsewhere: various milagro* repos at github.  The bundle John cited as an
example:
https://git1-us-west.apache.org/repos/asf?p=incubator-milagro-mfa-server.git
;a=log
looks to me like a lot more than a developer's working branch!


> If yes, then is it a problem to solve in managing this project?

It's a roadmap we want right now.  Why is nothing happening at Apache?  Does
the project really want to work at Apache (bearing in mind, working
elsewhere and dumping code to Apache is not a solution)?  Are all the team
on board?

I'm looking to you (everyone@milagro) to think through how work can migrate
to apache, and commit to migrating.  Then flesh out that roadmap!

Note that on the infrastructure side, we can do more now than when Milagro
first entered incubation.  I think gitbox is likely to feature in the
roadmap, if folks will use it!

--
Nick Kew

RE: Milagro Rescue Roadmap

[Go Yamamoto]

Hi Milagro team,

We need to talk to update the wiki page.

I have a question, what is our definition of "place elsewhere"?

Because of the nature of the pull-request driven workflow, the code is
updated at each participant's fork repository first. 
Does anybody think it is developed in a place elsewhere than Apache for this
situation?
If yes, then is it a problem to solve in managing this project?

Regards,
Go Yamamoto

-Original Message-
From: Nick Kew [mailto:n...@apache.org] 
Sent: Saturday, April 14, 2018 7:22 AM
To: gene...@incubator.apache.org; dev@milagro.incubator.apache.org
Subject: Re: Milagro Rescue Roadmap

On Thu, 12 Apr 2018 16:35:25 +0100
Nick Kew <n...@apache.org> wrote:

> Posting to both dev@milagro and general@incubator.

> Would folks be happy for me to set up a page for this purpose under 
> wiki/incubator?  I would propose a skeleton (mainly a set of headings) 
> and look to the community to flesh it out.
> 

OK, I've created a skeleton
https://wiki.apache.org/incubator/MilagroRescueRoadmap

With a list of headings based on my understanding of the situation.  I hope
others will review and improve my list, clarify the issues listed, and fill
in the big blanks.  If this can grow to a credible roadmap by the end of
April, I think we have the basis of a rescue!

Direct edits to the wiki are great.  If unsure about an idea, either add it
there as tentative, or discuss on-list.
Or of course both!

--
Nick Kew

RE: [VOTE] Retire Milagro

[Go Yamamoto]

Hi Nick,

Thank you for understanding the pull-request driven workflow.  We, this
Apache incubator project, need management on operation at
github/apache/incubator-milagro because it is in the critical path of the
pull-request driven workflow.  That is the reason why I am offering the
effort for the management as a participant of the project.  

We appreciate if you are happy to take a part in the management too.  I do
not think you are a man-in-the-middle because you have a role that connects
this project with the Apache eco-system.  Let's go forward together.

Regards,
Go Yamamoto

-Original Message-
From: Nick Kew [mailto:n...@apache.org] 
Sent: Tuesday, April 10, 2018 11:55 PM
To: dev@milagro.incubator.apache.org
Subject: Re: [VOTE] Retire Milagro

On Tue, 10 Apr 2018 16:30:25 +0900
"Go Yamamoto" <yamamoto...@lab.ntt.co.jp> wrote:

> Hi Nick,
> 
> I agree the infrastructure problem you have pointed out

My problem is that I'm man-in-the-middle here.  I have an incomplete
understanding of what you're looking for, including your first paragraph.

> We NTT request to allow for contributors to work at their own fork 
> repository.  All the changes on the code happens at local fork 
> repositories owned by each contributor, however, the changes at local 
> fork will be pull-requested to the official repo, and the operation 
> team at the official repo will review the pull-request and merge it to 
> the official.

Yes, that's normal.  Though as much as possible of that forked work should
take place in public repos, too: that's what git is good at!
I'd expect most local private forks to have a lifetime of just a few days -
while the developer works through an issue - before either becoming public
or abandoned.

> If this workflow is OK for everybody here, NTT would like to take the 
> effort of operational tasks and managements on the official repo at 
> least until we reach the first release.

How is that bringing the work to Apache?

--
Nick Kew

RE: [VOTE] Retire Milagro

[Go Yamamoto]

Hi Nick,

I agree the infrastructure problem you have pointed out have been blocking
the initial commit, and it blocks everything toward the release.  To solve
the problem, I think all what we need is the operational management at the
official github repo.  It is hard to solve the problem technologically
because Miracl's engineering team (and ours too) want to use CI tools, and
it means OAuth grants for access by the CI tools must be managed at the
repository on which they work.

We NTT request to allow for contributors to work at their own fork
repository.  All the changes on the code happens at local fork repositories
owned by each contributor, however, the changes at local fork will be
pull-requested to the official repo, and the operation team at the official
repo will review the pull-request and merge it to the official.  

If this workflow is OK for everybody here, NTT would like to take the effort
of operational tasks and managements on the official repo at least until we
reach the first release. 

I sincerely hope this proposal would contribute in resolving the blocker.
Please feel free to share your concerns if any.

Regards,
Go Yamamoto

-Original Message-
From: Nick Kew [mailto:n...@apache.org] 
Sent: Tuesday, April 10, 2018 8:07 AM
To: dev@milagro.incubator.apache.org
Subject: Re: [VOTE] Retire Milagro

On Sun, 08 Apr 2018 14:16:09 +
"John D. Ament" <johndam...@apache.org> wrote:

> All,
> 
> This is a call to vote to retire the Milagro podling.

+-0.  Subject to change in either direction.

For a long time, this project has not been happening at Apache, and on that
basis retirement seems appropriate.
My past attempts to prod it have met with no response[1].

On the other hand, some more promising activity has recently been seen on
this list, notably with the arrival of NTT folks and an active newcomer who
I've only just realised isn't an initial committer from the Miracl team!

I have been meaning for some time to try once more to prod it and would be
reluctant to vote for retirement before doing so.
I've been doing battle with a failing internet connection, but I've now
parted company with the ISP in question.
So hopefully I'll now be fine to review all list traffic since [1] and post
thoughts within 24 hours.

> Here are the documented problems:
> 
> - Development does not happen at Apache.  This is confirmed in changes 
> like [1] where you are trying to repoint mirrors away from the Apache 
> hosted repository into a Miracl hosted repository.

At the time the repos were created, there was an issue with folks being less
than happy with the level of github integration then available.  I touched
on this in [1], but should no doubt have been clearer.  IF THERE ARE
INFRASTRUCTURE ISSUES HOLDING THINGS BACK, THE TEAM NEEDS TO SPEAK UP!

> - No board report submitted for months.

Indeed, someone from the team needs to take responsibility.
In the early days I did too much of this myself, but it's not supposed to be
a mentor task!

[1] Most recently
http://mail-archives.apache.org/mod_mbox/milagro-dev/201711.mbox/%3C15102433
30.26629.45.camel%40mimir.webthing.com%3E

--
Nick Kew

RE: Platform dependency

[Go Yamamoto]

Hi Giorgio

We (NTT) are ready to take the effort at the minimum level, so we need 
communication with the PMC team.

We think the first step is to release the crypto library part at the official 
repository because it is the base.
The idea also should be discussed here.

Assuming we work for the release of crypto library first, I think we can start 
from 2-3 reviewers and one core editor.
After the first step we will need more reviewers.  
Probably 4-5 in ideal since some may review the frontend and some may the 
server side.

The reviewers had better be coming from different organizations, but I think it 
is optional at the beginning.

Regards,
Go Yamamoto


-Original Message-
From: Giorgio Zoppi [mailto:giorgio.zo...@gmail.com] 
Sent: Tuesday, April 03, 2018 12:12 AM
To: dev@milagro.incubator.apache.org
Subject: Re: Platform dependency

Hello Go,
The answer is when? How much resources (developer) do you need? I might spread 
the voices throughs meetup.
Best Regards,
Giorgio.


2018-04-02 10:58 GMT+02:00 Go Yamamoto <yamamoto...@lab.ntt.co.jp>:

> As far as I understand the official repository is here.
> https://github.com/apache/incubator-milagro
> The contents have been unchanged for 2 years while actual development 
> works have been active in other repositories.
>
> I think the problem is in lack of human resources for review/edit 
> pull-requests at the master repository.
> We need such active editorial efforts at the master repository to 
> support modern development style with CI/CD.
> CI/CD workflows require a fork repository at each organization, and 
> releases from organizations will be merged to the master by pull-requests.
> However nobody has been working for the role so far.
>
> NTT would like to solve the issue by taking the role, and would like 
> to join the management  loop of this project because we need to 
> discuss/define criterion for review and edit.
>
> Regards,
> Go Yamamoto
>
>
> -Original Message-
> From: Giorgio Zoppi [mailto:giorgio.zo...@gmail.com]
> Sent: Saturday, March 31, 2018 8:29 PM
> To: dev@milagro.incubator.apache.org
> Subject: Re: Platform dependency
>
> Ok,
> it is a mess to have spread repositories in two sites. I will expect 
> to have directly in the Apache ASF. I don't know which is the direct 
> repository.  For now i have been able to build the lib on ubuntu with 
> github no apache repo I am bit confused about 11 repos at Apache, 
> which code is not updated since 2 years..What is the block (to remove) 
> to move your current repository to apache? And when will be the first 
> release of at least the library? Can I help in planning and merging 
> the repositories?  If we dont release often, we cannot spread the 
> voice, integrate iwth other apache products and the community will not grow.
> Best Regards,
> Giorgio.
>
> 2018-03-29 9:31 GMT+02:00 Go Yamamoto <yamamoto...@lab.ntt.co.jp>:
>
> > Milagro MFA is designed without depending on specific frameworks, 
> > and it should work with react, too.
> >
> > If you mean native is a custom authentication module, the answer is no.
> > However, it should work with react using an LDAP authentication 
> > module and I hope this would answer your question.
> >
> > The code we have been trying to commit includes an LDAP wrapper that 
> > replaces the standard password authentication with Milagoro MFA.  As 
> > we demonstrated at ApachCon, Milagro MFA works with Django, 
> > WordPress, Drupal, and many other applications.
> >
> > Regards,
> > Go Yamamoto
> >
> > -Original Message-
> > From: Giorgio Zoppi [mailto:giorgio.zo...@gmail.com]
> > Sent: Thursday, March 29, 2018 4:58 AM
> > To: dev@milagro.incubator.apache.org
> > Subject: Re: RE: [DISCUSS] Retire Milagro
> >
> > Can be used milagro with react native? I mean the autentication.
> >
> >
> > 2018-03-12 10:13 GMT+01:00 Go Yamamoto <yamamoto...@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:johndam.

RE: Platform dependency

[Go Yamamoto]

Hi Giorgio,
Milagro MFA just replaces password authentication with MFA, so session tokens 
remains untouched.  REST would work with native authentication token.
Please share your use case if you have any issue or concern.

Go

-Original Message-
From: Giorgio Zoppi [mailto:giorgio.zo...@gmail.com] 
Sent: Friday, March 30, 2018 1:48 AM
To: dev@milagro.incubator.apache.org
Subject: Re: Platform dependency

Hi Go,
i mean in the current infrastructure can i use a REST webservice and that gives 
to React native an autentication token or something similar.
Giorgio.

2018-03-29 9:31 GMT+02:00 Go Yamamoto <yamamoto...@lab.ntt.co.jp>:

> Milagro MFA is designed without depending on specific frameworks, and 
> it should work with react, too.
>
> If you mean native is a custom authentication module, the answer is no.
> However, it should work with react using an LDAP authentication module 
> and I hope this would answer your question.
>
> The code we have been trying to commit includes an LDAP wrapper that 
> replaces the standard password authentication with Milagoro MFA.  As 
> we demonstrated at ApachCon, Milagro MFA works with Django, WordPress, 
> Drupal, and many other applications.
>
> Regards,
> Go Yamamoto
>
> -Original Message-
> From: Giorgio Zoppi [mailto:giorgio.zo...@gmail.com]
> Sent: Thursday, March 29, 2018 4:58 AM
> To: dev@milagro.incubator.apache.org
> Subject: Re: RE: [DISCUSS] Retire Milagro
>
> Can be used milagro with react native? I mean the autentication.
>
>
> 2018-03-12 10:13 GMT+01:00 Go Yamamoto <yamamoto...@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:johndam...@apache.org]
> > Sent: Sunday, March 11, 2018 10:34 PM
> > To: d...@milagro.apache.org
> > Subject: Re: RE: [DISCUSS] Retire Milagro
> >
> >
> >
> > On 2018/03/08 05:20:41, "Go Yamamoto" <yamamoto...@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.stoi...@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 
> > > <giorgio.zo...@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 <yamamoto...@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

Platform dependency

[Go Yamamoto]

Milagro MFA is designed without depending on specific frameworks, and it should 
work with react, too.

If you mean native is a custom authentication module, the answer is no.  
However, it should work with react using an LDAP authentication module and I 
hope this would answer your question.

The code we have been trying to commit includes an LDAP wrapper that replaces 
the standard password authentication with Milagoro MFA.  As we demonstrated at 
ApachCon, Milagro MFA works with Django, WordPress, Drupal, and many other 
applications.

Regards,
Go Yamamoto

-Original Message-
From: Giorgio Zoppi [mailto:giorgio.zo...@gmail.com] 
Sent: Thursday, March 29, 2018 4:58 AM
To: dev@milagro.incubator.apache.org
Subject: Re: RE: [DISCUSS] Retire Milagro

Can be used milagro with react native? I mean the autentication.


2018-03-12 10:13 GMT+01:00 Go Yamamoto <yamamoto...@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:johndam...@apache.org]
> Sent: Sunday, March 11, 2018 10:34 PM
> To: d...@milagro.apache.org
> Subject: Re: RE: [DISCUSS] Retire Milagro
>
>
>
> On 2018/03/08 05:20:41, "Go Yamamoto" <yamamoto...@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.stoi...@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 
> > <giorgio.zo...@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 <yamamoto...@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.zo...@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 <yamamoto...@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
> > > > >
> > > > > -Orig

RE: [DISCUSS] Retire Milagro

[Go Yamamoto]

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.stoi...@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 <giorgio.zo...@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 <yamamoto...@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.zo...@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 <yamamoto...@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...@lab.ntt.co.jp]
> > > Sent: Friday, February 09, 2018 1:24 PM
> > > To: 'dev@milagro.incubator.apache.org'
> > > <dev@milagro.incubator.apache.org>
> > > Subject: RE: [DISCUSS] Retire Milagro
> > >
> > > Simeon, please tell us whatever you need.
> > > I think it is obvious that the leadership team is responsible to 
> > > present a roadmap.
> > > I will be always willing to participate or to help.
> > >
> > > Go
> > >
> > > -Original Message-
> > > From: Giorgio Zoppi [mailto:giorgio.zo...@gmail.com]
> > > Sent: Thursday, February 08, 2018 8:01 PM
> > > To: dev@milagro.incubator.apache.org
> > > Subject: Re: [DISCUSS] Retire Milagro
> > >
> > > If there is a clear roadmap. You can decide to assign some tickets 
> > > to me and i will help.
> > >
> > > 2018-02-07 10:13 GMT+01:00 Simeon Aladjem <simeon.alad...@miracl.com>:
> > >
> > > > Hello,
> > > >
> > > > Sorry for being out of pocket for a while and not being able to 
> > > > participate in the discussion.
> > > >
> > > > Re the repositories reorganization - it hasn't been really clear 
> > > > how this needs to be done from a procedural stand point.
> > > > None of the contributors have the permissions to manipulate the 
> > > > project repositories, and AFAIK, only the project mentors can do 
> > > > that, but what needs to be done in order for this to happen, 
> > > > hasn't
> > been clear.
> > > > This was one of our pain points along the way.
> > > >
> > > > Re the roadmap - as I already mentioned, MIRACL didn't have 
> > > > resources to lead the project, but the question is - in a 
> > > > community like this, who is responsible to craft a roadmap?
> > > > The discussed direction is to focus the project on the crypto 
> > > > library, with which MIRACL and NTT agree, and I guess if/when 
> > > > NTT take the leading role on the project, they can propose a roadmap.
> > > >
> > > > We also have a more developed version of the crypto, with full 
> > > > unit-test coverage, which we can merge to the project when we 
> > > > figure-out th

RE: [DISCUSS] Retire Milagro

[Go Yamamoto]

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.zo...@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 <yamamoto...@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...@lab.ntt.co.jp]
> Sent: Friday, February 09, 2018 1:24 PM
> To: 'dev@milagro.incubator.apache.org' 
> <dev@milagro.incubator.apache.org>
> Subject: RE: [DISCUSS] Retire Milagro
>
> Simeon, please tell us whatever you need.
> I think it is obvious that the leadership team is responsible to 
> present a roadmap.
> I will be always willing to participate or to help.
>
> Go
>
> -Original Message-
> From: Giorgio Zoppi [mailto:giorgio.zo...@gmail.com]
> Sent: Thursday, February 08, 2018 8:01 PM
> To: dev@milagro.incubator.apache.org
> Subject: Re: [DISCUSS] Retire Milagro
>
> If there is a clear roadmap. You can decide to assign some tickets to 
> me and i will help.
>
> 2018-02-07 10:13 GMT+01:00 Simeon Aladjem <simeon.alad...@miracl.com>:
>
> > Hello,
> >
> > Sorry for being out of pocket for a while and not being able to 
> > participate in the discussion.
> >
> > Re the repositories reorganization - it hasn't been really clear how 
> > this needs to be done from a procedural stand point.
> > None of the contributors have the permissions to manipulate the 
> > project repositories, and AFAIK, only the project mentors can do 
> > that, but what needs to be done in order for this to happen, hasn't been 
> > clear.
> > This was one of our pain points along the way.
> >
> > Re the roadmap - as I already mentioned, MIRACL didn't have 
> > resources to lead the project, but the question is - in a community 
> > like this, who is responsible to craft a roadmap?
> > The discussed direction is to focus the project on the crypto 
> > library, with which MIRACL and NTT agree, and I guess if/when NTT 
> > take the leading role on the project, they can propose a roadmap.
> >
> > We also have a more developed version of the crypto, with full 
> > unit-test coverage, which we can merge to the project when we 
> > figure-out the repositories issue.
> >
> > Kind Regards,
> > Simeon Aladjem
> >
> > On 5/2/18, 6:49, "Go Yamamoto" <yamamoto...@lab.ntt.co.jp> wrote:
> >
> > We have been talking with Simeon and Kealan about the roadmap.
> > We think it will make sense if we release the crypto library 
> > first, and then the authentication server/clients second.  What do 
> > we need to authorize the plan?
> >
> > So far the code in the library looks mature and we have found no 
> > problems in actual use in our engineering activities.
> > It could be better to work for test codes more before the crypto 
> > library released since the current code does not seem to cover 
> > sub-normal cases necessarily.
> > It does not mean I think the improvements on test codes are 
> > required for the first release, they will at least help further 
> > development activities.
> >
> > BTW, our repository contains a lot of possible contributions on 
> > test codes.
> > I believe the code will help users and developers if they are merged.
> >
> > Regards,
> > Go Yamamoto
> >
> > -Original Message-
> > From: Giorgio Zoppi [mailto:giorgio.zo...@gmail.com]
> > Sent: Wednesday, January 31, 2018 6:29 AM
> > To: dev@milagro.incubator.apache.org
> > Subject: Re: [DISCUSS] Retire Milagro
> >
> > BTW,
> > do you have a roadmap? Do you want to support hardware as well? 
> > IS there  a todo list of things? When do you plan next release?
> >

RE: [DISCUSS] Retire Milagro

[Go Yamamoto]

All,

We again request to discuss renewing the roadmap and to start the official 
repository to share the codes we have worked for years.
Kelean, what do you think is blocking this obvious task?

If this project needs help in management, we are willing to participate.

Regards,
Go Yamamto

-Original Message-
From: Go Yamamoto [mailto:yamamoto...@lab.ntt.co.jp] 
Sent: Friday, February 09, 2018 1:24 PM
To: 'dev@milagro.incubator.apache.org' <dev@milagro.incubator.apache.org>
Subject: RE: [DISCUSS] Retire Milagro

Simeon, please tell us whatever you need.
I think it is obvious that the leadership team is responsible to present a 
roadmap.  
I will be always willing to participate or to help.

Go

-Original Message-
From: Giorgio Zoppi [mailto:giorgio.zo...@gmail.com]
Sent: Thursday, February 08, 2018 8:01 PM
To: dev@milagro.incubator.apache.org
Subject: Re: [DISCUSS] Retire Milagro

If there is a clear roadmap. You can decide to assign some tickets to me and i 
will help.

2018-02-07 10:13 GMT+01:00 Simeon Aladjem <simeon.alad...@miracl.com>:

> Hello,
>
> Sorry for being out of pocket for a while and not being able to 
> participate in the discussion.
>
> Re the repositories reorganization - it hasn't been really clear how 
> this needs to be done from a procedural stand point.
> None of the contributors have the permissions to manipulate the 
> project repositories, and AFAIK, only the project mentors can do that, 
> but what needs to be done in order for this to happen, hasn't been clear.
> This was one of our pain points along the way.
>
> Re the roadmap - as I already mentioned, MIRACL didn't have resources 
> to lead the project, but the question is - in a community like this, 
> who is responsible to craft a roadmap?
> The discussed direction is to focus the project on the crypto library, 
> with which MIRACL and NTT agree, and I guess if/when NTT take the 
> leading role on the project, they can propose a roadmap.
>
> We also have a more developed version of the crypto, with full 
> unit-test coverage, which we can merge to the project when we 
> figure-out the repositories issue.
>
> Kind Regards,
> Simeon Aladjem
>
> On 5/2/18, 6:49, "Go Yamamoto" <yamamoto...@lab.ntt.co.jp> wrote:
>
> We have been talking with Simeon and Kealan about the roadmap.
> We think it will make sense if we release the crypto library 
> first, and then the authentication server/clients second.  What do we 
> need to authorize the plan?
>
> So far the code in the library looks mature and we have found no 
> problems in actual use in our engineering activities.
> It could be better to work for test codes more before the crypto 
> library released since the current code does not seem to cover 
> sub-normal cases necessarily.
> It does not mean I think the improvements on test codes are 
> required for the first release, they will at least help further 
> development activities.
>
> BTW, our repository contains a lot of possible contributions on 
> test codes.
> I believe the code will help users and developers if they are merged.
>
> Regards,
> Go Yamamoto
>
> -Original Message-
> From: Giorgio Zoppi [mailto:giorgio.zo...@gmail.com]
> Sent: Wednesday, January 31, 2018 6:29 AM
> To: dev@milagro.incubator.apache.org
> Subject: Re: [DISCUSS] Retire Milagro
>
> BTW,
> do you have a roadmap? Do you want to support hardware as well? IS 
> there  a todo list of things? When do you plan next release?
>
> 2018-01-30 22:26 GMT+01:00 Giorgio Zoppi <giorgio.zo...@gmail.com>:
>
> > Hello everybody,
> > is there any way to save just the crypto library inside Apache? The
> > server  doenst make sense, there is no valuable code.
> > The crypto library including mpin protocol can be used from other
>     > projects. Currently there is no community.
> >
> >
> > 2018-01-30 22:12 GMT+01:00 John D. Ament <johndam...@apache.org>:
> >
> >> Simeon,
> >>
> >> In order for that to happen, someone would need to make sure Go
> >> Yamamoto has write access to the repositories.  I'm not sure 
> that has happened.
> >>
> >> John
> >>
> >> On 2018/01/30 14:49:07, Simeon Aladjem 
> <simeon.alad...@miracl.com>
> wrote:
> >> > Hi all,
> >> >
> >> > As a part of MIRACL, I feel that I have to provide our perspective
> >> > on
> >> the project.
> >> >
> >> > First of all, we did disengage with the idea to move the Milagro
> >&

RE: [DISCUSS] Retire Milagro

[Go Yamamoto]

Simeon, please tell us whatever you need.
I think it is obvious that the leadership team is responsible to present a 
roadmap.  
I will be always willing to participate or to help.

Go

-Original Message-
From: Giorgio Zoppi [mailto:giorgio.zo...@gmail.com] 
Sent: Thursday, February 08, 2018 8:01 PM
To: dev@milagro.incubator.apache.org
Subject: Re: [DISCUSS] Retire Milagro

If there is a clear roadmap. You can decide to assign some tickets to me and i 
will help.

2018-02-07 10:13 GMT+01:00 Simeon Aladjem <simeon.alad...@miracl.com>:

> Hello,
>
> Sorry for being out of pocket for a while and not being able to 
> participate in the discussion.
>
> Re the repositories reorganization - it hasn't been really clear how 
> this needs to be done from a procedural stand point.
> None of the contributors have the permissions to manipulate the 
> project repositories, and AFAIK, only the project mentors can do that, 
> but what needs to be done in order for this to happen, hasn't been clear.
> This was one of our pain points along the way.
>
> Re the roadmap - as I already mentioned, MIRACL didn't have resources 
> to lead the project, but the question is - in a community like this, 
> who is responsible to craft a roadmap?
> The discussed direction is to focus the project on the crypto library, 
> with which MIRACL and NTT agree, and I guess if/when NTT take the 
> leading role on the project, they can propose a roadmap.
>
> We also have a more developed version of the crypto, with full 
> unit-test coverage, which we can merge to the project when we 
> figure-out the repositories issue.
>
> Kind Regards,
> Simeon Aladjem
>
> On 5/2/18, 6:49, "Go Yamamoto" <yamamoto...@lab.ntt.co.jp> wrote:
>
> We have been talking with Simeon and Kealan about the roadmap.
> We think it will make sense if we release the crypto library 
> first, and then the authentication server/clients second.  What do we 
> need to authorize the plan?
>
> So far the code in the library looks mature and we have found no 
> problems in actual use in our engineering activities.
> It could be better to work for test codes more before the crypto 
> library released since the current code does not seem to cover 
> sub-normal cases necessarily.
> It does not mean I think the improvements on test codes are 
> required for the first release, they will at least help further 
> development activities.
>
> BTW, our repository contains a lot of possible contributions on 
> test codes.
> I believe the code will help users and developers if they are merged.
>
> Regards,
> Go Yamamoto
>
> -Original Message-
> From: Giorgio Zoppi [mailto:giorgio.zo...@gmail.com]
> Sent: Wednesday, January 31, 2018 6:29 AM
> To: dev@milagro.incubator.apache.org
> Subject: Re: [DISCUSS] Retire Milagro
>
> BTW,
> do you have a roadmap? Do you want to support hardware as well? IS 
> there  a todo list of things? When do you plan next release?
>
> 2018-01-30 22:26 GMT+01:00 Giorgio Zoppi <giorgio.zo...@gmail.com>:
>
> > Hello everybody,
> > is there any way to save just the crypto library inside Apache? The
> > server  doenst make sense, there is no valuable code.
> > The crypto library including mpin protocol can be used from other
> > projects. Currently there is no community.
> >
> >
> > 2018-01-30 22:12 GMT+01:00 John D. Ament <johndam...@apache.org>:
> >
> >> Simeon,
> >>
> >> In order for that to happen, someone would need to make sure Go
> >> Yamamoto has write access to the repositories.  I'm not sure 
> that has happened.
> >>
> >> John
> >>
> >> On 2018/01/30 14:49:07, Simeon Aladjem 
> <simeon.alad...@miracl.com>
> wrote:
> >> > Hi all,
> >> >
> >> > As a part of MIRACL, I feel that I have to provide our perspective
> >> > on
> >> the project.
> >> >
> >> > First of all, we did disengage with the idea to move the Milagro
> >> > Crypto
> >> code elsewhere.
> >> > All the code under the Milagro project refers to the crypto
> >> > repository
> >> that is under Apache, so https://github.com/milagro-crypto doesn't
> >> directly affect the project at the current.
> >> >
> >> > It does contain a more developed version of the original Milagro
>     >> > Crypto
> >> code, which will eventually find its way to the project,
> 

RE: [DISCUSS] Retire Milagro

[Go Yamamoto]

We have been talking with Simeon and Kealan about the roadmap.  
We think it will make sense if we release the crypto library first, and then 
the authentication server/clients second.  What do we need to authorize the 
plan?

So far the code in the library looks mature and we have found no problems in 
actual use in our engineering activities.
It could be better to work for test codes more before the crypto library 
released since the current code does not seem to cover sub-normal cases 
necessarily.
It does not mean I think the improvements on test codes are required for the 
first release, they will at least help further development activities.

BTW, our repository contains a lot of possible contributions on test codes.
I believe the code will help users and developers if they are merged.

Regards,
Go Yamamoto

-Original Message-
From: Giorgio Zoppi [mailto:giorgio.zo...@gmail.com] 
Sent: Wednesday, January 31, 2018 6:29 AM
To: dev@milagro.incubator.apache.org
Subject: Re: [DISCUSS] Retire Milagro

BTW,
do you have a roadmap? Do you want to support hardware as well? IS there  a 
todo list of things? When do you plan next release?

2018-01-30 22:26 GMT+01:00 Giorgio Zoppi <giorgio.zo...@gmail.com>:

> Hello everybody,
> is there any way to save just the crypto library inside Apache? The 
> server  doenst make sense, there is no valuable code.
> The crypto library including mpin protocol can be used from other  
> projects. Currently there is no community.
>
>
> 2018-01-30 22:12 GMT+01:00 John D. Ament <johndam...@apache.org>:
>
>> Simeon,
>>
>> In order for that to happen, someone would need to make sure Go 
>> Yamamoto has write access to the repositories.  I'm not sure that has 
>> happened.
>>
>> John
>>
>> On 2018/01/30 14:49:07, Simeon Aladjem <simeon.alad...@miracl.com> wrote:
>> > Hi all,
>> >
>> > As a part of MIRACL, I feel that I have to provide our perspective 
>> > on
>> the project.
>> >
>> > First of all, we did disengage with the idea to move the Milagro 
>> > Crypto
>> code elsewhere.
>> > All the code under the Milagro project refers to the crypto 
>> > repository
>> that is under Apache, so https://github.com/milagro-crypto doesn't 
>> directly affect the project at the current.
>> >
>> > It does contain a more developed version of the original Milagro 
>> > Crypto
>> code, which will eventually find its way to the project,
>> > but in order for this to happen we will need some repository
>> reorganization, which was communicated in the past, to the best of my 
>> memory.
>> >
>> > MIRACL is committed to continue and contribute to the Milagro 
>> > Crypto
>> code, but we were unable to play the leading role in the project for 
>> the last year or so.
>> > For this reason, it was proposed that NTT and Go Yamamoto will take 
>> > on
>> the leadership over the project going forward.
>> >
>> > I hope that it clarifies some points, and will help on getting the
>> project out of the mud and to start moving it forward.
>> >
>> > Kind Regards,
>> > Simeon Aladjem
>> >
>> > On 30/1/18, 15:54, "John D.Ament" <johndam...@apache.org> wrote:
>> >
>> > Hi Yamamoto
>> >
>> > I believe you're hitting the problem right on the head.  The
>> project was originally founded with a donation from MIRACL.  You can 
>> see that code changes continually go to 
>> https://github.com/milagro-crypto but no changes to Apache hosted git 
>> repositories.
>> >
>> > I understand your frustration, but the implications I am seeing 
>> > are
>> that MIRACL has no interest in working on code within the podling.
>> >
>> > John
>> >
>> > On 2018/01/30 05:17:42, "Go Yamamoto" 
>> > <yamamoto...@lab.ntt.co.jp>
>> wrote:
>> > > Hi John,
>> > >
>> > > NTT is currently using Milagro as a crypto library.  
>> > Retirement
>> of Milagro causes impact on our business, so I would like to ask for 
>> discussion what can we do for supporting Milagro.
>> > >
>> > > As I mentioned last time, we have code that is ready to commit.
>> > > Our repositories have been updated since then.
>> > > However, the way to commit the code to Apache repository is 
>> > not
>> clear for us.
>> > > As far as I recognize it is because the code from MIRACL is 
>> > not
>> placed on the Apache r

RE: [DISCUSS] Retire Milagro

[Go Yamamoto]

Hi John,

NTT is currently using Milagro as a crypto library.  Retirement of Milagro 
causes impact on our business, so I would like to ask for discussion what can 
we do for supporting Milagro.

As I mentioned last time, we have code that is ready to commit.
Our repositories have been updated since then.
However, the way to commit the code to Apache repository is not clear for us.
As far as I recognize it is because the code from MIRACL is not placed on the 
Apache repository.
Since MIRACL's code also have been updated continuously, it seems this 
management problem blocks starting the project for years.

I think we can discuss whether NTT team can take over the management of the 
Apache repository to resolve the problem.

Kind regards,
Go Yamamoto



-Original Message-
From: John D. Ament [mailto:johndam...@apache.org] 
Sent: Tuesday, January 30, 2018 1:06 PM
To: d...@milagro.apache.org
Subject: [DISCUSS] Retire Milagro

Hi All,

Mid last year [1] I reached out to the project about retirement.  At that 
point, some community members stepped up to help out the project.  However, I 
don't believe its been enough.

Since that has occurred:
- Milagro has missed reporting periods.  This has included multiple requests 
for a report by me.
- Requests for a special report clarifying the move of source code away from 
the ASF managed repos on github have been unanswered.
- On list activity has dropped to nearly nothing.
- Very little commit activity; most of your repositories have not been updated 
since we last spoke.

At this point, I believe its clear that Milagro should retire.

[1]:
https://lists.apache.org/thread.html/e6a5db6fab6c61156c2101aae003ed576ddb0e77f3bb2c037b405131@%3Cdev.milagro.apache.org%3E

RE: State of Milagro

[Go Yamamoto]

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:johndam...@apache.org] 
Sent: Sunday, October 29, 2017 7:35 PM
To: d...@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: Add member

[Go Yamamoto]

Hi All

The motion is carried as there are 3 +1 votes. Takanori can be added as a
committer.

Regards,
Go Yamamoto

-Original Message-
From: Go Yamamoto [mailto:yamamoto...@lab.ntt.co.jp] 
Sent: Saturday, September 30, 2017 12:22 AM
To: 'dev@milagro.incubator.apache.org' <dev@milagro.incubator.apache.org>;
'priv...@milagro.incubator.apache.org'
<priv...@milagro.incubator.apache.org>
Cc: 'g...@apache.org' <g...@apache.org>
Subject: Add member

Hi All,

I am resending this mail because the previous one is bounced by dev@milagro.

---
I would like to propose Takanori Matsumoto to be added to the committers of
the Milagro incubator Project.

Takanori is a software engineer with Mulodo Inc in Tokyo.  He has been
working with me for the code NTT have been contributing to the Milagro
incubator project.  He is very interested in participating in the Milagro
incubator project.
[ ] +1: Elect Takanori to the team
[ ]  0: Abstain
[ ] -1: Don't elect Takanori

Regards,
Go Yamamoto

Add member

[Go Yamamoto]

Hi All,

I am resending this mail because the previous one is bounced by dev@milagro.

---
I would like to propose Takanori Matsumoto to be added to the committers of
the Milagro incubator Project.

Takanori is a software engineer with Mulodo Inc in Tokyo.  He has been
working with me for the code NTT have been contributing to the Milagro
incubator project.  He is very interested in participating in the Milagro
incubator project.
[ ] +1: Elect Takanori to the team
[ ]  0: Abstain
[ ] -1: Don't elect Takanori

Regards,
Go Yamamoto

Re: [DISCUSS] Retire Milagro

[Go Yamamoto]

I think Nick’s comment is a good point to restart.

(1) communication channel beyond ML
As far as I know Slack will not allow guests by self enrollment.
If the only problem is in openness, then how about using a Slack bot that makes 
public archive?

(2) source code management
We prefer a version control system integrated with an issue tracking system.
As Patric commented, GitHub and JIRA will be a popular choice, and we strongly 
prefer them.
Anthony suggests a contribution workflow with them.  For me it looks very 
attractive idea for practice.


Regards,
Go Yamamoto


On Jun 28, 2017, at 1:47 AM, Nick Kew <n...@apache.org<mailto:n...@apache.org>> 
wrote:

On Mon, 2017-06-26 at 11:49 +0200, Patrick Hilt wrote:
Dear all,
It's clear there is a need to discuss. Unfortunately Miracl has gone
through a range of changes which impeded our support for Milagro. However,
we still do believe that Milagro is a viable project and would like to see
it succeed, albeit with a more focused scope. Looking at the news, it
certainly seems a necessity to have an official, open crypto focused
project.

Agreed there. The question is not whether it's a good project, but
whether it's an *Apache* project.  I should be sorry to see it retire,
but I think if it's to stay, it needs some more committment from
the project team.

Miracl's support for Milagro does raise an issue here.  One of the
most important characteristics of an Apache project is that it is
NOT so dependent on any single company as to dry up if that company
focuses elsewhere.

Overall, I totally agree with Go. We need to find a way to communicate and
manage a project that works for the contributors. Our "issues" are
particularly around real-time communication and GitHub integration (i.e.
having bi-directional sync'ing with Apache Git in place, which we've tried
to find about a while back).

I would echo what Anthony said in reply to Go, and add a few points.

Real-time communication channels like Slack are great, up to a point.
But they don't provide the same browsable, reviewable record as
an email archive (even if publicly archived, real-time chat is
too noisy).  And Milagro's slack is in private company space
most of which is no longer open to me, let alone to a newcomer
who would like to lurk quietly before mustering the confidence
to participate.

Regarding Github integration, that situation has advanced during the
time Milagro has been incubating.  The project might like to raise
the question again on general@incubator.  Along with the relationship
of Apache and Github JIRA: my current impression is that the github is
the more active, though still low-volume.


Along those lines, I'd be happy if we could have some guidance from the
community.

As for "reviving" and moving forward I'd like to propose we
1. determine communication channels beyond just the mailing list; the
Milagro Slack channel is not viable imho, since people with random email
domains can't add themselves. So we 'd need something else... again, input
here would be much appreciated!

IRC is a popular baseline.  Lots of Apache projects use Freenode.
Other channels are also acceptable: can Slack not be configured
to permit guest users?

2. determine how we're going to manage source code and stick with that
(github vs. git); from my perspective I have a strong preference for
github. So any info on bidirectional sync or best practises / approaches
from other Apache projects would be hugely appreciated

general@incubator would be a good place to raise that.  My own exposure
to full github integration is from Trafficserver, which was one
of the Apache projects to trial it.  When Milagro first entered
the incubator, infra were clear: it wasn't yet being rolled out
beyond the trial projects.

3. take stock of where we are currently in terms of contributors, pending
code, etc.

Indeed.  How has staff turnover at Miracl affected the roster?
In an ideal world it shouldn't, except insofar as new developers
may be recruited to relevant work.

4. chart a course forward in small incremental steps based on the above

We have a chicken-and-egg here.  An active and healthy community
draws interest.  The hard part is to bootstrap that community.

Currently we have a codebase that draws some interest, generally
through github, but at a modest level.  The individual who provides
fast and excellent replies to most of the github issues has (I think)
never put in an appearance at Apache.

I believe it would be useful to do 3. and 4. in-person / in-call, at least
partially.

Happy to give it a try, with a couple of reservations:
(a) Concern that it might reinforce a top-down process that works in
a company context but the team needs to get away from at Apache.
(b) A hint of deja-vu.

[Go wrote re: merge of NTT codebase]
Please advise us how we should communicate.

This mailinglist is always the primary channel for project
communication.  Issues raised by a large volume of NTT code
t

Re: [DISCUSS] Retire Milagro

[Go Yamamoto]

John,

If you are looking for persons who are to blame, probably you will find me one 
of them.

I believe we all of us want to make this project fruitful and successful.
So I will explain the reason why, since it will be useful to identify what we 
should discuss/learn/install to solve the problem.

First, we made https://github.com/CertiVox-i3-NTT not intended to be a fork of 
incubator-Milagro, but a fork from
Miracl’s original repositories. https://github.com/miracl
It is because NTT have been working together with Miracl to develop the very 
first version of public Milagro.

We supposed our code is merged at Miracl’s repo and pushed to the 
incubator-milagro.
However, as far as I know, Miracl had a difficulty because of unfortunate 
significant changes.

Probably we should have communicated in this ML that we need to rethink who 
will make the initial commit, looking at the repo with no initial commitment 
for months.
My apologies, we could talk better if I were more experienced in Apache 
projects.

Regards,
Go Yamamoto



On Jun 27, 2017, at 5:28 PM, John D. Ament 
<johndam...@apache.org<mailto:johndam...@apache.org>> wrote:

Go,



On 2017-06-25 23:31 (-0400), Go Yamamoto 
<yamamoto...@ntti3.com<mailto:yamamoto...@ntti3.com>> wrote:
Right.  This is an issue on openness.

We are willing to follow the openness.
For example, our code is open on the internet.
https://github.com/CertiVox-i3-NTT

It looks like you've forked Milagro on your company account.

However, we have difficulty in merging the code with other forks that are to be 
pushed to incubator-milagro.
One of the reason is lack of the communication channels that decide the merge.

This is odd to me.  Why do you require a second set of eyes to merge?  You are 
a committer on the project.  Feel free to commit straight to master.  Granted, 
I'm not sure if there was an agreed upon workflow.

Do you have pull requests open?


Please advise us how we should communicate.

I would recommend just sending emails to dev@.  See who responds.


NTT would like to contribute open source projects and have decided to 
contribute to Milagro project because we support the idea.  We also think the 
current situation is undesirable, and wish to change too.

With the notes about Miracl, are there any other contributors interested in the 
project?


I think we need an open ticketing board like by Jira or a shared issue board in 
GitHub.
All the problems in the project are shared and acknowledged there, and all the 
changes will be merged/rejected by ordinary pull-requests by git.
It is the best way we know, however, I am always willing to learn.

Go


From: anthony shaw <anthonys...@apache.org<mailto:anthonys...@apache.org>>
Sent: Sunday, June 25, 2017 6:40:24 PM
To: dev@milagro.incubator.apache.org<mailto:dev@milagro.incubator.apache.org>
Cc: d...@milagro.apache.org<mailto:d...@milagro.apache.org>
Subject: Re: [DISCUSS] Retire Milagro

Hi Go,

I thought this project was dead as well, your comment "we prefer
communicating using Slack and Hangout", probably highlights most of the
issue. This is not about preference, it's about openness; if you need to be
on the core team or part of NTT to be involved in the conversation, this is
not an open-source project at all. It's "source open" as Scott Hanselman
likes to say, your source code is on the internet, that's it.

You have to have an open and active community, otherwise if/when NTT
decides to pull funding from Milagro, the project dies.

The ASF does not enforce use of SVN, actually, most projects are now on Git
(and mirrored to GitHub). The Milagro project is untouched
https://github.com/apache/incubator-milagro

Regards,
Anthony Shaw

On Mon, Jun 26, 2017 at 7:47 AM, Go Yamamoto <yamamoto...@ntti3.com> wrote:

I agree we need to discuss.

I think the critical problem is in communication, not necessarily in the
level of activities.

I do not think Milagro is inactive.   We NTT have been trying to
contribute the code for more than a year, and still we have 10Ks lines of
code that wait for discussion on merge.

The problem is in the communication styles that divides the project.   For
example, we prefer communicating using Slack and Hangout, not in mailing
lists.   As far as I understand, most of technical discussions are in those
channels, and the code is stored and merged in GitHub spaces.  As the
result the activities are not visible from the projects' official
channels.  That is the problem.

I know one would say that is not an Apache project and the style is not an
Apache way.  I agree it makes sense.  However, we are not simply accustomed
to write codes communicating by mailing lists and using SVN.  Should we
learn to?  To be, or not to be, or to look for a balanced style.  That is
the point.

To start the discussion, I believe we can agree we all hope this project
is fruitful and productive.

I 

Re: [DISCUSS] Retire Milagro

[Go Yamamoto]

Right.  This is an issue on openness.

We are willing to follow the openness.
For example, our code is open on the internet.
https://github.com/CertiVox-i3-NTT
However, we have difficulty in merging the code with other forks that are to be 
pushed to incubator-milagro.
One of the reason is lack of the communication channels that decide the merge.

Please advise us how we should communicate.

NTT would like to contribute open source projects and have decided to 
contribute to Milagro project because we support the idea.  We also think the 
current situation is undesirable, and wish to change too.

I think we need an open ticketing board like by Jira or a shared issue board in 
GitHub.
All the problems in the project are shared and acknowledged there, and all the 
changes will be merged/rejected by ordinary pull-requests by git.
It is the best way we know, however, I am always willing to learn.

Go


From: anthony shaw <anthonys...@apache.org>
Sent: Sunday, June 25, 2017 6:40:24 PM
To: dev@milagro.incubator.apache.org
Cc: d...@milagro.apache.org
Subject: Re: [DISCUSS] Retire Milagro

Hi Go,

I thought this project was dead as well, your comment "we prefer
communicating using Slack and Hangout", probably highlights most of the
issue. This is not about preference, it's about openness; if you need to be
on the core team or part of NTT to be involved in the conversation, this is
not an open-source project at all. It's "source open" as Scott Hanselman
likes to say, your source code is on the internet, that's it.

You have to have an open and active community, otherwise if/when NTT
decides to pull funding from Milagro, the project dies.

The ASF does not enforce use of SVN, actually, most projects are now on Git
(and mirrored to GitHub). The Milagro project is untouched
https://github.com/apache/incubator-milagro

Regards,
Anthony Shaw

On Mon, Jun 26, 2017 at 7:47 AM, Go Yamamoto <yamamoto...@ntti3.com> wrote:

> I agree we need to discuss.
>
> I think the critical problem is in communication, not necessarily in the
> level of activities.
>
> I do not think Milagro is inactive.   We NTT have been trying to
> contribute the code for more than a year, and still we have 10Ks lines of
> code that wait for discussion on merge.
>
> The problem is in the communication styles that divides the project.   For
> example, we prefer communicating using Slack and Hangout, not in mailing
> lists.   As far as I understand, most of technical discussions are in those
> channels, and the code is stored and merged in GitHub spaces.  As the
> result the activities are not visible from the projects' official
> channels.  That is the problem.
>
> I know one would say that is not an Apache project and the style is not an
> Apache way.  I agree it makes sense.  However, we are not simply accustomed
> to write codes communicating by mailing lists and using SVN.  Should we
> learn to?  To be, or not to be, or to look for a balanced style.  That is
> the point.
>
> To start the discussion, I believe we can agree we all hope this project
> is fruitful and productive.
>
> I think Milagro still has a promising scope and good use cases in IoT, and
> I would like to continue leading the NTT's engineering team to contribute.
>
> Go
> 
> From: John D. Ament <johndam...@apache.org>
> Sent: Sunday, June 25, 2017 3:25:15 AM
> To: d...@milagro.apache.org
> Subject: [DISCUSS] Retire Milagro
>
> All,
>
> I'd like to bring up the idea of retiring the Milagro podling.   You've
> been incubating for about 18 months and from what I can tell there is no on
> list activity nor commits happening.
>
> John
> 
> This email message is intended for the use of the person to whom it has
> been sent, and may contain information that is confidential or legally
> protected. If you are not the intended recipient or have received this
> message in error, you are not authorized to copy, distribute, or otherwise
> use this message or its attachments. Please notify the sender immediately
> by return e-mail and permanently delete this message and any attachments.
> NTT I3 makes no warranty that this email is error or virus free. Thank you.
> 
>

This email message is intended for the use of the person to whom it has been 
sent, and may contain information that is confidential or legally protected. If 
you are not the intended recipient or have received this message in error, you 
are not authorized to copy, distribute, or otherwise use this message or its 
attachments. Please notify the sender immediately by return e-mail and 
permanently delete this message and any attachments. NTT I3 makes no warranty 
that this email is error or virus free. Thank you.

Re: [DISCUSS] Retire Milagro

[Go Yamamoto]

I agree we need to discuss.

I think the critical problem is in communication, not necessarily in the level 
of activities.

I do not think Milagro is inactive.   We NTT have been trying to contribute the 
code for more than a year, and still we have 10Ks lines of code that wait for 
discussion on merge.

The problem is in the communication styles that divides the project.   For 
example, we prefer communicating using Slack and Hangout, not in mailing lists. 
  As far as I understand, most of technical discussions are in those channels, 
and the code is stored and merged in GitHub spaces.  As the result the 
activities are not visible from the projects' official channels.  That is the 
problem.

I know one would say that is not an Apache project and the style is not an 
Apache way.  I agree it makes sense.  However, we are not simply accustomed to 
write codes communicating by mailing lists and using SVN.  Should we learn to?  
To be, or not to be, or to look for a balanced style.  That is the point.

To start the discussion, I believe we can agree we all hope this project is 
fruitful and productive.

I think Milagro still has a promising scope and good use cases in IoT, and I 
would like to continue leading the NTT's engineering team to contribute.

Go

From: John D. Ament 
Sent: Sunday, June 25, 2017 3:25:15 AM
To: d...@milagro.apache.org
Subject: [DISCUSS] Retire Milagro

All,

I'd like to bring up the idea of retiring the Milagro podling.   You've
been incubating for about 18 months and from what I can tell there is no on
list activity nor commits happening.

John

This email message is intended for the use of the person to whom it has been 
sent, and may contain information that is confidential or legally protected. If 
you are not the intended recipient or have received this message in error, you 
are not authorized to copy, distribute, or otherwise use this message or its 
attachments. Please notify the sender immediately by return e-mail and 
permanently delete this message and any attachments. NTT I3 makes no warranty 
that this email is error or virus free. Thank you.