1 |
Hello everyone! |
2 |
|
3 |
My name is Dmitry and I'm writing here because I've found a proposal to |
4 |
rewrite Catalyst in Gentoo GSoC-2013 Ideas page[1]. I know that application |
5 |
period hasn't started yet, but I already think that I'd like to take up |
6 |
this job. However I've found that before posting application I must perform |
7 |
some actions: |
8 |
|
9 |
1. Use the tools that you will use in your project to make changes to code. |
10 |
2. Participate in our development community. |
11 |
3. Give us your contact info and working hours. |
12 |
|
13 |
I'd like to begin from the second question, i.e. I'd like to introduce |
14 |
myself. I'm Russian student, who studies programming for three years |
15 |
already, though it's rather hobby than education. My speciality is |
16 |
classical philology and now I'm studying colloquial Latin and read |
17 |
classical authors in Italy. My interest to programming began when I've |
18 |
started to use Linux. It happened more than three years ago; I've begun |
19 |
with bash and Python, now I'm trying to explore C++, though I've begun to |
20 |
study it only two or three months ago and didn't have explored it so deep |
21 |
to tell that I know C++ (though I certainly already know some basics). |
22 |
|
23 |
Last year I've first time participated in GSoC with FSF and rewritten |
24 |
gnulib-tool huge shell script in Python to make it more portable and |
25 |
flexible[2]. I've successfully finished this work and decided to help |
26 |
gnulib-developers even in the future[3]. However, since I was missed to |
27 |
Italy for a long time to study Latin, I couldn't continue work so |
28 |
intensively like before (though even in Italy I've really never stoped |
29 |
working). Recently I've published a new version of gnulib-tool, which seems |
30 |
to be more easy to use and also better organized than the older one[4]. |
31 |
I've finished it some days ago (it also probably was a good exercise in |
32 |
Python) and will now develop this version (thus I've created a separated |
33 |
repository). There is a small (yet?) discussion in gnulib-tool list[5] |
34 |
about this update, though my mentor (Bruno Haible) didn't respond yet (but |
35 |
other gnulib developer has already written an answer). I'm planning to |
36 |
continue this work. |
37 |
|
38 |
Some other things were written before gnulib reimplementation. Some time |
39 |
before I've written a small Russian-Latin dictionary (which in fact was my |
40 |
first work in Python) for my cathedra and all people studying classical |
41 |
philology[6]. However, now I think that it needs reimplementation too |
42 |
(since I see that it could have been implemented better and also see some |
43 |
things which I could add like morphological parser from Perseus site[7] to |
44 |
explain word forms). For some time I've been creating some portability |
45 |
layers[8] between Python and Python3, but now I don't think it is necessary |
46 |
since I feel that the time to migrate to Python3 has probably already come. |
47 |
The last thing that I was working around is flex/yacc parsers generation |
48 |
and implementation for some classes in C++ (this work was initially begun |
49 |
to understand C++ better, but I think that it can be in future something |
50 |
more than just exercise); this work is also located in my github |
51 |
repositories[9]. |
52 |
|
53 |
If you think that my candidature may be considered, I'd like to ask some |
54 |
questions. |
55 |
As you've already understand, I've been used git for some time already. |
56 |
During the previous GSoC I intensively used git to work with code, though I |
57 |
can't say that I'm really experienced person (i.e. git push, git pull, |
58 |
diff, patch were enough for my previous project). However, I'm not sure it |
59 |
is enough. The other question is that it is really hard to find some |
60 |
project which uses python and emit patch to it to pass requirements. Could |
61 |
you advice a good bug, please? :-) |
62 |
|
63 |
If you think I have a chance, I can even answer the third question (about |
64 |
work hours, contacts, etc.). :-) |
65 |
|
66 |
Looking forward to your answers! |
67 |
|
68 |
P.S. Thanks for being so patience to read such a long letter till the end! |
69 |
|
70 |
[1] http://wiki.gentoo.org/wiki/Google_Summer_of_Code/2013/Ideas#Catalyst |
71 |
[2] http://www.gnu.org/software/soc-projects/ideas-2012.html#gnulib |
72 |
[3] https://github.com/ghostmansd/gnulib-python |
73 |
[4] https://github.com/ghostmansd/pygnulib |
74 |
[5] http://lists.gnu.org/archive/html/bug-gnulib/2013-04/msg00037.html |
75 |
[6] http://sourceforge.net/projects/quirinus |
76 |
[7] http://www.perseus.tufts.edu/hopper/morph |
77 |
[8] https://github.com/ghostmansd/gnupython |
78 |
[9] https://github.com/ghostmansd/quirinus |
79 |
|
80 |
-- |
81 |
With best regards, |
82 |
Dmitry Selyutin |
83 |
|
84 |
E-mail: ghostmansd@×××××.com |
85 |
Phone: +7(985)334-07-70 |