Change Details

=== Background === As a newcomer to the Wikimedia community and also my first experience as a professional developer in a team the onboarding has been a overwhelming and difficult experience. Given that it is a priority to acquire and retain 'non-wikimedians' and junior level developers I suggest that the [checklist for newly emplyed or trainees](https://se.wikimedia.org/wiki/Checklista_f%C3%B6r_nyanst%C3%A4llning_eller_ny_praktik) is complemented with a coherent recruitment process initially document based. [Several smaller](https://phabricator.wikimedia.org/project/view/2064/) initiatives are currently in progress. However, I see a lack of high (e.g. "culture, role-expectations") and middle-level (e.g. how and why we use the tools we use, suggestions on how to give feedback and support) introductions. A fairly simple way to start would be to base it on the article about [onboarding](https://en.wikipedia.org/wiki/Onboarding) and fill in the learnings in a simple, straigth-forward language with links to further reading. 1.A general introduction to Wikimedia Sverige (all newcomers) 2.A role-specific introduction for developers (can be a template for other roles) === Goals === These goals are taken from the Wikipedia article on [onboarding](https://en.wikipedia.org/wiki/Onboarding). These can be continually measured as simply as talking about them at e.g. monthly 30 minute team meetings to adress them promptly by collaboratively making them actionable. * higher job satisfaction * better job performance * greater organizational commitment * eduction in occupational stress * reduction in intent to quit

=== Background === As a newcomer to the Wikimedia community and also my first experience as a professional developer in a team the onboarding has been a overwhelming and difficult experience. Given that it is a priority to acquire and retain 'non-wikimedians' and junior level developers I suggest that the [checklist for newly emplyed or trainees](https://se.wikimedia.org/wiki/Checklista_f%C3%B6r_nyanst%C3%A4llning_eller_ny_praktik) is complemented with a coherent recruitment process initially document based. [Several smaller](https://phabricator.wikimedia.org/project/view/2064/) initiatives are currently in progress. However, I see a lack of high (e.g. "culture, role-expectations") and middle-level (e.g. how and why we use the tools we use, suggestions on how to give feedback and support) introductions. A fairly simple way to start would be to base it on the article about [onboarding](https://en.wikipedia.org/wiki/Onboarding) and fill in the learnings in a simple, straigth-forward language with links to further reading. 1.A general introduction to Wikimedia Sverige (all newcomers) 2.A role-specific introduction for developers (can be a template for other roles) === Goals === These goals are taken from the Wikipedia article on [onboarding](https://en.wikipedia.org/wiki/Onboarding). These can be continually measured as simply as talking about them at e.g. monthly 30 minute team meetings to adress them promptly by collaboratively making them actionable. * higher job satisfaction * better job performance * greater organizational commitment * eduction in occupational stress * reduction in intent to quit === Structure === It IS a lot to learn when you come as a fresh developer to the wikiverse and thankfully a lot is already written on how to get started. In order to avoid overwhelming the person which easily leads to unproductive stalling and stress it is helpful to sort and prioritize the information. 1. People stuff Expected behaviour at the office - shoes off, dishes, lunch-time, interrupting etc... [Expected behaviour for MediaWiki developers](https://www.mediawiki.org/wiki/Expected_behavior) Expected behaviour in context [partners e.g.](T154901), users, journalists, membership vs work etc 2. Tool stuff [Examples of experienced Phabricator users] (https://www.mediawiki.org/wiki/Phabricator/Project_management#Examples_from_teams_that_actively_use_Phabricator_workboards_for_project_management) The tools we use[see e.g.](T155170) Our technical quality standards[see e.g.](T154471)

=== Background === As a newcomer to the Wikimedia community and also my first experience as a professional developer in a team the onboarding has been a overwhelming and difficult experience. Given that it is a priority to acquire and retain 'non-wikimedians' and junior level developers I suggest that the [checklist for newly emplyed or trainees](https://se.wikimedia.org/wiki/Checklista_f%C3%B6r_nyanst%C3%A4llning_eller_ny_praktik) is complemented with a coherent recruitment process initially document based. [Several smaller](https://phabricator.wikimedia.org/project/view/2064/) initiatives are currently in progress. However, I see a lack of high (e.g. "culture, role-expectations") and middle-level (e.g. how and why we use the tools we use, suggestions on how to give feedback and support) introductions. A fairly simple way to start would be to base it on the article about [onboarding](https://en.wikipedia.org/wiki/Onboarding) and fill in the learnings in a simple, straigth-forward language with links to further reading. 1.A general introduction to Wikimedia Sverige (all newcomers) 2.A role-specific introduction for developers (can be a template for other roles) === Goals === These goals are taken from the Wikipedia article on [onboarding](https://en.wikipedia.org/wiki/Onboarding). These can be continually measured as simply as talking about them at e.g. monthly 30 minute team meetings to adress them promptly by collaboratively making them actionable. * higher job satisfaction * better job performance * greater organizational commitment * eduction in occupational stress * reduction in intent to quit === Structure === It IS a lot to learn when you come as a fresh developer to the wikiverse and thankfully a lot is already written on how to get started. In order to avoid overwhelming the person which easily leads to unproductive stalling and stress it is helpful to sort and prioritize the information. 1. People stuff Expected behaviour at the office - shoes off, dishes, lunch-time, interrupting etc... [Expected behaviour for MediaWiki developers](https://www.mediawiki.org/wiki/Expected_behavior) Expected behaviour in context [partners e.g.](T154901), users, journalists, membership vs work etc 2. Tool stuff [Examples of experienced Phabricator users] (https://www.mediawiki.org/wiki/Phabricator/Project_management#Examples_from_teams_that_actively_use_Phabricator_workboards_for_project_management) The tools we use[see e.g.](T155170) Our technical quality standards[see e.g.](T154471)