Name : Lee, GangHan
Email : outletinone_at_gmail.com
Project : revision analyzer
Synopsis :
We can show the visual changed contents of the revision using the result of
the analyzed Subversion’s revision. In addition to the use of statistics and
analysis of the current project, we can find out some problems of the
current committed code and we can proposal the way to improve a program of
the project.
Project Details:
Using version control with subversion to manage a project, I feel that it
was not enough. So I use ‘mantis’ that is issue management system and the
other project management tool. Sometimes i thank about the integration of
the tool would’ve been good, but i think that if subversion have more
ability to offer the function then it’s more useful.
The subversion repository have more information than i expected. All through
there are seem to exist only few data and document, but this is everything
include information about project which is committed.
To gathering information about this project, I found the project named
‘subvstats’ which is analyze tool of the subversions on the tigris.org. but
that is not enough to gain the information to use. I think revision’s data
can provide more useful info.
What how many committed , how many changed at regular intervals, how many
files are removed and inserted are basis function. We need to make to
provide more usefulness information.
Suppose, a bug in a specific part of the project. Maybe somebody modify the
code to fix. But unfortunately the logic consistently have trouble relating
before fixed area after modify. Then a great deal of code is distributed in
special area. This present situation is occred by ‘rapid change of the code
with no caution’ or ‘long period changed continually of the code’. And
revision analyzer will be a significant help to point out the situation.
Some modified source code of the project files are more than initially added
source code. And if the ratio of the both modified code and added code are
too many different than we can recognize there are some problem., It is may
be up to not carefully writing without testcase or the other things which
like planning change of the project. This frequently change is bad asfect of
the project. And we have to know that where is occur. And revision analyzer
notice to you.
By analyzing the conflicts that occur frequently on the basis of statistical
data can provide various alternatives way. .The source code part which
focusing by many people to modifying, if it will increase the conflict.
Revision analyzer should be warning about that. And revision analyzer can be
propose the better way to commit style via committed time period and
translation size of each time.**
All ideas are not quite yet. But I think that the subversion have to
indicate you with useful information about revision which will be committing
as well as committed.
Project Schedule:
I did not make a through plan. But I have blueprint about this project. And
this project will be develop increasingly. Also more realistic schedule and
specific facts are may be decided with mentor who advice to me about the
project.
But we have make some result of the project before end of the summer of
code. So in advance i planning the schedule about this. I think more
specific schedule is devided by prototyping which on week2.
week 1 : development environment setting and software program design
week 2 : prototyping for function available and software matrix
week 3 : make milestone plan and period via prototyping result, make plug-in
interface.
week 4 : Milestone 1 : extract data from committed revision
week x : Milestone 2 : using extracted data display statistics graphically
week x : Milestone 3 : plug-in dev : found area where too many changed too
many conflicts in regular period
week x : Milestone x : add function using plug-in style.
Academic Experience:
When i was high school, I started computer programming. And i currently
forth grade in Hanyang univ in south korea. My major is computer science. So
I was have many classes related my major. And my English skill is not
excellent but I try to learning the English with English conversation class.
Work/Internship Experience:
In south korea man who become 20 years have to go military. However i was
lucky. I was go to software company Instead of military. And I develop
computer and cell phone software for 2 years and a half year. So I have
confidence and experience. about the software development
And last winter vocation I was work in korea electrotechnology research
institute . in research center I was develop software to control the device.
The first time since starting the programming has developed many small and
useful program. Like web http daemon, instant messenger, game and utility.
I’m sure these experience are help to develop the software in the summer.
Open Source Development Experience:
I never part in open source project ever. But I have little experience about
moniwiki. I was not committed the source. However I make about then plugins
and share my friends who use the moniwiki. Moniwki is famous in south korea
student whom is computer science major. But at that time I don’t know the
feeling about the open source. But preparing summer of code, I am surprised
many open source organizations. And viewing the outcome what they are make,
I become excited condition. How great it is.
Obtained through the preparation for summer of code is changing
my think about opence source and my future way in software developer. This
time I hope that this chance will become a seed of start open source with
summer of code.
Thank you for reading.
from Lee, GangHan
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1533239
Received on 2009-04-03 17:35:23 CEST