Ben Balter • 6/22/2015

Merge by committee

Read Original

The article critiques the 'merge by committee' antipattern, where organizations manage open source projects with closed, scheduled meetings. It argues this closed-source workflow excludes global contributors, lacks transparency, and fails to capture decisions. It emphasizes that open source success requires embracing its inherent asynchronous, distributed, and transparent collaborative model.

0 comments
#software development #open source #workflow
Merge by committee

Comments

No comments yet

Be the first to share your thoughts!

Browser Extension

Get instant access to AllDevBlogs from your browser

Top of the Week

1
Quoting Thariq Shihipar
Simon Willison • 2 votes
2
Top picks — 2026 January
Paweł Grzybek • 1 votes
3
In Praise of –dry-run
Henrik Warne • 1 votes
4
Deep Learning is Powerful Because It Makes Hard Things Easy - Reflections 10 Years On
Ferenc Huszár • 1 votes
5
Vibe coding your first iOS app
William Denniss • 1 votes
6
AGI, ASI, A*I – Do we have all we need to get there?
John D. Cook • 1 votes
7
Dew Drop – January 15, 2026 (#4583)
Alvin Ashcraft • 1 votes