Also see #184 and https://cilium.slack.com/archives/CKC55JL8L/p1607371973036400 for discussion.

Could you add a commit that only renames readme.md? Seems like it's throwing off the diff somehow, I can't tell what has changed.

The contribution guidelines sgtm largely, I think we should include that new features have to be accompanied by tests, and that it's best to drop into the slack channel before starting work on a big feature to discuss the design. I'm not super fussed about commit messages, the more detail the better, etc.

Done:

• Added separate rename commit.
• Changes to README.md are now in f66f792. It's basically just line wrapping, consistent punctuation, consistent Markdown styling, adding a License section, and adding a # before the Slack channel name.
• Updated CONTRIBUTING.md to include what @lmb requested.

Thanks for the feedback, PR updated.

Gentle ping: can this be merged now?

This may be specific to people's situation, but leaving it here in case useful to others; if you're running into issues because git doesn't like the case-only filename change (readme.md -> README.md);

• if you're on a case-insensitive (but case-preserving) filesystem (macOS, Windows): configure git to not ignore case-only changes;

  git config core.ignorecase false

• if your CI doesn't like this (for example, runc CI failed on the rename go.mod: github.com/cilium/ebpf v0.4.0 opencontainers/runc#2875); adding a .gitconfig to your github repository to make the change configuration can help; (edit: ignore this: github doesn't use that file)

Hmm.. that config can actually be a bit of a pain as well, because there's no content changes in the readme git still gets confused when switching branches 😓

git checkout master
error: The following untracked working tree files would be overwritten by checkout:
	vendor/github.com/cilium/ebpf/readme.md
Please move or remove them before you switch branches.
Aborting