Thank you, Potch, for working on this and sharing it with us.
I have mixed feelings about this proposal.
On one hand, I like that we have a fully open, public meeting
that those who are interested in Mozilla can attend.
On the other hand, I recognize the accessibility issues present with the
current meeting format, and the resource burden it places on us in the
form of having to maintain two meetings in order to communicate fully.
Mike Connor's statement about choosing "strengthening our communication
with active non-employees" over preserving 100% transparency resonates
with me. I wonder, though, if it is a mutually exclusive choice.
What are possible ways to strengthen our communication with active
contributors, make meetings deliver greater value for the resources
spent, and increase transparency and accessibility to potential
contributors?
I'm also wondering what data is currently available to us about project
meeting attendance and how we can use that to inform this discussion.
Mostly I want to know how many people will be impacted by this decision
and in what ways can we offset that impact?
Publishing notes, with privileged information redacted seems to make
sense. Is there more we could do?
Could we also use this change as an opportunity to advertise other
channels that are public, but specific to particular projects? E.g. "Our
project-wide meeting is no longer totally public, but here are public
meetings you can attend to learn about specific initiatives you might be
interested in..."
There's a chasm to cross for an interested party to become an active
contributor. I'd like to know if the public meeting has been helping
people make that journey. And, if it has, what can we put in
its place if this proposal goes forward?
-Ck
On 05/21/2014 09:58 AM, Matt Claypotch wrote:
Hello!
I've been mulling over ways we can improve upon and evolve the
venerable Monday Mozilla Project Meeting for about a year now, and
recently been in discussions with Chris Beard, Mitchell Baker, and
Mardi Douglass about how we can adapt the current format of the
meeting to the changing needs of Mozilla. The following is a proposal
for some changes we'd like to make.
# Audience
The Project Meeting will switch from a 100% public call to available
for all Mozillians. The goal is to have as lightweight a barrier to
viewing and participating in the meeting as possible. The official
definition of the intended audience is "individuals who are active in
the project and/or have a good faith interest in the mission".
# Timing
Right now the meeting is scheduled at 11:00am Mountain View time
(PST/PDT). This is simultaneously too late for much of Europe and too
early for Asia. We'd like to move the call to earlier on Monday (9:00
or 9:30am) to better-accomodate Europe. The idea of rotating the
timing of the meeting was floated, but would likely result in it
being impossible to schedule around.
There is additional discussion of which day of the week to hold it,
with Tuesday being the likely candidate to avoid constant preemption
by Monday holidays.
# Format
The goal is to merge the current public meeting content with the
more casual conversational format of the internal staff meeting. By
merging them, the Project Meeting would grow to 45 minutes from its
current 30.
1) Friends of Mozilla - Thank-yous to contributions made to the
project in the last week. 2) Standing Updates - Certain goal-oriented
and mission-focused topics will have an every-week update given. This
is similar to the Product Updates but reduced in scope. 3) 3 Minute
Speakers - This is the current Speakers section as it currently
stands, with a slightly higher focus on timeliness. The number of
speakers in a given week will be capped for time-reasons to 5. 4) Q &
A - This will start with answers to questions that have been
pre-submitted via our Moderator system, and will transition to open
questions collected from IRC and Vidyo.
Currently calendar events are given a 'DJ read', this will be
retired, though the calendar will remain as a useful public resource.
New Hire/Intern/Community are undergoing a revamp as well, though
this is far less-defined. The goal is to move these intros out of
this meeting into another format (perhaps something akin to the
Taiwan intros?)
There are still several things to figure out before we fully roll-out
this new meeting format, and this thread as well as a Mozillans
Yammer thread are open for discussion. You can always reach out to me
directly as well!
The Project Meeting has become an unexpected and hugely special part
of my job at Mozilla, and I genuinely look forward to the discussion
and evolution of an excellent resource for the Mozilla Project.
It's your meeting!
~potch _______________________________________________ governance
mailing list governance@lists.mozilla.org
https://lists.mozilla.org/listinfo/governance
--
Christie Koehler
Education Lead, Community Building Team
https://mozillians.org/u/ckoehler/
ckoeh...@mozilla.com
+1 415-317-7603
_______________________________________________
governance mailing list
governance@lists.mozilla.org
https://lists.mozilla.org/listinfo/governance
