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

From OpenEMR Project Wiki
 
(6 intermediate revisions by the same user not shown)
Line 1: Line 1:
==Overview==
==Overview==
:The OpenEMR community is planning to submit an application for 2013 Google Summer of Code.
:The OpenEMR community submitted an application for 2013 Google Summer of Code on 3/29/2013.


==Details==
==Details==
*[http://www.google-melange.com/document/show/gsoc_program/google/gsoc2012/faqs GSOC 2012 FAQ]
*[http://www.google-melange.com/gsoc/homepage/google/gsoc2013 GSOC 2013 Home Page]
*Guessing the program announcement for 2013 will be sometime in February,2013.
*[http://www.google-melange.com/gsoc/document/show/gsoc_program/google/gsoc2013/help_page GSOC 2013 FAQ]


==TO DO==
==Completed==
*Figure out who will be the Organization Administrator (and also need a backup Organization Administrator)
*Organization Administrator and backup Organization Administrator
*List of mentors (and backup mentors)
:*Brady (primary) and Rod (backup)
::*"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)
*List of mentors
:::*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.
:*Brady Miller, Rod Roark, Kevin Yeh, Kevin McAloon, Kenneth Chapple, Devi Govindasamy and Brad Greg.
*Make an Ideas list page (proposed student projects or starting points)
*Make an Ideas list page (proposed student projects or starting points)
::*"An Ideas list should be a list of suggested student projects. This list is meant to introduce contributors to your project's needs and to provide inspiration to would-be student applicants. It is useful to classify each idea as specifically as possible, e.g. "must know Python" or "easier project; good for a student with more limited experience with C++." If your organization plans to provide an application template, it would be good to include it on your Ideas list. Keep in mind that your Ideas list should be a starting point for student applications; we've heard from past mentoring organization participants that some of their best student projects are those that greatly expanded on a proposed idea or were blue-sky proposals not mentioned on the Ideas list at all. A link to a bug tracker for your open source organization is NOT an ideas list."(from GSOC 2012 FAQ)
:*[[GSOC 2013 Projects]]
*Need to show that the OpenEMR project is important
*Need to show that the OpenEMR project is important
::*Optimize download statistics(ie. ensure all downloads are centralized from sourceforge)
:*Hopefully conveyed on the application.
::*Push for conference presentations
::*Push for deployment announcements
::*Continue amassing social tool followers
::*etc...
*Need to show that the OpenEMR community is healthy
::*Deal with OpenEMR/OEMR

Latest revision as of 08:05, 29 March 2013

Overview

The OpenEMR community submitted an application for 2013 Google Summer of Code on 3/29/2013.

Details

Completed

  • Organization Administrator and backup Organization Administrator
  • Brady (primary) and Rod (backup)
  • List of mentors
  • Brady Miller, Rod Roark, Kevin Yeh, Kevin McAloon, Kenneth Chapple, Devi Govindasamy and Brad Greg.
  • Make an Ideas list page (proposed student projects or starting points)
  • Need to show that the OpenEMR project is important
  • Hopefully conveyed on the application.
Retrieved from "https://www.open-emr.org/wiki/index.php?title=Google_Summer_of_Code_-_OpenEMR&oldid=14138"