Agenda for Env-and-Stacks WG meeting (2014-04-08)
mmaslano at redhat.com
Wed Apr 9 06:39:02 UTC 2014
On 04/09/2014 02:07 AM, Toshio Kuratomi wrote:
> On Tue, Apr 08, 2014 at 04:16:58PM +0200, Marcela Mašláňová wrote:
>> On 04/08/2014 03:02 PM, Toshio Kuratomi wrote:
>>> not sure that the ruby scl should have its own change. It needs to have
>>> the equivalent filed for the fpc to evaluate, though.
>>> Since the guidelines aren't final, probably open an fpc ticket so the
>>> fpc sees the request and more that it's needed for the fedora scl
>>> change. Although the scl package guidelines aren't final, the
>>> guidelines/criteria for approving the scl itself were approved so fpc
>>> should be able to evaluate it in parallel to finishing the packaging
>>> If we remove the ruby scl change we should add more to the main scl
>>> change, though, about expectations around the scl approval. For
>>> instance, we probably want to touch base with docs/marketing to see if
>>> they want to publicize scls in the exact same way as fedora changes or
>>> have a slightly different procedure.
>>> Also note, in case no one saw it in either fpc or fesco meeting notes,
>>> I'm traveling to a week and a half conference now followed by a week and
>>> a half of vacation.so I likely won't be around for any fedora meetings
>>> until april 27th (and playing catch up with my email for that first week.)
>> I'm trying to provide feature needed by Cloud WG, that's all. I can
>> file a new ticket on FPC, but wouldn't it just duplicate
>> communication about General SCL guidelines?
>> Ruby193 could test workflow around SCL in Fedora, that's another good
>> reason to try how far can I get it and what won't work :)
>> I would prefer to keep my changes as is and let FESCo decide.
> I sense a miscommunication here -- the Draft Guidelines for approving an SCL
> say that you need to get the FPC to approve new SCLs:
> I felt that a new FPC ticket would be good because this is the first SCL to
> be approved and the FPC likely won't become aware of it unless it's called
> out in a ticket.
Ok, that's new. It would be great to actually know, which part of
guidelines were already approved and which not. I'm following meeting
minutes and sometimes looked at logs from FPC, but I probably missed
Also you should probably add category in FPC ticket.
More information about the devel