incubator-flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Martin Heidegger ...@leichtgewicht.at>
Subject Re: Working groups - different approach
Date Mon, 13 Feb 2012 11:08:07 GMT
On 13/02/2012 19:01, Bertrand Delacretaz wrote:
> I disagree - busy mailing lists are good if well managed.

I have not too much experience with good management of mailing-lists. Is 
there some good article/thing to read about that?

> Using [translation], [testing] and similar tags in message subjects. As a
> shameless but IMO useful plug, see my blog post at [1] for a more
> detailed explanation based on Stefano Mazzocchi's "busy list pattern".

Do you think it would be good to predefine such tags in order for other 
people to not confuse them?
A definition would be a lot like a own mailing list (for example one 
could pre-set filters in his mail client of choice).

> As for people in charge, the PPMC is in charge of such things, and if
> only a subset of it is interested in translations, for example,
> getting votes for those people, while others abstain,

How does that work? In what time span can a PPMC member intercept? Is 
one PPMC that raises its voice enough?
What if no PPMC raises its voice?

> is good enough to make progress, no need to appoint specialists.

There are a lot of topics, i assume, where there are simply no 
specialists. However: If one is available
for "mentoring" a aspect (like translation) of Flex then I think, like a 
mentor, he should be addressable.

So analogue to:

    [TRANSLATION] my topic [MENTOR]

that requests for a project mentor. I can see special tagging like:

    [TRANSLATION] my topic [COUNSEL]

that requests for a PPMC member to chime in as the community can't reach 
a green path.
The phrasing "counsel" might not be adequate but I guess it shows where 
I am coming from.

> If such topics become too noisy on this list the project *might*
> decide to split lists, but splitting from the start is totally wrong
> IMO, as you'd split community and create an "us and them" mindset
> which is not good.

We already have a us and them mindset established. Namely: People that 
are not
efficient in a specific language (say Japanese/chinese/german) are the 
"them" as opposed
to "us" - the english speaking folks. Particularly for translation and 
group management this is
a important factor: But also in general: a japanese speaker that has a 
weak english might have
relevant questions/points. Do you know how this is addressed at 
established open source
projects?

> In summary, I think working groups can form right here and now, based
> on [tags] and people doing stuff.

Alright!

yours
Martin.

Mime
View raw message