5

To pull all the comments together, I'll take the question in parts. I usually state something in the Readme which reads like "Code written by [name and alias], licensed under GPLv3" ... Is this sufficient? In the sense that anyone who wants to exercise their free-software rights can safely do so, yes. But it's very helpful if you do a little more, as ...


4

The CC BY-NC license is most likely not the license you want if you are accepting contributions from others and you are considering publishing the work also as a physical book. As soon as there are multiple copyright holders to a work, all of them are bound by the license terms under which the contributions were made (which is typically the same license ...


3

Repository owners can delete issues and comments, but no, issues should usually not be deleted. If they are no longer needed they can be closed, but keeping them around can still be useful for future reference. If content needs to be removed e.g. because it contains sensitive information or because it contains harassment, then individual comments can be ...


3

Usual practice is to do one or more of these: Make your project work without configuration, by having good default options. (But this doesn't sound like an option for your project.) Include a template for the configuration file and document that people have to copy and rename it, and then put in their proper values. Have a script which interactively asks ...


Only top voted, non community-wiki answers of a minimum length are eligible