Growth/ko



현재 계획들
각 계혹의 업데이트와 각 계획에 속하는 프로젝트에 대해서는 성장 팀 업데이트를 참조하거나 성장 팀 소식지를 구독하세요.


 * 첫 날 이해하기 (편집자여행)
 * 개인화된 첫 날
 * 환영 설문
 * 참여 이메일 (잠재적인 프로젝트)
 * 새 사용자 홈페이지
 * 새 사용자 작업
 * 구조화된 작업
 * 링크 추가
 * 이미지 추가
 *  교열 (잠재적인 프로젝트) 
 * 사용자 프로필 (잠재적인 프로젝트)
 * 멘토 대시보드
 * 질문방에 집중
 * 도움말 패널
 * 긍정적인 강화
 * 커뮤니티 구성
 * Newcomer Experience Projects

Most of these happen via the extension. A small part of the analytics work happened within the extension.



반영 테이블
아래의 틀은 어느 성장 팀 작업이 어느 위키에 적용되었는지 확인할 수 있는 빠른 도구입니다. 각 프로젝트 페이지에서 자세한 사항을 확인할 수 있습니다.

목적
성장 팀은 2018년 7월에 결성되었습니다. 성장 팀은 Audiences 부서의 "새 콘텐츠" 프로그램을 뒷받침하며, 따라서 위키미디어 재단의 지식 평등이라는 장기 목표를 뒷받침합니다. 위의 계획들은 강한 공동체를 구성하여 넓고 깊은 내용을 온 세계에 채우기 위한 일들입니다. 이러한 목표를 달성하는 방식 중 하나가 새 사용자를 위키미디어 프로젝트에 참여하도록 하는 일입니다. 불행히도, 위키미디어 프로젝트에 처음 참여하는 사용자 중 극소수의 사용자만이 몇일, 몇주 후에도 기여를 계속합니다. 이러한 것은 위키미디어에 기여하려면 이전에는 알기 힘들었던 많은 문화적 능력과 기술적인 능력을 필요로 하기 때문일 것입니다. 성장 팀의 목표는 이러한 문제를 기술적인 변화를 통해 위키백과를 필두로 한 중규모 위키미디어 프로젝트에서 해결하는 것입니다.

이러한 작업을 중규모 위키백과에서 시작하게 된 데는 여러 이유가 있습니다. 이 프로젝트들은 많은 성장 가능성이 있고, 소프트웨어의 도움을 통해 극복할 수 있는 문제점이 여럿 있습니다. 성장 팀의 대부분의 작업은 2017년에 이루어진 새 사용자 경험 연구 프로젝트를 통해 정립되었습니다. 이 연구에서, 위키미디어 재단은 한국어 위키백과와 체코어 위키백과의 사용자들과 함께 새 사용자들이 위키백과에 정착하는 데 있어 발생하는 장애물에 대해 연구하였습니다. 이러한 관계를 이어가기 위하여, 새 소프트웨어 변경 사항은 다른 중규모 위키백과에 배포되기 전에 일부 파일럿 위키백과(표 참고)에서 선행 배포됩니다. 팀의 소프트웨어 변경 사항은 보통 다음 분류 중 하나에 포함됩니다:


 * 문맥적 도움: 새 사용자가 겪는 기술적 문제나 개념적 문제를 해결할 수 있도록 돕기 위해 위키백과 편집 경험을 바꿔나갑니다.
 * 면대면 도움: 편집자를 서로 연결하는 포럼 및 프로그램 등을 통해 숙련된 사용자가 새 사용자가 성공적으로 정착할 수 있도록 돕습니다.
 * 작업 권고: 새로 온 사용자가 위키 기술을 배우는데 도움이 되는 편집을 제안합니다.

Past projects

 * For information about the Growth team that existed from 2013–2015, see Growth/Growth 2014.
 * For information about the predecessor to this team, see Collaboration.

Past projects by various iterations of the team and volunteer developers:
 * AfC improvements
 * Map Improvements 2018
 * Edit Review Improvements
 * Thanks
 * Structured Discussions, formerly Flow, discussion and collaboration software. Now in production as opt-in for talk pages, help pages and village pump-style discussion forums, on select wikis, but new requests are currently not applied.
 * Notifications (Echo), a redesign of the notifications system in Wikipedia. It was deployed to all Wikimedia wikis in November 2013.
 * New Page Triage, redesigning the New Page Patrol experience.
 * WikiLove, a tool designed to encourage community health and reduce "bite".
 * MoodBar, a tool designed to encourage feedback from new users, with Feedback Dashboard supporting review by experienced members.
 * Article Feedback Tool, a tool designed to encourage readers to provide feedback on articles.

Goals and metrics
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: 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.


 * In the future, this section will contain links to the Growth team's reports that track our metrics.

What does it mean to "retain new contributors"?
For the purposes of this team, “new contributors” are people who have registered accounts on a wiki project, even if they have not made an edit. To “retain” them means that they make edits and continue to make edits over time. Though we hope that contributors are retained for months and years, we know that they will first have to make it through their first days and weeks. Those first days and weeks are more likely to be the Growth team’s focus.

There are different periods of time over which we can measure retention. One definition might be “second month retention”, meaning a contributor is "retained" if they edit during their first month and also edit during their second month. But another definition might be “second week retention”, meaning a contributor is "retained" if they edit during their first week and also edit during their second week.

As we work, the Growth team will determine which types of retention are most important to track and to increase. See this page for a formal definition of retention.

Background
Wikimedia projects need to have a constant stream of new contributors in order to become hubs for broad and deep content. New contributors replace experienced contributors who stop editing. They also increase the diversity of the editing community. This stream of new editors allows projects to grow their content while increasing the diversity of their content. But in many Wikimedia projects, the number of active contributors is decreasing or staying the same, and the retention rate of new contributors is also decreasing or staying the same. This issue was studied in the 2013 paper The Rise and Decline of an Open Collaboration System: How Wikipedia's reaction to popularity is causing its decline. The authors showed that active contributors in English Wikipedia began to shrink in 2007, with the major cause being increasing technical and cultural barriers for contributors. Since then, similar patterns have been seen in other Wikimedia projects.


 * Data showing the state of active contributors and contributor retention in Wikimedia projects is forthcoming.

Beyond the high-level numbers themselves, additional research suggests that many new contributors do not reach their full potential because contributing is both technically and culturally complicated. For instance, it is common for excited new contributors to have their first edits reverted or their first pages deleted without an informative explanation. This causes them to be confused and disappointed, and ultimately not to continue editing.

Together, the numbers, research, and stories, mean that we can do better to engage and retain new contributors. In particular, the Wikimedia Foundation decided to focus on mid-size Wikipedias because those projects need to grow their content, have challenges with contributor retention, and there is potential for software to help.

To better understand what causes new contributors to stay and to leave, the Wikimedia Foundation completed the New Editor Experiences research project in 2017. The project identified the main challenges experienced by new contributors to Wikipedia, and a set of potential solutions. See the “Challenges” and “Solutions” sections below for the details.

The Growth team formed to take action on the challenges and solutions identified by the research project. We will continue our relationship with the Czech and Korean communities by testing changes in those wikis first. When we discover changes that increase contributor retention, we will engage other communities to consider deploying those changes in more wikis.

Although much valuable research has already been done to help our team understand new editors, important open questions remain. The team records and prioritizes our open questions on this page. We will be deliberate about using research, data, surveys, and feature instrumentation to answer them.

Principles
The following is a list of healthy characteristics that we think wikis should exhibit with respect to new contributors. They are guiding principles for our team, and we hope to help make them a reality in the wikis we work with.


 * Diverse contributors lead to wikis with broad and deep content.
 * Contributors who want to make useful improvements to a wiki should all be able to find a place in the community where they fit in.
 * Contributors should be able to learn to edit on their own.
 * Contributors of any skill level should be able to ask for and receive help from other community members.
 * Contributors should be able to learn and edit in a supportive and non-confrontational environment.

Challenges
There are challenges that stand in the way of the principles above. The main challenges were identified by the New Editor Experiences research project that was completed in 2017. With the help of Czech and Korean community members, researchers interviewed 64 contributors to Czech and Korean Wikipedias to learn about why they started editing, what they found easy or difficult, and if they've stopped editing, why they stopped. The project surfaced a set of technical, conceptual, and cultural challenges, summarized below. Our team’s work will help wikis overcome these challenges so that the principles can become reality.


 * Technical: new contributors struggle with specific skills needed to contribute.
 * Editing: though Visual Editor is helpful for new contributors, it is hard for them to learn the process of building, citing, and publishing.
 * Communication: new contributors have trouble finding and using Talk pages. This is because Talk pages do not use Visual Editor, and because they work differently than other internet discussion systems.
 * Finding help: many wikis have scattered and inconsistent help materials that are difficult for new contributors to find and use.
 * Conceptual: new contributors have trouble learning core wiki policies and best practices.  The following are the concepts that are most challenging.
 * Community: many new contributors do not realize there is an active community behind each wiki project.
 * Verifiability and citations: all content must be attributed to reliable sources.
 * Notability: all content must have garnered enough broad attention to deserve an article.
 * Encyclopedic style and neutral point of view: articles should present content without bias toward one side of an argument.
 * Copyright: content should not violate the licensing of its sources.
 * Cultural: the wiki environment can be discouraging to new contributors who are trying to find where they fit in.
 * Personas: new contributors have different objectives for why they are editing, but it is hard to figure out how to accomplish them.
 * Framing: the way that contributors communicate impacts whether new contributors stay. Negative feedback can discourage further contribution.

Solutions
The Growth team will attempt multiple solutions to the above challenges, and we will learn and expand as we go along. These are the findings from the New Editor Experiences project that will guide the solutions we attempt:


 * Intermediaries: many new contributors have succeeded because a partner or mentor helped them learn to edit.  These partners are frequently found in off-wiki places like schools, libraries, or meetups.
 * Iterative learning: new contributors have more success when they learn editing skills over time in safe environments.
 * Outside help: new contributors frequently search for help outside of Wikipedia, either in off-wiki communications, or through other internet resources.

Those trends lead to two main categories of solutions to the challenges described above. The work of our team will usually fit into one of these categories:


 * Human-to-human help: forums and programs that connect contributors to each other so that experienced contributors can help newer contributors succeed.  This can include help desk forums, mentorship opportunities, or even off-wiki connections.
 * In-context help: changes to the Wikipedia editing experience to surface helpful guidance around technical and conceptual challenges.  This is guidance surfaced at the time it is needed, in the place where it is needed -- as opposed to on a separate page that may be difficult to find.

This page contains the list of ideas that the team has considered and discussed with communities.

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  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

How to work with us
Please review this guide describing how to engage with the Growth team.