Summer Coding 2010 proposal - Dorrie

For information how to complete this form, refer to Summer Coding 2010 step-by-step for students.

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. My name is Yuyeping
2. My email address is yuyeping@gmail.com
3. My wiki username is yuyeping
4. My IRC nickname is yuyeping
5. My wiki page is https://fedoraproject.org/w/index.php?title=User:yuyeping
6. My primary language is Chinese, English
7. Location, and what hours tend to work: Chongqing, China. 8:00 to 23:00 GMT+8
8. I would be developing Dorrie (URL: https://fedorahosted.org/dorrie/). I am going to develop some features for Dorrie. For example:
   • User management - integration with FAS.
   • Tabbed workflow with AJAX.
   • Search Packages.
   • Add default users to Kickstart. Custom root password.
   • Hostname
   • Default Wallpaper, home directory content,

About my project

1. My project name is Dorrie.
2. My project come from an idea on the Summer Coding 2010 ideas page (URL: Summer_Coding_2010_ideas_-_Dorrie).
3. Dorrie is a Web interface to build customized Fedora Remixes. It is a Free Software licensed under the GNU Affero General Public License v3 or later and written using Django/Python. It's support remote customise fedora custom Kickstart file, build custom LiveCD ISO image and download. now has basic function and framework. My job is add and enhance features including:
   • User management - integration with FAS. （useing python-fedora Fedora Account System Services )
   • Tabbed workflow with AJAX. (useing jQuery UI Library. )
   • Search Packages.
   • Add default users to Kickstart. Custom root password.
   • Hostname
   • Default Wallpaper, home directory content,
4. timeline for project
   • week 1: Communicate with mentor for detailed info, study project and install development environment.
   • week 2: Try finish first function: User management - integration with FAS.
   • week 3~5: Must finish the other request function: AJAX, search, user, hostname, default user management and so on. Add additional feature in the project's Features Planned according to my ability.
   • week 6~7: Testing and fix bug.
   • week 8: write documents.
5. Self-Convincing:
   • I'm a student in the graduate program of a Electronics and Communication Engineering, interested in open source, my undergraduate degree is computer science and technology which has a lot of software courses including Linux.
   • I am deep in embedded software, I have work experience before graduate school, use embedded Linux base software stack build a rich web-base management system for blade server management solution, this is a successful project which have used in business product.
   • Of course, I have python programming experience, I use python to do math.

About your project

1. What is the name of your project?
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.
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?
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.
   • If your project development progresses differently so there is not 90% functionality by the mid-term, you must be in regular contact with your mentor about this. Your mentor must not be surprised about the state of your project when the mid-term comes.
   • If you are not progressed this far in mid-term, you must have a plan with your mentor to fix the situation.
5. Convince us, in 5-15 sentences, that you will be able to successfully complete your project in the timeline you have described. This is usually where people describe their past experiences, credentials, prior projects, schoolwork, and that sort of thing, but be creative. Link to prior work or other resources as relevant.

You and the community

1. If your project is successfully completed, what will its impact be on the Fedora community? Give 3 answers, each 1-3 paragraphs in length. The first one should be yours. The other two should be answers from members of the Fedora community, at least one of whom should be a Fedora Summer Coding mentor. Provide email contact information for non-Summer Coding mentors.
2. What will you do if you get stuck on your project and your mentor isn't around?
3. In addition to the required blogging minimum of twice per week, how do you propose to keep the community informed of your progress and any problems or questions you might have over the course of the project?

Miscellaneous

1. We want to make sure that you are prepared before the project starts
   • Can you set up an appropriate development environment?
     • Yes.
   • Have you met your proposed mentor and members of the associated community?
     • Yes.
2. What is your t-shirt size?
   • L (175)
3. Describe a great learning experience you had as a child.
   • I like swimming, before primary school I learned how to swim by myself in a river near my house, by imitated other people's actions and practice.
4. Is there anything else we should have asked you or anything else that we should know that might make us like you or your project more?

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