Manifest for .NETMF (the current state and the future we want for it)

JSimoes · August 10, 2016, 8:20am

Just add this to NETMF GitHub. You may want to weigh in [url]https://github.com/NETMF/netmf-interpreter/issues/491[/url]

Terrence · August 10, 2016, 9:37am

@ JSimoes - Glad you stated the conversation.

Terrence · August 10, 2016, 3:22pm

Steve has a great follow up to @ JSimoes post over on GitHub about moving forward with netmf vNext.

…Hopefully I won’t scare or offend anyone by being blunt on this in an attempt to establish clarity:

github.com/NETMF/netmf-interpreter

Manifest for .NETMF (the current state and the future we want for it)

opened 12:17PM - 10 Aug 16 UTC

josesimoes

Discussion

This is the result of an ongoing reflection with a bunch of .NETMF friends/suppo…rters/users that's been happening in the past weeks. Understand that we are doing this with a positive and constructive attitude. We are not grumping or saying it just because we want to criticize. Considerations and the current state: - NETMF is a truly awesome framework with an incredible potential for commercial, hobbyist and learning scenarios. - Microsoft (for reasons that are not perfectly clear or made public) hasn’t be showing any love for this project for quite some time. - The move to GitHub was supposed to improve the community engagement and make the workflow easier. After more than one year none of that has become a reality. - Right now, as someone nicely put it, NETMF is going through an Ice Age. It sure looks like a zombie project, wandering and headed to nowhere. - NETMF announces itself as an "Open Source" project. Considering all the implications and ramifications that designation carries, this is not the reality we can see today. - There are a lot of smart, valuable and knowledgeable people out there who are willing to contribute. Those should be encouraged to do so and brought on board. What should change: - NETMF should become a true "Open Source" project. Steered by the community involved and managed by a team of people. - There should be a full team behind it. With roles assigned, clear tasks defined and expectations set. - A roadmap should exist. The community must have a saying on the direction of the project, what features are required, what needs to be changed or improved. - Issues should be answered and handled in a timely and respectful fashion. Pull requests should be encouraged and evaluated with a positive and constructive attitude. Contributions should be encouraged and cherished. - Microsoft (probably through the .NET Foundation) should be asked for their open support. Institutional support, that's for sure. But not only. Ideally they should be asked to contribute by marketing NETMF, making noise about it, mention it in Channel 9, Twitter, blogs and such. It wouldn’t hurt to commit a few more people to the project. - NETMF should be brought under the spot light, front and centre. Needs to be shown and be seen by makers, schools, universities and companies. Needs to be mentioned in the social networks. Needs to show that it's alive and has potential. A lot of potential!