-
-
Notifications
You must be signed in to change notification settings - Fork 10.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New Maintainer Checklist: add "real" name, meetup suggestion. #6185
Conversation
docs/New-Maintainer-Checklist.md
Outdated
@@ -79,6 +79,8 @@ If they are elected to the Homebrew's [Project Leadership Committee](https://doc | |||
|
|||
If there are problems, ask them to step down as a maintainer and revoke their access to all of the above. | |||
|
|||
In interests of loosely verifying maintainer identity and building camaraderie, if you find yourself in the same town (e.g living, visiting or at a conference) as another Homebrew maintainer you should make the effort to meet up. If you do so, you can expense your meal (within SFC policies). This is a more relaxed version of e.g. the Debian system to meet in person to sign keys with a legal ID verification. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To clarify, we’re talking about expensing the meals for both parties? This is quite a fun idea!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yup! That's what we've done at GitHub also as a gentle nudge and, with a peek at Homebrew's finances, we have enough funds to do that if people aren't being silly about it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@alebcay Durham Homebrew meetup? 😀
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@zachauten Having neglected my GitHub notifications for about five months 😅, I've missed this, but if you're still up for it, let's meet up sometime!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it'd be helpful to link the SFC reimbursement policy but otherwise 👍
We've had problems in the past with Homebrew maintainers being unwilling to disclose their identity or meet other maintainers so here are some very light-touch suggestions to address this in future. These ideas were run past the PLC and agreed there but I still welcome input from maintainers.
Co-Authored-By: Colin Dean <[email protected]>
00f6360
to
42c8861
Compare
Thanks for review and comments all! |
We've had problems in the past with Homebrew maintainers being unwilling to disclose their identity or meet other maintainers so here are some very light-touch suggestions to address this in future.
These ideas were run past the PLC and agreed there but I still welcome input from @Homebrew/maintainers.
brew style
with your changes locally?brew tests
with your changes locally?