Hello,

Well, Google has extended the deadline by one week. So that gives me
time to perhaps improve my proposal. I have posted the proposal that I
submitted which is still able to be edited until the end of the
application deadline. I know that it is weak, but I am not familiar
with writing technical proposals such as this. Any help and
suggestions to improve it would be appreciated.



Abstract:

VIM is a very good text editor. It is especially good in the fact that
it is extremely stable. But it still has it bugs like any program. My
goal is to eliminate as many of those bugs as possible to make VIM
even more robust and stable.

Proposal:

VIM is a very good text editor. It is especially good in the fact that
it is extremely stable. But it still has it bugs like any program. My
proposal is to make VIM more robust and stable by fixing as many bugs
as possible. I will use as my primary sources the todo list and the
vim-dev mailing list.

I will look at the issues listed and investigate whether it is a
documentation or user error if it is an actual issue in the VIM code.
If the code is to fault, that section of code will need to be
corrected and patched.


Background/Experience:

I am currently enrolled at Youngstown State University pursuing a
bachelor's degree in Computer Information Systems. In the past I had
taken a few courses in programming and learned Pascal and Basic/
VisualBasic. At the end of this semester I will have completed one
year of C++ courses. I have also this past year taken courses in UNIX
shell scripting and COBOL.

I have been using UNIX/Linux for over five years now, starting back
with Red Hat 9. I am currently dual-booting Slackware 12.0 and NetBSD
4.0 on my HP desktop computer.

In all that time, VIM has been my primary text editor. I have done a
wide survey of text editors, and I consistently found that VIM was the
best editor for me. I know the basics of using VIM, but I find I am
constantly finding new and more efficient ways to use VIM. For this
reason, I am excited about the possibility of helping out with the VIM
project.

--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

Raspunde prin e-mail lui