Re: Meeting minutes (April 10th)

[Lucas Rocha <lucasr gnome org>]

Hey,

2010/4/14 Andre Klapper <ak-47 gmx net>:
> Am Mittwoch, den 14.04.2010, 12:36 +0100 schrieb Lucas Rocha:
>> In the long term, I expect release team to only build and smoke test
>> core desktop. The apps moduleset could even be maintained by separate
>> group that would ensure the apps are complying with requirements,
>> building and running as expected.
>
> How well-defined would group membership be?
> Would that group also be part of the release team (which means we would
> introduce roles and responsibilities I assume) or separate (which does
> not make sense IMO as it makes it harder for communication and sharing
> knowledge)?
> To compare, http://techbase.kde.org/Projects/Release_Team lists a bunch
> of people each with specific areas assigned.

Well, maybe just having a couple release team members focused on that
would be enough. I like the idea of having more clear roles for each
r-t- member btw. Anyway, I only suggested a separate group because: a)
it's a delegable task b) the r-t can slack a bit more :-P

It's more important to have agreement on the more fundamental idea
that r-t wouldn't be building all apps for a release in the long term
though. Because that's what seems to be getting heavier and heavier on
each release. The r-t will end up taking days to build all GNOME
modules if we keep adding 1 or 2 modules every cycle... It's basically
unmanageable in the long term.

--lucasr