That's still not really a reason for GitHub to not respond. They don't have to agree or promise anything one way or another, but a response from GitHub outlining their position would at least give everyone a clear baseline for what to expect from GitHub in the future.
> a response from GitHub outlining their position would at least give everyone a clear baseline for what to expect from GitHub in the future.
Um, exactly?
A "Fuck off and die, you don't pay our bills" response is going to provoke outrage and maybe even action. It would certainly provide reinforcement for those of us who don't really like github for various reasons.
Not responding at all leaves things vague and doesn't provoke action.
Want github to respond? Start moving some famous projects off of github and onto something else. A couple big name projects that start making some other service look like the "default" winner and github will get REAL responsive.
Until people start moving projects (like this one), github doesn't have to care.
I just feel the risk of major projects moving (increasingly likely) seems much higher than the complexity of adding the couple very small features, that probably don't go against anything they might be doing Enterprise-side.
