I'll do the conversion script to Google's CSV - give me till maybe
tomorrow. For now, let's work on adding tasks/keeping the ones that are
valid this year too.

– V
­

On 10 October 2017 at 12:05, Francis Tyers <fty...@prompsit.com> wrote:

> Update this page:
>
> http://wiki.apertium.org/wiki/Task_ideas_for_Google_Code-in/
> Getting_started
>
> It might also be an idea to make the "default ways of communicating"
> clearer on:
> * http://wiki.apertium.org/wiki/IRC
> * http://wiki.apertium.org/wiki/Contact
>
> The ideas page is here, last updated in September:
>
> http://wiki.apertium.org/wiki/Ideas_for_Google_Code-in
>
> It needs to be updated, and someone (Vin?) should check the template to
> make sure that it's
> easy to convert to CSV for the Google upload thing. Also, we need a way to
> specify language
> pairs (some tasks will be multilingual) and a way to specify that a task
> can be repeated
> (meaning we will need some unique identifiers or something).
>
> I have sent out invitations to org admins (Mikel, Tino, Unhammer, Vin,
> Jonathan), if you
> are not on this list and would like to be org admin, let me know.
>
> We have 14 days to make this application spectacular, and to make sure we
> have enough mentors
> to participate, ¡ganbare!
>
> Fran
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Apertium-stuff mailing list
> Apertium-stuff@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/apertium-stuff
>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Reply via email to