Difference between revisions of "Google Summer of Code - OpenEMR"

From OpenEMR Project Wiki
Line 12: Line 12:
:::*All [[Repository_work_flow_structure#Integration_Developers_2|Integration Developers]] and [[Repository_work_flow_structure#Privileged_Developers_2|Privileged Developers]] are considered "committers" to OpenEMR.
:::*All [[Repository_work_flow_structure#Integration_Developers_2|Integration Developers]] and [[Repository_work_flow_structure#Privileged_Developers_2|Privileged Developers]] are considered "committers" to OpenEMR.
*Make an Ideas list page (proposed student projects or starting points)
*Make an Ideas list page (proposed student projects or starting points)
*Need to show that the OpenEMR project is important (for example, ensure all downloads are centralized from sourceforge)
*Need to show that the OpenEMR project is important
::*Optimize download statistics(ie. ensure all downloads are centralized from sourceforge)
::*Push for conference presentations
::*Push for deployment announcements
::*Continue amassing social tool followers
*Need to show that the OpenEMR community is healthy
*Need to show that the OpenEMR community is healthy
::*Deal with OpenEMR/OEMR

Revision as of 18:47, 22 May 2012

Overview

The OpenEMR community is planning to submit an application for 2013 Google Summer of Code.

Details

  • GSOC 2012 FAQ
  • Guessing the program announcement for 2013 will be sometime in February,2013.

TO DO

  • Figure out who will be the Organization Administrator (and also need a backup Organization Administrator)
  • List of mentors (and backup mentors)
  • "Mentors for their organizations must at least be committers for the corresponding project and their participation in Google Summer of Code on the organization’s behalf must be approved by the organization administrator via Melange"(from GSOC 2012 FAQ)
  • Make an Ideas list page (proposed student projects or starting points)
  • Need to show that the OpenEMR project is important
  • Optimize download statistics(ie. ensure all downloads are centralized from sourceforge)
  • Push for conference presentations
  • Push for deployment announcements
  • Continue amassing social tool followers
  • Need to show that the OpenEMR community is healthy
  • Deal with OpenEMR/OEMR