Unfortunately both Miguel and Rodolfo are no longer works in
Neutron QoS so there is no point to still have them listed as
chairs for this meeting.
Change-Id: I9fa9ffe11bfeac896123c2ee808fb92a7c877bbe
Meetings haven't happened in months, and the
long term mentoring is in the progress of being
updated and moved to being managed by oher groups-
likely the First Contact SIG or the Diversity WG.
Change-Id: Ie8f2346e4df837fb6a00903da8101911f72fec2c
As the most involved and fruitful participant of the group, he will take
over chairing the meeting starting next week.
Change-Id: I575cd1833c5975c339ce2979bf771d9e6e5b5671
Chef OpenStack previously held a slot for a weekly meeting in a shared
meeting channel, but dropped it in favor of office hours on an as-needed
basis. This change is to record the information about the times and
location.
Change-Id: I3b139893545e88ef456387fa38f62ce119c3fc21
We've been having weekly meetings in #openstack-powervm, but they
weren't noted here. This should get them listed on ical/eavesdrop.
Change-Id: Ifc580fcde712722bbfd07a40e73d516a75de3b67
During Dublin PTG, QA team decided[1] to have only
Office hours on openstack-qa channel and release the
meeting time slot.
This commit updates the QA meeting info with Office hours
new time and channel.
..1 https://etherpad.openstack.org/p/qa-rocky-ptg-rocky-priority
Change-Id: If11821606579c06dd61141747d976917f75e7c57
Update the chair to be the new PTL (me), and tweak the wording of the
description so it makes sense in this context.
Change-Id: I118552a16bcd4fdfca2a4881f3cf796c89b6b097
In Ic5a81ac1b2ef49c28522d9bd01d29a75b67eba95 we retired the schedule for
the Security Project team and created a new one fror the Security SIG,
as not part of the meeting schedule were shared keeping the 2 years of
history is slightly misleading. So update the start_date to be now'ish
Change-Id: I8d00adb0f3c1989dc6b52ed267a35a1aab60488d
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
On of the action items that came out of the keystone retrospective
during the Rocky PTG was that we should try and move our meeting to
be more accomodating to developers in APAC timezones. The consensus
was to move it two hours earlier.
In order to avoid a conflict, we'll have to move meeting rooms as
well.
Change-Id: Ic5d22e2804a51beecde8b5f35759a3d256239c70
