<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Sat, Aug 22, 2015 at 6:11 PM, Anita Kuno <span dir="ltr"><<a href="mailto:anteaya@anteaya.info" target="_blank">anteaya@anteaya.info</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On 08/22/2015 04:35 PM, Maish Saidel-Keesing wrote:<br>
> +1 To what Joshua said.<br>
><br>
> I would also like to understand what is the goal we are trying to<br>
> accomplish by moving this to a repo and submitting a CR and what does<br>
> this solve or improve on the current way we are doing things?<br>
<br>
</span>The point when I proposed this workflow last release cycle was to make<br>
the election officials job possible to complete with certainty all<br>
candidates had been acknowledged rather than lost in the noise while<br>
still being able to do the other daily activities the election officials<br>
have to accomplish while being election officials.<br>
<br>
Noise on the mailing list? Wasn't a concern for me then and isn't now,<br>
as an interested observer. Making sure the officials can have confidence<br>
in their work? Very important.<br></blockquote><div><br></div><div>I understand the workflow to be necessary due to the scale at which we're governing now. With over 40 PTL positions plus the six TC spots rotating, I sense we need to adopt tooling that ensures every project gets equivalent, trackable, audit-able, process-oriented support. </div><div><br></div><div>Anne</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Thanks,<br>
Anita.<br>
<span class="im HOEnZb">><br>
> Will it reduce noise? marginally (IMHO).<br>
><br>
> Maish<br>
><br>
> On 08/22/15 06:02, Joshua Hesketh wrote:<br>
>> I'm struggling to think of a way this might help enable discussions<br>
>> between nominees and voters about their platforms. Since the tooling<br>
>> will send out the nomination announcements the only real noise that is<br>
>> reduced is the "nomination confirmed" type emails.<br>
>><br>
>> While I think this sounds really neat, I'm not convinced that it'll<br>
>> actually reduce noise on the mailing list if that was the goal. I<br>
>> realise the primary goal is to help the election officials, but<br>
>> perhaps we can achieve both of these by a separate mailing list for<br>
>> both nomination announcements and also platform discussions? This<br>
>> could be a first step and then once we have the tooling to confirm a<br>
>> nominees validity we could automate that first announcement email still.<br>
>><br>
>> Just a thought anyway.<br>
>><br>
>> Cheers,<br>
>> Josh<br>
>><br>
>> On Sat, Aug 22, 2015 at 5:44 AM, Anita Kuno <<a href="mailto:anteaya@anteaya.info">anteaya@anteaya.info</a><br>
</span><span class="im HOEnZb">>> <mailto:<a href="mailto:anteaya@anteaya.info">anteaya@anteaya.info</a>>> wrote:<br>
>><br>
>> On 08/21/2015 03:37 PM, Jeremy Stanley wrote:<br>
>> > On 2015-08-21 14:32:50 -0400 (-0400), Anita Kuno wrote:<br>
>> >> Personally I would recommend that the election officials have<br>
>> >> verification permissions on the proposed repo and the automation<br>
>> >> step is skipped to begin with as a way of expediting the repo<br>
>> >> creation. Getting the workflow in place in enough time that<br>
>> >> potential candidates can familiarize themselves with the change,<br>
>> >> is of primary importance I feel. Automation can happen after the<br>
>> >> workflow is in place.<br>
>> ><br>
>> > Agreed, I'm just curious what our options actually are for<br>
>> > automating the confirmation research currently performed. It's<br>
>> > certainly not a prerequisite for using the new repo/workflow in a<br>
>> > manually-driven capacity in the meantime.<br>
>> ><br>
>><br>
>> Fair enough. I don't want to answer the question myself as I feel<br>
>> it's<br>
>> best for the response to come from current election officials.<br>
>><br>
>> Thanks Jeremy,<br>
>> Anita.<br>
>><br>
><br>
><br>
><br>
><br>
</span><div class="HOEnZb"><div class="h5">> __________________________________________________________________________<br>
> OpenStack Development Mailing List (not for usage questions)<br>
> Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
><br>
<br>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature"><div dir="ltr"><div>Anne Gentle</div><div>Rackspace</div><div>Principal Engineer</div><div><a href="http://www.justwriteclick.com" target="_blank">www.justwriteclick.com</a></div></div></div>
</div><span></span></div>