On 10 July 2015 at 15:56, Ankur Sinha <sanjay.ankur(a)gmail.com> wrote:
As opposed to interrupting the infrastructure folks? :P
I know what you mean, but really, it's not that much work especially if
there are multiple admins to a trac instance.
If you know what I mean then you're just trolling.
But then you haven't completely understood what I meant. When you
have a mailing list in place, those who want to keep a passive tab on
what's going on in apac trac can simply sign on to the mailing list
instead of asking to be added to the trac. The action of creating a
mailing list is a one-time while adding each person to trac scales
linearly. Besides, you can do a lot more with the mailing list, like
get a weekly digest instead of getting bombarded for every update in
every ticket.
The only complains I've seen on the ambassadors list is about
spam
posts. Most people don't mind getting e-mails that don't concern them
or their regions - they seem to be happy to skim the subject since it
gives them some idea of what's going on, i.e., keeps them in the loop.
I am not talking specifically about the ambassadors list. In general,
it is difficult to keep conversations on topic on broader mailing
lists if it is the only place to discuss everything. Very soon topics
become niche enough that only a small subset of recipients actually
care about what's going on.
Consider extrapolating this argument of yours to the project as a
whole. Would a single fedora contributors mailing list be useful?
Oh, completely, but I've rarely seen any regional list providing
such
summaries. If they do that, I'm for as many mailing lists as people
want.
Umm, weekly meeting minutes? I've rarely seen anything else happening
in the APAC community outside of these meetings.
I'd like to know what you think the main reasons are in that case
so
that we can look at how they can be addressed to improve communication
in the community.
I don't think it is necessary to have the level of engagement that you
seem to imply. It is generally a good thing that teams work in
separate spaces because it avoids distractions. If there is a
communication issue between specific teams then they need to work on
making sure that communication lines between them are clearer. Simply
merging both teams' communication lines will only increase the amount
of noise one has to filter to get to the bit they're interested in.
I, personally, strongly believe that fragmentation into small groups
is
one of the primary reasons - it adds an additional burden of updating
the entire community with summaries, and therefore, no one really does
it - not regional ambassador lists, generally not even different teams.
If you want to know what a team is doing, you need to join their list
and keep up with their work yourself.
It is definitely not meant to be a regional ambassador list. I don't
think the announcement tries to say that either - it talks about
tracking trac activity and budgeting, but there's also the 'issues
relevant to the apac region'. Think of this as a broader version of
the india mailing list, not as a narrower version of the ambassadors
mailing list.
Siddhesh
--
http://siddhesh.in