Differences between revisions 1 and 2
Revision 1 as of 2014-03-17 22:03:00
Size: 2913
Editor: ?VladBogolin
Comment:
Revision 2 as of 2014-03-17 22:27:34
Size: 3020
Editor: ?VladBogolin
Comment:
Deletions are marked like this. Additions are marked like this.
Line 6: Line 6:
This is a suggestion for the kind of information we'll find useful from students in their submissions. Remember -- you're going to be committing to several months' work. The more information and planning you can provide up-front, the more we (and Google!) will have to go on when we're ranking your application. Do not forget adding your submission at [[SummerOfCode2013/StudentApplications]]
Line 10: Line 8:
 * '''Background''': something about yourself: technical skills, experience, etc. Who are you? What makes you the best person to work on this project?  * '''Background''':
Line 15: Line 13:
 * '''Project title'''
 * '''Project details''': a more detailed description.
First of all, I am really enthusiastic to work to open source projects. Also, I must say that I consider that I have all the necessary skills in order to complete this project. I do not back away from difficult tasks and I am fully committed to finishing the project. I also plan to be an active developer after GSoC is over.

Least but not last, I think that this is a great opportunity to learn new things that will help me in my future career, so this makes me even more enthusiastic about the project.

 * '''Project title''': Get Muon ready
 * '''Project details''': Getting Muon, the apt frontend written by and for Kubuntu, in Debian. There are a great bit of ubuntu specific data that needs to be fixed up and provided in Debian. Besides this, the project aims to add a set of improvements to muon.
Line 21: Line 23:
 * '''Exams and other commitments''': do you have university exams inside the SoC period? If so, that's most likely not a problem but please tell us early!
 * '''Other summer plans''': are you getting married? Do you have a long vacation planned? Are you expecting to start a job? '''Be aware''' that if you are accepted for the summer, then Google will be paying you as though you were working for them. We (in Debian) will therefore expect you to be working 35-40 hours per week on your project. It is very unlikely that you will be able to combine a successful SoC with another summer job working for somebody else.
 * '''Exams and other commitments''': The starting coding period overlaps a bit with my exam period (I will probably have one or two exams in the last weeks of May). Also, in July I will have my final paper presentation (one or two days). This shouldn't be an inconvenient because I plan to have my final paper done until GSoC starts.
 * '''Other summer plans''': No other plans.
Line 25: Line 27:


Finally, I want to thank you for taking time to read my proposal. I hope we will collaborate during this summer but also after GSoC.

Student Application Template

To fill this in, copy the source text. Please don't rename the template.

I am a fourth year student at "Politehnica" University of Bucharest, Computer Science and Engineering Department. The main areas that I am interested in are: algorithms, computer graphics and operating systems.

My skills consist in a strong background in algorithms and data structures. As it comes to programming languages I prefer C/C++ and Java, in which I also have more experience (about 2 years in Java and more than 6 years with C). Apart C/C++ and Java, I have experienced the next programming languages: Python, Haskell, Scheme, Bash Scripting, Matlab, Assembly language, Clips, Prolog. When it comes to versioning tools, I am quite familiar with Git (I have developed several school team projects using it) and SVN (which I used during last summer GSoC and also for some school projects).

First of all, I am really enthusiastic to work to open source projects. Also, I must say that I consider that I have all the necessary skills in order to complete this project. I do not back away from difficult tasks and I am fully committed to finishing the project. I also plan to be an active developer after GSoC is over.

Least but not last, I think that this is a great opportunity to learn new things that will help me in my future career, so this makes me even more enthusiastic about the project.

  • Project title: Get Muon ready

  • Project details: Getting Muon, the apt frontend written by and for Kubuntu, in Debian. There are a great bit of ubuntu specific data that needs to be fixed up and provided in Debian. Besides this, the project aims to add a set of improvements to muon.

  • Synopsis: a short description.

  • Benefits to Debian

  • Deliverables: quantifiable results e.g. 'Port Debian to VAX', 'Write 3 articles for X website'.

  • Project schedule: how long will the project take? When can you begin work?

  • Exams and other commitments: The starting coding period overlaps a bit with my exam period (I will probably have one or two exams in the last weeks of May). Also, in July I will have my final paper presentation (one or two days). This shouldn't be an inconvenient because I plan to have my final paper done until GSoC starts.

  • Other summer plans: No other plans.

  • Why Debian?: Why are you choosing Debian? What attracts you about Debian?

  • Are you applying for other projects in SoC? Note that letting us know about this does not impact your chances of acceptance or rejection with us; we ask this because it helps us to resolve deduplications wherein a student is accepted for multiple projects.

Finally, I want to thank you for taking time to read my proposal. I hope we will collaborate during this summer but also after GSoC.