Raxa EMR is accepted to participate in Google Summer of Code™ in 2014! This is a great opportunity to help create our point-of-care system that will serve patients in India and around the world.
...
If you are an active participant in the Raxa EMR community and would like to be a mentor for 20132014, please edit this page and add your name to the list below.
...
We're happy you're interested in working on the Raxa EMR during Summer of Code 20132014. Here are some tips that we've prepared to help your application process be easier and more successful. These are all things you can do today to start getting involved.
...
- Become familiar with the Raxa EMR and your project before the start date.
- Complete a short "progress report" each week to help stay on schedule.
- Commit early. Commit often. This is an important value in our open source community - read why.
- Join the interns mailing list. (We'll help you with this.)
- You are now part of our developer community. We want you to feel like part of the team, so we hope you will:
- Have technical discussions on the Contributors Google Group
- Ask questions (the smart way) if you get stuck.
- Participate in our Weekly meetings via phone or Skype.
- Give one or more project presentations during those weekly meetings so we can see the cool stuff you're making.
...
- You will have fun!
- You will learn how to work within an open source project–a new project helping people save lives around the world.
- You will have dedicated time (4-5 hours each week) with an experienced mentor, and will have a secondary mentor for questions or problems.
- Our community will do its best to answer your questions and help you (make sure to ask questions the smart way).
- The Summer of Code program leaders (both at Raxa EMR and Google) will be available if any problems arise between students and mentors.
...
- Help your student be successful. Commit to spending a minimum of 4-5 hours each week with your student answering questions, giving advice, working together, and evaluating his or her progress.
- Complete a short "progress report" each week to help stay on schedule and catch potential problems early.
- Read the GSoC Mentoring Manual and ask questions if you have them.
- Reach out to the Summer of Code project leaders if you have questions or concerns.
- Have fun and work hard! The highest-performing mentors will get an expenses-paid trip to Google's headquarters in October to geek out with fellow mentors from other open source projects.
...
February 25 - March 9: | Would-be student participants discuss application ideas with mentoring organizations. |
March 10: | Student application period opens. |
March 21: | Student application deadline. |
Interim Period: | Mentoring organizations review and rank student proposals; where necessary, mentoring organizations may request further proposal detail from the student applicant. |
April 18: |
|
April 21: | Accepted student proposals announced on the Google Summer of Code20132014 site. |
Community Bonding Period: | Students get to know mentors, read documentation, get up to speed to begin working on their projects. |
May 19: |
|
Work Period: | Mentors give students a helping hand and guidance on their projects. |
June 23: | Mentors and students can begin submitting mid-term evaluations. |
June 27: |
|
Work Period: | Mentors give students a helping hand and guidance on their projects. |
August 11: | Suggested 'pencils down' date. Take a week to scrub code, write tests, improve documentation, etc. |
August 18: | Firm 'pencils down' date. Mentors, students and organization administrators can begin submitting final evaluations to Google. |
August 22: |
|
August 22: | Students can begin submitting required code samples to Google |
August 25: | Final results of Google Summer of Code20132014 announced |
Next Steps for Accepted Students
...
- 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.).
- Read Getting Started Guide, and ask others in the community if you have questions. If you ask questions the smart way, you'll get better responses.
- Get a development environment installed and running.
- Review our Conventions page.
- Get an RaxaEmr ID if you don't have one already. Create a user profile page.
- Set up a blog for GSoC. Send the URL to us. If you don't have a blog yet, you can create one for free at WordPress.com or Blogger.com.
- Browse the current Raxa EMR GitHub code specific to your project.
- Browse other GSoC organizations and the pages they have for their students. We want to be the best!
- Review the requirements for your project together with your mentor.
- Submit a formal written proposal to your mentor.
- Agree on final requirements with your mentor.
- Develop a project schedule (timeline) with your mentor.
...
- If possible, join the Raxa Meetings every Monday. You can participate by telephone or Skype. The 2nd and 4th Mondays of each month will be dedicated to Summer of Code, so make every effort to attend to listen to your fellow students' presentations (see the next section for details).
- We use JIRA as a tool for issue tracking and project management.
- Tips for using e-mail:
- If you have a highly specific question, contact your mentor.
- Technical discussions, ideas, and requests for feedback should be sent to the entire community on the mailing list.
- The Interns mailing list is for accepted students to discuss SoC administrative issues. This list should not be used for technical discussions.
- Skype or telephone — sometimes a short discussion can get ideas across much more efficiently
- Google Docs — an excellent tool for sharing and collaborating in real time on documents or spreadsheets
- Use this wiki often:
- Be sure to make a user profile page.
- Every project should have a Raxa EMR wiki page where you document your project, progress, technical details, show mock ups, etc.
- Scheduling tools:
- WorldTimeBuddy.com — to clarify/coordinate times around the world
- Doodle.ch — to coordinate meeting times for larger groups
...