Open Stack

On 16-09-21 01:11 PM, Doug Hellmann wrote:
> Excerpts from Clint Byrum's message of 2016-09-21 08:56:24 -0700:
>> Excerpts from Filip Pytloun's message of 2016-09-21 14:58:52 +0200:
>>> Hello,
>>>
>>> it's definately our bad that we missed elections in OpenStackSalt
>>> project. Reason is similar to Rob's - we are active on different
>>> channels (mostly IRC as we keep regular meetings) and don't used to
>>> reading mailing lists with lots of generic topics (it would be good to
>>> have separate mailing list for such calls and critical topics or
>>> individual mails to project's core members).
>>>
>>> Our project is very active [1], trying to do things the Openstack way
>>> and I think it would be a pitty to remove it from Big Tent just because
>>> we missed mail and therefore our first PTL election.
>>>
>>> Of course I don't want to excuse our fault. In case it's not too late,
>>> we will try to be more active in mailing lists like openstack-dev and
>>> not miss such important events next time.
>>>
>>> [1] http://stackalytics.com/?module=openstacksalt-group
>>>
>> Seems like we need a bit added to this process which makes sure big tent
>> projects have their primary IRC channel identified, and a list of core
>> reviewer and meeting chair IRC nicks to ping when something urgent comes
>> up. This isn't just useful for elections, but is probably something the
>> VMT would appreciate as well, and likely anyone else who has an urgent
>> need to make contact with a team.
> IRC channels are listed on team pages on governance.o.o. For example:
> http://governance.openstack.org/reference/projects/openstacksalt.html
>
> Core reviewers are accessible through gerrit. For example,
> https://review.openstack.org/#/admin/projects/openstack/openstack-salt,access
> leads to https://review.openstack.org/#/admin/groups/1268,members
>
> Meeting chair nicks are available on eavesdrop.o.o. For example,
> http://eavesdrop.openstack.org/#OpenStack_Salt_Team_Meeting
>
> It might make sense to automate pulling that information together into a
> single page somewhere, maybe the team page on governance.o.o.
>
> The larger point is that the community expects teams to be paying
> attention to the cycle schedule and taking care of the actions expected
> without being individually asked to do so.
>
>> I think it might also be useful if we could make the meeting bot remind
>> teams of any pending actions they need to take such as elections upon
>> #startmeeting.
> I could see that being useful, yes.
>
>> Seems like all of that could be automated.
>>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

I am not convinced this situation arose due to lack of available 
information.

Thank you,
Anita.