You know something that struck me, I noticed there were several teams last cycle that did not elect a PTL so this round I was watching to see if any teams did not have a PTL elected and presumed it was because of many of the reasons surfaced in previous emails in this thread including being heads down, watching other channels and potentially insufficient numbers of individuals interested in the PTL role.
So I waited and noticed Astara, Security and a handful of other projects did not have a PTL elected so I picked Astara because I am an OpenStack architect who specializes in SDN, security and distributed storage and applied. Of course I missed the deadline by about 2 hours but Security was another project I was interested in. So all this said, there are individuals interested in the PTL role to ensure project teams have someone handling the logistics and coordination. My issue however was that I was not yet eligible to be a candidate which I'll remedy moving forward. I'm still interested in serving as a PTL for a project that needs one. I personally believe that in the case of Security, there needs to be a dedicated team due to the nature and impact of security breaches that directly influence the perception of OpenStack as a viable cloud solution for enterprises looking (or re-looking) at it for the first time. I'm not a full-time developer but an architect so I am planning to open a new discussion about how PTL candidates are currently being qualified. Again, different thread. For this thread, if there is a concern about PTL interest - it's there and I would be open to helping the team in this regard if it helps keep the team activity in the OpenStack marquee. //adam *Adam Lawson* AQORN, Inc. 427 North Tatnall Street Ste. 58461 Wilmington, Delaware 19801-2230 Toll-free: (844) 4-AQORN-NOW ext. 101 International: +1 302-387-4660 Direct: +1 916-246-2072 On Wed, Sep 21, 2016 at 8:56 AM, Clint Byrum <cl...@fewbar.com> wrote: > 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. > > 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. > > Seems like all of that could be automated. > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
