[
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
[
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
[
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
[
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
[
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
[
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
[
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
[
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
[
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
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,
>
?
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
check it and response how this project should review the pull
request.
Regards,
Go Yamamoto
to resolve an issue in our JIRA.
He will have some points to discuss with this list.
Regards,
Go Yamamoto
m 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: R
[
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
[
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
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
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
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
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
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.
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
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
, 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
: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
.
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
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
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
-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 o
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" <yam
, 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
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
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
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' <
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
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
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),
it
(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 comm
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
39 matches
Mail list logo
