Talk pages consultation 2019/ja

トークページの協議は2019年2月から6月にかけて行うグローバルな協議で、ウィキメディアンとウィキで表現や解釈ができる人々と共に、ウィキのコミュニケーション改善に役立つツールの定義に取り組みます. 協議では、ウィキメディアのコミュニティの可能な限り広い範囲からインプットを募集したいと願っており – プロジェクト群の別や言語版、また視点もさまざまになると望ましい – 製品のコミュニケーション用機能関連の方向性を見つけ、製品チームが次の会計年度に取り組めるようにすることが狙いです.

協議の目的
トークページはウィキテキストで書かれるのであって、ソフトウェアが作成するものではありません. 因習が文化として通用する場であり、初心者を戸惑わせたり、経験豊富な編集者には厄介なこともあります. 適切に返信するためにコロンの個数を数えること、自身の署名をするにはティルダを使用すること、参加している節ではなく代わりにトーク ページ全体をウォッチリストに登録する必要があること、簡単に返信するためのリンクがないこと ― これらは誰にとっても面倒です.

同時に、トークページがウィキテキストでうまく進む面もたくさんあります. 何も書いてない編集ウィンドウを開いた人々は、非常に柔軟で適応性のあるテンプレートや技術を発明する自由を得てきました. 議論のやり取りは、その場、その場で変えていくことができます. Using diffs and revisions means that you can always see what's been done on a page, when, and by whom. The functionality that helped people collaborate on millions of encyclopedia articles for fifteen years shouldn't be dismissed as old-fashioned and useless.

Wikimedia Foundation product teams have worked on communication tools before: (started in 2010) and  (started in 2012). Both of these projects have been used successfully on many wikis, although they've also both been heavily criticized, and neither has gained wide acceptance on many of the largest wikis.

We want all contributors to be able to talk to each other on the wikis – to ask questions, to resolve differences, to organize projects and to make decisions. Communication is essential for the depth and quality of our content, and the health of our communities. We believe that this is essential for us to reach our goal of providing free access to the sum of all human knowledge.

この協議に期待されること
One sentence, one paragraph, and one document that describe the overall direction of what we will build.

By the end of this consultation, we'll have an overall product direction for a set of communication features that a product team will be able to work on in the coming fiscal year. We'll have a rough consensus that our contributors agree with that overall approach, including both new contributors and longtime veterans, in multiple languages and across multiple projects.

By the end of the consultation, we'll be able to answer these questions:


 * Are we building one feature, or more than one?
 * Are we improving previous systems, or building a new tool?
 * How will we balance ease of use with the advanced feature set that our most complex use cases require?
 * What are the important open questions that the product team should investigate and test?

The result will not be a complete, detailed product specification. Detailed plans will be developed and revised by the product team over time, informed by design, testing and continued close partnership with our users. But we'll have a solid place to start, and we'll be confident that the team is on the right track.

To encourage trust and good faith, the consultation and ultimate product development will be entirely public and transparent. Every step will be documented on wiki.

Possible solutions
For this process to work, we need to be open to all kinds of directions. It's possible that at the end of this consultation, we end up with any of the following:


 * Building features on top of wikitext talk pages, to make them easier and more efficient.
 * Using Visual Editor on talk pages, with extra features.
 * Building a new software feature that isn't StructuredDiscussions/Flow.
 * Building on top of the existing StructuredDiscussions/Flow feature.
 * Building more than one solution – it's possible that we define separate sets of requirements for user talk conversations, content/project page conversations, common workflows and RFCs, and that there are two (or more) different features.
 * Something completely different that we haven't considered yet.

Non-goals
While we are interested in all good ideas, and might take some up in future, some things are out of scope for the current project:


 * Off-wiki discussion platform – Discussions need to be on the wikis, using Wikimedia accounts.
 * Temporary content – Discussions need to be stored on wiki, so they can be found and referenced later.
 * Tools for a niche audience – Discussions are designed for everyone, with equity in mind. We're not building a tool only for a subset of users (e.g., experience, language, preferred device.)
 * A social network per se – Discussions on Wikimedia should primarily be in service of improving content on the wiki.
 * Real-time discussions – Real-time discussions have value, but our current focus is on asynchronous discussions for the reasons mentioned in points above.
 * The status quo – Leaving talk pages exactly as they are.

参加しよう
We are currently in the planning stage. Please read this page and provide feedback on the overall process for this talk page consultation:

We're also looking for volunteers to be the primary contact for participant groups throughout this process.

You can also help build the list of the many different ways people talk to each other.

最終的な決定
プロジェクトはTrevor Bolliger (製品マネージャー)、Benoît Evellin (コミュニティ関与専門家)、Sherry Snyder (コミュニティ関与専門家) ならびにDanny Horn (製品管理部長) が主導します.

複数のコミュニティや関係者発信の情報は非常に重視しています. 皆さんの言うことに耳を傾け、皆さんのニーズを理解してこそ、良い決断を下すことができると深く信じています. しかしながらどのソフトウェアをサポートするか、最終決定はウィキメディア財団にお任せいただき、そのために入手できる情報のすべて、ウィキメディア運動の教育目的や運動の2030年の戦略の方向性を十分に考慮します.

意思決定の基準
2019年のトークページ協議では最終判断はウィキメディア財団が下しますが、そもそも何か前提となる結論を想定してこのプロジェクトに取り組んだのではなく、きっかけは純粋な興味であって、集まったフィードバックを正当に理解したいという思いだけです. 以上が出揃ったところで、さまざまな点の折り合いをつけるという難しい判断がいくつも求められます. 結論を求める段階に達した段階で、有効な選択肢は全て下記の判定基準に照らして検討します.


 * 私たちの価値観に最もふさわしいものはどれ (とどれ) か？
 * 知の資産価値という戦略的方向性に最も見合うのは？
 * ニッチな利用者ではなく、最大公約数の利用者と使用事例に適しているのは？
 * どの選択肢がユーザー体験として最も手が届きやすく、より多くの使用機器や利用者の技術力の差に無関係に使えるか？
 * 持続可能性の高さの観点から、技術の変化や使用事例の発展、利用者の期待の進化に影響されにくい製品を作成するには、どの選択肢が最適か？
 * プロジェクトの目標達成において、最もリスクが少ないのはどの選択肢か？