{"action":"created","issue":{"url":"https://api.github.com/repos/nodejs/community-committee/issues/186","repository_url":"https://api.github.com/repos/nodejs/community-committee","labels_url":"https://api.github.com/repos/nodejs/community-committee/issues/186/labels{/name}","comments_url":"https://api.github.com/repos/nodejs/community-committee/issues/186/comments","events_url":"https://api.github.com/repos/nodejs/community-committee/issues/186/events","html_url":"https://github.com/nodejs/community-committee/issues/186","id":279521716,"number":186,"title":"Node.js Strategic Initiatives beyond technical matters","user":{"login":"DiegoZoracKy","id":2091071,"avatar_url":"https://avatars3.githubusercontent.com/u/2091071?v=4","gravatar_id":"","url":"https://api.github.com/users/DiegoZoracKy","html_url":"https://github.com/DiegoZoracKy","followers_url":"https://api.github.com/users/DiegoZoracKy/followers","following_url":"https://api.github.com/users/DiegoZoracKy/following{/other_user}","gists_url":"https://api.github.com/users/DiegoZoracKy/gists{/gist_id}","starred_url":"https://api.github.com/users/DiegoZoracKy/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/DiegoZoracKy/subscriptions","organizations_url":"https://api.github.com/users/DiegoZoracKy/orgs","repos_url":"https://api.github.com/users/DiegoZoracKy/repos","events_url":"https://api.github.com/users/DiegoZoracKy/events{/privacy}","received_events_url":"https://api.github.com/users/DiegoZoracKy/received_events","type":"User","site_admin":false},"labels":[{"id":517038002,"url":"https://api.github.com/repos/nodejs/community-committee/labels/cc-agenda","name":"cc-agenda","color":"e99695","default":false}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":22,"created_at":"2017-12-05T20:37:06Z","updated_at":"2017-12-28T02:17:32Z","closed_at":null,"author_association":"NONE","body":"# Node.js Strategic Initiatives beyond technical matters\r\n\r\n## Summary\r\n\r\nThis issue proposes the creation of a document like TSC's Strategic Initiatives, but not so focused on technical subjects. The suggestion is to have topics more related to the business side of the Node.js community. With strategies to ease and give more confidence on the adoption of Node.js.\r\n\r\nIt seems to me that Node.js would be more adopted if companies could be more confident, by having a better sense that developers are around their location to join their team. Consequently developers would be more willing to dive deep on it, knowing that a great opportunity to be hired is out there.\r\n\r\nI believe that would be great for us all, if Node.js Foundation could take a step on this direction and start (or improve), the communication on this sense.\r\n\r\nSome of the initial ideas I propose are to facilitate developers and companies to find themselves and to bring awareness on how Node.js is being used.\r\n\r\n**Node.js People Everywhere (npe)**\r\n\r\nIn order to easily answer the question: *Where are the Companies and the Developers?*, I believe that a list/directory of companies using Node.js, and Node.js Developers can be great. It would include where they are, how they are using it, providing features to search by location or by scope/skills.\r\n\r\nThis will help companies and developers to find each other, and to make them understand the profile of what is around.\r\n\r\nI'm describing it better at: #184. There we can go deep on a discussion specifically about this idea.\r\n\r\nFrom January onwards I will have some spare time to invest efforts on it, in case we agree on having that.\r\n\r\n**LinkedIn**\r\n\r\nThe major LinkedIn group is managed by a company, and I believe that would be way better if there was an official group there. I've created an issue (#185) for us to discuss the pros of having it, and the cons of not having a group, more open, embracing the whole community.\r\n\r\n**Content**\r\n\r\nThe Node.js main website is the first place where people go, to know more about it. If they can't find what is being searched for, is not guaranteed that they will try to look in another place. There is no content related to that scope I'm mentioning here, and if there is some, it is a bit hidden.\r\n\r\nThe Node.js channel on YouTube has some videos with people telling why Node.js was chosen, and the \"use cases\" section on the website (that I couldn't find it anymore, at the last time I checked) is something that should have more importance, in my opinion. The video from Walmart that used to be on the main page was a good help on that sense.\r\n\r\n## Initial motivation and reasons (long text)\r\n\r\nThe TSC has a \"Strategic Initiatives\" document, which I think is a really great initiative to keep the good working being done, and also to share with the community what's going on. I would like to know if it's possible, and if it is felt important, to have another document as the \"Strategic Initiatives\", but with a scope more on the business level. Here, \"businesses level\" is also very related to the developers community, and not just to the one who owns, or is starting a company.\r\n\r\nTo explain better, I'm sharing parts (slightly modified) of an email I sent to @mhdawson, regarding this topic:\r\n\r\nYou guys have been doing a great job on Node.js, thank you all for that. It has been great all you have done and I can feel really safe about the direction the project is taking towards the future. I'm 100% sure that choosing Node.js as the basis of my current and next projects is a great move. I can see all the many benefits we have in technical terms, and also, how I can move faster and be very productive working with it. Having front-end and back-end teams sharing code, where they can work together creating and maintaining modules, is really powerful.\r\n\r\nHowever, I have a feeling that I just can say all of that because despite of any position I had, or will have in the future, I will be still a developer. One with hands on coding. That leads me to be close to what is happening. Through technical talks, writings, looking at new modules being published, and also publishing modules and writing technical articles myself. But to a person that doesn't have this kind of profile (maybe, doesn't have it  anymore), and it is in a position of making decisions, where can one find data to be informed about how Node.js can be great for its business? For example:\r\n\r\n* Are there Node.js developers in my area?\r\n* Where are they?\r\n* Once found, are they back-end developers, users of some front-end tooling, IoT?\r\n* How teams can benefit from having Node.js on the stack?\r\n* How could sharing code between front-end and back-end make me move faster, and thus reduce the costs of a project?\r\n* How a culture of modularity can benefit my team?\r\n* How the good job of the TSC impact my business in terms of reliability, security, LTS support, etc.?\r\n\r\nWhen looking for companies investing heavily in Node.js I can't find many, even though we know about some big names here. Doing the inverse, to find Node.js developers, it is not easy either. A Node.js developer can mean a lot of things nowadays. Looking for someone to work with API servers, it is easy to end up with profiles of people that range from a user of some front-end tooling, to someone willing to work with IoT.\r\n\r\nI just can find some companies investing for real on Node.js when looking abroad (BTW, I'm from Brazil). I talked recently with some foreign companies that were willing to relocate people to work with Node.js. This episode can makes us think about why weren't they able to find people to work with Node.js around there? The VP of engineering of one of those companies mentioned to me something like \"we are choosing Node.js, but it hasn't being easy to find people to work with it\".\r\n\r\nIn my point of view, it can end up on a bad loop where companies are not so sure about choosing Node.js, and that can make developers feeling that maybe it is not a good idea to invest on it."},"comment":{"url":"https://api.github.com/repos/nodejs/community-committee/issues/comments/354215301","html_url":"https://github.com/nodejs/community-committee/issues/186#issuecomment-354215301","issue_url":"https://api.github.com/repos/nodejs/community-committee/issues/186","id":354215301,"user":{"login":"DiegoZoracKy","id":2091071,"avatar_url":"https://avatars3.githubusercontent.com/u/2091071?v=4","gravatar_id":"","url":"https://api.github.com/users/DiegoZoracKy","html_url":"https://github.com/DiegoZoracKy","followers_url":"https://api.github.com/users/DiegoZoracKy/followers","following_url":"https://api.github.com/users/DiegoZoracKy/following{/other_user}","gists_url":"https://api.github.com/users/DiegoZoracKy/gists{/gist_id}","starred_url":"https://api.github.com/users/DiegoZoracKy/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/DiegoZoracKy/subscriptions","organizations_url":"https://api.github.com/users/DiegoZoracKy/orgs","repos_url":"https://api.github.com/users/DiegoZoracKy/repos","events_url":"https://api.github.com/users/DiegoZoracKy/events{/privacy}","received_events_url":"https://api.github.com/users/DiegoZoracKy/received_events","type":"User","site_admin":false},"created_at":"2017-12-28T02:17:32Z","updated_at":"2017-12-28T02:17:32Z","author_association":"NONE","body":"@bnb, I agree. I believe we'll be discussing on the specific issues for now. "}}
{"actor":{"display_login":"DiegoZoracKy"}}