devp2p licensing and other legal concerns

This repo should have a clear license and clear message to contributors under what license they are contributing works.

For specifications, CC-0 is one option.

However, patent coverage is something else that needs to be considered. I have brought the patent issue up for EIPs as well, so consider this issue just to be licensing for now.

Apr 01 '19 01:04 bmann

I'm not sure how to proceed here.

Oct 22 '19 14:10 fjl

@fjl for starters, follow the EIP repo in applying CC0 to the spec.

Oct 25 '19 01:10 bmann

The part I don't understand is: why does a having a license matter for this project? There is nothing to protect here. We want people to implement the specs in software, and it's fine if anybody copies the specs and turns them into something else.

Oct 25 '19 09:10 fjl

Any of your contributors can assert copyright if they don’t explicitly give it away. You’re protecting the open-ness. Without a license, all contributions are either owned by the individuals or by their employers (based on their employment). Why? Because we have messed up copyright laws.

Oct 26 '19 05:10 bmann

Have a look at https://choosealicense.com/ and specifically https://choosealicense.com/no-permission/ which is also available from the front page of that site.

Feb 04 '20 00:02 rlegene