IntroductionThe planning team had a great time coming up with tasks for students to do. Now we would love for the Joomla! community to suggest more tasks that we can use in the future. If you have a task, just add it as a comment to this page. Here is the format that we used to create the tasks: Ideally we should use the same structure for all of the tasks. This should help us in terms of evaluating the work done and help the student in terms of understanding the scope of the project. Also, not coincidentally, it will make the work of mentors easier because they will spend less time explaining what the task actually is after a student has claimed it. One line summaryJust as in most issue trackers we need a one line descriptive summary of the task. This should also be used in the link from the category page. Describe the task.The better the description of the task, the better the outcome is likely to be. Give as much explanation of what you mean as possible, using concrete language. If you know that there are steps involved, try to describe them. If there is reading or research that the student will be required to do in order to complete the project include this. Skills needed Describe the skills needed to do this task. Please include at least one, even if it is "Familiarity with Joomla!" Skills could include: knowledge of a specific software or html, proficency in written English, language proficiency, graphic design skills and so on. We want the student to be able to complete the task and making sure the student who claims a task has the appropriate skill set is part of that. DifficultyWe would like to have two levels of difficulty, more or less, basic and advanced. Work ProductDescribe what you actually expect the student to produce in order to meet the terms of the task. This might be a memo or report, a piece of code, a patch file, or something similar. It should be tangible and also realistic for a high school student working in a limited time frame. This is what will ultimately be used to determine if a task has been successfully completed and the student receives the payment for completion, so the more clear the better. However, it might be useful to specify the description as a minimum since we want to encourage students to go as far as they would like. LicensingUse one of these licenses: General public license (GPL) version 2 Joomla! Electronic Documentation License CategoryWhen creating a task make sure to assign it to a category in the first label field. If you delete what is there by default you will get a dropdown of the official categories. If you aren't sure just do your best. The contest rules require that tasks be assigned to these categories. You can add other labels if you want, but make sure to do the category. Extra Credit (Optional)Describe follow up tasks that would improve the overall contribution quality. Time LimitEach task needs to have a time limit specified. This is the length of time between when a student claims a task and when the student must hand in the work. There is a three day grace period. Time limits should be realistic given the ages and skill levels of students, but not so long that they inspire students to claim a task on the first day and then not do any work on it for weeks. TemplateSo here is a template that can be copied and pasted into the issue manager. One line summaryDescriptionSkills NeededDifficultyWork ProductLicensingEither the GPLv2 or the Joomla! Electronic Document License Extra Credit (optional)Time Limit
|
Sign in to add a comment
