Growth/Team/ja
The Growth team
-
Benoît Evellin
運動コミュニケーション専門職 -
Dennis Mburugu
技術管理者 -
Elena Tonkovidova
QA 技術者 -
Morten Warncke-Wang
データ科学者 -
Julieta Fernández
UXデザイナー -
Sergio Gimeno
シニアソフトウェアエンジニア -
Kirsten Stoller
上席製品管理者 -
Cynthia Simiyu
ソフトウェア技術者 -
Martin Urbanec
シニアソフトウェアエンジニア -
Michael Große
シニアソフトウェアエンジニア
History and Objective
A Growth team existed from 2013–2015, see Growth/Growth 2014 .
The current Growth team was formed from the Collaboration team.
2018-2019
Growth チームは2018年7月に業務を開始しました。
観衆部門の「New Content」プログラムにサポートを提供し、代わりにウィキメディア財団の長期目標である「公平な知識」に参加します。 Those initiatives are about building strong communities that bring broad and deep content to people all over the world. それを実現するには、ウィキメディアのプロジェクト群へ参加する新規利用者が糸口となります。 Unfortunately, very few people who start contributing continue to contribute in the days and weeks after they begin. 原因は貢献を続けるには文化的・技術的な技量を求められ、それらはなかなか学びにくいからです。 The Growth Team's objective is to address this problem through software changes that help retain new contributors in mid-size Wikimedia projects, starting with Wikipedias.
As stated in the Audiences department’s 2018-2019 annual plan, the Growth team’s goal is:
Increase retention of new contributors in the target wikis, Czech and Korean Wikipedias.
To determine whether we’re meeting our goal, we have specified metrics and set targets for them:
評価指標 | ターゲット |
---|---|
New contributor retention in target wikis | 10% increase |
Mentor retention in target wikis | Sustainable rate |
The first metric, “new contributor retention”, is the main metric we use to measure our impact. The second metric, “mentor retention”, will be relevant for interventions that involve mentorship. As we focus our work, we will consider whether that second metric is the right fit for the team at this time.
We need to create a more specific definition of “new contributor retention” in order for it to be useful. See the section below on “What does it mean to ‘retain new contributors’?” for our team’s thinking.
We began our work with mid-size Wikipedias for a few reasons. それらのプロジェクト群には成長の可能性が大きいこと、それでいて問題点もいくつかあり、解決にはソフトウェアを利用できそうだからです。 このチームが業務に取り組むモチベーションは、2017年に実行した新人編集者の経験 新人編集者の経験 調査プロジェクトに根差しています。 その調査では新規貢献者を妨げる問題点の理解を目指して、ウィキメディア財団がチェコ語版と朝鮮語版ウィキペディアのコミュニティと協働しました。 Continuing that relationship, we will be testing software changes on a few pilot Wikipedias (see the table ) before deploying to other mid-sized Wikipedias.
Our software changes will usually fall into one of these categories:
- In-context help - 技術や概念の課題に関する有用なガイダンスを浮上させ、ウィキペディアの編集経験を変える。
- Human-to-human help - 編集者同士を結び付けるフォーラムやプログラム。経験豊富な寄稿者から寄稿が成功するよう、初学者を助けることを目指す。
- Task recommendations - 新規参加者がウィキの腕前を上げるように、編集の課題を出題。
How we work
The Growth Team follows several principles as we work toward our objective.
- We keep in close communication with the communities our team affects, so that our work remains grounded in reality.
- We start with small interventions, learn quickly, and adjust our approach.
- We make decisions based on evidence from experiments, data, and user research.
- We take the time to equip ourselves with the tools we need to be flexible and work quickly.
- The software we build gives flexibility to the communities who use it, so they can modify and improve it on their own.
- When we know something doesn’t work, we remove it cleanly and learn for the future.
- We follow the Wikimedia Product Guidance for working with communities.
- Please report bugs at Phabricator, using the
Growth
tag - How we triage incoming tasks and other chores, is detailed at Growth/Team/Chore list .
- Our daily chores are documented at Growth/Team/Chores
- Please report bugs at Phabricator, using the
How we do things
This page contains information (and subpages, mostly) on how the Growth team does things.
Growth/Team/Task Completion Definition
ページ
- Growth/Team
- Growth/Team/Chore list
- Growth/Team/Chores
- Growth/Team/Norms
- Growth/Team/QA
- Growth/Team/Skill Matrix
- Growth/Team/Skill Matrix (Team Consolidated)
- Growth/Team/Task Completion Definition
- Growth/Team/ar
- Growth/Team/dtp
- Growth/Team/en
- Growth/Team/es
- Growth/Team/fr
- Growth/Team/ja
- Growth/Team/pt-br