| 1 |
On Sat, Oct 13, 2018 at 8:59 AM James Le Cuirot <chewi@g.o> wrote: |
| 2 |
> |
| 3 |
> On Sat, 13 Oct 2018 13:28:02 +0200 |
| 4 |
> Ralph Seichter <gentoo@××××××××.de> wrote: |
| 5 |
> |
| 6 |
> > Is there any way I could help the Gentoo team? Any vacancies that need |
| 7 |
> > to be filled, or work that needs to be done? |
| 8 |
> |
| 9 |
> Following what I said above, we need more actual bona fide developers |
| 10 |
> who have done the quizzes, understand the issues, can most important |
| 11 |
> can take responsibility for their own contributions. |
| 12 |
> |
| 13 |
> There is the proxy maintainers project, where we can accept |
| 14 |
> contributions with a little less scrutiny, but I personally feel that |
| 15 |
> these contributors really should just become developers. It doesn't |
| 16 |
> matter if you're only interested in one or two packages, any help is |
| 17 |
> very welcome. |
| 18 |
> |
| 19 |
|
| 20 |
I have to imagine that while waiting to become a dev (or not), it |
| 21 |
would still be useful if contributors would like to skim pull requests |
| 22 |
and find ways to contribute to them. |
| 23 |
|
| 24 |
If a dev has pointed out an issue with a pull request, consider |
| 25 |
offering a patch to fix the issue. |
| 26 |
|
| 27 |
If a pull request hasn't been looked at, consider looking at it and |
| 28 |
offering patches to resolve any issues you see. |
| 29 |
|
| 30 |
Sure, ultimately a dev still has to review/commit, but I imagine any |
| 31 |
help with triage will just make their life easier, which means they'll |
| 32 |
be able to get more commits into the actual tree. |
| 33 |
|
| 34 |
And of course all the skills you would use to clean up pull requests |
| 35 |
are for the most part the same ones you'll need to become a dev. |
| 36 |
Also, reading a bunch of dev comments about quality issues with pull |
| 37 |
requests will make you aware of the kinds of QA issues people |
| 38 |
routinely run into, and you'll be less likely to create the same |
| 39 |
problems. |
| 40 |
|
| 41 |
In my experience the best way to get accepted as a committer in just |
| 42 |
about any kind of FOSS project is to basically do just this. Sooner |
| 43 |
or later you'll be noticed and short-listed. You'll also rub |
| 44 |
shoulders with people who are likely to become mentors, and since |
| 45 |
recruiter availability is limited they're going to be bound to focus |
| 46 |
on applicants who are active already. |
| 47 |
|
| 48 |
-- |
| 49 |
Rich |
Archives