From Fedora Project Wiki

Revision as of 12:44, 18 May 2010 by Egg90 (talk | contribs)

Random list of application requirements

  1. Must include a schedule that was worked out with mentor
  2. Keep on eye on the Talk: page that is associated with the proposal page you create. Click on the discussion link on the top of your proposal page. The Talk: page is where mentors comment on your proposal.
  3. Make sure you have clicked on the watch link on the top of your proposal page(s) and Talk: page(s). Use the link to my preferences at the top of the page to set your Watchlist preferences to email you when changes are made.


About me

  1. What is your name?
    • Haohua Li
  2. What is your email address?
    • lihaohua90@gmail.com
  3. What is your wiki username?
    • egg90
  4. What is your IRC nickname?
    • egg90
  5. What is your primary language? (We have mentors who may speak your preferred languages and can match you with one of them if you request.)
    • Chinese
  6. Where are you located, and what hours do you tend to work? (We also try to match mentors by general time zone if possible.)
    • China(GMT+8), From afternoon to Midnight(GMT 4:00 - GMT 16:00)
  7. Have you participated in an open-source project before? If so, please send us URLs to your profile pages for those projects, or some other demonstration of the work that you have done in open-source. If not, why do you want to work on an open-source project this summer?
    • Yes, I participated in some open-source projects before.These are some of them: 
Fetion Weather Forcast http://fetionwf.appspot.com
   [Source Code: http://code.google.com/p/fetionwf]

 Sending weather forecast using Chinese Mobile Fetion SMS to you or your Fetion friends.
 You can have your own schedule that when to send the SMS.
 It contains the the weather forecast of major city in China.

RenRen Farm Helper -_- http://renrenfarm.appspot.com
   [Source Code: http://code.google.com/p/renrenfarmhelper]
  • Project page
  1. English Version:
  2. Chinese Version:

About your project

  1. What is the name of your project?
    Auto-Codec FTP
  2. Does your project come from an idea on the Summer Coding 2010 ideas page? If so, provide a link for reference, as well as a link to any discussions with mentors about your proposal.
    No, it's original. But we still don't have a mentor.
  3. Describe your project in 10-20 sentences. What are you making? Who are you making it for, and why do they need it? What technologies (programming languages, etc.) will you be using?

    It's a FTP client with an easy to use interface.

    There's a general problem in non-English speaking countries. The ftp servers in these countries always don't use UNICODE to code the return data. This causes the unreadable codes in local software. Therefore, the most important feature of our project is to solve the inconsistent coding between the servers and local operation system. This can provide convenience to non-English speaking countries' users.

    In addition, our FTP client may also offer the following features,
    1) A list including major universities and enterprises open FTP server. The list support for custom and up-to-date by us.
    2) Automatically prevent disconnecting by the server.
    3) Optional record the last successful FTP login password.
    4) Auto FTP detection to judge whether the FTP servers is connectable and the connecting speed in the list. (via “ping”)
    5) Daily tips to help the users learn the features of the software.

    We are using Python 2.6 and PyQt4 to program.
  4. What is the timeline for development of your project? The Fedora Summer Coding work period is 11 weeks long, May 24 - August 9; tell us what you will be working on each week. (As the summer goes on, you and your mentor will adjust your schedule, but it's good to have a plan at the beginning so you have an idea of where you're headed.) Note that you should probably plan to have something "working and 90% done" by the midterm evaluation (July 5-12); the last steps always take longer than you think, and we will consider canceling projects that are not mostly working by then.

    Here is our Schedule:

    5.1-5.20
    Start the designing of the project.
    Work out the wiki page.
    Communicate with the community.

    5.21-5.31
    Software requirements analyze.

    First Week in June
    Start coding. Design the basic core system of the program.

    Second and Third Week in June
    Perfect the core code.
    Implement the details of the function.

    Forth Week in June
    Design the GUI.

    7.1-7.12
    Project is nearly complete. (90%)
    Ready for midterm evaluation.

    7.13-7.20
    Continue the project, optimizing the code efficiency.

    7.21-7.31
    The preparation of the documents.
    Remove bugs and ready for release.

    8.1-8.9
    Final check and fix for the project.
    Complete the project.

Note: you will post this application on the wiki in the category Category:Summer Coding 2010 applications. We encourage you to browse this category and comment on the talk page of other applications. Also, others' comments and your responses on the talk page of your own application are viewed favorably, and, while we don't like repetitive spam, we welcome honest questions and discussion of your project idea on the mailing list and/or IRC.

The NeL project has some good general recommendations for writing proposals. We encourage Summer Coding code to include tests.

Comments

Use the Talk:Summer Coding 2010 student proposal application to actually make comment, which then appear here on the main proposal page. You can use this link to make a new comment].

plus talk

Retrieved from "https://fedoraproject.org/w/index.php?title=Summer_Coding_2010_student_proposal_Auto_Codec_FTP&oldid=174656"