4 ms·
In practice people I know who've built startups on top of tech they built at universities haven't run into problems. A common strategy is to open-source any cod
by _delirium 10y ago
In practice people I know who've built startups on top of tech they built at universities haven't run into problems. A common strategy is to open-source any code you might want to later use commercially, as a way of throwing it over the fence. Your startup can then use it on whatever terms you open-sourced it under (probably BSD/MIT, if you want to give your later self maximum flexibility). Granted, so can anyone else. But usually the research-prototype code itself isn't enough to build a competitor, and the common case for research code open-sourced by a grad student in some random .tar.gz code dump on their website (or worse, included as a file appendix to their thesis), is that nobody else will even so much as look at it.
The university may have to approve this, but at major CS departments approving students to open-source the code that goes with their thesis is pretty rubber-stamp, at least if it's self-contained.
- lvs 10y agoIntellectual property generated in other fields does not benefit from this kind of liberal license loop-hole, unfortunately. We cannot open-source all applied science according to the current rules.
- _delirium 10y agoAreas where universities are aggressive about patenting definitely have other problems, yeah. Fortunately in CS academia, software patents are relatively uncommon. Not unheard of, but only a small percentage of non-hardware theses end up involved in a patent filing.
- rz2k 10y agoWhat were Marc Andreessen and Eric Bina positions at the University of Illinois' NCSA when developing Mosaic? Even the name Mozilla points to the acrimony over that dispute over intellectual property.