Difference between revisions of "Task ideas for Google Code-in/Getting started"
Jump to navigation
Jump to search
Firespeaker (talk | contribs) |
Firespeaker (talk | contribs) |
||
| Line 10: | Line 10: | ||
* '''Find an interesting task:''' |
* '''Find an interesting task:''' |
||
== |
== Access == |
||
For some tasks, you may need access to Apertium resources, like the '''wiki''' or our '''[[subversion]] repository'''. Usually this is no problem, you just need ask a mentor or an org admin. |
|||
==Links== |
==Links== |
||
Revision as of 18:47, 7 November 2016
This page will describe some steps you can take to get involved with the Apertium project in the Google Code-in. First of all, thanks for reading! We're very enthusiastic about getting new contributors to Apertium and to helping spread our passion for language technology.
First steps
So, what are the first steps ?
- Talk to us This is the most important! Nothing in Apertium is too hard without the right amount of help. And we like helping, so just get in contact. The best way to contact us is on IRC, and the best way to use IRC is with a client like irssi,[1] weechat[2] or hexchat.[3]. A good tip is to hang out on IRC, even if no-one is talking when you enter. People can be in different time zones, and channel activity peaks depending on the time.
- Install Apertium: Not all tasks require Apertium to be installed, but if you're planning to work with Apertium, it's a good idea to do this early.
- Find an interesting task:
Access
For some tasks, you may need access to Apertium resources, like the wiki or our subversion repository. Usually this is no problem, you just need ask a mentor or an org admin.
