> Is there an approach you can choose early in a project on that prevents ever getting in trouble later? 1. Never accept outside contributions in principle. Wo

> Is there an approach you can choose early in a project on that prevents ever getting in trouble later? 1. Never accept outside contributions in principle. Works fine for SQLite, for example. 2. Pick a well-known copyleft license and just stick with it. Works fine for Linux, for example. 3. Use a well-known permissive license that allows redistribution of modified code under a different license without burdensome conditions. Works for lots of projects. 4. Force contributors to assign copyright to an entity that people will trust forever. Ostensibly works for FSF folks, academia, etc. 5. Don't worry about it. Let others pay for lawyers doing law stuff. You can delay making the decision until you have at least a dozen of actual contributors.