Go, On 2017-06-29 19:00 (-0400), Go Yamamoto <[email protected]> wrote: > John, > > If you are looking for persons who are to blame, probably you will find me > one of them.
I'm by no means trying to find people to blame. My objective is to look at each podling out there and make sure it's viable enough to be a project. > > 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. This is actually an incredibly useful explanation. Thank you for it. So with Miracl not supporting the work, do you feel comfortable as an individual committing to the ASF hosted repository instead of the github repository created by NTT? If not, what could we do to help you get there? > > Regards, > Go Yamamoto > > > > On Jun 27, 2017, at 5:28 PM, John D. Ament > <[email protected]<mailto:[email protected]>> wrote: > > Go, > > > > On 2017-06-25 23:31 (-0400), Go Yamamoto > <[email protected]<mailto:[email protected]>> 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 <[email protected]<mailto:[email protected]>> > Sent: Sunday, June 25, 2017 6:40:24 PM > To: [email protected]<mailto:[email protected]> > Cc: [email protected]<mailto:[email protected]> > 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 <[email protected]> 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 <[email protected]> > Sent: Sunday, June 25, 2017 3:25:15 AM > To: [email protected] > 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. > ________________________________ > > > ________________________________ > 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. > ________________________________ >
