It's an unwritten rule to use COPYING for copyleft licenses (such as GPL) and LICENSE for non-copyleft licenses (such as MIT or BSD).
Also I changed the formatting slightly to match the template used at Github as this formatting seems to be what most projects are using nowadays.
Are there any internal or external links to ./COPYING?
@MarcoFalke I fixed that. I haven't touched src/univalue and src/secp256k1 as these seem to be imported from separate repositories (where PRs are pending: https://github.com/bitcoin/univalue/pull/1 and https://github.com/bitcoin/secp256k1/pull/376)
I'm not aware of any such a rule... There appear to be other MIT-licensed projects using COPYING.
NACK.
IMO not worth the huge diff that this generates. And I've never heard of this "rule". For the legal standing it makes no difference.
I can't see how you "fixed" my concern. External links still give the 404 GitHub page for ./COPYING.
I think it is good enough to keep as is for now.
weak ACK as it is the default for GitHub repositories (AFAIK). Meh otherwise.
the default for github repositories
But we're not striving to be a default github repository, it is not a goal to shape the project after their preferences :-)
It's just not worth the effort, I'd prefer focusing on the zillions of actual user-facing issues that are open.