I am very happy to see that the New Developers Quarterly report is raising
some interest. Yes, there are important problems of sustainability in our
developer community that deserve attention.
On Wed, Oct 18, 2017 at 8:21 PM, Fæ <fae...@gmail.com> wrote:
> Suggestion, throw away the current plan and rather than using findings
> to create incremental improvement, try something completely
> different before all the wheels fall off. I look forward to seeing
> some serious radical initiatives.
The good news is that we have done this already. :)
The retention numbers for this quarter correspond to the newcomers who
landed between ~April-September 2016. We can expect there developers
attracted by our hackathons in Jerusalem and Esino Lario, and the
corresponding Google Summer of Code and Outreachy rounds. It was by that
time when the Technical Collaboration team at the Wikimedia Foundation (who
co-organizes these activities with mentors and affiliates) was digging
beyond our apparent success, deeper into the problem of developer
retention. Then we started to think that we should focus on new developers,
even if that meant less focus for our more experienced technical
Since then, we have radically changed our plans and we are experimenting in
various ways. You can find a comprehensive explanation in a blog post
published last week: How Technical Collaboration is bringing new developers
into the Wikimedia movement
Since we are discussing about new developers, let me also recommend you
another blog published just yesterday: Towards building an African
Wikimedia Developer Community
Wikimedia volunteers and affiliates, we welcome your ideas and involvement!
When our developer community grows, everybody benefits.
Engineering Community Manager @ Wikimedia Foundation
Wikimedia-l mailing list, guidelines at:
New messages to: Wikimediafirstname.lastname@example.org