Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 5.3

Write Code. Save Lives.

...

  1. If you don't have one yet, get an OpenMRS ID and create your user profile page. Upload an avatar photo. Make sure you are subscribed to the developer mailing list.
  2. If you haven't read it yet, read the GSoC Student Guide.
  3. Contact your mentor immediately and create a communication plan for now through the time of final evaluations. You should communicate once each week, if not more frequently. Determine the best way to communicate (e-mail, IRC, IM, Skype, telephone, etc.). Post the communication plan in your personal space on the OpenMRS wiki.
  4. Get OpenMRS installed and running. Read Developer Guide, 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. If you have quesitons about anything you read, contact your mentor or anyone the community.
  7. Set up a blog for GSoC. Send the URL to Unlicensed user 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. Browse other GSoC organizations and the pages they have for their students. We want to be the best!
  9. Review the requirements for your project together with your mentor and agree on the final list of requirements with your mentor.
  10. Submit a formal written proposal and project timeline to your mentor. Make sure your mentor agrees with both. Post them in your personal space on the OpenMRS wiki.

...

  • Every accepted student will be required to give a short (15-minutes: 10 minutes presentation, 5 minutes questions-and-answers) presentation/demo of their project twice during the program. You can use our screen sharing tools to demo your project. Look in the table of projects, mentors, and students above to determine which group you are in.
  • Check your calendars now to make sure these dates are OK for you. If you have a serious conflict with one of these dates, contact a student in a different group and trade dates with them. Both students should then notify Unlicensed user Michael Downey.
  • Students presenting early in the program can focus more on their plan and design strategy. Later presentations should be more of a "demo" and show your working project in-progress.

Group

1st Presentation

2nd Presentation

A

9 June

28 July

B

23 June

11 August

C

14 July

25 August

Tips for applicants and accepted students

...