Hello, everyone£¡
My name is Junjie Peng, you can call me Junjie. I'm a postgraduate in
Chinese Academy of Science. CS is my major. Last year I developed a
handphone map client on j2me when I acted as an intern in a company in
Beijing. It runs well on Nokia s60 products(E50 and 6300 are my testing
model). You can use it for browsing a map for a city, searching POIs such as
restaurants then getting the deep info and searching bus lines. But it is
limited heavily for the location APIs aren't open to common cellphones in
China now. I played the main role of this project. In this project,I
developed a Log tool for j2me cellphones and it simplified our latter works
greatly. In a considerable part of my work, I tried different strategies to
exploit the ability of the connection limited devices, such as compressing
and decompressing the data of maps and pois, and bringing a sliding window
to improve the read efficiency. I have harvested a lot from this project,
including SVN, unit testing, agile development (especially Test-Driven
Development) and some knowledge about Geocoding.
It was my first time to touch a version tool. SVN gives us a good
efficiency. I enjoyed it! I wish to be accepted for GSOC by Subversion. I
expected to get a deep knowledge of version control tools, gain experience
about software framework, and improve its performance for world-wide range
of develops.
I hope I will be eligible for GSOC. I'm familiar with java and C. I
have also developed some MIS with c#, asp.net, sql server. Besides, I can
perform well on Data Structure, and I am one of the chief reporters in our
college. I have read "Hacker's Guide to Subversion", I would like to follow
it's instructions in my development. In fact, we did the same way last year.
However, I'm not familiar with the source code of SVN. Besides, last year, I
enjoyed SVN through the eclipse plug-in, so I have few experience on CUI of
SVN. It also needs time and your help to conquer it.
I have two ideas:
1.) *Straight trace for items deleted and renamed. *In SVN, take a file for
example, if it is deleted, it can not be checked out directly from the
project after *twice* commitment. It can only be checked out before the
point it was first committed. Projects, packages and directories including
projects have the same problem. In the familiar way, If it is renamed, when
committed, the log records as that the file is deleted first and a file with
new name added later. After *twice* commitment, If we need browse the trace
for the file before the rename operation, we need check out the parent node
including the file. It's not a nature performance!
2.)* Remove the verbose update operation. *Before checking in, we need
synchronize or update, it's easy to accept. But after a commitment, it's
necessary to update again immediately, otherwise a little asynchronies will
occur between the client and server. Maybe SVN should update itself after
the commitment.
Maybe the two ideas are not so suitable for a GSOC idea. The first one is a
little simple; the second seems like a bug. I also like ideas in the list
posted. All of them point to a fact problem.
It's exciting to writing this letter for me, hope for your replies and
instructions!
Good luck!
Junjie Peng
Received on 2008-03-22 16:14:57 CET