Congratulations to the 15 students selected to work with us during Google Summer of Code 2017, we had very good students applying this year and are so thankful to all our mentors who reviewed each proposal carefully until we could identify the best, for students not accepted this year take carriage and keep active and perhaps re-apply next year, I (@k.joseph) did the same after my first failed attempt but was later successfully twice the following years. As a community we are exited and are looking forward to having a great productive summer of write code save lives.
To the accepted students: Please note, were are now in The Community Bonding period (May 4-30) which is intended to help you get ready to start contributing to OpenMRS. you will not receive any of your stipend until after successfully passing your first evaluation at the end of June. see: GSoC timeline
Please read this entire post very carefully. After reading this post, there are several steps you must take immediately. Failure to perform any of these tasks before the end of the community bonding period (May 4 - 30, 2017) may cause your disqualification from the program.
This week: Introduce yourself on OpenMRS Talk in the appropriate pinned topic at the top of the #community:gsoc category. Tell us a little bit about yourself, your interests, your selected project, and why you find OpenMRS interesting. We will use OpenMRS Talk for all official communications about the program, so check it every day. Complete this task in the next week.
In two weeks time: Get your blog ready. You must post an update blog entry every week during GSoC. Start now so you get in the habit of writing at least one post every week. You don’t have to create a new blog for GSoC; it’s OK to use an existing one and rather just have a GSoC category in which all your posts will be.
Contact your mentor immediately. Set up a schedule and plan for communication with your mentor each and every week, and stick to it. Remember, we’re an open source project and public interaction is important, it is a key principle of open source, work happens where everyone can see it. Similarly, all work done by you should be shared in a publicly available repository such as IRC/Telegram or here on Talk. Make sure your mentor has identified one or more backup mentors if she or he is not available. Prepare a detailed project plan (week by week) with milestones with your mentor and post it in the appropriate category on OpenMRS Talk, with the #gsoc2017 tag. Complete all these tasks before the end of the community bonding period on 30 May 2017.
Be prepared to submit a weekly status report form. We’ll post more information about this on OpenMRS Talk before the coding start date. The status report is very short but very important; it helps us to ensure your project is on track and things are going well. If you miss filing 3 status reports, you’ll be removed from the program, so remember to add this to your weekly schedule!
As much as you can attend the daily scrum meetings that happen on IRC where any of your blockers would be shared and you receive instant support.
Once again, congratulations! We are impressed by your accomplishments so far, and hope you are just as pleased to be part of our community of so many wonderful people!
If you have any questions about participating in GSoC, or just want to chat with your fellow students, use the #community:gsoc category here on OpenMRS Talk. We look forward to hearing from you!
@k.joseph & @harsha89 OpenMRS Organization Administrators for Google Summer of Code
?