| 1 |
On 10/26/2018 05:42 PM, Michael Orlitzky wrote: |
| 2 |
> On 10/26/2018 04:40 AM, Michal Prívozník wrote: |
| 3 |
>> |
| 4 |
>> So the desired way is to use github pull requests? That is rather |
| 5 |
>> unfortunate. |
| 6 |
> |
| 7 |
> In this case there's no "project" associated with libvirt-snmp; but if |
| 8 |
> there were, it would have a <project-name>@gentoo.org alias that you |
| 9 |
> could send patches to. |
| 10 |
|
| 11 |
Well, why don't we create something like virtualization@g.o? That |
| 12 |
would be a mailing list to discuss virtualization related topics. |
| 13 |
|
| 14 |
Bugzilla is still the official (and in this case, |
| 15 |
> best) place to put these in my opinion. |
| 16 |
|
| 17 |
I don't think so. I've been attaching patches to BZ in the past and the |
| 18 |
response time was very poor. I know everybody is working on gentoo in |
| 19 |
their spare time and I appreciate it, but why not use something that |
| 20 |
works for both sides? I think that if we want to attract more volunteers |
| 21 |
we have to have a process that goes the least into their way. |
| 22 |
|
| 23 |
> |
| 24 |
> Personally I don't mind them on the -dev list, but they do get sent to a |
| 25 |
> thousand people who have no interest in or ability to commit them. |
| 26 |
> |
| 27 |
|
| 28 |
That is the case on every mailing list. Every -dev list has number of |
| 29 |
subscribes far bigger than number of people with commit access. |
| 30 |
|
| 31 |
But I respect your decision guys. I am going to stop posting patches |
| 32 |
until there's an agreement on how to do that. |
| 33 |
|
| 34 |
Michal |
Archives