Difference between revisions of "Ideas for Google Summer of Code"
(→Ideas) |
|||
Line 31: | Line 31: | ||
| mentors = [[User:Francis Tyers|Francis Tyers]] |
| mentors = [[User:Francis Tyers|Francis Tyers]] |
||
| more = /Python API |
| more = /Python API |
||
}} |
|||
{{IdeaSummary |
|||
| name = Develop a morphological analyser |
|||
| difficulty = easy |
|||
| skills = XML |
|||
| description = Write a morphological analyser and generator for a language that does not yet have one |
|||
| rationale = A key part of an Apertium machine translation system is a morphological analyser and generator. The objective of this task is to create an analyser for a language that does not yet have one. |
|||
| mentors = [[User:Francis Tyers|Francis Tyers]] |
|||
| more = /Morphological analyser |
|||
}} |
}} |
||
Revision as of 21:03, 18 January 2021
This is the ideas page for Google Summer of Code, here you can find ideas on interesting projects that would make Apertium more useful for people and improve or expand our functionality. If you have an idea please add it below, if you think you could mentor someone in a particular area, add your name to "Interested mentors" using ~~~
The page is intended as an overview of the kind of projects we have in mind. If one of them particularly piques your interest, please come and discuss with us on #apertium
on irc.freenode.net
, mail the mailing list, or draw attention to yourself in some other way.
Note that, if you have an idea that isn't mentioned here, we would be very interested to hear about it.
Here are some more things you could look at:
- Top tips for GSOC applications
- Get in contact with one of our long-serving mentors — they are nice, honest!
- Pages in the development category
- Resources that could be converted or expanded in the incubator. Consider doing or improving a language pair (see incubator, nursery and staging for pairs that need work)
- Unhammer's wishlist
- The open issues on Github (or on Sourceforge). The latter are probably out of date now since migrating to Github.
If you're a student trying to propose a topic, the recommended way is to request a wiki account and then go to
http://wiki.apertium.org/wiki/User:[[your username]]/GSoC2020Proposal
and click the "create" button near the top of the page. It's also nice to include [[Category:GSoC_2020_student_proposals]]
to help organize submitted proposals.
Ideas
Python API for Apertium
- Difficulty:
2. Medium - Size: default Unknown size
- Required skills:
C++, Python - Description:
Update the Python API for Apertium to expose all Apertium modes and test with all major OSes - Rationale:
The current Python API misses out on a lot of functionality, like phonemisation and segmentation and doesn't work for some OSes like Debian. - Mentors:
Francis Tyers - read more...
Develop a morphological analyser
- Difficulty:
3. Entry level - Size: default Unknown size
- Required skills:
XML - Description:
Write a morphological analyser and generator for a language that does not yet have one - Rationale:
A key part of an Apertium machine translation system is a morphological analyser and generator. The objective of this task is to create an analyser for a language that does not yet have one. - Mentors:
Francis Tyers - read more...