1 |
Hi, everyone. |
2 |
|
3 |
TL;DR: if nobody comes up with a good solution and implements it, we'll |
4 |
be discontinuing support for GitHub as contribution platform for Gentoo |
5 |
and automatically closing all PRs except for those meant for proxy- |
6 |
maint. |
7 |
|
8 |
|
9 |
We've put a significant effort to make it convenient to use GitHub to |
10 |
contribute to Gentoo. Many users have appreciated that, and so did many |
11 |
developers. I think we can call that a success. However, I don't think |
12 |
that's really successful enough. |
13 |
|
14 |
The main goal for using GitHub was to make it easy both for users to |
15 |
submit their contributions, and for Gentoo developers to review |
16 |
and merge them. However, for that to work out we'd actually have to have |
17 |
more Gentoo developers *care* and we don't have that. |
18 |
|
19 |
We have maybe a dozen developers who are actually looking through their |
20 |
own pull requests. Everything else is usually reviewed by the few active |
21 |
proxy-maint team members who are simply overwhelmed with work. What's |
22 |
even worse, they are regularly attacked by other developers which |
23 |
doesn't really encourage further work. |
24 |
|
25 |
The two major problems we have are: |
26 |
|
27 |
1. Developers who refuse to review pull requests to their packages. |
28 |
Yes, I can understand that some people have their reasons for not using |
29 |
GitHub. However, I do not consider it appropriate if they refuse to use |
30 |
GitHub to review pull requests for their Gentoo packages but at the same |
31 |
time use it for their own toy projects and/or work. |
32 |
|
33 |
In any case, those developers effectively mean that we either have to |
34 |
close the contributions in the users' face or proxy them to maintainers. |
35 |
The first solution harms contributors, the second adds a lot of work. |
36 |
|
37 |
2. Developers who ignore GitHub mail for whatever reason, and expect us |
38 |
to ping them on every contribution. We just don't have the resources to |
39 |
track everyone who might or might not have gotten a notification, or |
40 |
maybe he should be pinged twice, or maybe he doesn't want to use GitHub |
41 |
except he added his account to Gentoo org for the fun of it... |
42 |
|
43 |
In either case, the results are that pull requests stay open without any |
44 |
reply for a long time, we spend a significant effort trying to get |
45 |
someone to merge them, and when someone finally gets to them it turns |
46 |
out they need to be updated... This doesn't really work for our users, |
47 |
neither does it make things easier for us. If anything, it just means |
48 |
some of us end up doing a lot of extra work for no final benefit. |
49 |
|
50 |
Unless someone has a very good idea how to solve this, I will declare |
51 |
pull requests for regular packages unsupported 7 days from now, that is |
52 |
on 2017-11-07. After that date, as time permits I will update |
53 |
the relevant documentation and modify the scripts to automatically close |
54 |
incoming pull requests with appropriate explanation. |
55 |
|
56 |
Pull requests will still be supported by proxy-maint. That is, pull |
57 |
requests against proxy-maintained packages and new packages will be kept |
58 |
open and assigned to proxy-maint team. If someone wants to, I can |
59 |
include him in the exclusion list as well -- however, I'd like to avoid |
60 |
keeping the list too long to avoid confusion. The generic image would be |
61 |
'we use GitHub for internal work with our proxied maintainers, external |
62 |
contributions go via whatever else'. |
63 |
|
64 |
Thanks to all the people who put their work into submitting pull |
65 |
requests, reviewing them and supporting us. |
66 |
|
67 |
-- |
68 |
Best regards, |
69 |
Michał Górny |