GSOC 2017/Student Application Mandymy

Contact Information

• Name: Mandy Wang
• FAS ID: Mandymy
• Email: wangmychn@gmail.com
• Blog: https://mandywangblog.wordpress.com/
• Github: https://github.com/MandyMY
• Twitter: @MandyMY_
• IRC: Mandy (freenode)
• Location: Shanghai, China
• Working Hours: 18:00 - 24:00 (CST); 10:00 – 16:00 (UTC)

About Me

Do you have any past involvement with the Fedora Project or another open-source project as a contributor? What kind of contributions have you made (code and non-code)? Please share any public contributions you have made (urls, etc.) What are you studying? Why? What motivates you to do your best? How do you stay focused? Briefly describe how you organize your work.

Why Fedora?

Why do you want to work with the Fedora Project? Do you plan to continue contributing to the Fedora Project after GSoC? If yes, what sub-project(s) are you interested with?

Why Migrate Plinth to Fedora Server?

Which specific project interests you? If you are proposing your own project, do it here. If you are proposing the project, explain why it benefits the community. Have you contacted the mentor(s) listed for the project? What relevant experience do you have for this project? What do you want to gain from this project? Describe this project in your own words. What does it mean to you? What do you think the final deliverable is?

A Rough Schedule

• May 5 - 20:
  • Integrate into the community;
  • Be familiar with the existing code and the code style;
  • Learn more about Linux, including apt, dnf, Deb and RPM;

• May 21 - 30:
  • Prepare and complete the details of the project, such as listing the modules, the documents which need to be modified in the future;
  • Make Gantt chart for the detailed schedule;

• May 31 - June 26:
  • Convert the first half of the modules from Deb-based to RPM-based, including:
    • Replace the apt command code with the dnf command code or fit both of them;
    • Change the Deb-based packages into RPM-based packages which play the same roles;
    • Test after each module finished;

• June 27 - 30:
  • Mid-term examination, submit the evolution of my mentor;

• July 1 - 24:
  • Convert the second half of the modules from Deb-based to RPM-based, including:
    • Replace the apt command code with the dnf command code or fit both of them;
    • Change the Deb-based packages into RPM-based packages which play the same roles;
    • Test after each module finished;
  • Check out if any module is omitted;

• July 25 - 28:
  • Mid-term examination, submit the evolution of my mentor ;

• July 29 - August 21:
  • Make a RPM package for Plinth from source and setup a repo for it in Copr;
  • Test inside a Virtual Machine, refer to the HACKING;
  • Modified README.md and requirements.txt to fit Fedora which is RPM-based;
  • Add the guide of RPM-based package to Plinth User Guide and create a wiki page for it in Fedora;

• August 22 - 29:
  • Review all achievements;
  • Submit the code, project summaries, and final evaluation of my mentor.

My Specific Plans from May to September

I need to complete my graduation thesis in the early June, then I plan to gap a half year before the next degree, so I have enough time to work with this project.