On 08/21/2015 07:39 PM, Rich Freeman wrote:
> On Fri, Aug 21, 2015 at 11:10 AM, hasufell <hasuf...@gentoo.org> wrote:
>> On 08/21/2015 08:50 AM, Ulrich Mueller wrote:
>>>>>>>> On Fri, 21 Aug 2015, hasufell  wrote:
>>>
>>>> Like allowing that devs may or may not use games.eclass, so that
>>>> users cannot expect consistent behavior for games anymore?
>>>
>>> Sorry, but that is not accurate. Usage of games.eclass has been
>>> deprecated by QA [1] (with the council's mandate [2]), so devs should
>>> not use it any longer.
>>>
>>> Maybe QA should be stricter in enforcing its policies, in order to
>>> avoid such false impressions in future?
>>>
>>> Ulrich
>>>
>>> [1] 
>>> https://wiki.gentoo.org/wiki/Project:Quality_Assurance/Meeting_Summaries#Games_team_policies_issue
>>> [2] https://projects.gentoo.org/council/meeting-logs/20140812-summary.txt
>>>
>>
>>
>> May I remind you that
>>
>> """
>> - Motion: "The council encourages the games team to accept join
>>   requests and elect a lead. In the event they don't elect a lead
>>   within 6 weeks, we will consider the team as dysfunctional and thus
>>   disband it."
>>   Accepted with 6 yes votes and 1 abstention.
>> """
>>
>> has never happened? There has been no vote, but the team has not been
>> considered dysfunctional. Instead we are just acting like it doesn't
>> exist, more or less. Sounds good?
> 
> Well, we did say we would disband it.  We just didn't follow through.
> Would you be happier if we did disband it?
> 

I don't know. Stick to your word, maybe?

So far, neither the council, nor QA, nor ComRel were particularly
helpful with the situation.

And QA "proxying" policy-discussions/decisions for a non-functional team
is not a solution (the thread has a clear "QA:" prefix and I don't think
that was by accident).

If the team is disbanded, then regular tree policy applies and
everything goes through the regular community discussion/decision
channels without the need of QA putting their prefixes/hats everywhere.

If a new team is constituted, then they might establish new policies,
also without QA dictating anything. And I would give that some time,
which means don't start funny mass commits/conversions.

Reply via email to