105 karma · joined February 26, 2015
Thanks for the mention. We have been chatting with maintainers this past year and recommend new contributors as the best metric to start identifying repo health.
Another example is the rate of selection, how many contributors outside the core team or employees.
We plan to expose more metrics like these in app really soon.
Check out our guide for maintainers https://docs.opensauced.pizza/maintainers/maintainers-guide-...
Also still working on improving the discovery part but also wanted to mention everything is open sourced and we also have an API for anyone build with the data.
Interested Observer here. What is Microsoft's primary product you are referring to? Windows or Office. From a quick Google search, it seems like Office (based on revenue).
1 save open source projects and write notes about them to eventually make a contribution
2 try out solving a problem using a new technology, GraphQL
you can also connect your github repo to have a atomic deploys, which is more than you get from gh pages. https://www.netlify.com/blog/2016/08/11/from-unstable-to-rel...
however Netlify has no limits on builds :)
One thing I don't see a lot of is opinions in React on deploying. I wrote a blog post on deploying this new boiler using netlify, pretty straight forward. https://www.netlify.com/blog/2016/07/22/deploy-react-in-30-s...