{"action":"created","issue":{"url":"https://api.github.com/repos/NETMF/netmf-interpreter/issues/527","repository_url":"https://api.github.com/repos/NETMF/netmf-interpreter","labels_url":"https://api.github.com/repos/NETMF/netmf-interpreter/issues/527/labels{/name}","comments_url":"https://api.github.com/repos/NETMF/netmf-interpreter/issues/527/comments","events_url":"https://api.github.com/repos/NETMF/netmf-interpreter/issues/527/events","html_url":"https://github.com/NETMF/netmf-interpreter/issues/527","id":188738477,"number":527,"title":"Future of .NETMF (take #999999)","user":{"login":"josesimoes","id":1881520,"avatar_url":"https://avatars.githubusercontent.com/u/1881520?v=3","gravatar_id":"","url":"https://api.github.com/users/josesimoes","html_url":"https://github.com/josesimoes","followers_url":"https://api.github.com/users/josesimoes/followers","following_url":"https://api.github.com/users/josesimoes/following{/other_user}","gists_url":"https://api.github.com/users/josesimoes/gists{/gist_id}","starred_url":"https://api.github.com/users/josesimoes/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/josesimoes/subscriptions","organizations_url":"https://api.github.com/users/josesimoes/orgs","repos_url":"https://api.github.com/users/josesimoes/repos","events_url":"https://api.github.com/users/josesimoes/events{/privacy}","received_events_url":"https://api.github.com/users/josesimoes/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":22,"created_at":"2016-11-11T11:16:55Z","updated_at":"2016-11-18T21:31:37Z","closed_at":null,"body":"It’s been 3 months + 1 day since #491 was published. Along with #493, a reasonable amount of discussion was generated and some very interesting points were made. We even got a new branch on the repo for a “v5” where some high level documentation was stored.\r\n\r\nNow let me ask you this: what has really changed since then? \r\nWhere is .NETMF today compared to where it was 3 months, 6 months, 12 months ago? \r\nHas it moved forward? \r\nDo we have more community engagement?  \r\nWere any of the main issues that plague .NETMF solved or at least addressed? \r\nDo we have a plan? A roadmap? \r\nIs there a team working on any of this?\r\n\r\nI’ll dare to say that the .NETMF project hasn’t – if we want to be totally honest about it – moved an inch.\r\n\r\nIt’s about time that we stop beating around the bush and get to the point: .NETMF is not getting anywhere and it won’t go anywhere with what is there today!! This should have become quite obvious by now...\r\n\r\n@smaillet-ms, because you are [.NETMF project main contact](https://www.dotnetfoundation.org/net-micro-framework) let me ask you this: what else is needed for you to let community people in? What else is needed for you to relinquish total control of .NETMF?\r\n\r\nIf nothing changes (and I mean drastically and really fast) the moribund .NETMF will be completely dead. (Except on a few repos here and there were it will live forever that belong to people that really love it and will keep working on it no matter what)\r\n\r\nNote: this will be my last take on .NETMF future and governance. I’ve made a few attempts to shake people’s minds and have them contribute and step in. If I’m the only one seeing things this way, then I’m the one who is wrong and I have to shut the f#$% up."},"comment":{"url":"https://api.github.com/repos/NETMF/netmf-interpreter/issues/comments/261647181","html_url":"https://github.com/NETMF/netmf-interpreter/issues/527#issuecomment-261647181","issue_url":"https://api.github.com/repos/NETMF/netmf-interpreter/issues/527","id":261647181,"user":{"login":"Stabilitronas","id":6960796,"avatar_url":"https://avatars.githubusercontent.com/u/6960796?v=3","gravatar_id":"","url":"https://api.github.com/users/Stabilitronas","html_url":"https://github.com/Stabilitronas","followers_url":"https://api.github.com/users/Stabilitronas/followers","following_url":"https://api.github.com/users/Stabilitronas/following{/other_user}","gists_url":"https://api.github.com/users/Stabilitronas/gists{/gist_id}","starred_url":"https://api.github.com/users/Stabilitronas/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Stabilitronas/subscriptions","organizations_url":"https://api.github.com/users/Stabilitronas/orgs","repos_url":"https://api.github.com/users/Stabilitronas/repos","events_url":"https://api.github.com/users/Stabilitronas/events{/privacy}","received_events_url":"https://api.github.com/users/Stabilitronas/received_events","type":"User","site_admin":false},"created_at":"2016-11-18T21:31:37Z","updated_at":"2016-11-18T21:31:37Z","body":"@smaillet-ms I'm sorry Steve. I didn't mean any hostility. I used to love NETMF, but as a commercial entity, I'm pretty much much forced to drop NETMF support in all high-tech product I'm in charge of. Because, you know, whatever you say, one tiny commit per week  is just not enough to call a project \"active\" these days IMO. And seems like I'm not the only one, given this very thread.\r\n\r\nAs a software manager, when multiple people tell me \"you're going the wrong way\", I always re-evaluate my decisions, because it's a very good indicator that, in fact, I'm going the wrong way. In such cases, instead of furiously defending myself, I always ask as myself: maybe I'm wrong? Maybe I should shange my course? Maybe they're right? So please, take my criticism in a constructive way.\r\n\r\nBut, again, you're the sole master of NETMF. I'm not questioning that. Other guys, like @josesimoes, will either fork it or let it go your way. Your way is one commit per week. Sorry man, that's just not enough to make NETMF great again these days."}}
{"actor":{"display_login":"Stabilitronas"}}