Agreed this will impact some organizations in negative ways such as the non-for-profit orgs. To that Github offers support in this sense here: https://github.com/nonprofit
Like others, without specific data, I would assume this will impact the majority of users on Github for the better and that organizations with many contributors needing access to private repos are the minority. In any pricing structure change, there is always going to be a minority that is impacted negatively. I don't think Github would have made this decision without analytics to back it up.
Another fair point is I think this structure is more appealing to companies who prefer to look at cost-per-employee for something that is an everyday tool rather than cost-of-architecture.
Everyone who is crying right now would be crying more if Github were to make the price free for private repos because with that, the amount of open source libraries they use would be cut in half.
This is what I want to see more of, I get very worried about any tech claiming to overtake the UI layer of your application and make it cross platform. It never makes sense to do IMO. Logic and models though however, I can't wait!
You're contradicting the problem that you've set out to solve. Now at a hackathon, when debating with my team which frameworks to use etc we now have another scaffolding tool to debate over. This involves those who might not like yeoman, may not prefer the template library you're giving them. As well there will be those who've looked at your repo and simply don't agree with the code your scaffolding.
I like the idea, I really do, but the problem you're solving is all wrong. This isn't a solution for teams to get organized, because in the end you're just another member of their team saying "This is whats best".
This is a solution for a team who finds themselves at a real-time/node/web-app hackathon working with technologies they don't know and its a quick way to guide them in "A" direction, weather its the right or not they will decide once they learn more.
Agreed this will impact some organizations in negative ways such as the non-for-profit orgs. To that Github offers support in this sense here: https://github.com/nonprofit
Like others, without specific data, I would assume this will impact the majority of users on Github for the better and that organizations with many contributors needing access to private repos are the minority. In any pricing structure change, there is always going to be a minority that is impacted negatively. I don't think Github would have made this decision without analytics to back it up.
Another fair point is I think this structure is more appealing to companies who prefer to look at cost-per-employee for something that is an everyday tool rather than cost-of-architecture.