1 |
hi, |
2 |
|
3 |
how would be handled cases where you and me agreed that you will take |
4 |
care of pull requests on behalf of sound@ and proaudio@? and what if a |
5 |
package is maintained by multiple maintainers or even some maintainers |
6 |
and a project, each with a different preference? how that would be |
7 |
solved to not bring in some confusion? and how about maintainers that |
8 |
are not gentoo devs? and what if there are packages that have a |
9 |
maintainer that is mia but has the no-accept policy set and some other |
10 |
dev would like to fix a package that has an annoying bug (using a pull |
11 |
request by a contributor) as the reported maintainer is mia, or a |
12 |
contributor might want to maintain the package? and what if a maintainer |
13 |
wants pull requests just for some packages and not for others? and what |
14 |
if a pull request is referenced from a bug at bugzilla but the |
15 |
maintainer does not accept pull requests? |
16 |
|
17 |
sorry for this flood of questions but atm it brings confusion to me :-) |
18 |
from my point of view and personal preference, i appreciate pull |
19 |
requests from contributors if those are of a decent quality, but for me |
20 |
it's hard to easily find out the relevant pull requests. with the new |
21 |
packages.gentoo.org it might be easier in the future but i'm not sure |
22 |
yet how reliable it is atm as for example the list of outdated packages |
23 |
for proaudio@ |
24 |
(https://packages.gentoo.org/maintainer/proaudio@g.o/outdated) |
25 |
does not seem to be updated or i misunderstood something. the same goes |
26 |
for the list of bugs |
27 |
(https://packages.gentoo.org/maintainer/proaudio@g.o/bugs) which |
28 |
seems to be missing some bugs as my list with "Assignee: |
29 |
proaudio@g.o" has 96 bugs atm compared to 76 bugs at |
30 |
packages.gentoo.org. |
31 |
|
32 |
fordfrog |
33 |
|
34 |
|
35 |
Dne 18. 08. 20 v 14:05 Joonas Niilola napsal(a): |
36 |
> Hey, |
37 |
> |
38 |
> some of you may already have seen the new packages.gentoo.org page, |
39 |
> https://packages.gentoo.org/ |
40 |
> |
41 |
> and the new maintainer pages in it, |
42 |
> https://packages.gentoo.org/maintainers |
43 |
> |
44 |
> If you open a maintainer page, |
45 |
> https://packages.gentoo.org/maintainer/juippis@g.o |
46 |
> |
47 |
> you can see a tab called "pull requests" there, |
48 |
> https://packages.gentoo.org/maintainer/juippis@g.o/pull-requests |
49 |
> |
50 |
> with description saying: |
51 |
> "If you also like to help the Gentoo project, you can consider sending a |
52 |
> Pull Request via GitHub. |
53 |
> Before doing so, you might want to take a look at the wiki page." |
54 |
> |
55 |
> I'm suggesting of adding a new metadata flag to our Wiki's |
56 |
> User:/Project: page which then prints a message to this page saying |
57 |
> whether the maintainer (be it project or user), "accepts" or "deals |
58 |
> with" Github contributions. The wording can be a bit better, but it'd be |
59 |
> there to **notify** our **contributors** whether their time and effort |
60 |
> will most likely be wasted making a pull request for this particular |
61 |
> maintainer. |
62 |
> |
63 |
> This note would then be displayed in every package the maintainer is |
64 |
> assigned to, |
65 |
> https://packages.gentoo.org/packages/media-libs/rlottie/pull-requests |
66 |
> |
67 |
> I'd imagine a simple switch in Wiki could do it. No need to add anything |
68 |
> to ::gentoo repo. The switch can be visible in User:/Project: page, but |
69 |
> it doesn't have to. Unspecified metadata flag would print something like |
70 |
> "This maintainer hasn't specified whether they handle Github pull |
71 |
> requests. If you wish to help using Github, please also open a bug prior |
72 |
> to that and link your pull request commit to that bug (add link to |
73 |
> glep-66 here)". Or just default it to "No." |
74 |
> |
75 |
> Note that the bug text could always be displayed nevertheless, since |
76 |
> that is still the main channel to communicate with maintainers. |
77 |
> |
78 |
> It's undeniable we get a lot of pull requests and unfortunate that many |
79 |
> are left without any attention to rot. |
80 |
> https://github.com/gentoo/gentoo/pulls |
81 |
> |
82 |
> I think this would serve both parties - devs and contributors, with |
83 |
> little to no cost. |
84 |
> |
85 |
> -- juippis |
86 |
> |
87 |
> |