How would you suggest we track who has commit access, etc? The same
way we do with developers, via a developer bug?
I ask because I've noticed a lot of inactive proxied maintainers—one
of which had been listed in metadata.xml for 6 years but had never
committed to ::gentoo.
BUT, we can't write a simple gitolite ACL that limits the content within profiles/package.mask or other files in profiles/ (we can write hooks
that might be able to do this, but that still requires the challenge of validation inside the file).
I'd EXPECT a contributor to WANT to package.mask a cutting edge version
so it has time to bake and get well-tested, but if they can't do both
parts of the commit themselves, this process is likely problematic.
How do we make the mentorship process more lightweight?
(and possibly the quiz process, I haven't seen how the quiz has changed
since I last mentored)
Let's start with a potential intersection of your two ideas:
(these numbers are arbitrary, but try to reflect what I see some of the trusted contributors doing)
- 9 good submissions (patches or PRs) over a 3 month period [must be at least 3/month]
- will get you an invite from recruiters to join
- either without a mentor, or a lightweight mentor
2nd RFC: Recruiting proven contributors without a mentor
I'm aware recruiters don't really need to ask a permission here, but I believe it's great to gauge the general feelings about this beforehand.
What would you say if recruiters started more actively approaching
potential developers? And currently I'm talking about people who have
been active for a very long time (+year or two), who keep up with development-wise changes in Gentoo (eclasses, EAPI, virtuals...),
participate in the community, and always provide top-quality
contributions, but for some reason never got a mentor? I'd like to point
out that this method would only be for the very few ones and recruiting through mentoring would still be the desired method.
Recruiting through
recruiters would still require the candidate to fill the
ebuild/developer quiz, and they'd have to pass it without a mentor. So
I'll emphasize: Currently only few special ones would qualify.
Once again new council has been elected: congratulations to the chosen members! And once again many nominees expressed their wishes to see more non-developer contributors to become official developers. Yet, only very
few people (if any) are interested in mentoring them. I get it, the relationship between a mentor and their mentee is very intimate, and mentoring takes a lot of time. While the Github PRs are helping us
increase the user contributions merged, perhaps it's distancing us from creating stronger bonds with the contributors? But more about this topic later.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 300 |
Nodes: | 16 (2 / 14) |
Uptime: | 97:03:14 |
Calls: | 6,699 |
Calls today: | 4 |
Files: | 12,232 |
Messages: | 5,349,344 |