Meetings and mailiglists/decision finding process

Sankarshan Mukhopadhyay sankarshan.mukhopadhyay at
Tue Aug 14 17:41:58 UTC 2007

On 8/14/07, Thorsten Leemhuis <fedora at> wrote:

[massive snip]

Nearly all projects face the same problems (some do sometimes, others to often)

> - only meet on IRC every second week

*with* a defined agenda in place

> - only meet on IRC all four week or when there is a need to

experience (somewhat limited in my case) shows this to be an overkill sometimes

> - somehow accept stuff on the mailing lists if possible. Kind of "send a
> proposal, if some people give a "+1" on the list and no one objects from
> the SIG within some days consider it accepted". Sure, it's often not
> that easy and we needed to work out more details for such a scheme, but
> it could be  or something into that direction. That way the SIG or EPEL
> contributors get more influence and we might need the Steering Committee
> only if a decision can't be found

If there's a set of points to be discussed with some initial seeding
of pros and cons, the mailing list might function as a thermometer as
to how an IRC meet would go if it were called for the same issue

> - weekly status mail from the owners of major tasks

This would actually serve well if summed up monthly as to "what was achieved"


You see things; and you say 'Why?';
But I dream things that never were;
and I say 'Why not?' - George Bernard Shaw

More information about the epel-devel-list mailing list