<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">
It looks like your email was already replied to:
<div class=""><br class="">
</div>
<div class=""><a href="http://lists.openstack.org/pipermail/openstack-dev/2016-November/108141.html" class="">http://lists.openstack.org/pipermail/openstack-dev/2016-November/108141.html</a></div>
<div class=""><br class="">
</div>
<div class=""><br class="">
<div>
<blockquote type="cite" class="">
<div class="">On 30 Nov 2016, at 18:38, Rob C <<a href="mailto:hyakuhei@gmail.com" class="">hyakuhei@gmail.com</a>> wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<div dir="ltr" class="">[Resending without the PTLs in CC because it got my mail stuck in the spam filters]
<div class=""><br class="">
</div>
<div class="">
<div style="font-size:12.8px" class="">I'm struggling to find good info on when the adjusted PTL nomination cycle starts.</div>
<div style="font-size:12.8px" class=""><br class="">
</div>
<div style="font-size:12.8px" class="">I've checked here: <a href="https://releases.openstack.org/ocata/schedule.html#pike-ptls-self-nomination" target="_blank" class="">https://releases.<wbr class="">openstack.org/ocata/schedule.<wbr class="">html#pike-ptls-self-nomination</a> but
it looks like the 'elections' section was supposed to be added to the table and wasn't. </div>
<div style="font-size:12.8px" class=""><br class="">
</div>
<div style="font-size:12.8px" class="">I know from the updates to the charter that the elections should happen on or before R-3 but it doesn't provide any clarity on how much before then the nominations should be made?</div>
</div>
<div class=""><br class="">
</div>
<div class="">Cheers</div>
<div class="">-Rob</div>
</div>
<div class="gmail_extra"><br class="">
<div class="gmail_quote">On Tue, Nov 1, 2016 at 7:45 PM, Doug Hellmann <span dir="ltr" class="">
<<a href="mailto:doug@doughellmann.com" target="_blank" class="">doug@doughellmann.com</a>></span> wrote:<br class="">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
PTLs,<br class="">
<br class="">
As we did for the Mitaka and Newton cycles, I want to start this<br class="">
cycle by making sure the expectations for communications with the<br class="">
release team are clear to everyone so there is no confusion or<br class="">
miscommunication about any of the process or deadlines. This<br class="">
email is being sent to the openstack-dev mailing list as well as<br class="">
the PTLs of all official OpenStack projects individually, to<br class="">
improve the odds that all of the PTLs see it. I will not be<br class="">
taking the extra step of CCing individual PTLs or liaisons for<br class="">
future emails.<br class="">
<br class="">
(If you were a PTL last cycle, you may want to skip ahead to the<br class="">
Things for you to do right now section at the end.)<br class="">
<br class="">
Volunteers filling PTL and liaison positions are responsible for<br class="">
ensuring communication between project teams happens smoothly. As<br class="">
a community, we rely on three primary communication<br class="">
strategies/tools for different purposes:<br class="">
<br class="">
1. Email, for announcements and for asynchronous communication.<br class="">
<br class="">
We will be using the "[release]" topic tag on the openstack-dev<br class="">
mailing list for important messages related to release<br class="">
management. Besides special announcements and instructions, I<br class="">
will send the countdown emails I sent last cycle, with weekly<br class="">
updates on focus, tasks, and upcoming dates. PTLs and release<br class="">
liaisons should configure your mailing list subscription and<br class="">
email client to ensure that those messages are visible (and<br class="">
then read them) so that you are aware of all deadlines, process<br class="">
changes, etc.<br class="">
<br class="">
2. IRC, for time-sensitive interactions.<br class="">
<br class="">
There are far too many of you (56) to make it realistic for the<br class="">
three members of the release team to track you down<br class="">
individually when there is a deadline. We need you to do your<br class="">
part by making yourself available by configuring your IRC<br class="">
bouncer to listen in #openstack-release. You are, of course,<br class="">
welcome to stay in channel all the time, but you need to be<br class="">
there at least during deadline periods (the week before and<br class="">
week of each deadline).<br class="">
<br class="">
3. Written documentation, for relatively stable information.<br class="">
<br class="">
The release team has published the schedule for the Ocata cycle<br class="">
to <a href="http://releases.openstack.org/ocata/schedule.html" rel="noreferrer" target="_blank" class="">
http://releases.openstack.org/<wbr class="">ocata/schedule.html</a>. Although<br class="">
I will highlight dates in the countdown emails, you may want to<br class="">
add important dates from the schedule to your calendar.<br class="">
<br class="">
Some projects have also added their own project-specific<br class="">
deadlines to that list. If you have something unique, please<br class="">
feel free to update it by patching the openstack/releases<br class="">
repository. There is no need to add a project-specific deadline<br class="">
that is the same as the global deadline.<br class="">
<br class="">
The Ocata cycle overlaps with several major holidays, including<br class="">
the new year. If you are planning time off, please make sure your<br class="">
duties are being covered by someone else on the team. Its best to<br class="">
let the release team know in advance so we dont delay approval<br class="">
for release requests from someone we dont recognize, waiting for<br class="">
your +1.<br class="">
<br class="">
Please ensure that the release liaison for your project has the<br class="">
time and ability to handle the communication necessary to manage<br class="">
your release. The release team is here to facilitate, but<br class="">
finishing the work of preparing the release is ultimately the<br class="">
responsibility of the project team. Failing to follow through on<br class="">
a needed process step may block you from successfully meeting<br class="">
deadlines or releasing. Our release milestones and deadlines are<br class="">
date-based, not feature-based. When the date passes, so does the<br class="">
milestone. If you miss it, you miss it. A few of you ran into<br class="">
problems in past cycles because of missed communications. My goal<br class="">
is to have all teams meet all deadlines during Ocata. We came<br class="">
very very close for Newton; please help by keeping up to date on<br class="">
deadlines.<br class="">
<br class="">
<br class="">
Things for you to do right now:<br class="">
<br class="">
1. Update your cross-project liaison on<br class="">
<a href="https://wiki.openstack.org/wiki/CrossProjectLiaisons#Release_management" rel="noreferrer" target="_blank" class="">https://wiki.openstack.org/<wbr class="">wiki/CrossProjectLiaisons#<wbr class="">Release_management</a><br class="">
<br class="">
2. Make sure your IRC nickname and email address listed in<br class="">
<a href="http://git.openstack.org/cgit/openstack/governance/tree/reference/projects.yaml" rel="noreferrer" target="_blank" class="">http://git.openstack.org/cgit/<wbr class="">openstack/governance/tree/<wbr class="">reference/projects.yaml</a><br class="">
are correct. The release team, foundation staff, and TC all<br class="">
use those contact details to try to reach you at important<br class="">
points during the cycle. Please make sure they are correct,<br class="">
and that the email address delivers messages to a mailbox you<br class="">
check regularly.<br class="">
<br class="">
3. Update your mail filters to ensure you see messages sent to<br class="">
the openstack-dev list with [release] in the subject line.<br class="">
<br class="">
4. Reply to this message, off-list, so I know that you have received it.<br class="">
A simple “ack” is enough.<br class="">
<br class="">
Doug<br class="">
<br class="">
PS - If you need help setting up an IRC bouncer, take a look at<br class="">
<a href="https://doughellmann.com/blog/2015/03/12/deploying-nested-znc-services-with-ansible/" rel="noreferrer" target="_blank" class="">https://doughellmann.com/blog/<wbr class="">2015/03/12/deploying-nested-<wbr class="">znc-services-with-ansible/</a><br class="">
or <a href="https://dague.net/2014/09/13/my-irc-proxy-setup/" rel="noreferrer" target="_blank" class="">
https://dague.net/2014/09/13/<wbr class="">my-irc-proxy-setup/</a> for a puppet<br class="">
version.<br class="">
<br class="">
</blockquote>
</div>
<br class="">
</div>
__________________________________________________________________________<br class="">
OpenStack Development Mailing List (not for usage questions)<br class="">
Unsubscribe: <a href="mailto:OpenStack-dev-request@lists.openstack.org" class="">
OpenStack-dev-request@lists.openstack.org</a>?subject:unsubscribe<br class="">
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" class="">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br class="">
</div>
</blockquote>
</div>
<br class="">
</div>
</body>
</html>