[openstack-dev] [all] Question for the TC candidates

Jeremy Stanley fungi at yuggoth.org
Wed Apr 29 15:55:49 UTC 2015

On 2015-04-29 12:59:35 +0300 (+0300), Maish Saidel-Keesing wrote:
> Excerpts from Jeremy Stanley's message of 2015-04-28 16:21:17 +0000:
> >/  On 2015-04-28 16:30:21 +0100 (+0100), Chris Dent wrote:
> />/  [...]
> />/  > What's important to avoid is the blog postings being only reporting of
> />/  > "conclusions". They also need to be invitations to participate in the
> />/  > discussions. Yes, the mailing list, gerrit and meeting logs have some
> />/  > of the ongoing discussions but often, without a nudge, people won't
> />/  > know.
> />/  [...]
> />/  />/  Perhaps better visibility for the meeting agenda would help? As in
> />/  "these are the major topics we're planning to cover in the upcoming
> />/  meeting, everyone is encouraged to attend" sort of messaging?
> />/  Blogging that might be a bit obnoxious, not really sure (I'm one of
> />/  those luddites who prefer mailing lists to blogs so tend not to
> />/  follow the latter anyway).
> /
> I am not sure that you want people chiming in every single TC
> meeting - that will become quite chaotic.

As a constituent, I feel it's not only my right but also my duty to
address the TC on relevant topics if I'm concerned they're not
considering certain aspects/implications of what's being
deliberated. Arbitrary, off-topic banter from random lurkers is of
course unwelcome because it adds unnecessary noise and slows down
the meeting, but I do think people who have concerns should be
encouraged to participate (keeping to the agenda of course) as long
as it's constructive and not preventing the TC from holding a
productive meeting.

I also attend meetings of the Foundation Board, even though I'm not
a board member. As with any government, if you elect people, you
should certainly engage with them in appropriate venues. Sometimes
that means being present for their public assemblies (be they
physical or virtual) so you can participate in those discussions.
Jeremy Stanley

More information about the OpenStack-dev mailing list