[Openstack-security] Process for OSSG Lead Elections
Bryan D. Payne
bdpayne at acm.org
Sun Mar 2 22:18:41 UTC 2014
While this list has been quiet, I have had a few side conversations with
people. Based on the feedback I've received, I changed the meeting
attendance requirement to need 3+ meetings to be considered active. I did
not change the timeline.
I will put together a list of the active members in a Google Doc. If,
after seeing the list, someone believes I have made a mistake then just let
me know.
We are scheduled to begin this process tomorrow. I'll send out a reminder
email at that time.
Cheers,
-bryan
On Thu, Feb 27, 2014 at 12:35 PM, Bryan D. Payne <bdpayne at acm.org> wrote:
> As discussed in the past two OSSG meetings, Rob and I will be stepping
> down as the co-leaders of OSSG at the summit in May. We would like to have
> an election process to choose the next leader as this is a community driven
> group.
>
> I've been working out the specific details for the election, which is
> largely based on the PTL / TC election process used by the broader
> OpenStack community. To ensure that everyone is up to speed, please review
> the election process:
> https://wiki.openstack.org/wiki/Security/OSSG_Lead_Election_Spring_2014
>
> We began discussing this in the OSSG meeting today. Some initial areas of
> discussion were around the following points:
>
> 1) Is attending a single IRC meeting sufficient to be considered an
> "active member"? Perhaps we should increase this requirement to 3 or more
> meetings?
>
> 2) Does the current proposed timeline work?
>
> There may be other items that catch people's eyes as well. Please use
> this thread to discuss the process and suggest improvements. I will help
> mediate that discussion with the goal of arriving at something we all feel
> comfortable with.
>
> Cheers,
> -bryan
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-security/attachments/20140302/64786bd7/attachment.html>
More information about the Openstack-security
mailing list