Bikeshedding

We are basically the steering committee that makes decisions on release schedules and other project management issues - the things that cannot be effectively done by the community at large without running into security, privacy or 'bikeshedding' issues. ❋ Unknown (2010)

A simple “been there – done that – it was an incredibly stupid idea” can save everyone from quite some headache and bikeshedding. ❋ Unknown (2009)

Development moved slowly because endless bikeshedding impaired efforts to reconcile technical differences between the disparate Nokia and Intel software components. ❋ Ryan Paul (2011)

Among the pitfalls he mentions are undirected and inconclusive discussions about detail (including bikeshedding and resource fetishism -- look those terms up if you need to). ❋ Unknown (2010)

But I'm sure that I could find huge bikeshedding threads on fedora-devel about this if I really cared why this was decided. ❋ Unknown (2009)

The parallel with Microsoft users vs. Java users seems to be all too obvious: Microsoft as the strict father: If you are loyal you will be rewarded, but if you stray you will be punished; whereas in the Java (or Python) community benefits and moral goodness flow from helping each other (which includes sharing open source software, and, apparently, bikeshedding: -). ❋ Unknown (2009)

We had bikeshedding galore … confusion everywhere … I'm pretty sure I contrubuted to the confusion even when I was trying to reduce it. ❋ Unknown (2009)