Switch scheduling to monthly without rotation, following the discussion
at the March 6 meeting.
Also allow dots in IRC usernames so that Felix does not trigger the typo
police.
Change-Id: I0f88241560e887362f990dd2dc808732cdeca515
The openstack-tox-pep8 job is failing with:
AttributeError: 'FlakesChecker' object has no attribute 'CONSTANT'
Fix by using a newer version of hacking and fix problems it found.
Change-Id: I26e7309d9f90cbad877f8f65ba8c2ec0ee023c70
There is no need for 4 meeting channels, especially now that
we allow meetings to happen in team channels.
Let's remove #openstack-meeting-4 by moving the few meetings
still happening there to other available meeting channels.
Assuming it gets the required +1s, this change will be merged
Thursday, Mar 19 at 15utc (after the Glance meeting completes)
Once this merges, we can retire #openstack-meeting-4.
Change-Id: I96890de13083c09bdd677bf44b6eee535e6fde20
With some IRC meetings having moved to team channels, we have
a lot more room in the "common" meeting rooms. To the point
where #openstack-meeting-cp and #openstack-meeting-5 are taking
up valuable bot space (bots can only join so many channels) for
very little usage.
Furthermore, the benefit of using common channels is that the
team activity is publicized to meeting channel lurkers, and
neither #openstack-meeting-cp not #openstack-meeting-5 gathered
a faithful attendance.
This propose to consolidate meetings to the other meeting channels
(#openstack-meeting{,-alt,3,4}) by moving the only two meetings
that actually took advantage of those two meeting rooms.
Once this merges, we can start the work of removing those from the
meeting bot watch.
Change-Id: Iafcba92f908f4305492737ffea2771acf85a7fbc
By default, report when a slot has less than a weekly slot
available, but allow users to specify another sensitivity.
Change-Id: I8a52d9fb39039af049f419ac31b3281d6b057dac
The count_slot_usage.py tool was not updated when the
monthly and quadweekly recurrences were added. Do that
now.
Change-Id: I978726c13a910549b2f81f4b21c28ca05ba09c26
Yaml.load() return Python object may be dangerous if you receive a YAML
document from an untrusted source such as the Internet. The function
yaml.safe_load() limits this ability to simple Python objects like integers or
lists.
While we're there switch to https for the load so we can be more
confident this is 'correct' data
Reference:
https://security.openstack.org/guidelines/dg_avoid-dangerous-input-parsing-libraries.html
Change-Id: I89adc358f1b3e934788a416b7ef7ea8bfc1a45db
Now that the governance resolution to allow teams to host meetings in
their channels [1] has merged and all defined channels have a meetbot[2]
get the valid channel list from infra's canonical source.
[1] I631e2597bf818c5e4b2f813da14764d2cb55d0ce
[2] I6a8a1cedd8a83e3e856e8df4aba4d0a584912eb0
Change-Id: I09e4fc07c486905a55ef06604b05493532175bf5
Recently it was decided[0] to drop the recurring meeting and switch to
a more adhoc basis. This change is to update the meeting information
and release the slot in #openstack-meeting-4
[0] http://lists.openstack.org/pipermail/openstack-dev/2017-August/120410.html
Change-Id: Icadb78dbf8cb242716c3d11f8ae236767192c220
Add #openstack-meeting-5 to the list of channels you
can schedule meetings against.
Add the channel to the count_slot_usage.py script so
that it reports accurate information.
Depends-On: If8b4e31af2eb647f249a578ec7f585cb23fdc559
Change-Id: Ic9b38e99cf434557b7b568f02b12b16e4efc432c
If we encounter a problem rather than printing and exiting actually fail.
This will mean that the pep8 tox environment will also fail.
Change-Id: Ife80bc2761fcb075057a17337d2ab63459be2da4
Since Ken'ichi took over as the QA chair tools/check_chair.py has been
issuing:
qa-team-meeting.yaml
Ken'ichi Ohmichi (oomichi): Needs Fixing
Which hasn't been failing (see follow-up change). This review adds ' as
a valid character in a meeting chair's name.
Change-Id: I767370629841cbce9f43385a8ab6a8861feb48ac
Meeting links as printed out by count_slot_usage.py improperly
used format(), resulting in %s leftovers in the output. This
change fixes that.
Change-Id: Id63df83841014474e89655e0f6e75cd0ace3da41
This add a simple tool to verify that the 'chair' in every yaml file
matches the canonical format.
Change-Id: I88b566cb23a5f350b603a1bb16415d335bbbbaed
A quick script to read the yaml files and count the used time slots.
Co-Authored-By: John L. Villalovos <john.l.Villalovos@intel.com>
Change-Id: I8a21c26ca1e90f8e45be81ed1fcdca634c0a8593
Having community hours events in the irc-meeting repo has been somewhat
contentious. Now that the 'Neutron PTL Office Hours' is a thing of the
past we can remove that from the list off acceptable channels.
Change-Id: I70e08ccf7b16a12e8da9e850be400e4df14e3c93
The current script is broken due to format changes in projects.yaml from
governance project. We are now explicitly specifying the IRC and email
for each name. This patch fixes it.
Change-Id: I5f7f0d94f91923710b569a344c77bf47006aa99e
Create a new tool called check_channels.py that ensures that the irc
channel is one which is capable of running a fully functional MeetBot
*or* one that is an 'office hours' type event that doesn't use MeetBot.
Also create a tox textenv to run it. Once this is clean we can add a
gate job to run these checks and vote.
Change-Id: I57a725b55fb611214d0f0eec08179aae01c1e49a
The cross-project meeting starts with a courtesy ping for each PTL. Now
that we are adding more projects, it is useful to have a tool to build
the list instead of keeping a static copy somewhere.
Change-Id: If23bf302e912557fbb44b5e68747956308bccf64