El 2017-12-02 20:36, Shardul Chiplunkar escribió:
Based on what I've seen of other organizations, I think we could
benefit from 'chains' of tasks. Each task in a chain would require the
student to have completed work equivalent to the previous tasks. The
first one or two tasks in the chain would be beginner tasks, easier
than our current beginner tasks but not as easy as the linked one
above (which I think is too easy).
Chain 1:
- "Download and compile one Apertium translation pair, and send a
screenshot of trial translations."
- "Add 200 words to the bilingual dictionary" or "Add 1 lexical
transfer rule"
- "Add 500 words to the bilingual dictionary" or "Add 10 lexical
transfer rules" or "Write a constrastive grammar" or ...
Chain 2:
- "Install a few translation pairs from your distribution software
repository (or download and compile if you want to). Fork APy and run
it locally on your computer. Send a screenshot of trial queries." or
similarly for html-tools
- all the issue-fixing or feature-proposal tasks for APy or similarly
for html-tools
- tasks which involve modifying or testing with components of both
("Fix html-tools behavior when APy is down" etc.)
Similar 'chains' could be made for begiak and the lt toolbox tasks.
How does this idea sound?
Shardul C.
It was my understanding, that like the "get on IRC" tasks, "chained
tasks"
which require a student to have done something previously are not
allowed by Google. Personally I think they are a great idea, but I
thought it wasn't allowed. Perhaps this could be asked on the mentors'
list ?
F.
------------------------------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/apertium-stuff
