製品技術諮問評議会/2025年8月付PTACフィードバック勧告草案
製品技術諮問評議会（PTAC＝Product and Technology Advisory Council）は1年限りの試験運用グループで、コミュニティ参加者とウィキメディア財団の職員で構成されます。役務はウィキメディア財団に対して技術の方向性に関する支援と助言を提供し、ウィキメディア運動に対して長期の製品・技術面の優先順序を進言します。
取り組み2件をめぐっては、最近、コミュニティから反応が寄せられ、それを受けて、英語版の〈井戸端〉（Village pump）では記事の概要を AI 生成する実験が行われ、そこから派生する形で同じ井戸端でWMFが持ち込もうとする AI 機能についてコメントを募集し、語調チェックにも懸念が示されました。製品技術諮問評議会はこれらを受けて作業グループ2件を設けるとブレインストームに取り組み、主題はそれぞれ財団として実験や製品開発をめぐる意思疎通と実施法をどうすれば改善できるか、また製品開発の情報更新をめぐるコミュニティとの関与の方法をどうするかとしました。
On July 23, the working groups within the PTAC proposed the following recommendations for experiments that the Wikimedia Foundation can conduct to see if the experiments increase transparency, trust, and lead to more constructive engagement between the Wikimedia Foundation and Wikimedia communities.
- On-wiki discussion: Bring the community to this conversation and work with them to determine key channels for these conversations to occur. Provide the same resources with specific examples of how this didn’t go well, and solicit ideas for how it could go better.
- Community members champion and drive community discussion: PTAC members (or other community members) participate in key product communications topics to help provide context regarding the experiments and guide feedback in conversations with communities.
- Central overview: Building a central overview of all ongoing and upcoming experiments, where community members can track the development of features and keep track of currently ongoing development work.
- Defining labeled phases for experiments: Explicitly labelling what stage of development a particular experiment is in, for example, exploration, testing, validation, iterative improvement, beta, graduation, termination/concluded. This will allow community members to understand what stage a particular experiment is in and what kinds of feedback are going to be most valuable.
- Better prepared feedback sections: Often, when Wikimedia Foundation teams ask for feedback, there is a gap between what the team expects in terms of feedback and the kind of feedback the community provides. Having a better prepared feedback section would probably lead to better feedback being provided by the community, specifically on the areas the team expects feedback on.
The Product and Technology Advisory Council invites feedback from community members on the experiments (and proposals) above until August 22, following which, (provided there are no objections) we will forward these recommendations to the Wikimedia Foundation’s Product and Technology department, who will subsequently look into ways of implementing and incorporating these recommended experiments.
Following the feedback we received from the community, as well as PTAC working group conversations, we have iterated on the recommendation further in order to finalize it. This recommendation will be presented to the Foundation’s Product and Technology teams so that they can conduct experiments and communicate product updates in a way that increases transparency, trust, and leads to constructive engagements.
- Explain prioritization decisions: Explain the rationale for why certain pieces of work are being prioritized and not prioritized. Explain clearly why the Foundation says "no" to some work.
- Definition clarity for success vs failure: Be clear about definitions of success and failure, and engage the community on these criteria for experiments.
- タイミングが肝要：コミュニティ参加者の皆さんとの対話は早い時期に着手し、実験もしくは機能設計の早い段階でどのようなフィードバックが建設的で有効か明白に示すこと。オフウィキの協働空間でコミュニティとやり取りするなら、たとえば Discord（ディスコード）、Telegram（テレグラム）あるいは広報を手厚くしたコミュニティ打ち合わせなど、多くの場合、このような初期のフィードバックに適した空間があります。
- Communicate as close as possible to the community: PTAC would like the Foundation to engage and communicate with the community as granularly as possible, ideally on a per-wiki basis. However, this experiment necessarily adds the overhead of translating each announcement and conversation into multiple languages. Both the PTAC and the Foundation recognize that many plans and communications are often not broadly translated. The Foundation would appreciate help from the community in sharing the workload of translations.
- On-wiki discussion: Bring the community to this conversation and work with them to determine key channels for these conversations to occur. Provide the same resources with specific examples of how this didn’t go well, and solicit ideas for how it could go better.
- Community members champion and drive community discussion: PTAC members (or other community members) participate in key product communications topics to help provide context regarding the experiments and guide feedback in conversations with communities.
- Central overview: Building a central overview of all ongoing and upcoming experiments, where community members can track the development of features and keep track of currently ongoing development work.
- Defining labeled phases for experiments: Explicitly labelling what stage of development a particular experiment is in, for example, exploration, testing, validation, iterative improvement, beta, graduation, termination/concluded. This will allow community members to understand what stage a particular experiment is in and what kinds of feedback are going to be most valuable.
- Better prepared feedback sections: Often, when Wikimedia Foundation teams ask for feedback, there is a gap between what the team expects in terms of feedback and the kind of feedback the community provides. Having a better prepared feedback section would probably lead to better feedback being provided by the community, specifically on the areas the team expects feedback on.
これら勧告事項（recommendations）はウィキメディア財団製品技術部門（Product and Technology department）と共有した後、推奨された実験の組み込み方とどう実施するか検討の予定です。