| Current revision |
Your text |
| Line 1: |
Line 1: |
| - | {{Task/Record | + | {{Task/Header}} <!-- keep this line --> |
| - | |<!-- (optional) A short, one line, description of what this task is
| + | == Description == |
| - | about. Only enough to distinguish it from other tasks. The details
| + | == Rationale == |
| - | will go in the section below. Default is the name of the current
| + | == Assign To == |
| - | page. -->|
| + | [[Training Committee]] : {{member|Alieza Cyr}} |
| - | Description = | + | |
| - | Record a description of training events that have occurred
| + | |
| | | | |
| - |
| |
| - | |<!-- (optional) Status of the task. Default is "Open". Use one of the
| |
| - | following:
| |
| - | Open - task has work to be done.
| |
| - | Closed - task is complete or cancelled. -->|
| |
| - | Status =
| |
| - |
| |
| - |
| |
| - | |<!-- (optional) The priority of this task. Use a number like 1, 2, 3
| |
| - | or 1.5. Lower numbers are higher priority. You can use the same
| |
| - | priority number as on other tasks. -->|
| |
| - | Priority =
| |
| - |
| |
| - |
| |
| - | |<!-- (optional) A rough estimate in hours of how long the task will take.
| |
| - | Generally you don't have to be very accurate, so can choose rough
| |
| - | numbers like: 1, 2, 5, 10, 20, 50. Use just the number, don't
| |
| - | add the word "hours" or "h". -->|
| |
| - | Estimate hours =
| |
| - |
| |
| - |
| |
| - | |<!-- (optional) The person this task is assigned to. Use the full name
| |
| - | which they have as an account on this wiki. If more than one person
| |
| - | list only one person as the lead. -->|
| |
| - | Assigned to = Brett Wuth
| |
| - |
| |
| - |
| |
| - | }}
| |
| - | == Rationale ==
| |
| - | used to validate members are being appropriately trained
| |
| | == Details == | | == Details == |
| - | For every training event that we host, we should record a description of what the training event included.
| |
| - | This will allow us to determine later which members have what training.
| |
| - |
| |
| - | For a typical two-hour training session like we have with our regular monthly meetings,
| |
| - | a two sentence description would be sufficient.
| |
| - |
| |
| - | Alternatively, if the instructor provided a set of slides, an outline, or a hand-out that
| |
| - | really describes what the training event covered, there may be no need to write anything
| |
| - | just upload or link to the related material.
| |
| - |
| |
| - | All the training events should be listed in our [[Calendar]].
| |
| - | It's a different person's task to keep the calendar up to date,
| |
| - | but if the event isn't listed, you can add it.
| |
| - |
| |
| - | The event listing in the calendar should link to a page all about the event.
| |
| - | That page should have a section labelled "Record" where you can include
| |
| - | your description or upload the material from the training event.
| |
| - | == To do ==
| |
