Notice: We have migrated to GitLab launching 2024-05-01 see here:

Version 13 (modified by Chris Johns, on 11/22/14 at 05:37:32) (diff)


SoC Project Management

Table of Contents

  1. SoC Project Management
  2. Q&A

Congratulations on being accepted to the Summer of Code! We hope this is a positive experience for you and we want to help you have fun and for your project to succeed.

This page outlines expectations for how you will manage your project and interact with the community. Hopefully these processes will make your project visible to the entire community and keep you on track for a successful completion.

  • Create a wiki page in the RTEMS Wiki dedicated to your project if none exists, and change the Open Projects entry for your project into a link to your project's Wiki page. Update the page as it moves from idea to reality. At the end, your page may have howto, technical details, etc about the project.
  • Create a code repository at for your project. If your project is modifying one of the RTEMS repositories, you should fork that repository from You will use github to keep your work publicly available all summer long. You should commit and push all of your work to github on a daily basis any time that you make changes to your code.
  • Create a public Google Calendar for your project so mentors and interested parties can track your schedule. Add deliverables and other deadlines from your proposal to your calendar.
  • Update the table in the SoC proposal section for now with links to the above.
  • Continue to communicate frequently and publicly. Use the RTEMS Development Mailing List as much as possible. This gives you access to more experts in more time zones than direct connections with your mentors or on IRC.
  • Do NOT struggle needlessly. If you have a blocking issue, ask for help. There are no bonus points for suffering.
  • Do NOT disappear. If you need a leave of absence let us know. We can spend time to give you advice on what you can do offline. If you disappear and don't tell us, we have to assume that you are dropping out.
  • Avoid dumping large amounts of code on your mentor. and you should submit patches incrementally to the rtems-devel mailing list for a broader audience.
  • If your project involves projects other than RTEMS, submit patches to those projects according to how their community manages patches. If your project needs to submit patches to an FSF project, you need to get your FSF paperwork ready. Talk to your mentor about this possibility.


  • What are the instructions to the student if the mentor is inaccessible at some stage during the program?

We will assign each project with at least two mentors. If you have any difficulty contacting your mentors, email Joel Sherrill, Chris Johns, and Gedare Bloom. If you do not get a response in a reasonable time, say 48-72 hours to allow for holidays and weekends, then bring the issue up on the RTEMS Development (rtems-devel) Mailing List.