<div dir="ltr">Adam and the SFC may think these funds are 100% fungible, but I think we have an ethical obligation towards the goals of the proposal, which Chris has nicely summarized.<div><br></div><div>regards.</div><div><br></div><div>-walter</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Feb 24, 2016 at 1:11 PM, Chris Leonard <span dir="ltr"><<a href="mailto:cjlhomeaddress@gmail.com" target="_blank">cjlhomeaddress@gmail.com</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 Wed, Feb 24, 2016 at 11:29 AM, Laura Vargas <<a href="mailto:laura@somosazucar.org">laura@somosazucar.org</a>> wrote:<br>
><br>
><br>
</span><span class="">> Specific info that would help, includes:<br>
><br>
> - Grant Time frame<br>
> - Is there a Max- Min Budget / Project / Language<br>
> - Are there activities/projects/languages restrictions<br>
> - Are there fixed rates for translators<br>
> - Are there fixed rates for logics roles<br>
> - Required Documentation<br>
> - And any other relevant information to help comunity members formulate<br>
> their translations projects within this logic.<br>
<br>
</span>Laura,<br>
<br>
I do not believe such details would be contained in the grant itself,<br>
but I must admit that I don't think I ever asked for or saw the<br>
TripAdvisor grant paperwork. Chances are it is not very informative.<br>
<br>
What I think is perhaps most relevant to your request for information<br>
is the attached document which is a template that was developed by the<br>
SFC for the purpose of enabling L10n proposals to be made and<br>
definitively approved for payment by our fiscal sponsor. This is<br>
really where the "rubber meets the road" (a car enthusiast's term for<br>
where the action is or where things actually happen). Read the<br>
attached, I think you'll get the general flavor.<br>
<br>
To your detailed questions I will try to provide a little more color,<br>
noting that while I am not a SLOB any more, and so only speak for<br>
myself, but I have been engaged in the L10n/i18n community in various<br>
capacities for a while.<br>
<br>
> - Grant Time frame<br>
<br>
I think the timeline in the attached document is one year, that is not<br>
so much to restrict a successful and productive project from going<br>
forward longer than that by mutual agreement, but to protect<br>
SugarLabs/SFC from a non-performing contractor so the undispensed<br>
funds might be uncommitted and reallocated elsewhere on a timely<br>
basis, if needed.<br>
<span class=""><br>
> - Is there a Max- Min Budget / Project / Language<br>
<br>
</span>No Min that I know of, but you'd have to ask, I don't think this<br>
should be treated as a "petty cash" fund. Max is set by funds<br>
available and approval received. Project and Language to be described<br>
in the Proposal.<br>
<span class=""><br>
> - Are there activities/projects/languages restrictions<br>
<br>
</span>So far the only executed (or proposed and un-executed) agreements were<br>
for work on L10n on Sugar-related strings on our Pootle instance, so<br>
we could track deliverables easily.<br>
<br>
At one point there was discussion of payment for development new<br>
needed glibc locales committed upstream (that is a requirement for<br>
Sugar to use the language), but that came after I had committed the<br>
ayc_PE, quz-PE, quy_PE, niu_NU, niu_NZ locales, split the pap_AN<br>
locale into pap_CW and pap_AW, rework of ht_HT, etc., etc.so there was<br>
no executed agreement, just discussion in principle. I wouldn't<br>
morally oppose recompense for finally committing to glibc the agr_PE<br>
draft locale that I sent to Sebastian for testing (thanks for the<br>
improvements, and yes we will get it into glibc in due time), but I<br>
haven't pushed to formalize any paperwork, so there isn't any to<br>
share.<br>
<span class=""><br>
> - Are there fixed rates for translators<br>
<br>
</span>Not really, expectation would be averaging roughly at current internet<br>
published rates (or somewhat better for the rarer indigenous<br>
languages), maybe something in the 15-30 cent/word range, but<br>
milestone based, not piece-work. I think that is an important point<br>
to keep in mind.<br>
<span class=""><br>
> - Are there fixed rates for logics roles<br>
<br>
</span>Nothing specified, propose something and justify it to the SLOBS/SFC.<br>
I've drawn no remuneration for serving in an oversight capacity (yes<br>
the strings came in, yes they LOOK like the language requested, yes<br>
they pass error checks, etc.).. Again, I think the desire is to be<br>
milestone-based, not hourly rates.<br>
<br>
> - Required Documentation<br>
<br>
Besides a fully negotiated/approved proposal and executed version of<br>
the attached template adjusted accordingly, there is also a small one<br>
page copyright assignment document needed from each contributor, Just<br>
detail stuff, I could look for a copy of that somewhere, but it is not<br>
interesting or particularly negotiable, just a pro forma thing.<br>
<span class=""><br>
> - And any other relevant information to help comunity members formulate<br>
> their translations projects within this logic.<br>
<br>
</span> I'm striking out on my own here, but I don't think we want to pay for<br>
things that volunteers will do if we are doing our job as a project.<br>
Payment should be reserved for areas where there are substantial<br>
barriers that could be overcome with just a little grease on the<br>
wheels. What do I mean by this? I would not want to see us pay for<br>
Spanish or French strings, but I might be very happy to hear that the<br>
SLOBS have dedicated funds to speed up Awajun or start Shipibo-Conibo<br>
L10n (if proposed).<br>
<br>
To a certain extent, part of that calculation also includes a "target<br>
audience" of users waiting and people willing to get the work to them<br>
in already being in pace (e.g. Peruvian and Mexican indigenous<br>
languages even potentially smaller ones, the more widely used native<br>
languages of Oceania and Africa (e.g. Madaqascar), Haitian Kreyol,<br>
etc., might be good investments whereas Klingon or Esperanto might<br>
not). That increases the potential for realizable impact. I<br>
personally think new glibc development passes this test by virtue of<br>
being a one-time thing that has potentially global impact wherever<br>
Linux is used, as well as being a requirement for Sugar's i18n/L10n<br>
process.<br>
<br>
Anyway, those are my own thoughts on the matter and I think they are<br>
pretty reasonable, but it up to the SLOBs to make such calls on a<br>
case-by-case basis.<br>
<br>
cjl<br>
<br>_______________________________________________<br>
SLOBs mailing list<br>
<a href="mailto:SLOBs@lists.sugarlabs.org">SLOBs@lists.sugarlabs.org</a><br>
<a href="http://lists.sugarlabs.org/listinfo/slobs" rel="noreferrer" target="_blank">http://lists.sugarlabs.org/listinfo/slobs</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature"><div dir="ltr"><div><font><font>Walter Bender</font></font><br><font><font>Sugar Labs</font></font></div><div><font><a href="http://www.sugarlabs.org" target="_blank"><font>http://www.sugarlabs.org</font></a></font><br><a href="http://www.sugarlabs.org" target="_blank"><font></font></a><br></div></div></div>
</div>