Re:The story of Google Guava and patches
by codeonfire on Sunday March 11, 2012 @10:05PM
(#3692049)
The simple solution for dealing with Google-scale bureaucracy is to fork and continue pushing forward. Then when that fork gets locked down, create a new one. Not every project is going to be bureaucracy impaired, but there is a correct procedure when it is. Multi-round "grueling" code reviews, and API review meetings? W.T.F.
[ Parent
| on HN ]
There are no comments on this comment yet.