| 1 |
> Why taking it against arch teams? How is that different from "certain |
| 2 |
> maintainer not taking care of a bug that holds stabilization of certain |
| 3 |
> package by some time measured in months" ? I'll tell you my answer: 'no |
| 4 |
> difference at all'. |
| 5 |
|
| 6 |
You are right, there's not much difference. However, I brought up the topic because |
| 7 |
I felt like this particular situation was a bit of a problem that needed to be |
| 8 |
addressed. Yours is also one that can/should potentially be addressed, and I advise |
| 9 |
you to recommend the council discuss it as well. |
| 10 |
|
| 11 |
My goal wasn't to point fingers or to call anyone lazy. My goal was to address that |
| 12 |
if development in this certain area has stagnated, how can those of us who it |
| 13 |
affects continue to move forward? This is simply an area that is "gray" and needs |
| 14 |
to be discussed. There are many other gray areas that need to be discussed too. |
| 15 |
|
| 16 |
I understand we all have real lives and are volunteers. But if there are areas that |
| 17 |
we are responsible for and we aren't able to meet the needs/demands of the other |
| 18 |
developers in those areas, it's only fair to let them continue moving forward. |
| 19 |
|
| 20 |
I never even mentioned any specific arch in my original request, nor did I call any |
| 21 |
developer out. So please, nobody needs to take this personally. |
| 22 |
|
| 23 |
Caleb |
| 24 |
|
| 25 |
-- |
| 26 |
gentoo-dev@l.g.o mailing list |
Archives