Add lead-maintainer

[daviddias]

ref: ipfs/community#301 (comment)

[daviddias]

This is the first PR towards the goal of ipfs/community#301 (comment)

I've updated the permissions of this repo to

I believe these restrictions to be sane, but would like someone to double check.

[victorb]

The "require status checks to pass before merging" option needs to have a status check that is marked as required, otherwise this option does nothing. Should probably be the continuous-integration/jenkins/pr-merge status check as that one includes the full jenkins build on merge.

I think "Restrict who can push to this branch" should be activated and no one should be allowed to push directly to master. From the screenshot, you'll be able to push but no one else.

[daviddias]

@victorbjelkholm Thank you! Just updated to

[daviddias]

@victorbjelkholm would you like to have the honor to review this PR so that I can merge it ? :)

[victorb]

Awesome, looks good!

[victorb]

The target branch requires all commits to be signed. Learn more about signing commits.

Working well for this repo at least! :)

[daviddias]

@victorbjelkholm you'll need to approve again

[vmx]

@diasdavid The screenshot shows that "Require signed commits: Commits pushed to this branch must have verified signatures." is ticked. Is that intentional and a must?