1 |
Rich Freeman posted on Thu, 30 Jun 2016 20:24:43 -0400 as excerpted: |
2 |
|
3 |
> In this case I can assure you that people were frustrated that it took |
4 |
> as long as it did to end up with a decision, and it largely was because |
5 |
> we recognized the controversy. There were multiple rounds of meetings |
6 |
> and numerous opportunities to provide feedback. Ultimately, however, |
7 |
> providing feedback does not guarantee any particular result. |
8 |
|
9 |
Indeed. |
10 |
|
11 |
This bit of the previous discussion has been missing from this round so |
12 |
far, but FWIW, one of the big frustrations from the council side and I |
13 |
think from most looking on (certainly me) was that they /begged/ games |
14 |
team to step up and present a reasonable defense of their policy and |
15 |
provide some sort of presumably opposing viewpoint from which to work |
16 |
toward a compromise somewhere in the middle. |
17 |
|
18 |
And they begged games team to work with them to let other devs on the |
19 |
team and help get them up and running with policies, etc, as bugs were |
20 |
piling up. |
21 |
|
22 |
But the problem was, games team was pretty much MIA, in terms of any form |
23 |
of communication whatsoever. While some individual games team members |
24 |
were still maintaining their individual ebuilds, /nobody/ was willing or |
25 |
able to speak for the team, and to help with other ebuilds that were |
26 |
effectively left rotting, because games team, at least as an actually |
27 |
working /team/, simply /wasn't/, any more. |
28 |
|
29 |
There were volunteers who /tried/ to get on the team. No ack from the |
30 |
lead or anybody to speak for the team. Nobody to bring them upto speed |
31 |
on policies, etc. And nobody answered council or QA questions about why, |
32 |
and what could be done to fix it. And the eclass was left rotting as |
33 |
well, an area that's definitely QA's territory, again seemingly with |
34 |
anybody willing to reply apparently vanished from earth. |
35 |
|
36 |
Meanwhile, games were flourishing in overlays, because games in gentoo |
37 |
itself had become a toxic wasteland with the absent games team asserting |
38 |
control, but with nobody willing or able to do anything about it. |
39 |
|
40 |
|
41 |
So eventually, after repeated /begging/ from both QA and council with, |
42 |
essentially, crickets in response... |
43 |
|
44 |
Council had to act to bring back some sort of sanity. Including working |
45 |
to finally close a long open security bug on at least one game /because/ |
46 |
of the way gentoo was handling things -- it wasn't a problem on other |
47 |
distros because they didn't have a special games group to deal with. |
48 |
|
49 |
Even then, /nobody/ was willing to volunteer to lead the newly reforming |
50 |
games team, and few were willing to even be members. By this time |
51 |
everything involved with it was simply too toxic, I guess. |
52 |
|
53 |
So what council did first, was basically formerly declare than anyone |
54 |
that wanted could commit new (not yet in-tree) games on their own, |
55 |
without having to fear games team vetoing or reverting. And the eclass |
56 |
was deprecated as effectively unmaintained, simply recognizing the fact. |
57 |
|
58 |
And even /that/ was basically the minimum necessary to get some |
59 |
functionality back, hoping it might wake someone up on games team to at |
60 |
least have someone to work with and to try to compromise with. |
61 |
|
62 |
But six months later, we still don't see a newly reactivated and gaining |
63 |
health games team trying to get back in the game, as it were. |
64 |
|
65 |
And the /biggest/ problem, we /still/ don't have anyone of the former |
66 |
members (remember, no one further could join as it was too dysfunctional) |
67 |
volunteering to step up and actually head the thing, maintain or arrange |
68 |
for maintenance of the eclass, etc, despite the fact that some are still |
69 |
raising objections to moving ebuilds off the eclass, etc. |
70 |
|
71 |
Bottom line, the former games team is /still/ dysfunctional and basically |
72 |
dead, and can't even pull itself together enough for there to be any |
73 |
other realistic alternative /but/ to have QA continue to work on moving |
74 |
existing ebuilds off of it, as proposed here. This has gone on for |
75 |
/years/, and truth be, it's really a bit late now, even if games team |
76 |
/were/ to suddenly resurrect and try to reverse things now. |
77 |
|
78 |
But that /still/ isn't happening. There's others objecting, still saying |
79 |
it's not their use-case but it's a shame... and it is a shame... but at |
80 |
some point, that stinking rotting corpse just /must/ be buried or burned |
81 |
or otherwise disposed of. Otherwise, it's just a worsening public health |
82 |
hazard, however much of a shame that death might be. |
83 |
|
84 |
-- |
85 |
Duncan - List replies preferred. No HTML msgs. |
86 |
"Every nonfree program has a lord, a master -- |
87 |
and if you use the program, he is your master." Richard Stallman |