1 |
Dnia 2015-09-13, o godz. 20:56:07 |
2 |
Andrew Savchenko <bircoph@g.o> napisał(a): |
3 |
|
4 |
> On Sat, 12 Sep 2015 21:12:25 +0200 Michał Górny wrote: |
5 |
> > Hello, everyone. |
6 |
> > |
7 |
> > The current workflow for handling github pull requests is at least |
8 |
> > suboptimal. Handling pull requests takes a fair effort from the few |
9 |
> > developers contributing there, and the progress is often stalled by |
10 |
> > package maintainers which are either unresponsive or not registered on |
11 |
> > github at all. That's why I'd like to get your ideas on how we could |
12 |
> > improve the workflow. |
13 |
> > |
14 |
> > |
15 |
> > |
16 |
> > Current workflow |
17 |
> > ================ |
18 |
> > |
19 |
> > Let's summarize the current workflow first. Right now, there's a few |
20 |
> > Gentoo developers who actively monitor pull requests on gentoo/gentoo |
21 |
> > repository. Those developers review incoming pull requests and help |
22 |
> > submitters get their contributions in shape. Some of those developers |
23 |
> > also try to 'CC' (@-mention) package maintainers to get their attention |
24 |
> > on the pull request. |
25 |
> > |
26 |
> > Sadly, @-mentioning sucks for a few reasons: |
27 |
> > |
28 |
> > 1. Many of the Gentoo developers have different nicknames on GitHub. |
29 |
> > Some developers don't even set their real names which makes them even |
30 |
> > harder to find. |
31 |
> > |
32 |
> > 2. Teams can be created only by repository 'owners' (which pretty much |
33 |
> > is equivalent of Infra). Which practically means I'm the only person |
34 |
> > migrating teams (projects, herds) to GitHub. |
35 |
> > |
36 |
> > 3. GitHub notifications are not very reliable. Some developers get only |
37 |
> > some of them via mail, some don't. And some simply don't care. |
38 |
> > |
39 |
> > 4. Some developers openly refuse to work with contributors via GitHub. |
40 |
> > Proxying them manually is not really productive. |
41 |
> > |
42 |
> > |
43 |
> > |
44 |
> > Potential solution: bi-dir github <=> bugzilla integration |
45 |
> > ========================================================== |
46 |
> > |
47 |
> > My current idea would be pretty much that: |
48 |
> > |
49 |
> > 1. a new dedicated Gentoo bug would be automatically created for every |
50 |
> > pull request on github, |
51 |
> > |
52 |
> > 2. all comments from github would be automatically copied to bugzie. |
53 |
> > All bugzie comments would be automatically copied to github, |
54 |
> > |
55 |
> > 3. resolving the bug would automatically close the relevant pull |
56 |
> > request. |
57 |
> > |
58 |
> > This way, all pull requests can be assigned to package maintainers in |
59 |
> > Bugzilla without having to resort to GitHub user or team names. All |
60 |
> > involved parties would get more reliable Bugzilla notification mails. |
61 |
> > They could choose to either use the provided URLs to discuss the pull |
62 |
> > request on GitHub, or discuss it directly on Bugzilla, whichever is |
63 |
> > more convenient to them. |
64 |
> > |
65 |
> > The additional Bugzilla load should be manageable, though we may want |
66 |
> > to employ some kind of rate limiting in case someone though it'd funny |
67 |
> > to spam our bugzilla via spamming github. |
68 |
> > |
69 |
> > Problems: |
70 |
> > |
71 |
> > - handling line comments (probably a Bugzie comment with quoted code |
72 |
> > snippet), |
73 |
> > |
74 |
> > - handling comment edits and removals, |
75 |
> > |
76 |
> > - some people will get double mail for each comment, |
77 |
> > |
78 |
> > - extra bugs for existing issues (we shouldn't really try to reuse |
79 |
> > existing bugs for this). |
80 |
> > |
81 |
> > |
82 |
> > |
83 |
> > What are your thoughts? Any other proposals? |
84 |
> |
85 |
> Gentoo workflow should not depend on a proprietary tools like |
86 |
> github issue tracker and github pull requests. |
87 |
|
88 |
Thank you for your insightful comment. That's very helpful. Really, |
89 |
thank you a lot. Gentoo would be much worse without such helpful |
90 |
comments. Why do we need community at all, when one developer with his |
91 |
helpful comments can provide all there is ever needed by the distro. |
92 |
|
93 |
-- |
94 |
Best regards, |
95 |
Michał Górny |
96 |
<http://dev.gentoo.org/~mgorny/> |