http://korma.wmflabs.org/browser/code_contrib_new_gone.html lists
* People with first submission in last three months
* Contributors that have not contributed in the last 6 months
I irregularly check the first list and ping on patches without review, but
* we do not use the available information in a process incorporated to our routines.
* except for anecdotes, we do not know or understand why people move on.
We should think about
* plan a process that allows more regular checking to get the attention of reviewers for patches by newcomers
* potentially congratulate the contributor after merging the first patch and provide motivation and hints to try and find a second task to work on,
* ask ourselves if we really want to wait six months for users leaving to get aware of them or whether to shorten that time frame,
* ask users who leave / have left to give us quick feedback and help improving, potentially via #surveys.
Context: https://meta.wikimedia.org/wiki/Technical_Collaboration/Strategy mentions "offering a learning environment and growth path to technical contributors".
-----
**See Also:**
{T73357}
{T64324}