[CentOS-devel] Meetings infrastructure?

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 03/17/2015 09:22 AM, Dave Neary wrote:
> Hi everyone,
> 
> I would like to have a kick-off meeting for the CentOS NFV SIG
> next Thursday, at 14h UTC, and I had a question about meeting
> infrastructure - is there a preferred meeting method (IRC, phone,
> hang-outs, etc)? For the first meeting, I would like to have a
> phone call, and I can arrange a conference call bridge, but I
> thought perhaps CentOS preferred/required SIGs to use something a
> bit more community friendly.

We've been all over the place in practice, but I *think* the agreement
is generally the same.

For regular meetings, IRC is preferred for the usual reasons -- ease
of understanding for non-native speakers, low barrier, easy
transcripts, easily searchable, etc.

We have an unwritten practice of kicking a SIG off with a video
meeting, and having an occasional (4x/year?) of doing a video sync to
work through things. Google Hangouts has been the choice as giving
realtime read-only to a wide audience, instant meeting archive, etc.

> What infrastructure for community meetings exists, and how can I
> go about reserving a time slot if there's something like an IRC
> meeting channel with meetbot recording minutes?

Use #centos-devel on Freenode for regular IRC meetings, centbot is
your meetbot instance. The only trick is that minutes are not posted
live automatically, you need to ping Arrfab or Evolution to do that
after the meeting. (Protection from spammers.)

We don't have enough going on that we cross each other on IRC, but it
would be a good idea to a single wiki page that lists all regular
meetings. I've got that on my todo list now to get up soonest.

- - Karsten
- -- 
Karsten 'quaid' Wade        .^\          CentOS Doer of Stuff
http://TheOpenSourceWay.org    \  http://community.redhat.com
@quaid (identi.ca/twitter/IRC)  \v'             gpg: AD0E0C41
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iEYEARECAAYFAlUIWu8ACgkQ2ZIOBq0ODEEsYACg1ovIb060biOIGZjTxLoqWTzO
aqUAnR6yY57H8YUgBR1LVyOeTPELnPdm
=bBMg
-----END PGP SIGNATURE-----