3 ms·
I like seeing things like this. There are two practical problems that come to mind (not fundamental problems): 1. Many traditional distros - Debian (and by ext
by geofft 9y ago
I like seeing things like this. There are two practical problems that come to mind (not fundamental problems):
1. Many traditional distros - Debian (and by extension Ubuntu), Fedora (and by extension RHEL), etc. - won't carry your software if it breaks the Open Source Definition in this way. If you're targeting npm modules, this isn't a problem at all, given how much technical work needs to be done to get the average npm module in one of these distros. :-) But there are lots of sizable use cases where this is a problem, and the Open Source Definition has become something of a Schelling point.
One solution in the Debian/Ubuntu case (I'm less familiar with the Fedora/RHEL side of this) is to package your software for Debian "non-free" and Ubuntu "multiverse", which are for software that can be freely redistributed but is not Free Software and therefore not officially part of the distro / officially supported to the same extent. This isn't an extremely popular choice right now, but I think that could change.
2. Sort of expanded from there, really the value of an open-source project is far more in its community, that is, in the trust that it will continue to do the thing you want it to do as your requirements and the world around it change, not in the code as it is. I don't think that the most valuable thing you have to offer is your software, and I do think that compared to ongoing support and maintenance and interaction with users, the value of the software itself is probably approximately $0, yes. As a perhaps-controversial example, consider systemd: there are plenty of other service managers with similar approaches to process supervision, and plenty of other inits, but systemd has the property that everyone expects Red Hat to continue funding full-time development on it for many years, there's a lot of people on StackOverflow who have answered questions about it, etc. That's not particularly a function of the code itself; that's a function of an entity like Red Hat standing behind it and basically every distro having adopted it.
Speaking for myself, at least, I'm unlikely to try to convince an employer that we should use some piece of software that's sorta-open-source when actually-open-source options exist, unless the support around it is so good that we might as well treat it as a normal proprietary competitor that happens to make source available to customers if they want. Mostly I'm hesitant because I don't expect other companies to do the same thing, and I therefore don't expect the ecosystem to grow.
If you can cause people to believe that License Zero software is as viable as open-source software with a similar level of functionality, that ecosystems will grow around it as well as with open-source software, etc., it definitely sounds like this model is better for long-term sustainability of the project.
- kemitchell 9y agoThanks for your time on these comments. I may have to eat some words about the general quality of HN discussion ;-P Your point on OSD-gated repositories is dead on. As a practical matter, I think many of s run non-free software on Linux. I'm typing this into Chrome on Debian, and I'm sure I've enabled some non-free APT repos. It's also interesting to see how many of the "current generation" hosts and repositories made the jump from OSD-only to "anything you're willing to have us distribute". GitHub's in that box, with npm. There is definitely a potential holdout problem on adoption. But if there's any big, general, meta conclusion to take from Open Source in recent years past, it's that little players make independent decisions that add up to a compelling proposition, and enterprise follows the value. Niggling structural or terms objections fall away.
- mwcampbell 9y ago> I don't think that the most valuable thing you have to offer is your software What about the OP's point that typical OSS business models don't provide an incentive to write great software, but may in fact provide an incentive to not do so? Consider the fact that great software should just work with minimal support or training.