3 ms·
Maybe the open source community needs a sort of standard way of declaring/disclaiming how production-ready a project is, and how much effort we intend to put in
by tlrobinson 14y ago
Maybe the open source community needs a sort of standard way of declaring/disclaiming how production-ready a project is, and how much effort we intend to put into supporting it.
- jamesbritt 14y agoPeople should assume that if there is no affirmative declaration of "This is production ready" then the code is not production ready. If there is no affirmative declaration of "I will be actively supporting this beyond my own personal needs" then assume that the code will not be supported beyond the personal needs of the project owner. Or people can just ask, instead complaining (however well-intended) that their assumptions have turned out false. This is like people who build a business on some aspect of Twitter or Facebook then complain that Twitter or Facebook is shutting them out. If you are using someone else's code or API make sure you get some positive, unambiguous statement from the owner about what to expect. Things can still go south, but then you at least have a legitimate gripe.
- steveklabnik 14y agoIn the gist, even though the Ember Data README states that it's not production ready, the author complains that it 'should be' or something. We have that standard, it's called '1.0'.