As mentioned here, GSoC contributors are required to post (at least) one blog entry a week during the period of the GSoC program. All the GSoC contributors are requested to have a blog set up about the community bonding period, and add a post on this thread as a kick start.
Provide a link to your blog post. Please tag all your GSoC posts with the tags #openmrs and #gsoc2023 .
Please let us know how you found out about GSoC, we’re interested to hear if this happens through word of mouth, from websites/forums/chat, or other campaigns/presentations at universities and colleges.
Note : If you already have an existing blog, feel free to use that, otherwise you’ll need to set up a new blog for this. You’re welcome to use a traditional free blog service (such as wordpress , blogger , medium etc.) or host your own.
If you have any questions or comments, please don’t hesitate to reach out to your project mentors and/or GSoC Admins @jayasanka@kdaud
Hello everyone! I’ve shared my community bonding period experience in the following blog:
Week 0: Community Bonding
I discovered the Google Summer of Code (GSoC) program during the period of global lockdown caused by the COVID-19 pandemic, during which I sought to expand my knowledge and skills about opensource #gsoc2023#openmrs
Hi GSoC contributors, it’s really interesting to read through your community bonding experience especially your interactions with your mentors, squads and the community. Further still, it’s great that you used the period to learn and understand more about your project objectives, structuring project timeline together with your respective mentors and setting up the development environment. Cheers!
It's now time to code ...<Write Code, Save Lives />
We suggest that weekly blogs are done at the start of each week(Mondays) to help us ensure your project is on track and check that everything is going well. The blog will be reporting what you will have worked on during the previous week. The next status report is due next week Monday, 5th June, by EOD in your local timezone