Ask HN: When is your side project 'production-ready'?

You should make it very clear to the person asking that while you've been using it in non-mission-critical production scenarios for some time, it is still an incomplete and actively developed project with changes and fix bugs on a regular basis and that you provide no warranty or guarantee of fitness for any particular purpose (this is in the MIT license that you're using, but you don't want to promise anything beyond what's in the license which is "we promise nothing.").<p>Basically, Dashku is "incorporate at your own risk" software, with the additional note that the hosted version is absolutely not for mission-critical use, that it may become unavailable at any time for any reason and for any duration.<p>Basically, you want to be sure you're shielded from someone in a "sue everyone!" mindset coming after you just because you wrote a piece of software that was later incorporated into someone else's package where you have no control over how they use it, whether they apply bug fixes, whether they make changes, etc.<p>There's a reason that an awful lot of commercial software EULAs out there include language specifically referring to the software not being suitable for mission-critical, failure-critical, medical, etc. purposes.

Have you had a lot of people that aren't you try to break the living hell out of it? Especially those not familiar with the usual workflow? Especially those that take pride in destroying things?<p>If it can pass that, and you're confident going forward from there, then I would think it's ready.

You might want to fix the readme link to the MIT license, as it's broken. Why not paste in the full text? They have that warning about no liability and no warranty which might be really important for you.

Just fyi that the screenshot on the github page has the word 'nigga' on there from someones comment.