4 ms·

One rather dull, but important, aspect to think about early on is licensing. More permissive licenses seem to be preferred today, especially if you want submiss

One rather dull, but important, aspect to think about early on is licensing. More permissive licenses seem to be preferred today, especially if you want submissions from corporate entities. Related to that is keeping some kind of contributors record (the important point being you at least have a valid email for every person that submitted something).

duncan_bayne 12y ago
If you use an over-permissive license, you run the risk of a company like Apple growing to a multi-billion-dollar enterprise off the back of your hard work, then migrating in a proprietary direction once rich. Whether that's a problem or not is up to you and your sense of fairness :) My preference is the LGPL, for reasons I explain in the boilerplate README for my FOSS work: ===== The GPL is specifically designed to reduce the usefulness of GPL-licensed code to closed-source, proprietary software. The BSD license (and similar) don't mandate code-sharing if the BSD-licensed code is modified by licensees. The LGPL achieves the best of both worlds: an LGPL-licensed library can be incorporated within closed-source proprietary code, and yet those using an LGPL-licensed library are required to release source code to that library if they change it. =====