Write Code. Save Lives.

Students, Projects, & Mentors

Next Steps for Accepted Students

After accepted students are announced, here's what should happen:

1. If you can, attend the Developers Forum (Inactive) on Thursday 26 April to briefly introduce yourself and meet other students.

2. Contact your mentor immediately. Make a plan to communicate with them regularly - at minimum, once each week. Determine the best way to communicate (e-mail, IRC, IM, Skype, telephone, etc.).

3. If you haven't yet, join our developers mailing list to keep track of what's going on in our development community and our IRC channel to spend time with other community members & students.

4. Get OpenMRS installed and running. Read Developer Documentation, Getting Started as a Developer, and ask others in the community if you have questions. If you ask questions the smart way, you'll get better responses.

5. Get a development environment installed and running.

6. Review our Conventions page.

7. Set up a blog for your work on open source projects, including GSoC. Send the URL to @Michael Downey. If you don't have a blog yet, you can create one for free at WordPress.com or Blogger.com.

8. Browse the current OpenMRS code specific to your project.

9. Review the requirements for your project together with your mentor.

10. Agree on final requirements with your mentor, and post a formal written proposal including project schedule (timeline) on which you both agree.

Project Presentations

• During the summer, each student will be required to give two (2) short presentations during our weekly Developers Forum (Inactive) to explain and demonstrate their project twice during the program. You can use our screen sharing tools to demo your project.

• Thursday 24 May: "Speed-Geeking" Student Introductions. Provide 1 slide and take 2 minutes to answer the following questions:

  • Who are you?

  • Where are you from?

  • What's your project about?

  • What's a fun fact about you that few people know?

  • Plus, 1 minute for any questions from others.

• Thursday 21 June: 10-minute presentations of project work-in-progress including a short demo (Group A)

• Thursday 28 June: 10-minute presentations of project work-in-progress including a short demo (Group B)