Gsoc2018 Community Bonding Period At Openmrs.

Week 1


Openmrs is a medical Record System and is aimed at improving health care delivery in resource-constrained environments by coordinating a global community that creates a robust, scalable, user-driven, open source medical record system platform.The community bonding period of my gsoc 2018 at openmrs began on april 23rd after the good new reached me of haven been selected on the project Password Reset Via Email project. Even though i was in one way or the other participating in the community already. This period made me strengthen my interaction with the community even more. I started by Me claiming and issue ( Trunk-5221 )which i worked on and as well attending the daily scrum meeting of the openmrs community. I have been very much welcomed and i get a lot of assistance and feedback from the community in places where i got stuck while working on the ticket which i cliamed, after a scrum meeting some one of the community was assigned to help me out resolve the blocker that is preventing me from working. This went on for about a week and i was able to make a pull request on the ticket which i claimed. This marked the end of my first week of Community Bonding Period. 

How i came to know about google summer of code(gsoc).


 I knew about gsoc in my second year of university studies ie 2016. and this was as a result of my belonging to one of the club in the university by name elite programmers club. this was mentioned and elaborated on by one of the senior students of the faculty of engineering and technology by name Nyah check. From there i was also opportuned to attend event some of which were opensource and GDG Buea, Google i/o where i was properly exposed to opensource and many other activities that relate to programming and my field of studies.

Comments

Post a Comment

Popular posts from this blog

Algorithm Design A Call For Concern To Software Engineers

Image
Algorithms in its entirety are often misunderstood and misinterpreted by most of the software engineers or developers. Technically every software or program you develop does use an algorithm and in most cases brute-force that is the obvious solution and at times the easiest. In computer science and software engineering, the concern is in solving problems and any problem that needs to be solved requires a solution in a finite amount of time and using the smallest amount of resources as possible.  In this post is the discussion about the importance and need for a software engineer to be able and capable of designing a good algorithm in his or her software development lifetime. This post will also go further to demonstrate on the side effects that you as a developer have without basic knowledge of algorithms,  the software that you build and the community that uses the software you build. Importance of good algorithm design. Algorithm design is important because They make ...
Read more

A health wise peep into the life of a home based developer

First look at the lifestyle of a developer: Basically, a home-based developer though it applies to an office developer. It all begins with the lifestyle of the individual. Haven lived in this lifestyle and among other developers who equally lived a similar lifestyle, I can say the following.  Most developers take it as a lifestyle in that skipping breakfast is the order of the day and telling you that the last meal they take was maybe yesterday afternoon is a common wording that you can hear. This is not because they don’t have the means to get the food but most times because they neither felt hungry nor hadn’t any time to look for something and eat. This even goes further when they happened to get something and eat they eat what is termed junk food. Here I mean they go for what is readily available and takes less effort to acquire. They end up with things like bread, or just carbohydrate food. That is if we are to qualify it as food then they might spend their remaining time...
Read more

Week Twelve

Image
Week 12. This week commenced and i fully worked on making sure all the hanging pull request with respect to the core have been merged and closed. I accomplished these by hastening up my speed in fixing reviews, then i created new branches called general fix where all the light works related to renaming adding exception modifying exception messages and as well writing tests. Rest webservice. After sucessfully finishing with the core and everything merged, I went straight away to the  rest webservice module where i added 2 endpoint to handle the get with provided activation and a post with new credentials  password and activation key. this i did before consulting my mentor and  after consulting him. There was alot of other design changes such. i had to send and email message to my two mentors ie primary mentor and backup mentor. I also posted on talk here   from this talk post i received many criticism and all of them were positively to my benefits in finishing u...
Read more