1 |
Ühel kenal päeval, K, 01.11.2017 kell 09:00, kirjutas Michał Górny: |
2 |
> W dniu śro, 01.11.2017 o godzinie 12∶48 +1300, użytkownik Kent |
3 |
> Fredric |
4 |
> napisał: |
5 |
> > On Tue, 31 Oct 2017 14:19:30 +0100 |
6 |
> > Michał Górny <mgorny@g.o> wrote: |
7 |
> > |
8 |
> > > The harm is that issues are left unnoticed, and users are left |
9 |
> > > on the ice. |
10 |
> > |
11 |
> > That's exactly the problem with bugzilla today. |
12 |
> > |
13 |
> > We're not closing bugzilla. |
14 |
> > |
15 |
> > Closing PR's as an option doesn't improve the situation. |
16 |
> > |
17 |
> > Closing bugs due to being open more than a month doesn't help users |
18 |
> > either, it just pisses them off further. |
19 |
> |
20 |
> The difference is that Bugzilla has a clear assignment rules, and |
21 |
> unless |
22 |
> one screws them up, we can monitor the situation and reassign them as |
23 |
> inactive maintainers are removed. |
24 |
> |
25 |
> PRs are pretty much one big bucket of mess, and the more of them are |
26 |
> open, the harder it is to figure out what they are about and what's |
27 |
> the status of them. |
28 |
> |
29 |
> And yes, GitHub sucks at this. |
30 |
|
31 |
Could we tell non-proxy-maint PRs to establish a cross-reference |
32 |
between a bugzilla entry and the GH PR? Then if a bugzilla entry |
33 |
exists, which points at the PR (via URL, See Also, something new or |
34 |
whatever we decide suitable), the PR is kept open after that one week, |
35 |
otherwise automatically closed with info how to create a bugzilla entry |
36 |
for this and re-open the PR? |
37 |
|
38 |
GH is a nice tool for letting users host their patches in an git- |
39 |
am'able way. It would be nice to keep it, but given that point 2) in |
40 |
your original post is unsolved, it's not OK to sidestep maintainers |
41 |
until that isn't solved (and the mentioned "attacks" happen because the |
42 |
same people are constantly ignoring global gentoo conventions in this |
43 |
area). This bugzilla entry, to go with it, would solve it in terms of |
44 |
existing maintainer timeout agreements. |
45 |
|
46 |
|
47 |
Mart |