by warp on 12/1/2016, 6:50:27 PM
Presumably you want your code to be open source to allow others to contribute.
It is important to pick the right license for your project, because it will change which contributors you will attract (and what your competitors can do with your code). Using a popular well-known license will make it easier for contributors, because they (or their employer) don't have to worry about understanding a license they've never heard of.
So preferably pick something like GPLv2 (use the "or any later version" wording for max compatibility), Apache v2 or MIT.
If possible, don't use a CLA, you don't need it [1] and it's just a bunch of extra paperwork for you and your contributors.
[1] https://sfconservancy.org/blog/2014/jun/09/do-not-need-cla/
We're in private beta right now, but since it's such a security-critical product, from the beginning we've planned on open sourcing the entire business. With a little more than a month until we plan to launch and do that, we're starting to get all of our ducks in a line and are hoping the HN community can help us avoid making common mistakes!
My question for the HN community is this: if you run an open source business, what issues have you run into that we might? Are there any we should definitely do before we open source everything?