User:Mary.szmary/proposal2017

Contact information

Name: Maria Sheyanova
E-mail: masha.shejanova@gmail.com
IRC: maryszmary
SourceForge: maryszmary
Phone number: +79169223114
Timezone: UTC+3

Why is it that you are interested in the Apertium project?

I have participated in GSoC 2016 with Apertium, which made me involved in this project, this is one of the main reasons why I am interested in contributing to Apertium. Another reason is that, being a linguist, I find it beneficial to develop linguistic tools, and Apertium gives me a good opportunity to do so.

Which of the published tasks are you interested in? What do you plan to do?

I am planning to work on UD-annotatrix. This will include making a user-friendly interface, which would enable linguists to make syntactic annotation quickly and easily.

Reasons why Google and Apertium should sponsor it

Syntactic annotation is blah blah (why it'a important). Currently there is an interface for doing syntactic annotation called brat with both online and offline. However, the interface has a number of issues. Firstly, blah blah...

There is also a project aimed to make a toolkit for working with dependency trees in Apertium. At the moment, it allows to visualize the trees (the interface works with three annotation formats, namely CONLL-U, CG3 and SD). The aim of my project is to create an easy-to-use, quick and interactive interface tool for UD annotation. The tool should work both online and offline and allow a user to edit the annotation in both graphical and text modes.

A description of how and who it will benefit in society

The result of this work is going to be useful for linguists who deal with dependency annotation.

---

Field of work and available resources

Apertium has a web-interface for visualising syntactic trees written in Java-Script and HTML. The main idea of this project is to

---

Work plan

Overview

post application period

• Understanding the architecture of the existing project
  
• Improving my knowledge of Java-Script
  

community bonding period

• Closer examination and evaluation of the tools that can be used:
  • blah;
  • blah blah blah ;
• Thinking more about the architecture of the app

work period

• 1st month: qwerty
• 2nd month:
• 3rd month:

Schedule

week 1:
weeks 2-3:
week 4: check the completeness of the dictionaries (I think I can use Russian and Polish corpora for that)
Deliverable #1
week 5-6: write the lexical choise (consider generating them automatically using corpora I have access to)
week 7: estimate the validity of the rules
week 8: start writing the transfer rules
27 June: midterm evaluations deadline
Deliverable #2
week 9-10: write the transfer rules
week 11: evaluating, testing
week 12: clean up the code, last fixes, writing documentation
Project completed: a language pair of release quality or close to it

List your skills and give evidence of your qualifications

I'm a 4th year bachelor student of Linguistic Faculty in NRU HSE (Russia).
Programming skills: Python, Bash, R, Java-Script (not very experienced, but ready to quickly learn).
Other computer skills: HTML, XML, CSS.
Languages: Russian (native), Polish, English, German, basic knowledge of Indonesian.
Experience: I already worked on a couple of projects which included making a web-interface. For example, a have written a web-interface for a unified online dictionary of antonyms. The project is written in Flask (Python), HTML and CSS. I also have another flask project, which consists in making online linguistic exercises. Apart from these projects, I am currently working on a much larger Django project, which is to make a universal linguistic corpus platform.

Coding challenge: I’ve fixed the #18 issue on the project's github.

List any non-Summer-of-Code plans you have for the Summer

At the beginning of June I will be finishing a project aimed to make a universal corpus platform, but, as the work on that project is mostly going to be done earlier, I do not think, that it will significantly affect my ability to work on the GSoC project. After that, I have no other no-GSoC plans.