Dmitry Andreev
<klieg.polar AT gmail DOT com>
- Country (born / living in)
- Russia
- Academic experience
- i am in my final year as a student, Lomonosov Moscow State University, Department of Computational Mathematics and Cybernetics.
- Your current occupation
- student
- Software projects you have already participated in
- parus.sf.net, modify network_test utility. Now i'm using it in my diploma.
- I'm currently working on satellite images parallel processing library
- Other stuff you like to tell here
- Sorry for my bad english, i'm working on it. I'm good in reading, but my writing and talking skills are bad.
Experience Level
- Experience in coding in general
- started 2005, ??? hours
- Experience in Python coding
- started 2009, ?? hours
- Your favourite programming language(s), best first
- C/C++, Python
- Tools you use for development
- vim
- MPI profiling tools: Vampir, IBM HPCT MPI Tracer/Profiler
- ipython for experiments
- Did you already do full day work (8h/5d) over some weeks on some software project yet?
- N
- If not, is your motivation good enough that you think you can do that for MoinMoin?
- Y
Project(s) you apply for and your ideas for them
Project: Wiki-like formats support
DOM -> wiki (for gui editor and other applications)
The hard part of this convertor is how to return macro from tree to wiki-macro format, because some of them may be stored in tree in raw html ( http://moinmo.in/BastianBlank/TreeOutputFormatter )
reST -> DOM
There are many rst2any converters, so it's not a problem to make -> DOM converter, but after
DOM -> reST (for gui editor and other applications)
old reST may not be equal to result of reST->DOM->reST. reST has specific format of hyperlinks.
Mediawiki markup -> DOM
Mediawiki allows some html tags, so, for base Mediawiki format converter is needed some part of html -> DOM. Also will be good to add
I think all can be done in this sequence, or maybe it's better to start with reST -> DOM -> reST, it will give some experience with DOM converters before creating DOM -> wiki.
Timetable:
24.05 - 14.06 (20-21 days): create and test DOM -> wiki (20.05-05.06 i have exams, i don't know how many time they take)
- 15.06 - 22.06 (7-8 days): if any problems with code, and time for macro representation in gui questions and in other wiki formats;
23.06 - 05.07 (12-13 days): reST -> DOM -> reST convertor, create and test.
06.07 - 12.07 (5-6 days ): if any problems with integreating reST -> DOM -> reST, test wiki -> DOM -> reST and reST -> DOM -> wiki
- -- mid-term evaluations 12.07-15.07 (1 day)
DOM -> wiki
reST -> DOM -> reST
13(16).07-30.07 ( x days, less if only base syntax, more if extensions like highlight) Mediawiki markup -> DOM
- 31.07 - 05.08 if any problems and code cleaning time.
- 06.08 - ?? i'm also think about i18n proposal, but i still have many questions about it, so maybe i will have time to solve problems in i18n with DOM tree
If you want you can join us at chat.freenode.net #moin see MoinMoinChat and talk about it -- ReimarBauer 2010-03-24 08:38:05