Talk pages project/Replying/ja

このページでは編集機能チームの取り組みとして、ウィキペディアの16件のトーク用名前空間を対象に、投稿者のワークフローであるトークページのコメントに返信する手順を扱います. 特定のコメントへ返信するための新しいワークフローであり、トークページでもっと楽に生産的に参加できるように、また投稿者のうち初学段階から先へ進んだジュニア投稿者 も編集経験を積んだシニア投稿者 も直感的に使えるように目指します.

このイニシアティブはじつは当チームのより大きな努力目標として、投稿者同士の効率的な協力実現というものに付随し、しばらく前から意識されてきました. その実現にはコミュニティに根付いた慣習に基づき、トークページを進化させようとしています. その方向性は、より経験の長い投稿者が貢献しつつ他の編集者との連携と作業調整のしやすさを目指し、同時に投稿歴の短い貢献者にもオンウィキの意思疎通をもっとわかりやすく直感的にこなせるようにすることにあります.

このプロジェクト開発を追跡し参加するには、ぜひ英語版のページをウォッチリストに追加するようお勧めしています. 先方のページは今後も以下の目的で使います.


 * 暫定的なデザインを共有し、フィードバックを収集
 * 試作版のテスト
 * この機能の開発状況の更新
 * このプロジェクに関して質問を受け付け発信する (たとえば計測、実装その他. )

これは何か
返信ツールとは、トークページの投稿の文末に現れるボタンです. クリックすると返信用の枠が開き、返信しようとする投稿に間違いなく手軽に書けるようにします. 正しくインデントして、通知を正確に送り、投稿者に代わって署名を記するなどのことができます.

あわせてヘルプ:協議用ツール#返信ならびにトークページプロジェクト/機能の概要（画面キャプチャが揃っています）

過去の情報
''この節ではプロジェクトの経緯について情報を掲載します. ''

2022年5月27日
5月19日に返信ツールに新しい経験が導入され、自分が返信を書きかけている段階で同じ投稿に対してコメントが新規投稿されたときにインジケーター（comment indicator）が表示されます.

編集機能チームでは、この改善点の設計を主導したBeta Kots さんを称えたいと思います.

2022年3月9日
規模の拡大

2022年3月7日月曜日には英語版ウィキペディアにおいて、デスクトップ版返信ツールを全ての人に（ログインしていても匿名でも）利用可能にしました. ''この展開の詳細は Phabricator に記録があります. ''

2022年2月18日
規模拡大

本日付で返信ツールをウィキメディアのウィキ群において、デスクトップ版返信ツールを全ての人に（ログインしていても匿名でも）利用可能にしました. ただし除外したところはウィキペディアの英語版（T296645）、フランス語版（T297533）、ロシア語版（T297410）です.

''トークページプロジェクトの機能を展開したウィキ群総覧の確認は、トークページプロジェクト/実装の現況をご参照ください. ''

新規コメントの通知

当チームでは利用者にリアルタイムで通知する機能の導入に取り組んでおり、返信ツールを使って返信を書きかけている間に、同じ投稿に誰か別の人が新規のコメントを投稿したとき発動します. ''試作版を使ってみるには、手順の説明とフィードバックの投稿先はこのリンクを開いてください. ''

2021年12月7日
規模拡大

本日12月7日付でデスクトップ版返信ツールを既定で誰でも — ログインしてもしなくても – mediawiki.org で使えるようになりました. ツールを試すならTalk:Talk pages project/Usability でどうぞ（トーク:トークページ/使い心地）.

2021年11月17日
規模拡大

本日11月17日付でデスクトップ版返信ツールは既定で全ての人が、ログインしていてもいなくても使えるようになりました – コモンズで.

2021年10月29日
規模拡大

10月23日月曜付で、デスクトップ番返信ツール を既定で誰でも—ログインしていてもいなくても–フランス語版ウィキペディアで使えるようになり on desktop to everyoneat the

ボランティアの皆さんとの会話が進行中で、議題は返信ツールをウィキペディアの英語版、フィンランド語版、ドイツ語版に既定で有効な機能として展開するべきかどうかでした.

2021年10月15日
新しい機能

Starting next week, you will gain the ability to preserve text formatting when pasting content into the 返信ツール's  mode.

2021年9月30日
規模拡大 Today, 30 September, the 返信ツール became available as an on-by-default feature at all Wikimedia Wikis except the projects listed here:


 * English Wikipedia
 * Finnish Wikipedia
 * French Wikipedia
 * Russian Wikipedia
 * German-language Wikipedias
 * Commons
 * Meta-Wiki
 * Mediawiki.org

In the coming weeks, we will start conversations with volunteers at the wikis listed above about the prospect of offering the 返信ツール as an on-by default feature there as well.

In the meantime, you can see how often people are using the 返信ツール to publish トークページのコメント投稿 by visiting https://dtcheck.toolforge.org/dtstats.html.

2021年8月31日
規模拡大

Today, 31 August, the 返信ツール became available as an on-by-default feature at 21 new Wikipedias:

Spanish (eswiki), Italian (itwiki), Japanese (jawiki), Persian (fawiki), Polish (plwiki), Hebrew (hewiki), Dutch (nlwiki), Hindi (hiwiki), Korean (kowiki), Vietnamese (viwiki), Thai (thwiki), Portuguese (ptwiki), Bengali (bnwiki), Egyptian (arzwiki), Swahili (swwiki), Chinese (zhwiki), Ukrainian (ukwiki), Indonesia (idwiki), Amharic (amwiki), Oromo (omwiki), Afrikaans (afwiki).

2021年8月6日
使用

本日時点で、返信ツールを使いトークページのコメントが25万回超、投稿されました.

 モードの新しいツールバー

Yesterday, 5 August, the  mode toolbar that was introduced as an opt-in setting in May, became available to all people who have the 返信ツール enabled by default. Note: you can still turn this toolbar off if you would like within 特別:個人設定.

返信ツールの既定の提供先をさらに拡大

In the coming weeks, we expect to be able to resume plans with offering the 返信ツール as a default-on feature for all users at all projects. Once the next set of wikis where the 返信ツール will be offered by default is finalized, we will post an update to this page.

For context, plans to offer the 返信ツール more broadly had been stalled while we worked with the Performance and Data Persistence Teams on infrastructure enhancements to ensure the 返信ツール continues to function as expected at this larger scale.

2021年5月13日
 モードの新しいツールバー

As of Tuesday, 11 May, you can enable a toolbar within the 返信ツール's   mode. This toolbar introduces easier ways for pinging other people and inserting links into the comments you are drafting.

To start, this new mode is being offered as an opt-in 個人設定. You can enable it by taking the following steps


 * 1) Ensure you have the 返信ツール enabled
 * 2) Visit
 * 3) Locate the   section
 * 4) "Check" the checkbox next to the setting that reads:
 * 5) Click
 * 6) ✅ You are done. You should now see the new toolbar whenever you open the 返信ツール's   mode

23 April 2021年月日
A/B 試験の結果 The results are in from the A/B試験 of the 返信ツール that ran from 11 February through 10 March on 22 Wikipedias. What follows are the conclusions we are drawing from these results and the steps we are taking next.

Conclusions


 * The 返信ツール decreases disruption:
 * There was a 79.5% decrease in the revert rate of comments ジュニア寄稿者 made with the 返信ツール compared to comments ジュニア寄稿者 made with page editing.
 * There was no significant increase in the number of ジュニア寄稿者 who were blocked after publishing a comment with the 返信ツール
 * The 返信ツール causes ジュニア寄稿者 to have more success publishing comments :
 * 72.9% of ジュニア寄稿者 who opened the 返信ツール were able to publish at least one comment during the A/B試験 compared to 27.6% of ジュニア寄稿者 who attempted a comment using page editing. This amounts to a 160% increase in the comment completion rate of ジュニア寄稿者 who used the 返信ツール during the test than those who used page editing.
 * ジュニア寄稿者 using the 返信ツール are 7.2 times more likely to publish a comment they start than ジュニア寄稿者 using page editing.

The full report can be found here: 返信ツール AB Test Report.

次の段階

Considering the A/B試験 has shown the 返信ツール causes a greater percentage of ジュニア寄稿者 to publish a comment without a significant increase in disruption, we will proceed with the plan we shared in T252057 to begin making the 返信ツール available as an 無効にする 個人設定at all Wikimedia projects. The sequence and timing of these 実装s will be finalized in T280388.

2021年3月23日
実装s

23 March, the Reply and the New Discussion Tools will be available as an opt-in beta feature at the German Wikipedia, so it will be at all Wikimedia Sister Projects from 23 March.

16 March 2021
A/B試験

On 10-March, the 返信ツール A/B試験 finished. We are now analyzing the data and expect to have results for you to review in the next four to six weeks.

実装s

Yesterday, 16-March, the Reply and the New Discussion Tools became available as an opt-in beta feature at the English and Russian Wikipedias and all Wikimedia Sister Projects (except German Wikipedia).

Note: you can review how and where all Talk pages project features are available here: Talk pages project.

12 February 2021
A/B試験

On 11 February, an A/B試験 of the 返信ツール started at 22 Wikipedias (full list here). During this test, 50% of all editors at the Wikipedias included in the test will have the 返信ツール automatically enabled, and 50% will not. People at these wikis will still be able to turn the tool on or off in Special:個人設定s. The results of this test will help the team decide whether people benefit enough from the tool for it to begin being made available by default, at all projects. We expect to have results to share in 2-3 months.

22 January 2021
Engagement metrics On 5 January 2021, the team completed an analysis of the first ~2.5 months of 返信ツール 使用 at the three wikis where it is available by default (Arabic, Czech and Hungarian). The findings are encouraging, tho not conclusive considering the limited sample size.

A notable finding from this analysis: the edit completion rate for ジュニア寄稿者 using the 返信ツール is 4x higher than the edit completion rate for people using full-page wikitext editing.

You can review these findings in more detail by reading the Metrics section below and/or reviewing the full report: 返信ツール workflow engagement metrics.

17 December 2020
Completion rates for comments made with the 返信ツール and full-page wikitext editing. の詳細 and limitations are in this report.

A/B試験

We have decided the key metric we will use to compare the A/B試験's  and   groups will be the rate at which people in either group publish the comments they initiate. More information in can be found in the Metrics section below and in Phabricator here: T252057.

It is important to note that we are not considering notable positive changes in the rates at which people start and continue participating on talk pages as well as the rates at which people are participating on talk pages in disruptive ways as prerequisites for the 返信ツール being made available to all people, at すべてのウィキ, as an 無効にする user 個人設定. We've come to think this for the following reasons:


 * Evidence to date suggests the 返信ツール is having the intended short-term impact: ジュニア寄稿者とシニア寄稿者 have an easier time participating in existing conversations.
 * We assume notable changes in the rates at which people start and continue participating on talk pages will likely get expressed over a longer period of time (read: they will not be detectable during the course of the upcoming A/B試験).

2 December 2020
Measuring engagement

The team is analyzing the 返信ツール 使用 data from the Arabic, Czech and Hungarian Wikipedias, where the tool has been available as an 無効にする feature since 24-September-2020.

This analysis will help us determine whether people, across experience levels, are having success using the 返信ツール and whether people are using the tool in ways that disrupts others.

We will post the results of this analysis in the Metrics section below (see: "Analysis 2: Engagement"). You can expect these results to be posted no later than January, 2021.

Evaluating impact

The team is preparing to run an A/B試験 to evaluate the impact the 返信ツール has had on how people use talk pages. This test will help the team decide whether we should move forward with plans to offer the tool to all people, at すべてのウィキ, as an 無効にする user 個人設定.

More の詳細 about the test can be found in the Metrics section below (see: "Analysis 3: Impact").

4 November 2020
実装 planning

Today, 4-November, the 返信ツール became available as an opt-in Beta Feature at an additional ~250 Wikipedias. This means the 返信ツール is now available as either a Beta Feature or 無効にする user 個人設定at all Wikipedias except for the following projects: English, Finnish, Gan, German, Inuktitut, Kazakh, Kurdish, Russian, Tajik, and Uzbek.

28 October 2020
実装 planning

In the coming weeks, we are planning to offer the 返信ツール as an opt-in Beta Feature at all remaining Wikipedias except for the following projects: English, Gan, German, Inuktitut, Kazakh, Kurdish, Russian, Tajik, and Uzbek.

An exact date has not yet been set. Once it has, we will announce it on this page and in Tech/News.

''*Note: the above was also mentioned in this week's Tech/News. See: Tech/News/2020/44.''

2020年10月16日
実装

去る10月14日水曜日に、「返信ツール」を選択式のベータ機能としてさらに30件のプロジェクトに実装しました（訳注：先行する実装先は当初の協力先ウィキペディア4件と途中参加を参照）. この実装の目的は、返信ツールはウィキペディアには独得の書き方(*)や表記方式の言語版があるため、編集者が実際に使えるのか、便利かどうか確認を目指します（*＝たとえば単語が長い、フォントの大きさを細かく使い分ける、地方語が多岐にわたる、使用頻度が低いフォントの採用など）.

''返信ツールを現状で採用するプロジェクトの総覧は右のリンク先をご参照：現在のイニシアティブ. ''

2020年9月25日
実装

去る9月24日木曜日、返信ツールは以下のウィキペディアですべての利用者 (ログインもIPも) が利用できるようになりました. アラビア語版、チェコ語版、ハンガリー語版. この実装により、ベータ機能では有効にしなかった、もしくは閲覧中のトークページのURL を にした人々にも初めて利用可能になりました.

この実装の基本的な目標とは、経験歴の長短にかかわらず、投稿者がこの機能を使えて価値があると認めるかどうか、理解することです. ''実装のプロセスに関して、当チームの取り組みの詳細は右のリンクをご参照ください. 実装のプロセス. ''

アラビア語、チェコ語、ハンガリー語版のウィキペディアで皆さんが返信ツールをどのように使って編集活動をしているか、最近の更新にフィルターをかけて絞り込むとわかります.


 * アラビア語版：https://w.wiki/dgV
 * チェコ語版：https://w.wiki/dT7
 * ハンガリー語版：https://w.wiki/dT6

2020年9月14日
編集要約欄の自由記述

2020年9月17日木曜日のうちに、制作ウィキで返信ツールを利用中の人は全員、このツールを使ってコメントを投稿する時の編集要約欄が自由記述式になります.

この機能を利用するには、テキスト入力枠の下部にある高度（ ）リンクを押します（画面キャプチャの「自由に書ける編集要約欄を実装」をご参照. ）

2020年8月28日
編集要約欄を自分流に書き換える

ボランティアの皆さんが共有したフィードバックに発想を得て[i][ii][iii][iv]、返信ツールはまもなくコメントを投稿する時の編集要約欄が自由記述式になります.

2020年8月7日
実装


 * 2020年8月6日、返信ツールをベータ機能として次のウィキペディアに実装する予定です. カタルーニャ語、中国語、チェコ語、ジョージア語、朝鮮語、セルビア語、ソラニ語、クルド語、スウェーデン語.

2020年7月31日
計測


 * 今週初め、チームでは提携ウィキ4件で返信ツールをどのように活用したか、分析しました（2020年3月31日から同6月30日の期間. ）
 * この解析で答えを出したかった疑問とは次の通り：使った人は価値があるツールだと思ったでしょうか？
 * まとめとしては返信ツールを使用した皆さん*は、価値があると認めています.

''*分析の詳細は以下の計測節をご参照ください. ''

2020年7月22日



 * 計測：2020年3月31日から同6月30日にわたり、提携ウィキの利用者が返信ツールをどのように使ったか、分析中です. 集計終了は2週間先を見込んでおり、このページ内の「計測」節に掲出の予定です.
 * 調整：使いやすさテスト（6月実施）の反響を受け、ツールの調整・拡充に取り組んでいます. 課題一覧、拡充をめぐる議論先のリンクはこちら.
 * 自由記述式の編集要約欄を支持： Topic:Vju7lfcav875rt8r.
 * ツールバーの調整：Topic:Vq9yz2a4xa2upy4p

2020年6月26日


バージョン 2.0 使いやすさテストでわかったこと


 * 返信ツールのバージョン 2.0 で導入した新機能を評価し、編集初学者（ジュニア Junior＝編集歴100件）と経験者（シニア Senior＝編集歴500件超）が直感的に使えるかどうか、使いやすさテストを2回実施、テスト被験者に一連のタスクを経験するようにお願いしました.
 * テスト結果の公開先：バージョン 2.0 試作版 (usertesting.com + mediawiki.org).

2020年6月17日
バージョン 2.0 の実装


 * 本日2020年6月17日、返信ツールのバージョン 2.0 を以下の場所に実装しました.
 * バージョン 2.0 はベータ機能として、提携先ウィキぺディアで実装（アラビア語版、オランダ語版、フランス語版、ハンガリー語版. ）

2020年6月5日
バージョン 1.0 実装


 * ツールのバージョン 1.0 はベータ機能としてmediawiki.org に実装しました. 有効にするには個人設定を開きベータ機能タブで "Discussion tools" の横の箱にレ点（☑️）があると確認してください.

2020年5月26日
バージョン 2.0 実装


 * 本日付で返信ツールのバージョン 2.0 は提携先ウィキすべての利用者に対して、特定の URL 経由で公開しました（アラビア語版、オランダ語版、フランス語版、ハンガリー語版. ）
 * 上記のウィキでこのツールのバージョン 2.0 を使ってみるには、返信ツールを導入済みのウィキでどれかページを開き、URL 欄の文字列末尾に、次の記述  を書き加えます.
 * この新しいバージョンが期待どおりの挙動をすると確認した段階で、提携先ウィキのベータ機能として利用を開始する予定です.

2020年5月1日
バージョン 1.0 実装


 * この 4 週間にわたり、新しい返信ツールのバージョン 1.0 をベータ機能として提携先ウィキで利用可能にしました.
 * 実装プロセスの第2ステップにしたがい、トークページ名前空間の外部 で議論が発生しても返信ツールを確実に利用できるよう、注視しました. この件に関する観察は次のとおりです.
 * そのページに  構文がある限り、どのページでも返信ツールを利用できます.
 * これはたとえばオランダ語ウィキペディアの井戸端空間 The Pub でも返信ツールが使用可能という意味です. これについて投稿されたコメントは、当該の最近の更新経由で参照できます. 
 * 来週中には、返信ツールは署名ボタンが表示されるページであれば、どの名前空間でも使えます.
 * これにより、"新しい節" タブがないページでも返信ツールを使えます. たとえばフランス語版ウィキペディアのビストロ（井戸端）Le Bistroなど、他のページからは参照読み込みされるページでは特に便利です. 
 * 他のページから参照読み込みされるコメントに対しても、返信ツールが使えます.
 * これにより、たとえばオランダ語ウィキペディアでページ削除を協議するページで、返信ツールが使えます（Wikipedia:Te_beoordelen pagina. ）

バージョン 2.0 実装

チームでは目下、バージョン 2.0 関連で2件の領域に集中しています.


 * 1) 他の人に @-言及もしくはピン通知する簡単な方法.
 * 2) テキスト入力のモードをソースモード  とビジュアルモード  に切り替えたり戻したりする方法.

''この場をお借りしてPbsouthwood、Pelagic、Samat、TheDJの皆さんにはバージョン 2.0 模型に関する丁寧な設計関連のフィードバックを寄せていただき、感謝します. ''

2020年4月3日
バージョン 2.0 設計

2020年3月31日
バージョン 1.0 実装


 * 本日付で返信ツールの新しいバージョン 1.0 をベータ機能として以下の提携先ウィキに実装しました. アラビア語版、オランダ語版、フランス語版、ハンガリー語版.
 * 新しいツールがみなさんの期待どおりの働きをするよう、これら4件のウィキでボランティアの皆さんと共同し、この先2、3週間は機能の使われ方を見守り、その後、対象を広げて実装、利用者個人設定で選択できるようにする計画です.
 * 実装の手順については次のリンク先をご参照ください. 実装のプロセス.

2020年3月26日
バージョン 1.0 実装


 * 返信機能のバージョン 1.0 は現在、テスト中です. QA のプロセスが重要な問題を引き起こさないと確認できた段階で、早ければ来週中に、新しい返信ツールをベータ機能としてアラビア語版、オランダ語版、フランス語版、ハンガリー語版ウィキペディアに実装します.

2020年3月13日
バージョン 1.0 実装


 * 新しい返信ワークフローのベータ版実装は延期され、期間はまだ予測できません. 対象はアラビア語版、オランダ語版、フランス語版、ハンガリー語版ウィキペディアです. 新たに日程が決まり次第、このページで告知します.

2020年3月12日
実施済み


 * バージョン 1.0 使い方の決まりのまとめ：チームは最近、使い方の規準のテストと展開を行いました. 貢献者が新しい返信ツールをうまく使えたかどうか、他の人に負の経験をさせるような使い方がされていないか評価する役に立ちます.

2020年2月28日
実施済み


 * バージョン 1.0 実装：2月18日木曜日、この機能のバージョン 1.0 を固有の製品テスト用 URL で次の4件のウィキペディアに向け実装しました. アラビア語版、フランス語版、オランダ語版、ハンガリー語版.
 * 皆さんとともに（ご協力感謝！）当チームは機能を何度もテストし、画面表示が正しい位置か、期待通りの挙動をするか確かめました. みなさんからのフィードバック共有の会話は、次のリンク先で閲覧したり投稿したりできます. MediaWiki、アラビア語版ウィキペディア、オランダ語版ウィキペディア、フランス語版ウィキペディア、ハンガリー語版ウィキぺディア.
 * 実装のプロセスと状況：チームが公表した返信ツールの実装先と手順の情報はこちら：Talk pages project/replying.

2020年2月17日
実施済み


 * この機能の次の繰り返し作業で取り入れる機能群の候補をまとめました. 機能候補の一覧はこちら：.

2020年1月24日
実施済み


 * 利用者インターフェースをバージョン 1.0 の機能向けに完成、リアルタイムのプリビューの見た目も含みます. バージョン 1.0 実装後のこれらきのうの見た目は、模型版をご用意しました. File:New replying mockup (v1.0).

2019年12月17日
実施済み


 * 利用者テスト：チームは利用者テスト2件を完了しました. どちらも対象はウィキペディアの活動に慣れているがトークページは未経験もしくは少ししか参加していない人たちです. 1回目のテストは、現状のトークページに参加しようとして、どんな壁にであうのか知るためです. 2回目のテストでは使いやすさの問題の解明をめざし、試作版のバージョン 1.0 を使って特定のコメントに返信する時、ワークフローがどう改善されるか調べました. これらのテストの詳細は次のリンクをご参照ください. 利用者テスト.

影響
''This section discusses the three quantitative analyses we have planned to evaluate the usefulness, usability and impact of the 返信ツール. These analyses are discussed in detail below.''

Analysis 1: Adoption
In this first analysis, we sought to learn whether people at the Arabic, Dutch, French and Hungarian Wikipedias, where the 返信ツール had been available as a Beta Feature since 31-March-2020, were finding the tool valuable.

To determine the extent to which people were "finding the tool valuable" we looked at how frequently people were using the tool (as measured by the number of distinct days they use it on) and how intensely people were using the tool (as measured by the total number of edits they make with the 返信ツール and the percentage of total talk page edits they used the 返信ツール to make).

Understanding the above helped us determine the tool was ready to be made available as an 無効にする feature at these wikis and made available as an opt-in Beta Feature at others.

Timing

This analysis was completed on 28-July-2020.

Findings

The data below included people who have used the 返信ツール as a Beta Feature at the Arabic, Dutch, French and Hungarian Wikipedias, between 31-March and 30-June-2020:


 * 328 people posted at least one comment using the 返信ツール
 * 69.5% of people posted ≥ 2 comments with the 返信ツール
 * 61.3% of people posted a comment using the 返信ツール on ≥ 2 distinct days*
 * 23.6% of people used the 返信ツール to make over half of their talk page edits**

Report

You can review the full analysis results in this Jupyter notebook: https://nbviewer.jupyter.org/github/wikimedia-research/Reply-tools-analysis-2021/blob/master/Adoption-Metrics/Replying-Tool-Adoption-Metrics.ipynb.

''*A "distinct day" was defined as a distinct calendar day. Therefore, some of these edits may have occurred 24 hours apart and some may have occurred only a few hours apart depending on what time of day the edit was made.''

**This data is a bit noisy in so far as there are some edits that cannot be made with the 返信ツール (e.g. starting a new section, editing existing content, etc.) and the software is not currently able to differentiate between comments and other talk page edits.

Analysis 2: Engagement
The next analysis we did was needed to help determine whether people, across experience levels, were having success using the 返信ツール and whether people were using the tool in ways that degrades the experiences of others.

This analysis's findings were used to decide whether the 返信ツール is functioning well enough for its impact on user behavior to be tested via a larger-scale (read: at wikis beyond our partner wikis) A/B試験.

Timing

This analysis was completed on 5-January-2021

Conclusions

The high rate at which people who used the 返信ツール to publish the comments they started writing, combined with the lack of clear evidence of disruption, led the team to think the 返信ツール was ready to be tested at a larger scale via an A/B試験. More の詳細 below.

Findings


 * The edit completion rate for ジュニア寄稿者 using the 返信ツール is 4x higher than the edit completion rate for people using full-page wikitext editing. Source
 * People who have made <1,000 cumulative edits, are between 32% and 510% more likely to publish edits with the 返信ツール (across modes) than they are with full page wikitext talk page editing. Source
 * <1% of comments ジュニア寄稿者 post with the 返信ツール are reverted within 48 hours, across wikis (this number is higher for シニア寄稿者 ). Source

Analysis 3: Impact
In this last analysis, we sought to learn two things:


 * 1) Does the 返信ツール cause ジュニア寄稿者 to be more successful publishing comments on talk pages?
 * 2) Does the 返信ツール cause more disruption to other volunteers?

To answer the questions above, we ran an A/B試験 of the 返信ツール from 11 February through 10 March on 22 Wikipedias. The results from this test can be found in the "Findings" section below.

Timing

This analysis was completed on 23-April-2021. The A/B試験 ran from 11-Febraury-2021 through 10-March-2021.

Conclusions

The clear evidence that shows the 返信ツール causes a greater percentage of ジュニア寄稿者 to publish a comment without a significant increase in disruption, signals to the team that it would benefit all Wikimedia Projects and volunteers to have the 返信ツール made available as an 無効にする 個人設定.

Findings

The data below included logged-in users who had not previously interacted with the 返信ツール (defined as users whose  個人設定was empty).


 * 72.9% of ジュニア寄稿者 who had access to the 返信ツール were able to publish at least one comment during the A/B試験 compared to 27.6% of ジュニア寄稿者 who did NOT have access to the 返信ツール.
 * ジュニア寄稿者 were 7.2 times more likely to publish a comment than ジュニア寄稿者 using page editing.
 * There was a 79.5% decrease in the revert rate of comments ジュニア寄稿者 made with the 返信ツール compared to comments ジュニア寄稿者 made with page editing.

Report

You can review the full analysis results here: https://wikimedia-research.github.io/Reply-tools-analysis-2021/ /.

背景
This year, the Editing Team is committed to improving how contributors communicate and collaborate on Wikipedia, using talk pages.

For talk pages to be valuable, contributors need to intuitively know how to participate in the conversations that happen on them.

The trouble is – as previous user testing, the Talk Page Consultation and the team's research uncovered – contributors, across experience levels, find replying to specific comments on Talk pages to be challenging.

Specifically, the team's research has found:


 * More experienced contributors find it difficult to locate the specific comment they are wanting to reply to when participating in long, multi-person conversations, within big blocks of wikitext.
 * Newer contributors report not being sure how to reply to a conversation, regardless of its length or complexity.

In exploring an affordance for replying to specific comments on talk pages, we are striving to make participating productively on talk pages easier and more intuitive. We think doing so will help newer contributors understand and use talk pages as places to communicate with others and help more シニア寄稿者 collaborate more efficiently.

課題
One part of building new features is codifying social conventions in software. In this context, "conventions" could mean deciding what character the software should use for automatically indenting or outdenting replies. "Conventions" could also mean deciding how the software should represent the first comment in a discussion in wikitext: ''Is there a linebreak between the reply and the original comment? Is the reply added to the line immediately following the original comment in the discussion? Is there another way this comment should be represented?''

It is unlikely all communities will answer these questions in the same way. This means the software needs to be built in a flexible enough way to accommodate these different 個人設定s. This is possible, although it adds complexity to the design and development processes.

設計
To increase the likelihood this enhancement is useful for contributors across experience levels, we have broken down the improvements we have planned into a series of releases. These different releases are outlined in more detail in the "Versions" section below.

Also below are the latest iteration for the designs we are planning to implement in バージョン1.0. If you have thoughts about anything included in this section, we would value you sharing them on the talk page: Talk:Talk pages project/replying.

❗️Please consider the features included below as drafts and expect them to evolve as we learn new things.

バージョン1.0
This バージョンwill introduce the basic reply functionality to validate the core workflow. This バージョンwill likely include the following features:


 * An affordance for replying to specific comments
 * A text box for composing replies using wikitext
 * A way for signatures to be appended to comments, automatically
 * A way for those comments to be indented or outdented, automatically

You can try a 試作版 of バージョン1.0 of the new replying workflow here: https://en.wikipedia.beta.wmflabs.org/w/index.php?title=Talk:Cats.

A mockup showing how バージョン1.0 will likely look once it is deployed can be seen in this 画面キャプチャ: File:New replying mockup (v1.0).png

バージョン2.0
Assuming バージョン1.0, and any smaller releases that follow, helps us to validate and refine the core replying functionality, バージョン2.0 will likely include enhancements to make it easier and intuitive for ジュニア寄稿者 to draft and post their replies. This バージョンwill likely include the addition of the following features:


 * Opt-in/out of watching the talk page as part of the replying workflow
 * Populating the reply text input with instructional text to make it clear who you are responding to.
 * Drafting and formatting replies using a rich text editor
 * Switching between "rich text" and "source" writing modes while preserving any content contributors have already written
 * Mentioning/notifying specific users in a conversation without needing to know about or interact with wikitext
 * Editing a specific comment
 * Note: It is not likely editing a specific comment will be included in the initial release of バージョン2.0. This is due to the technical complexity involved with implementing this functionality. You can learn more about this "technical complexity" and the initial implementation we have planned in Phabricator here: T245225.

技術情報
The replying feature is implemented via the DiscussionTools extension.

Troubleshooting information is available at Help:DiscussionTools/Why can't I reply to this comment?

実装
This section contains information about how and where the Replying feature is and will be deployed.

実装 status
To see what projects the 返信ツール is available, please visit: Talk pages project.

実装 decisions
Deploying バージョン1.0 as a Beta Feature to partner wikis

On Monday, 16-March-2020, the team is planning to deploy バージョン1.0 of the new workflow for replying to specific comments on talk pages as a Beta Feature on the following Wikipedias: Arabic, Dutch, French and Hungarian.

This decision is the outcome of the team being confident in the following:


 * Reply links are available in the places (read: talk pages, across namespaces) where people expect them to be.
 * The core parts of the Replying workflow (e.g. writing a comment, previewing a comment, formatting a comment, discarding a comment and publishing a comment) are working in the ways people expect.
 * The Replying workflow is not disrupting existing talk page content.

This confidence is based on the team and volunteers testing the new Replying workflow on >75 different talk pages in three talk namespaces on the 4 Wikipedias where the feature will be deployed.

This testing proved necessary for identifying and resolving issues related to the core parts of the replying workflow. Issues like:


 * The replying text box remaining after cancelling a reply: T245574.
 * Reply links appearing after list items that were not comments: T245692 (thank you, User:Bdijkstra).
 * Reply links not appearing after comments that contained signatures with an invisible Unicode character: T245784.
 * The 返信ツール not working in Safari: T245781.
 * The 返信ツール removing a page from your watchlist: T245579 (thank you, User:Tacsipacsi).
 * Broken and incomplete table syntax causing page corruption: T246481.

This testing was also important for identifying additional use cases the team is actively working to provide support for. Use cases like being able to reply to comments transcluded from a subpage. For more の詳細 on this work, see this Phabricator task: T245694.

実装 process
The 実装 of this feature will happen in four steps. These four steps are described below.

Before the team decides to move on to the next ステップin the 実装 process, they will do two things:


 * 1) Make contributors affected by the next planned 実装 aware of where to test the バージョンof the feature the team is planning to deploy, how the feature will be deployed and what informed the 実装 decision. Announcements containing this information will be posted as updates on this project page and publicly on すべてのウィキ affected by the planned 実装.
 * 2) Invite contributors to share their input about the next 実装 the team is planning. Contributors will be invited to share their input about the next 実装 on the talk page and on pages where the 実装 is announced.

第1ステップ: Beta cluster
実装 目標

The 目標 of このステップin the 実装 process is to answer these questions:


 * Do contributors find replying to comments using the feature intuitive?
 * Are any parts of the workflow broken (e.g. writing and formatting a reply, cancelling a reply, previewing a reply, publishing a reply)?

実装 の詳細

To make sure the feature behaves in ways contributors expect, new versions of the feature will be deployed to the Beta Cluster. This way, contributors will be able to safely experiment with new versions of the Replying feature without needing to worry about affecting existing content or contributors.

第2ステップ: Beta Feature
実装の目標

実装プロセスにおけるこのステップの目標とは、以下の質問に応じるためです.


 * Is the feature available where it should be?
 * Does the feature affect existing talk page content in unintended ways?
 * Are there any issues that prevent contributors from being able to respond to comments?

実装の詳細

To make sure the feature behaves in ways contributor expect on production wikis before exposing the feature to a large number of people, the feature will be deployed as a Beta Feature.

第3ステップ: 利用者の個人設定（無効にする）
実装の目的

実装プロセスにおけるこのステップの目的は、以下の質問に応じるためです.


 * Are people able to successfully post replies using the feature?
 * Is the feature having any unintended affects (e.g. encouraging disruptive トークページのコメント投稿 edits)?
 * Are people finding the feature valuable?

実装の詳細

幅広い人々がこの機能をうまく使えているか役に立つと感じているかどうか検証するため、この機能を利用者の個人設定で無効にする対象として実装します'''. '''

第4ステップ: A/B試験
実装の目標

実装プロセスにおけるこのステップの目標とは、この機能の設計意図であった影響を備えているかどうか、理解します. これを検討するため、この実装段階を使って答えを求めます.


 * 新しい返信用の機能は、ジュニア寄稿者ならびにシニア寄稿者にとってウィキペディアの特定のトークページにおいて、より直感的に手軽に使えるかどうか？

実装の詳細

To determine whether the feature had the impact it was intended to have, the team will run an A/B試験 on a to-be-determined set of wikis.

The team is finalizing the の詳細 of this A/B試験.

第5ステップ: すべてのウィキ
直近の実装4段階から得たエビデンス（証拠）から、返信機能はシニア寄稿者にとって、トークページで特定のコメントへの返信を手軽にかつ直感的にすると示唆されたことから、未展開のウィキペディア全てに実装の予定です. その方法と時期についてはチームに委任され、対象のウィキのボランティアの皆さんとともに、この機能の信頼性と期待どおりの動きをするかどうか確かめます.

使い心地テスト
''この節には、当チームが行う利用者テストの説明に使い、寄稿者の期待どおりにこの改訂版の経験が働くかどうか確かめます. ''

バージョン2.0 試作版
返信ツールのバージョン2.0で導入した新しい機能を評価し、ジュニア寄稿者とシニア寄稿者が直感的に使えるかどうか、使い心地テストを2回実施して、参加者にいくつかのタスクに取り組んでもらいました.


 * ジュニア寄稿者を募集したテスト1回（閲読：ウィキペディアを読み慣れた人で、ウィキペディアのトークページはこれまでにごくわずかしか使っていないか、もしくはまったく使ったことがない人対象）を usertesting.com 経由で実施.
 * One test recruited シニア寄稿者 (read: people who have experience using Wikipedia talk pages) via mediawiki.org.

Overall, these tests demonstrated the majority of ジュニア寄稿者とシニア寄稿者 were successful in using バージョン2.0 of the 返信ツール to write, format and publish comments on Wikipedia talk pages.

You can learn about the overall impressions people had, the key areas for improvement and 次の段階 below.

Overal impressions

シニア寄稿者 described the tool as well-balanced and expressed appreciation for the new automatic pinging feature. Here are a few noteworthy comments:


 * "I can insert a link to an [sic] user page inserting an @, after which a list of usernames pops up. That is nice."
 * "...this [pinging] is a game changer."
 * "Nice tool for both beginners and experienced users."
 * "Good tool, simple to use, it's good for what it's made for."

ジュニア寄稿者 who were able to find the 返信ツール successfully completed the tasks they were asked to and described the tool as being intuitive and straightforward to use.

With this said, when peoples' focus moved from the 返信ツール to the broader talk page, they became confused and uncertain about "where" they were and what they ought to do.* Here are a few comments we thought were noteworthy:


 * "It was pretty straightforward. streamlined process here i like the fact that it's very stripped down and doesn't feel data intense.so not overwhelming by any stretch of the imagination. the colors are pleasing to the eye... simple to navigate interface. Overall it works the way i'd expect it to."
 * "I'm a little confused about what User talk: Alice is..."
 * "Doesn't look like the sort of usual messaging interface you might see on a website."

* Note: ジュニア寄稿者 not recognizing talk pages as places to communicate with other editors is a finding that continues to surface[1] and something we plan to address later in the Talk pages project.

Task analysis

The table below shows whether participants in each test group were able to complete the following tasks with バージョン2.0 of the 返信ツール.*

You can review the broader themes these tests helped our team identify in the "Key themes" section below.

*Note these test findings were compiled on 10-June-2020.

Areas for improvement

These are the broader areas for improvement that surfaced through these usability tests. You can review how we plan to address these themes in the "次の段階" section below.


 * 1) The tool's two modes:   and
 * 2) * Some シニア寄稿者 were surprised to learn when viewing a diff that the  mode automatically signed the comment they posted.
 * 3) * Some ジュニア寄稿者 did not find the difference between the  and   modes to be clear.
 * 4) Pinging
 * 5) * Some シニア寄稿者 said they would not have known the pinging feature was available had they not been instructed to try it.
 * 6) * Some シニア寄稿者 wondered whether ジュニア寄稿者 would be confused by the normal link inspector that is presented when a ping within a drafted comment is selected.
 * 7) Commenting in long threads
 * 8) * シニア寄稿者 found it can be easy to "lose the tool" when trying to comment in a conversation and/or on a page with many comments.
 * 9) ** An example: when trying to respond to a comment that has many existing replies, it can be difficult to simultaneously look at the comment you are responding to and the comment you are drafting using the 返信ツール.
 * 10) * シニア寄稿者 found the tools within the  mode hard to "reach" when working on a large screen and when writing a lengthier comment.
 * 11) Edit summaries
 * 12) * Some シニア寄稿者 wondered whether supports for custom edit summaries would be added.

次の段階

To address the issues and opportunities these two usability tests surfaced, the team will be working on improvements to make the following come true;


 * Contributors, across experience levels, can easily mention/ping another person in the comment they are writing.
 * Example improvement: adding an icon to the  mode's toolbar that communicates there is a feature for pinging people.
 * Contributors, across experience levels, know how the tool's two input modes function and how they relate to one another.
 * Example improvement: revising what the  /  modes are called and how prominently they appear in the interface.
 * Contributors, across experience levels, find the tool well suited for commenting in talk page conversations, regardless of how many conversations (read: sections) and comments they contain.
 * Example improvement: revising where the text input area appears on the page and how it behaves when the page is scrolled.

You can track the progress we make on the areas above by watching this page and/or by reading this Phabricator workboard: phab:返信ツール バージョン2.0.

バージョン1.0 試作版
To see how the バージョン1.0 試作版 affected ジュニア寄稿者' experience replying in conversations on talk pages, the team ran a control test with 5 participants on usertesting.com. You can review the test findings below.

How were we testing?
This usability test was run on usertesting.com with 5 participants who were each screened to ensure they were technically advanced web users who have used Wikipedia before.

In order to compare the revised replying workflow to the existing workflow, each test participant was asked to complete the same tasks on a desktop computer, while narrating their experience:


 * 1) Navigate to an existing discussion happening on a test wiki talk page
 * 2) Draft and publish a response in that discussion
 * 3) Locate their published response on the talk page
 * 4) Navigate to the talk page's history page and locate the reply they had just posted
 * 5) Start drafting another reply, but discard it before publishing

What did we find?
Overall, the 試作版 seems to have improved Junior/newer contributors' experiences replying in an existing conversations. On average, it took participants using the 試作版 half the time to publish a reply compared to the time it took them in the previous test, using full page editing.

Task completion


 * ✅All participants were able to locate the specific discussion on the talk page they were being instructed to reply to
 * ✅All participants successfully composed and published a reply in an existing discussion
 * ✅All participants properly indented and signed their comments
 * Note: the tool does this for them automatically.
 * ✅All participants were able to locate their published response on the talk page
 * ✅All participants were able to find the talk page history page
 * ❌1 out of 5 participants was able to quickly locate the edit they had just made on the talk page's history page
 * ✅All participants were able to cancel their second reply before publishing it

Results

The 試作版 seems to have made it easier for Junior/newer contributors to reply to existing conversations on talk pages. Test participants used phrases like, "straight-forward," "no-problem whatsoever," and "really easy" to describe their experiences.

With this said, there are still parts of the replying workflow participants found difficult that could be improved:


 * Making it easier to visually distinguish between different replies in a discussion
 * Making it easier to identify who the author of a comment is and who they are responding to
 * Making the "Reply" call to action easier to discover
 * Revising the automatically generated edit summary to make it easier for contributors to identify their reply on the History page.

More の詳細 can be found in this ticket on Phabricator: T236921#5744471.

次の段階

The team will decide if and when to make the improvements mentioned above (e.g. making it easier to visually distinguish between different replies in a discussion) and do further testing with more experienced contributors (this has started here: バージョン1.0 試作版 test).

Existing reply experience
To identify the challenges ジュニア寄稿者 face when trying to participate in conversations on talk pages, the team ran a control test of the existing (full page) editing workflow.

How were we testing?
This usability test was run on usertesting.com with 5 participants who were each screened to ensure they were technically advanced web users who have used Wikipedia in some capacity before.

Each test participant was asked to do the following tasks on a desktop computer, while narrating their experience:


 * 1) Navigate to an existing discussion happening on a test wiki talk page
 * 2) Draft and publish a response in that discussion
 * 3) Locate their published response on the talk page
 * 4) Start drafting another reply, but discard it before publishing
 * 5) Navigate to the talk page's history page and locate the reply they had just posted

What did we find?
Below is a summary of our findings from this user test. More の詳細 can be found in this ticket on Phabricator: T239175#5723843.

Task completion


 * ✅All participants were able to locate the specific discussion on the talk page they were being instructed to reply to
 * ✅All participants successfully composed and published a reply in an existing discussion
 * ❌0 out of 5 participants properly indented and signed their comments
 * ❌1 out of 5 participants noticed they had not signed their comments
 * This one person remarked, "I probably should have put my user name, but i didn't".
 * 3 out of 5 participants were able to locate their published response on the talk page.
 * Note: it took several participants multiple minutes to do this
 * ✅4 out of 5 participants were able to find the talk page history page and locate the reply they had just posted
 * ✅4 out of 5 participants were able to cancel their second reply before publishing it

Results

This test highlighted an important tension many ジュニア寄稿者 seem to face: they finish the task they set out to complete without realizing they might have done so incorrectly. And if they do realize they have made a mistake, they are not equipped to fix it because the proper conventions are not intuitive enough for them to understand.

次の段階

The team will be doing two things in response to this test:


 * The team will be doing additional testing in different namespaces and languages (see: Partner wikis).
 * We will run a usability test of the 試作版 with contributors, across experience levels, to see how it affects their experiences replying to comments on talk pages.

いきさつ
トークページを介して寄稿者の経験を改善しようと、さまざまなプロジェクトがこれまで、また現在も取り組んでいます. 当プロジェクトはトークページの存在意義を支えます. 当プロジェクトが参考にしている他のプロジェクトをメインページにまとめ、下記にも載せました. もしこのプロジェクトにも注目した方が良いというお勧めがありましたら、ぜひこのページに加筆してください.


 * Convenient Discussions
 * フロー（Flow）満足度調査/報告
 * Moderated Testing, November 2014: talk pages and Flow（2014年11月小規模テスト：トークページとフロー）
 * Reply-link（返信リンク）
 * トークページの協議

用語集
トークページプロジェクト用語集（Talk pages project glossary）はトークページについて協議や文書化をするときに使う言葉の意味を取り違えないよう、皆さんとの意思疎通が効率良く進むよう、プロジェクトの進行に役立つように作りました.

関連項目
https://quarry.wmflabs.org/query/48614 – 編集者が返信ツールを使った回数を計数