1 |
On 07/30/2014 06:26 AM, Anthony G. Basile wrote: |
2 |
> On 07/29/14 22:16, Jack Morgan wrote: |
3 |
>> On Sat, Jul 26, 2014 at 04:29:51PM -0400, Anthony G. Basile wrote: |
4 |
>>> On 07/26/14 09:44, Pacho Ramos wrote: |
5 |
>>>> El sáb, 26-07-2014 a las 09:37 -0400, Anthony G. Basile escribió: |
6 |
>>>>> On 07/26/14 09:28, Pacho Ramos wrote: |
7 |
>>>>>> El sáb, 26-07-2014 a las 14:55 +0200, Andreas K. Huettel escribió: |
8 |
>>>>>>> Am Samstag, 26. Juli 2014, 13:56:02 schrieb Pacho Ramos: |
9 |
>>>>>>> |
10 |
>>>>>>>> I guess we will need to wait for the next Council to officially |
11 |
>>>>>>>> decide |
12 |
>>>>>>>> to do this as it will be a big change for ppc* users :/ (I |
13 |
>>>>>>>> remember |
14 |
>>>>>>>> their action was needed for the move to testing of some arches |
15 |
>>>>>>>> and the |
16 |
>>>>>>>> "package-by-package" proposal for others) |
17 |
>>>>>>>> |
18 |
>>>>>>>> Also, I am not sure if any other arch teams (sparc, ia64?) |
19 |
>>>>>>>> would want to |
20 |
>>>>>>>> get this policy too :| (I got ppc* because this concrete case ;)) |
21 |
>>>>>>> At first this is an arch team decision. No need for the council. |
22 |
>>>>>>> |
23 |
>>>>>>> (Given that in this case there is a responsive and addressable |
24 |
>>>>>>> arch team...) |
25 |
>>>>>>> |
26 |
>>>>>>> -- |
27 |
>>>>>>> |
28 |
>>>>>>> Andreas K. Huettel |
29 |
>>>>>>> Gentoo Linux developer |
30 |
>>>>>>> dilfridge@g.o |
31 |
>>>>>>> http://www.akhuettel.de/ |
32 |
>>>>>>> |
33 |
>>>>>> The problem is that blueness looks to be the only member currently |
34 |
>>>>>> replying :/, I have checked their page and I see no team lead or |
35 |
>>>>>> similar. Then, I am not sure how to get the ok to proceed or not |
36 |
>>>>>> :| (to |
37 |
>>>>>> prevent this from getting stalled and we keep trying stabilizing |
38 |
>>>>>> all the |
39 |
>>>>>> things). |
40 |
>>>>>> |
41 |
>>>>>> I remember from older thread (one related with udev |
42 |
>>>>>> stabilization), that |
43 |
>>>>>> blueness was also the only one replying. |
44 |
>>>>>> |
45 |
>>>>>> |
46 |
>>>>> Yeah, not having a clear lead is a problem. No one wants to just |
47 |
>>>>> make a |
48 |
>>>>> big decision on behalf of the team without making sure everyone is on |
49 |
>>>>> board. Pacho, do you have access to timberdoodle? If so, join both |
50 |
>>>>> teams and just take the initiative and let any other "claimants" step |
51 |
>>>>> forward now. BTW, taking the lead doesn't mean doing all the work |
52 |
>>>>> yourself. I want to see ppc/ppc64 in good shape. I'll be happy to |
53 |
>>>>> write scripts to do the demoting to ~ etc etc. |
54 |
>>>>> |
55 |
>>>> I don't even know about timberdoodle :( |
56 |
>>>> |
57 |
>>>> I forwarded the mail to both alias (as I forgot first time), then, |
58 |
>>>> hopefully they will review it :/ |
59 |
>>>> |
60 |
>>>> Will CC them again to this just now with this link to allow all to |
61 |
>>>> read |
62 |
>>>> the full thread: |
63 |
>>>> http://comments.gmane.org/gmane.linux.gentoo.devel/92151 |
64 |
>>>> |
65 |
>>>> |
66 |
>>>> |
67 |
>>> I think its clear who cares about ppc/ppc64. If there are no |
68 |
>>> objections, I'll take the lead of those teams and see this plan |
69 |
>>> through. I'll wait a few days for people to voice concerns. Then I'll |
70 |
>>> start by generating a list of all stable and testing packages on ppc |
71 |
>>> and |
72 |
>>> ppc64. I'll post then and then continue the conversation on just the |
73 |
>>> ppc and ppc64 lists. Don't worry, I won't start dropping to ~ until we |
74 |
>>> have a concise plan and we're all on board. |
75 |
>> I don't think you can/should just take over the leadership of an arch. |
76 |
>> Why not have meeting/discussion for team members. Especially since you |
77 |
>> are proposing such a big change. |
78 |
>> |
79 |
>> |
80 |
>> Thanks, |
81 |
>> |
82 |
> |
83 |
> Okay, any members of the ppc team please speak up. I'll wait a week. |
84 |
> |
85 |
I'm still trying to escape from grad school and getting married this |
86 |
fall, so my contributions have been limited at best, which is why I've |
87 |
been shying away from throwing in my two cents. That said, while I'd |
88 |
rather not just remove stable keywords until there's a reason, I have no |
89 |
problem with dropping keywords for stuff that is holding up |
90 |
stabilization bugs if that's what it takes for things to move forward. |
91 |
If you'd like to have a meeting about it, that's fine too. |
92 |
|
93 |
-Joe |