Meetings no longer have to be in meeting channels

The policy around where it is appropriate to have team
meetings evolved, but the Project Team Guide did not
reflect that evolution.

Change-Id: I9c306461beaa39fae95ed8f1014b47fbbc89f7a9
This commit is contained in:
Thierry Carrez 2018-06-26 11:59:32 +02:00
parent a64e080fd6
commit 15ec22abc2
1 changed files with 6 additions and 7 deletions

View File

@ -15,18 +15,17 @@ Public Meetings on IRC
======================
OpenStack projects are required to have their team meetings (if any) on the
Freenode :term:`IRC` network in one of the publicly logged team meeting
Freenode :term:`IRC` network in one of the publicly logged
channels managed by the OpenStack infrastructure team. As part of
working in an open community, the logging of meetings allows those who
cannot participate at the meeting's designated time to read the logs
and participate asynchronously.
Worth noting is the fact the OpenStack infrastructure team maintains a limited
number of meeting channels. The reason for this limitation is to force
teams to spread their meetings around. This allows for participation by people
all around the globe. It also allows people to attend multiple meetings where
otherwise they may have a conflict if we had a larger number of channels and
most meetings took similar timeslots.
The OpenStack infrastructure team maintains a limited number of channels
dedicated to meetings. While teams can hold meetings on their own team IRC
channels, they are encouraged to use those common meeting channels to give
their meeting some external exposure. The limited number of meeting channels
encourages teams to spread their meetings around and reduce conflicts.
To schedule a team meeting, please go to the eavesdrop_ site and follow the
instructions there. All meeting reservations are managed through gerrit