On Tue, Apr 29, 2014 at 10:27 AM, Kalev Lember <kalevlember(a)gmail.com> wrote:
On 04/29/2014 03:08 PM, Christian Schaller wrote:
>> 5) Installation and compose methods work with rel-eng (live image
>> default, but install tree necessary for compose. PXE/netboot iso?
>> etc)
> Anyone who can take this on? Maybe Kalev?
Sure, happy to take this on.
>> I'm sure I'm missing a few things here. Please chime in with what
I'm
>> forgetting. In short, there's more than enough work to go around.
>>
>> Lastly, we've been rather quiet as a WG as of late. The Cloud WG is
>> going through a confirmation process with their members to make sure
>> people are still interested and willing to do work. That's not a bad
>> idea for ourselves. WG members, please take the time to reply with
>> whether or not you wish to remain a WG member.
> I do, and I do think that we need to find a better way to function as a
> working group. I take part of the blame here for not pushing more on
> this myself. Maybe we should try to structure our work like FeSCO? Since
> the plan is for the working groups to replace many of the functions of
> FeSCO then this would maybe be a good model?
I am interested in continuing as well.
Regarding the perceived quietness, I can think of two things:
One is that the #fedora-workstation irc channel isn't working very well
since everybody is using the #fedora-desktop channel instead for
everyday communication. Might make sense to officially ditch
#fedora-workstation?
We could. I have no attachment to it personally, but the existing
#fedora-desktop has it's own historical user set and it's on a
different IRC server from the rest of the Fedora channels.
Another thing that makes it seem quiet is that we don't have
regular
weekly meetings. Other teams are doing those and it seems to be a good
way to show the world what is going on in the WG -- with meeting status
reports and all that stuff.
Right. Christian suggested using more of a FESCo model, which would
mean regular meetings (perhaps every-other week?) and possibly a trac
instance to track work items. Originally we avoided this overhead
because the intention was to "Get stuff done", but in hindsight that's
lead to a lack of transparency and accountability.
Unless there are major objections or helpful other suggestions, I'll
work with the Fedora infrastructure team to get a trac instance setup
and we can work out meetings shortly. (I hate trac, but there's no
better solution that I'm aware of.)
josh