Hello @aethelwulffe @teryhill @tony
I thought of some tasks for GCI, but i’m not sure whether they are good or not. I’m posting it here, and if you find anything to be modified, then please do let me know :
[1] Install Laravel on Mac/Linux/Windows. [2] Mapping current database with layout. i.e, making a proper document for forms with labels in UI and their related table. [3] Writing seeders for remaining table. [4] Writing test cases for database. (optional)
I think Robby wants everything stated at the 13-year-old level. I have known plenty of 13-year olds, and even one 10 year old that could do anything you care to set them on, but that is not a general standard.
I assume each of these tasks are intended to be sequential, and related to Laravel. I would title them “Laravel Project Task 1”, et cetera.
We need little tasks too, you know, “onesies”. I think “find one or more functions or methods that are duplicated in the code base, and document their existence and locations in a github issue” may be a fairly advanced achievable. This could be a lead up to a second task of "replace a duplicated function with calls to a common class library".
-Art
Ok. I got you. By “test cases for database” I meant, writing code to properly validate tables (its fields, creation etc), correct data is inserted as record (like no varchar field should store integer or any other type), checking proper constraints between tables, checking indices and migration compatibility. But yeah this will become a complicated task. Writing seeders are not so complicated, but I agree they will need to reference tables.
I like your idea of finding duplicate methods and documenting them.
Mapping database is also complicated but if a someone of 17 yrs age can do that. 
Sorry, I already posted the duplicate method stuff.
I have added 10 tasks to the list, several of them that may be done multiple times.
I will stop for now and let others have a chance. 
So can first 2 tasks be added? viz. installing Laravel and mapping current database.
@r0bby I will edit the tasks and also mention which tasks would be for beginner
I want tasks written in a way that kids can understand them.
Right,
So provide feedback…nice, respectful, calm feedback. You know, like:
/"Dear poster of this task. Are you having a nice day? I was wondering, and somewhat worried about you, because my impression of the content of the task you just posted made me think that you might be close to overdosing on amphetamines. May I suggest that you take a handful of barbiturates instead, and then perhaps we can work on paring this task down from the stratosphere. "/
My GrandMa always said you catch more bee’s with Honey than Vinegar.
I think they can. The task that @Asha_Surapaneni suggested is not to make a dictionary, but rather to showcase, how a medically sound term can be created. So maybe in the description of the task, we should require the student to capture screenshots of how they go to https://snomedbrowser.com/ (SNOMED dictionary) or http://www.icd10data.com/ (ICD dictionary) and add those terms as mapping to the concept.
I think that the task will need plenty of laid-out resources to give them a good start and keep them on track, but yes, totally a 13 year-old can do that. Now a 15-year old has typically already lost the brains they won’t get back until they are somewhere between 18 and 35, but yeah, a 13 year old can handle this.
Dude. Just add a task! Get something on the scoreboard. Provide some good resource links if it is complex.
Okay – Let’s add resources to the tasks. It’s COMPLETELY okay to do that…but I want to ensure we get contributors… ensure that the work we get is quality.
I apologize to anyone if I came off harsh…let’s try to follow the guidelines I laid out – it’s for uniformity purposes.
The Etherpad is there so that tasks can be added as you come up with them. Just add tasks – and please also add resources for students to do research.
Right on Robby. How close are we to having a good enough range of tasks.
I’ll look at them and start migrating them over this weekend. We had a decent amount from last year but I wanted more variety.
Variety and scale…better yet, scale-able tasks or ones that can be done multiple times. Hard the first time, then you get into production mode, and other kids can follow a peer example.
A good handful of tasks should be multiple per student.
@Asha_Surapaneni, the mockup plus component tasks for LH Toolkit can be dependent tasks. I do like that idea but we need to be clear that they need to be done either one after the other or together. Even better, one of us should do the UI mockups and have the students implement it…whatever works is fine by me…I’d prefer one task but if we can break it up into 2 – that’s fine too.
@Asha_Surapaneni – I moved your tasks to the bottom of the document
Go through the Radiology workflow with the old UI and make 2 UX recommendations
Watch this youtube video(will get link soon) about the general radiology workflow and go through this blog post(still to be written) which gives you steps of how to accomplish the workflow in the video using the LibreHealth Radiology module and make 2 UX recommendations from your experience.
If you need help, be sure to post your question to our forums or ask in our chatroom for Google Code-In.
This must be original work and must be in your own words. Any assets you use must be Creative Commons and attributed accordingly, or be your own original work.
@ivange94 where is the youtube video?
Make a video tutorial showing how to install radiology-owa(new UI) - Beginner
See this blog post(coming up shortly) about how to install the new UI on a running version of toolkit server. Make a video tutorial showing how someone can successfully install the UI
If you need help, be sure to post your question to our forums or ask in our chatroom for Google Code-In.
This must be original work and must be in your own words. Any assets you use must be Creative Commons and attributed accordingly, or be your own original work.
@ivange94 blog URL is missing.