Top tips for GSOC applications - Revision history

Ahmed Siam: Fix the link.

2023-02-27T23:51:14Z

Fix the link.

Ahmed Siam: The GSoC student guide have been moved to github so i updated the link of the guide along with some edits.

2023-02-27T23:49:24Z

The GSoC student guide have been moved to github so i updated the link of the guide along with some edits.

Popcorndude: direct people to public communication channels

2021-03-18T15:20:01Z

direct people to public communication channels

Popcorndude: /* What NOT to put in your application */

2020-04-17T20:15:20Z

What NOT to put in your application

Popcorndude: /* What NOT to put in your application */

2020-04-17T19:22:11Z

What NOT to put in your application

Popcorndude at 19:18, 17 April 2020

2020-04-17T19:18:52Z

Nmathur54 at 07:58, 26 March 2019

2019-03-26T07:58:03Z

Nmathur54 at 20:22, 25 March 2019

2019-03-25T20:22:29Z

Nmathur54: /* Template */

2019-03-25T20:21:19Z

Template

Nmathur54: /* Template */

2019-03-25T20:19:29Z

Template

@@ Line 69: / Line 69: @@
 * In a language pair of your own choice, try to edit the files, break stuff, and then make it work again &mdash; and then tell us about it.
 * If you think you know the problem better than the mentor does, it could be that you have misunderstood it. Read more about Apertium before making assumptions based on your existing experience.
-* While your code is compiling, look through the [https://google.github.io/gsocguides/student/writing-a-proposal/ GSoC student guide]
+* While your code is compiling, look through the [https://google.github.io/gsocguides/student/writing-a-proposal GSoC student guide]
 * Ask for an account on this Wiki, that way we can work collaboratively on applications. You should ask on our mailing list or on the IRC channel you just joined and an [[Special:ListAdmins|admin]] will create it for you.

@@ Line 69: / Line 69: @@
 * In a language pair of your own choice, try to edit the files, break stuff, and then make it work again &mdash; and then tell us about it.
 * If you think you know the problem better than the mentor does, it could be that you have misunderstood it. Read more about Apertium before making assumptions based on your existing experience.
-* While your code is compiling, look through the [http://write.flossmanuals.net/gsocstudentguide/writing-a-proposal/ GsoC student guide from FLOSS manuals]
+* While your code is compiling, look through the [https://google.github.io/gsocguides/student/writing-a-proposal/ GSoC student guide]
 * Ask for an account on this Wiki, that way we can work collaboratively on applications. You should ask on our mailing list or on the IRC channel you just joined and an [[Special:ListAdmins|admin]] will create it for you.

@@ Line 21: / Line 21: @@
 * '''Do the coding challenge'''
 ** Every idea will have a coding challenge to perform, this is basically a test to see if you have the required skills to do the project or if you can acquire them in a short amount of time.
+== Contact Us! ==
+If you haven't talked to us yet, the best next step is almost certainly talking to us. [[IRC]] is the fastest way to get a response. You can also join the [[Contact|apertium-stuff mailing list]]. Either way, come on and post your question or proposal and someone will be around to help.
+Either way, post '''publicly'''. If anyone can jump in and answer the question, you're likely to get better and quicker answers and others can learn from it as well.
 == What '''NOT''' to put in your application ==

@@ Line 37: / Line 37: @@
 ** Some of the things listed on [[Ideas_for_Google_Summer_of_Code|the ideas page]] contain all the information you need to propose a project. Other ideas are just a starting point. Either way, '''come talk to us''' and we'll help you fill in the gaps.
 ** Also, we may have forgotten to update the idea list. Some of the things on it may have been done last year or maybe another project has done something that affects the one you're looking at. Again, talk to us and we'll help you sort it out.
+* '''English-Hindi translation'''
+** See [[Ideas_for_Google_Summer_of_Code/Adopt_a_language_pair]]. Working on the <code>eng-hin</code> has been attempted many times in the past and very little progress has been made. Are there any other languages that you speak that you could pair with one of those?
 ==Other tips==

@@ Line 36: / Line 36: @@
 * '''Exactly what it says on the ideas page'''
 ** Some of the things listed on [[Ideas_for_Google_Summer_of_Code|the ideas page]] contain all the information you need to propose a project. Other ideas are just a starting point. Either way, '''come talk to us''' and we'll help you fill in the gaps.
+** Also, we may have forgotten to update the idea list. Some of the things on it may have been done last year or maybe another project has done something that affects the one you're looking at. Again, talk to us and we'll help you sort it out.
 ==Other tips==

@@ Line 63: / Line 63: @@
 There are a couple of options, either email our mailing list (<tt>apertium-stuff@lists.sourceforge.net</tt>) or come on [[IRC]] and ask one of the mentors to add you an account. In both cases you will need an email address and a username.
+==Template==
-'''Apertium GSOC 2019'''
-== '''Template''' ==
 <pre>
 Name:
 E-mail address:
 Other information that may be useful to contact you (e.g. IRC):
 Why is it that you are interested in Apertium?
 Which of the published tasks are you interested in? What do you plan to do?
@@ Line 91: / Line 88: @@
 * '''Deliverable #1'''
+* Week 5:
+* Week 6:
+* Week 7:
+* Week 8:
+* '''Deliverable #2'''
+* Week 9:
+* Week 10:
+* Week 11:
+* Week 12:
+* '''Project completed'''
+Include time needed to think, to program, to document and to disseminate.
+If you are intending to disseminate to a conference, which conference are you intending to submit to. Make sure
+to factor in time taken to run any experiments/evaluations and write them up in your work plan.
+List your skills and give evidence of your qualifications. Tell us what is your current field of study,
+major, etc. Convince us that you can do the work.
+List any non-Summer-of-Code plans you have for the Summer, especially employment, if you are applying for
+internships, and class-taking. Be specific about schedules and time commitments. we would like to be sure you have
+at least 30 free hours a week to develop for our project.
+</pre>
+[[Category:Google Summer of Code]]

@@ Line 91: / Line 91: @@
 * '''Deliverable #1'''
-== '''Contact Information''' ==
-'''Name''' – Neerav Mathur
-'''Location''' – Agra, Uttar Pradesh, India -282001
-'''E-mail''' – nmathur54@gmail.com
-'''Mobile no.''' - +919719009548
-'''Github''' - https://github.com/ommathur54
-'''Time Zone''' - UTC +5.30
-== '''Skills And Experience''' ==
-My name is Neerav Mathur. I am 4th semester post graduate student at K.M.Institute of Hindi and Linguistics, Dr. Bhimrao Ambedkar University Agra, Uttar Pradesh, India. I am studying Linguistics and during my previous semesters I have learnt Python, Machine Translation, XML. As part of my previous semester course project, I trainer and tested MALT Parser for Magahi Language. In order to do it, me and my classmate Mohit also developed a small treebank for the language. In the current semester, we are further expanding the treebank and we plan to implement the first full-fledged parser for the language. I am also working on the development of a machine translation system for English-Magahi language pair. As you would notice, I am more generally interested in developing resources and technologies for under-resourced Indian languages. As part of this, I am interested in building a morphological analyzer for Braj Language (spoken in Braj Region of Agra, Mathura, Alighar, Bharatpur, etc in Uttar Pradesh and Rajasthan, India) using the Apertium platform. I am working on Digital Dictionary for Sema language, and I am interested in making of morphological analyzer for Braj Language. And this rise my more interest in NLP, Machine Learning etc.
-== '''University Courses:''' ==
-Programing (Python, Xml, HTML)
-Computer Tools for Linguistics Research
-Linguistics Courses (Phonetics, Morphology, Syntax, Semantics, Field work, Sign Language, Machine Translation)
-Theories of Machine Translation and Machine Translation (practical)
-== '''Technical Skills:''' ==
-Programing Language – Python.
-Web Design – HTML .
-Databases – MySQL.
-Languages – Hindi (Native), Braj, English.
-== '''Why Interest In Machine Translation ?''' ==
-I am studying Linguistics and during my previous semesters I have learnt Python, Machine Translation, XML. As part of my previous semester course project, I trainer and tested MALT Parser for Magahi Language. In order to do it, me and my classmate also developed a small treebank for the language. In the current semester, we are further expanding the treebank and we plan to implement the first full-fledged parser for the language. I am also working on the development of a machine translation system for English-Magahi language pair. As you would notice, I am more generally interested in developing resources and technologies for under-resourced Indian languages. During my fourth semester I attend Hands-on workshop on machine Translation where I get information about MT systems (Apertium) for under resourced languages and how morphological Analyzer help in increasing the performance of MT in rule based system. From there my interest get rised for MT.
-== '''Why Interest In Apertium ?''' ==
-This organization works on things which are very interesting for me as a linguist & computational linguist: (rule-based) machine translation, languages, NLP and so on. I get more interested with Apertium  when I get information in MT workshop that Apertium works with all kind of languages which is very important for support for all languages.
-Also Apertium community is very friendly and very helpful to new members, members here are always ready to help us ( Apertium community reply frequently on what ever query do we have ). It encourages me to work with  Apertium.
-== '''Task And Plan ?''' ==
-Task - I am interested in building a morphological analyzer for Braj Language (spoken in Braj Region of Agra, Mathura, Alighar, Bharatpur, etc in Uttar Pradesh and Rajasthan, India) using the Apertium platform.
-== '''Reason Why Apertium And Google Sponsor It ?''' ==
-Braj is one of the most under-resourced Indian language. Which is spoken in Braj Region of Agra, Mathura, Alighar, Bharatpur, etc in Uttar Pradesh and Rajasthan, India. It is spoken by 1,556,314  native speaker (according 2011 census) . There is no Braj translator present online or offline and there is no rule-based translator with morphological analyzer. So I believe we can improve the quality of translation by applying rule-based model (Apertium).
-== '''Description Of How And  Who It Will Benefit In Society ?''' ==
-Firstly, Morphological Analyzers will help in increasing the performance of Machine translation in rule based system, especially for morphologically rich languages. I want to work on this project to make morphological analyzer for developing English - Braj MT system.
-Secondly, no such work has been done on MT for Braj Language, so my work will contribute to reduce the human work and improve the translation for Braj Language.
-== '''Work Plan''' ==
-'''Week 1''' -  Preparing linguistic rule for Morphological analyzer.
-'''Week 2''' -  Preparing linguistic rule for Morphological analyzer.
-'''Week 3''' -   Tokenizing the data.
-'''Week 4''' -  Prepare tag set.
-'''Deliverable #1'''
-Submit the Tokenized and prepared tagset
-'''Week 5''' -  Preparing the affix list validate (Prepared Suffix list ) in corpus
-'''Week 6''' – Writing the program to develop Braj morphological analyzer.
-'''Week 7''' - Writing the program to develop Braj morphological analyzer.
-'''Week 8''' -  Train and test the model.
-'''Deliverable #2'''
-Submit the program and trained, test model
-'''Week 9''' - Test the model with different domain of word.
-'''Week 10''' -  Fixing the occurring error in model.
-'''Week 11''' -Again train and test the model.
-'''Week 12''' - Evaluation of results or model.
-'''Project Completed'''
-Submission of project

@@ Line 66: / Line 66: @@
 == '''Template''' ==
+<pre>
+Name:
+E-mail address:
+Other information that may be useful to contact you (e.g. IRC):
+Why is it that you are interested in Apertium?
+Which of the published tasks are you interested in? What do you plan to do?
+Include a proposal, including
+    * a title,
+    * reasons why Google and Apertium should sponsor it,
+    * a description of how and who it will benefit in society,
+    * and a detailed work plan (including, if possible, a schedule with milestones and deliverables).
+=== Work plan ===
+* Week 1:
+* Week 2:
+* Week 3:
+* Week 4:
+* '''Deliverable #1'''
 == '''Contact Information''' ==