Summer of Code: Keli Hu
2005-09
Google's Summer of Code program (SoC) was "designed to introduce students to the world of open source ソフトウェア 開発", and it worked. Successful 関係者s were given a cash reward, but from the accounts 供給するd by those 関係者s, the cash was the least of the reward. The knowledge acquired and community 参加するd in （機の）カム in first. OpenOffice.org was and is not only a fascinating if challenging codebase to work with but the community made the 成果／努力 fun, 刺激するing, and in the words of one 回答者／被告, "the best summer of my life."
Over the next week and half, I'll be publishing a short 一連の accounts by the 関係者s. To read other accounts, visit the Articles page. Today, Keli Hu discusses the work done during his Google Summer of Code. As in the previous interview, I asked a 始める，決める of questions 経由で email over a period of several weeks, the first asking about the Google SoC 事業／計画（する）, the 残りの人，物 follow-ups.
Tell us about yourself and how you got 利益／興味d and 伴う／関わるd in OpenOffice.org....
I'm Keli Hu, a 1st year Ph.D. student from 中心 for Language （警察などへの）密告，告訴（状） 過程ing, Beijing Language and Culture University (CLIP, BLCU), 中国.
What got you 利益／興味d in OpenOffice.org?
Many Natural Language 過程ing (NLP) techniques can be 連合させるd with the office 控訴, and I think there is still a lot to do in this area. I know how important OOo is to the open-source ソフトウェア community, and I think joining OOo 開発 the best way to make use of my knowledge and 与える／捧げる to the community.
述べる your 事業／計画（する）....
My 事業／計画（する） 関心s a grammar checker for OpenOffice.org, with Thomas Lange as my 助言者. This 事業／計画（する） was not on the 名簿（に載せる）／表（にあげる） of 提案するd Summer of Code (SoC) 事業／計画（する）s for OpenOffice.org, so I was a little surprised that it was 受託するd. What I 提案するd was a standalone grammar checker with English and Chinese support which could be 統合するing into OOo later. Because I really don't have any experience in OOo 開発 before, and OOo is such a big 事業／計画（する）, I was not sure how far I could go in two months if I dug into OOo 開発.
Things didn't go やめる 井戸／弁護士席, really. At first I was distracted by some academic work, so I did not start until July 15th. After some discussion with my 助言者, we agreed that we should first find out about an interface, and at the same time I should 始める，決める up a SDK and 収集する a few examples. I felt more worried later because of a few things: 1. Because the grammar checker is probably going to be a UNO 構成要素 like the （一定の）期間 checker, the programming languages I could choose were 限られた／立憲的な to C++ and Java, while I was somewhat 推定する／予想するing to use Python because I was more 生産力のある in Python. Anyway, I chose C++. 2. License 問題／発行する. I can't use GPL sources, and 基本的に I should be copyright 支えるもの／所有者 of my code, さもなければ the 調査 of license 問題／発行する would probably be even longer than the SoC 率先. [OpenOffice.org is 現実に LGPL. -Ed.]
Such 存在 the 事例／患者, it's almost impossible to do what I 提案するd in a short period of time. I'd rather spend more time on OOo and 令状 the grammar checker from scratch, make a simpler 実施 and 改善する it 徐々に after SoC. After all, getting a 認める to do open source ソフトウェア is just a good point to start, but definitely not my goal.
I spent やめる some time on 調査／捜査するing 存在するing grammar checkers, and 代案／選択肢 approaches of 器具／実施するing different 構成要素s in the grammar checker. Fortunately my 助言者 decided that I can 選ぶ up a simple interface first, so I don't have to worry about that for now, maybe because the discussion about interface I started at the mailing 名簿（に載せる）／表（にあげる） didn't 生成する much 利益／興味. :-(
Setting up the SDK seemed to be 平易な at first, until I started to use libraries outside of OOo. To 削減（する） it short, the ABI change from gcc3.3 to gcc3.4/4.0 原因（となる）d me a lot of trouble. After that settled, everything went much more 滑らかに, and just a few days ago [as of end of August --Ed.] I 完全にするd a rather simplistic 実施. Now the SoC is 製図／抽選 a の近くに, I have a few more days to 改善する the code, but things other than that are out of my 支配（する）／統制する. Anyway I've done what I could, and I really learned a lot. 広大な／多数の／重要な thanks to Google and OpenOffice.org, and my 助言者 Thomas Lange.
Thanks to Keli and Google for sponsoring the (Northern 半球) Summer of Code! In the next few days, 主要な up to OOoCon 2005, I'll publish other interviews of student developers who had a 広大な／多数の／重要な summer with OpenOffice.org thanks to Google's Summer of Code.
Return to Articles
