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. ________________________________
