3 ms·
The GNOME development lifecycle, illustrated for newcomers: 1. Mark all current issues as stale or wontfix when no new work is getting done 2. Partner with/cr
by smoldesu 4y ago
The GNOME development lifecycle, illustrated for newcomers:
1. Mark all current issues as stale or wontfix when no new work is getting done
2. Partner with/create new software feature that is going to "finally fix the Linux desktop"
3. Expand codebase around new feature, leaving an abundance of cruft and dead code in their wake
4. (YOU ARE HERE) When everything inevitably breaks, they abandon the new feature and blame some perceived open-source boogieman
5. Development falters, funding cuts out, maintainers bail or something else happens that causes progress to return to a standstill (return to Step 1)
- dsp 4y ago“The Cascade of Attention-Deficit Teenagers Model” https://www.jwz.org/doc/cadt.html https://www.jwz.org/doc/cadt.html
- 22c 4y agoLinks to jwz.org are not friendly to HN referrals.
- josephcsible 4y agoI wonder why this site doesn't just automatically add rel="noreferrer" to all links to that domain.