<div dir="ltr"><div>I support these two funding requests too.<br><br><br><br><br><br><br></div>satish<br><br></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Dec 12, 2017 at 12:06 AM, Glenn McKnight <span dir="ltr"><<a href="mailto:mcknight.glenn@gmail.com" target="_blank">mcknight.glenn@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi All <div><br></div><div>We have submitted proposals which have been funded. ie. Captioning, Policy Tracking and LACRALO Mailing List issues</div><div><br></div><div>Dev suggested a Open Data analysis of ICANN pages and an improved group chat ie. Mattermost or SLACK. . I support these two ideas and we can flesh them out.</div><div><br>G</div></div><div id="m_7147735338501230383DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2"><br>
<table style="border-top:1px solid #d3d4de">
<tbody><tr>
<td style="width:55px;padding-top:13px"><a href="http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail" target="_blank"><img src="https://ipmcdn.avast.com/images/icons/icon-envelope-tick-green-avg-v1.png" alt="" style="width:46px;height:29px" width="46" height="29"></a></td>
<td style="width:470px;padding-top:12px;color:#41424e;font-size:13px;font-family:Arial,Helvetica,sans-serif;line-height:18px">Virus-free. <a href="http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail" style="color:#4453ea" target="_blank">www.avg.com</a>
</td>
</tr>
</tbody></table><a href="#m_7147735338501230383_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2" width="1" height="1"></a></div><div class="gmail_extra"><br clear="all"><div><div class="m_7147735338501230383gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr">Glenn McKnight</div><div dir="ltr">NARALO Secretariat<br><a href="mailto:mcknight.glenn@gmail.com" target="_blank">mcknight.glenn@gmail.com</a><br>skype gmcknight<br>twitter gmcknight</div><div>289-830 6259<br>.</div></div></div></div></div></div></div></div></div>
<br><div class="gmail_quote"><div><div class="h5">On Mon, Dec 11, 2017 at 1:05 PM, Judith Hellerstein <span dir="ltr"><<a href="mailto:judith@jhellerstein.com" target="_blank">judith@jhellerstein.com</a>></span> wrote:<br></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5">
<div text="#000000" bgcolor="#FFFFFF">
<div class="m_7147735338501230383m_-2934564673961378791moz-forward-container">
Dear TTF Members, <br>
<div class="m_7147735338501230383m_-2934564673961378791WordSection1">
<p class="MsoNormal">
<br>
The FY19 Additional Budget Request process has started. This
process pertains to a dedicated part of the overall ICANN
annual budget that is set aside to fund specific requests from
the community for activities that are not already included in
the recurring ICANN budget. FY19 Additional Budget Requests
cover the period 1 July 2018 through 30 June 2019. <br>
</p>
<p class="MsoNormal"><br>
</p>
<p class="MsoNormal">Last year the TTF along with Outreach and
Engagement put in two requests one was for the LACRALO
Translation project which ICANN staff decided to take on and a
second was a request for a policy tracking proposal and while
it did not get funded since ICANN was doing a similar process
it did get us noticed. We can put this in again or if others
have any other ideas would be great to hear them</p>
<p class="MsoNormal"><br>
</p>
<p class="MsoNormal">
The relevant information is available on the <a href="https://community.icann.org/display/atlarge/At-Large+FY19+Additional+Budget+Request+Workspace" target="_blank">At
Large Special Budget Request Wiki Page</a>, including the
key deadlines, details of the process, principles and the
request template.
<br>
<br>
<b>IMPORTANT:</b> The members of the ALAC Finance and Budget
Sub-Committee (FBSC) agreed to the following criteria for
At-Large proposals:
<u></u><u></u></p>
<ul type="disc">
<li class="MsoNormal">
Outreach should not be a major focus. Activities to improve
engagement with existing members is encouraged.
<u></u><u></u></li>
<li class="MsoNormal">
If any request is made on outreach, it should probably go
through the CROP program and not this special request
process.
<u></u><u></u></li>
<li class="MsoNormal">
Proposals should include ways in which will make the ALAC
and/or the At-Large community more effective and develop the
At-Large community.
<u></u><u></u></li>
<li class="MsoNormal">
RALO requests must go through a bottom up process within
their RALO prior to being submitted for consideration by the
FBSC.
<u></u><u></u></li>
<li class="MsoNormal">They must be explicitly supported by the RALO
representatives on the FBSC.
<u></u><u></u></li>
<li class="MsoNormal">
Staff is currently expecting that basic resources for
community communications/printing will be supported through
the core ICANN budget, but that community proposals for
printing, etc. will be accepted as a back-up in case
expectations change. Specific proposals for communications
resources beyond simple printing and editing functions
should be prepared and submitted.
<u></u><u></u></li>
</ul>
<p class="MsoNormal"> <b>IMPORTANT:</b> <b>Between now and
January 12, 2018 the RALOs and WG's are asked to review any
ALS request or complete a template on behalf of the RALO and
send requests to
<a href="mailto:staff@atlarge.icann.org" target="_blank">At-Large Staff</a>.</b> <br>
</p>
<p class="MsoNormal"><br>
</p>
<p class="MsoNormal"><font size="+1">These proposals will be
discussed with the FBSC starting on January 15 <br>
Any revisions to accepted proposals need to be sent to the
FBSC for final review by January 19, 2018. <br>
The FBSC to review all the RALO requests on January 29 <br>
</font><br>
I hope to hear from others with suggestions of proposals that
we could submit. We will also hold a meeting in January. <br>
</p>
<p class="MsoNormal"><br>
</p>
<p class="MsoNormal">Judith Hellerstein</p>
<p class="MsoNormal">Chair of the Technology Task Force<br>
</p>
<span style="color:black"></span><u></u><u></u>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
</div>
</div>
<br></div></div>______________________________<wbr>_________________<br>
ttf mailing list<br>
<a href="mailto:ttf@atlarge-lists.icann.org" target="_blank">ttf@atlarge-lists.icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/ttf" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/l<wbr>istinfo/ttf</a><br>
<br></blockquote></div><br></div>
<br>______________________________<wbr>_________________<br>
ttf mailing list<br>
<a href="mailto:ttf@atlarge-lists.icann.org">ttf@atlarge-lists.icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/ttf" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/<wbr>listinfo/ttf</a><br>
<br></blockquote></div><br></div>