Difference between revisions of "DevelopersTraining"
Brandon Bot (talk | contribs) (Refactored to use standard open task categories Category:OpenTask, Category:DevelopmentTeam) |
|||
|
(One intermediate revision by the same user not shown) | |||
| Line 16: | Line 16: | ||
* <strike>Ask [[Ethan]] to create developer accounts on nimbus for each of the new hires</strike> | * <strike>Ask [[Ethan]] to create developer accounts on nimbus for each of the new hires</strike> | ||
| − | |||
</noinclude> | </noinclude> | ||
| + | [[Category:DevelopmentTeam]] | ||
| + | [[Category:OpenTask]] | ||
Latest revision as of 20:59, 7 February 2008
What (summary)
To make sure that the new hires learn all the articles in New_Developer_Orientation.
Why this is important
Training our new hires is something that we take very seriously. It is important that our new hires get up to speed quickly.
DoneDone
-
New hires are comfortable with vim editors. -
when all new hires know enough ruby that they can jump into our projects. -
They know enough Linux and GIT - They can install MediaWiki and Compost and understand how the pieces work together.
Steps
-
Ask Ethan to create developer accounts on nimbus for each of the new hires