We’ve tried (unsuccessfully) to sell the codebase. Meanwhile, some of our most loyal users are now asking us to open source it. Part of me feels this would be a meaningful way to give back and ensure the project doesn’t completely disappear.
However, I can also foresee a lot of technical and legal complications, not to mention potential maintenance burdens.
Has anyone here been through this before? Any lessons, regrets, or advice?
Thanks a lot in advance!
(AI used to improve spelling)
Dealing with 5 year old code is okay now. In 10 years it will cause you pain. It's like going back to an ex after you lose attraction. It never works out and hurts both parties (in this case your users, because you won't maintain it or want to pretty soon)
Just don't. Keep a copy wherever others suggested, keep a photo in the folder with the ex-bf/gf think about it every few years (I wonder how she is doing - in a Morty voice) and quickly move on!
Because you don't want to become a maintainer. Just make it clear that it is provided as-is, without support.
It does after all represent a lot of value having been poured into it, worthy of a better ending than rm -rf, even if it didn't reach break-even.
Shouldn't have a maintenance burden. That burden will be extinguished with the corporation.
If I were you, I'd put it on github with a corporate account, leave a readme that it's abandoned and then mark the repo read-only.
Let (interested) customers know and encourage them to fork it. Disable issues and pull requests before you publish.
Alternatively, put a source dump on your website, and let people know they can put it on Github, but you're not doing it. If nobody republishes it before the corporate site goes down, it is what it is.
Because “startup” is often used in a weak sense only to mean “new business,” there may not be corporate protections for the beneficial owners of this startup.
If it is a Silicon Valley style startup, then the founders probably ought to talk to their investors because that relationship matters and the investors probably know something about open sourcing code bases from shut downs.
EDIT: to clarify as I realize that was pretty vague.
1) Depending on how you use your dependencies you may have a licensing conflict that makes the GPL incompatible.
2) I think your shareholders/VCs/whoever holds the equity (or if you're bankrupt the senior bondholders) probably own the copyright for the code so you would need their permission.
If you really want to put an open source project out in the world the right way, taking what you learned and building an appropriate code base might be a better route.
And if you don’t really want to put an open source project out in the world, that’s okay.
Your customers had an interest in paying you enough to stay in business. They did not pay enough (and maybe because you did not charge enough).
And to me, it seems like you are probably ready to move on and now is probably a good time for moving on. Good luck.
Or to put it another way, if it’s not a hell-yes, it’s a No in practice. Even if you don’t want it to be one. Open source projects need enthusiasm. Only Google can get away with throwing code over the wall.
That's not true. The OP mentions there are current users. Some of the current customers might be able to use ANY distribution to patch problems for a while. Eventually, someone mightneed to decide on serious maintenance or not. But initially it quite possibly would not require much.
When there are current users, the future may not be a thriving project but may be simply a patched up current solution. Nothing wrong with that.
I suspect this is the case pretty often: a current solution is not great but it's in place. The code itself is nothing to write home about, but it's in place. Patching problems in the code might be the easier path for the user.
Logical Possibility != Statistical LikelihoodIn my opinion; if you can't sell it you could also try to hand it over to another company / third party. Finding someone to take over a project takes a bit of time but it'd allow for it to survive.
However you need legal advice, fast. First talk to a lawyer who understands this.
In exchange of the code ask them to make a non profit organization and handle the rights to them. They will be responsibles for their security in case of vulnerabilities.
Software is hard to kill. See Softpress Freeway as an example in the same industry.
With AI and other tools developing rapidly, I wouldn't be surprised if someone was able to do things with your code in ways you didn't expect, even if you choose not to open source it yourself.
throwawayffffas•7mo ago
> Legal complications
If your code was written by you and you are not infringing on any patents and you don't have any client data in your repos, you should be fine I guess, but I am not a lawyer.
Just make it MIT and open it to the public. Make sure there are no keys or credentials in the repos either.
amadeoeoeo•7mo ago
ezekg•7mo ago
amadeoeoeo•7mo ago
justinrubek•7mo ago
throwawayffffas•7mo ago
It will be also easier for other people to find them and report or fix them.
In general it's a bad plan to rely on code secrecy for security. It's security through obscurity which never works out. All the cryptography schemes and algorithms are public. Most of the public internet runs on open source code. Transparency is a strength, not a weakness.