Question- should the guide include something about licensing?

[archaeogeek]

Firstly, many thanks for this guide, we've found it really useful when creating contributors guidelines for projects. I was wondering if it should, however, contain something about licensing and how that impacts on contributions? For example, should it point out that if you contribute to an open source project then generally speaking your contribution is also licensed under the same license?

[sigmavirus24]

That sounds like a reasonable addition to me. I think I for one always take that knowledge for granted.

[bitprophet]

Thanks for the question/comment! I agree that it's a common omission in this type of material, and that we should add it. I'm whipping up some basic language now but I'd love some second/third opinions on it once it's posted.

[bitprophet]

Auto-link/close should occur by the time I post this comment...please see that commit for the diff.

FWIW, I considered appending the "feel comfy with the license" bullet with some sort of "if you're not sure what this means, don't worry too much about it - though perhaps take a brief moment to educate yourself - [link]".

Except, a) not sure what the absolute best link would be and b) slightly hesitant to just slam a link in there because links from this sort of central document carry some endorsement weight. I don't want to endorse something without at least a bit of care. Thoughts welcome!