tl;dr: Cover will die a slow, unmaintained death while the former Cover employees work on completely unrelated Twitter projects. Oh well.
tl;dr: Cover will die a slow, unmaintained death while the former Cover employees work on completely unrelated Twitter projects. Oh well.
I had the idea before starting Floobits (YC S13 yadda yadda), and of course, we've made a pledge: https://floobits.com/pledge
This helps the company as well as customers. People are more likely to adopt your product when they know you'll give them the source code if your company dies.
It's helped in subtle ways that I didn't predict. For example: If I ever think of taking shortcuts or building embarrassingly bad software, I remember that the public will likely see this code one day.
If you run a company, consider making a responsible sunset pledge. If you use a SaaS tool, consider asking that company to make one.
1. http://geoff.greer.fm/2012/09/19/a-responsible-product-sunse...
Why, exactly?
This probably won't be a popular view on HN, but I think a lot of people complain about companies shutting things down for the sake of complaining.
Cover was a free, beta application with a very limited number of users. There was no personal data saved by it and no future plans announced. For those users Cover will continue to work today like it did yesterday. And yet the top voted comment is complaining about it being shutdown. Pfft!
In general, customers want a supported product (eg, the endless complaints about every single startup bought by a larger company, even when they completely open source their product).
In most cases a pledge like this puts extra restrictions on what a startup can do. I'm not saying screw over your customers if you get bought, but making a pledge is completely different to building some kind of data export facility if it ends up being needed. Why take on challenges that you don't need?
In some cases (typically enterprise focused) some kind of business continuity plan is absolutely appropriate. In many consumer-focused app start ups? Not so much.
About open sourcing the code : If the acquiring company sees the "existing" product as IP even if they do not see the product/service making (enough?) money - they may consider the "code" as IP. In such case - the acquired company may not be "legally" allowed to make the code open source.
This happens so often it would be great to have a standard and clear expectations.
For example, what happens when "Cover" is discontinued, but it got bought for the underlying technology? It needs to be open sourced because of that.
I think it's the point of the author of the comment here.