{"id":895,"date":"2008-07-27T17:10:56","date_gmt":"2008-07-27T22:10:56","guid":{"rendered":"http:\/\/www.bytebot.net\/blog\/?p=895"},"modified":"2008-07-27T17:10:56","modified_gmt":"2008-07-27T22:10:56","slug":"failure-we-cant-spell-failure-without-u","status":"publish","type":"post","link":"http:\/\/www.bytebot.net\/blog\/archives\/2008\/07\/27\/failure-we-cant-spell-failure-without-u","title":{"rendered":"Failure – we can’t spell failure without U"},"content":{"rendered":"

Sparse notes, from An Open Source Project Called “Failure:” Community Antipatterns to Know and Avoid<\/a>. Both lists of panel members are inaccurate (and I seemed to have forgotten to take the list down, myself).<\/p>\n

Blocking anti-pattern
\nfeature you really want implemented, someone blogs it saying they’re going to do it, and a few years later, there’s nothing done<\/p>\n

Docs? We don’t need no stinkin’ docs!
\nLook at SQL-Ledger and their documentation… this is our hero… Project around for 10 years, and most people end up using a fork of it instead.<\/p>\n

Don’t screw around with licenses. Licenses are a social contract defining what people can do with your code and what you expect from them when they use it. Most open source license enforcement is done via peer pressure, not court order.<\/p>\n

Community members have emotional attachments to licenses and responses to changes in them.<\/p>\n

Share this:<\/h3>