The application period ended yesterday and Google will announce accepted organizations tomorrow. We currently have 14 mentors. If you are interested in mentoring and haven’t signed up yet, please sign up using this short 3 minutes form https://goo.gl/forms/AHtqYb9N5UrREd7K2
We had over 150 tasks which where mostly from previous gci years. These tasks don’t cover all categories yet. GCI tasks can fall under one of the following categories
Coding (No task for this category yet)
Documentation / Training (Enough tasks for this category)
Please these tasks are meant for kids between the ages of 13-17. And will be mostly new members to the community. The above tasks assume familiarity with the platforms already and some don’t state clearly what is needed. When updating these tasks please do well to also denote them with one of the following tags, beginner/coding/documentation/outreach/research/QA/user-interface, this will make my life easier when adding these to the gci website. See other gci tasks for examples.
Mentors if you need to create more tasks, please first visit the sample tasks. You can query tasks using one of the following labels, beginner/documentation/outreach/coding/QA/user-interface. And your priority in creating new tasks should be
We definitely do not need GCI-145 or GCI-146, since these were done by students in GCI 2016 and resulted in our OpenMRS Implementers Guide and OpenMRS Developer Manual, both of which are in GitBook format and hosted in GitHub. If we could point to specific sections of these books that are outdated, we would certainly benefit from some GCI tasks to review & update outdated parts of these manuals.
We could certainly use better REST API documentation. @pascal or @bholagabbar may have thoughts on this. Personally, I’d like to see our REST API documentation focus more on readability & usability than automation, come out from the Legacy UI (e.g., implemented as an OWA and accessible from System Administration screen) along with a version hosted at rest.openmrs.org that doesn’t require authenticating or navigating through a demo app, and, more importantly, contain lots of guidance and implementation notes beyond the specific elements (i.e…, text describing the purpose of tips for when/how to use the resource). While migrating to an OWA is probably beyond a GCI task, maybe asking GCI students to create a GitBook of the API would generate some of this missing text in a desired format (markdown) that could be used to make our REST API documentation friendlier to a new user (e.g., more like this than this).
Hmm, I feel that introducing students to the concept of an API in general is the farthest we can go as far as GCI is concerned. Having them make a request to the demo OpenMRS API inserting a patient or something of that sort seems like a good idea for a GCI task. I’m not sure if improving REST API documentation should be in our agenda for GCI. Simply having students copy paste and format documentation by picking it up from one source into another without understanding it doesn’t sound like a good idea.
@shivtej remember when these tasks will be published on on the gci website, it won’t be so obvious which project that task is coming from. And most of the titles won’t attract students.
Also I didn’t like how had to navigate multiple links just to fully undeserved what a particular task is about. My advice is, create a base task with all the information needed to complete it. Then make the rest of your task dependent on the base task. That way students will only attempt the other tasks if they have completed the base task hence they already have all the information they need.
Very unlikely. We need to assume that students come in with very little background in Software development. A huge chunk of our winners in the past years have come in absolutely clueless and nonetheless learnt and succeeded.
They’d need to know what an API is, the know what Swagger’s purpose is, then understand what validation is and if they’ve come this far, then try fixing issues.
@dkayiwa can we have a few non beginner coding tasks? Each student can complete a max of 2 beginner tasks after which beginner tasks will disappear from their dashboard. This means if a student has already complete 2 non coding beginner tasks they may never have the chance to work any of your coding tasks as they’ll disappear from their dashboard.
@ivange94, sorry for the delayed response.
I have updated the title of the tasks and regarding base task and all, we have organized these tasks like that only.
AC-332 is parent task where all the information is written and in subtasks, specific information is written. Any student will first go to any subtask and then get more information from the parent task. And there is no actual work in the parent task so can’t use it as base task.
Let me know if still we want to follow another structure.