Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Fix formatting issues


  1. Commit to spending a minimum of 4 hours each week to be available to guide and mentor students (not just your assigned student).
  2. Commit to being present in IRC and/or Telegram to help answer questions as much as your schedule allows, at a minimum of 4 hours each week.
  3. Prepare a good overview of your project idea(s) and have them linked to this wiki page.
  4. Watch OpenMRS Talk for questions about your project idea(s).
  5. Review student proposals and work with other mentors and organization admins to select the best candidates for OpenMRS.
  6. Treat returning students who have applied with as much (or more!) scrutiny than first-time students.

Selecting Students

  • Selecting the most suitable student for the project you mentor is a crucial part of GSoC as it directly affects the outcome of the program. When evaluating candidates, you can consider the following things:
    1. Understanding of the Project: Check if the student clearly understands the project idea, how they plan to approach it, and what outcomes they expect. Look for well-explained proposals that show the student has done research on the project, including its background, goals, and why it matters to OpenMRS.
    2. Technical Proficiency: Evaluate the student's technical ability to execute the project successfully. This can be done by reviewing their prior work, such as code contributions, projects, github activites etc.
    3. Alignment with Project Goals: Determine how well the student's proposal aligns with the goals and requirements of the project. Look for creativity, innovation, and feasibility in their proposed solutions.
    4. Community Engagement: Consider the student's involvement and engagement with the OpenMRS community. This includes participation in discussions, contributions to documentation, and responsiveness to feedback.
    5. Be Mindful of AI-Generated Proposals: With advancements in technology, there might be instances of AI-generated project proposals. While these proposals may appear polished, look for genuine understanding, personalization, and originality in the student's ideas.
  • Refer to the GSoC Guide on selecting a student for additional insights and best practices.
  • You can also use our marking rubric as a guide when assessing student proposals. You can find it here.
  • Feel free to reach out to the Org Admins if you require assistance or have any questions during the selection process. Their support can be valuable in making informed decisions and ensuring a successful GSoC experience for both mentors and students.

After student selection

  1. Ensure your student is ready & active. They should have a dev environment, be regularly communicating in the community, and have prepared a project plan together with you. (See above for student expectations.)
  2. Read the GSoC Mentor Guide and ask questions if you have them.
  3. Be sure to CC your backup mentor on communications with the student so your backup mentor can keep abreast of the project's progress in case she needs to step in for you if you have an emergency that will take you away from GSoC for more than a week during the program.
  4. Reach out to the Summer of Code organization administrators if you have questions or concerns.
  5. If the student is not active during the community bonding period, please contact the organization administrators.