コミュニティ技術

From Meta, a Wikimedia project coordination wiki
This page is a translated version of the page Community Tech and the translation is 64% complete.
Outdated translations are marked like this.

コミュニティ技術はウィキメディア財団のチームで、コミュニティ要望調査を運営しています。経験豊富な利用者に向けてキュレーション※1やモデレーション※2のツールを構築・改善し、ボット運用者の支援などを手がけています。このチームは、活発な貢献者からの依頼を受けて設立しました。当チームは編集者やボランティア開発者、ウィキメディアの他チームと密接に連携しています。(※:1=キュレーションとは情報収集と整理)。2=モデレーションとは内容チェックと評価付け。)

現在の選ばれたプロジェクト

To complete as many wishes as possible, Community Tech attends to the voted wishes with a prioritisation framework in mind. The framework guides how we come about the current selected projects.

プロジェクト プロジェクトの現状
Multiblocks
  開発中
IPA用に音声を作成
Handed over
Edit-Recovery Feature
  開発中
段落分割の差分のより良い取り扱い
  完了
Sharing QR codes
  開発中
記事作成後にウィキデータ項目へのリンクを自動提案
  開発中
クリックで再生する音声リンク
  完了
ライブプレビューを既定で有効にする
  完了
Extend "Who Wrote That?" tool to more wikis
  完了

チームの使命

運動の技術的なプラットフォームの必要性を洗い出し、必要なツールを従事する貢献者と共に構築し支援することです。

価値

  • 知識:何かについて知っているという事実。特定の主題、場所、状況その他に関する大まかな理解や親和性。
  • 親切であること:相手をいつくしみ、礼儀を守り、友好的で寛大、穏やかで異論を受け入れ、相手の立場を理解しようとする人、あるいは温かな心や気質を備えた人で、心構えの特徴は他者への思いやり – に加えて役に立とうとする志 – があることです。
  • コラボ (協働すること):他者と力を合わせて共通の目的を達成すること。

情報更新


January 4, 2024: Shaping the Future of the Community Wishlist Survey

Community Tech has made some preliminary decisions about the future of the Community Wishlist Survey.

In summary, we would like to develop a new, continuous intake system for community technical requests that improves prioritization, resourcing, and communication around wishes. Until the new system is established, the Community Tech team will prioritize work from the recently audited backlog of wishes rather than run the survey in February 2024. We are also looking to involve more volunteer developers in the wishlist process, beginning with the first-ever community Wishathon in March 2024.

Please read the announcement in detail either on the Diff blog or MetaWiki, and give your feedback.

October 26, 2023: Edit-Recovery is now available for testing in Beta

Hello community, we have some updates. Edit-Recovery wish (formerly known as Auto-save feature) is now available on Beta Cluster, and you are invited to test it.

Start editing any page on any Beta site, for example simple.wikipedia.beta.wmflabs.org, but don't publish your change. Wait 5 seconds and close the tab. Reopen the tab. Your edit should be recovered!

We are working to make the feature more visible with an element like a toast notification when restoring edit data, with the option of discarding the recovered data.

October 17, 2023: An Update on Multiblocks Wish

We have selected Multiblocks the #14 wish in the Community Wishlist Survey 2023. The objective of the wish was to introduce layering blocks (a.k.a multiblocks). We have created a project page to share information about our approach. Please visit and give feedback.

September 25, 2023: It's Time for Wishathon!

The quarterly online hackathon known as Wishathon, organized by Community Tech to help fulfil more wishes from The Community Wishlist Survey, starts from Monday, 25 September 2023, to Friday, 29 September 2023.

Wishathon engages other Wikimedia Foundation staff to help fulfill more wishes, and also foster cross-team and cross-departmental collaboration.

August 8, 2023: Wish Updates

Hello everyone, there have been a few changes since our last major update in April 2023.

Displaying categories on mobile

We hoped to implement Display the categories on the mobile site for everyone – after completing the Better Diffs wish. Unfortunately, our key partner, the Web team, will not tackle this wish now. The importance of categories to readers must be researched further to prioritize this wish instead of other pending wishes. But wish fulfilment is often on a rolling basis, so your feedback is welcome. In the meantime, we are working on the Auto-save feature, the #8 wish in the Community Wishlist Survey 2023, which has been renamed to the Edit-Recovery Feature to reflect more accurately what the feature is.

Who Wrote That

Secondly, we have responded to the Extend ‘Who Wrote That?’ tool to more wikis and currently, Who Wrote That? (WWT) is now available on 8 more Wikipedias – French, Italian, Hungarian, Japanese, Indonesian, Portuguese, Dutch, and Polish. This brings the total number of wikis with WWT up from five to 13.

June 22, 2023: Next-steps for Auto-save feature

The CommTech team is reviewing any investigations, discussions, patches that have happened around the Auto-save feature wish to determine what is next.

Please read about the project, and help answer some questions including how long we need to save the data for the auto-save functionality and what we should store in the database to be able to make autosave functionality work.

June 22, 2023: IPA transition to Language Team

Community Tech will hand over the IPA project to the Language Team this June. This decision is due to the Language team's expertise in localization, and their focus to create a suite of open language-supporting services such as the MinT machine translation service among other things.

April 27, 2023: Continuing on 2022 and starting the 2023 Wishlist

Dear Community Wishlist Survey Participants,

We would like to thank you for your participation in the 2023 Community Wishlist Survey. The survey is a crucial element in helping us prioritize the development of new features and improvements to make Wikimedia projects better for everyone.

Starting work on 2023

We are pleased to announce that the Community Tech team has identified the "Display the categories on the mobile site for everyone" wish as the priority for the team to work on in the coming months after we complete the work on Better Diffs for paragraph splits. This was also Wish #18 on the 2022 Wishlist. This decision was based on the wish's technical and design feasibility, as well as its potential impact in improving the user experience of the mobile site for all users.

We understand the importance of this feature for the community, and we are excited to work on it. We will keep you updated on the progress we make and will provide more information on the timeline for implementation as soon as possible. In addition, we’ve begun investigating how to Extend “Who Wrote That?” tool to more wikis, the seventh #7 most popular wish from 2023 and hope to make great progress on that work in the coming months. We anticipate launching Who Wrote That? tool to French Wikipedia in the coming days, with several other languages to follow in the coming weeks.

Dark Mode

We want to provide an update on the "Dark Mode" wish that was voted for in the survey. We are excited to inform you that the Web team has taken on this wish and plans to work diligently on its development. However, due to technical constraints and design feasibility, the Web team will be releasing the first version of the "Dark Mode" feature in Beta. We understand the importance of accessibility and inclusivity, and we are committed to ensuring that this feature meets the needs of all users. Additionally, there are many templates that need to be adjusted, and volunteers need to be alerted to modify before the "Dark Mode" feature can be fully released. The Web team will work on documenting these issues, and we appreciate your patience in this process. We encourage you to subscribe to the Web team's newsletter to follow the updates about this project.

I would also like to take a moment to thank the volunteers who took the time to collaborate with me in good faith during my tenure here and share that I am departing the Wikimedia Foundation and this team. Thank you to those of you who took the time to participate in proposals, problem solving with us, and to those of you who volunteered and tackled technical pieces of granting wishes – I will carry that inspiration with me for the rest of my career.

In my absence, a Product Trio will absorb my responsibilities so you can expect to reach out to the Engineering Manager KSiebert (WMF), Tech Lead DMaza (WMF), and Principal designer JSengupta-WMF as a united Product Trio after my departure in early May. You can expect to communicate with the team in the same way as before, the Talk pages for Projects, Updates, and the Team are the best way to reach the team. We collectively would also like to thank you once again for your participation in the Community Wishlist Survey. Your input helps us prioritize and improve Wikimedia projects, and we look forward to your continued engagement in the future.

Sincerely,

NRodriguez (WMF) and the rest of The Community Tech Team

March 13, 2023: Better diff handling of paragraph splits update

The team has continued work on this wish on both the engineering and design side and we wanted to share the updates with you.

Thank you to all of you who took the time to engage with us and provide feedback on the talk page. We read through all of the feedback and did an aggregate analysis on the points made. We then combined your feedback on those proposed designs, as well as unmoderated user research, and we've finalized the proposed designs to go into engineering for the improvements regarding the wish changes.

Please see the designs in this update which include:

  • Switching between diff modes via dropdown
  • Improving the accessibility of inline diffs with legends and tooltips for desktop
  • Improving the display of a change that introduced a new line or paragraph
  • Improving the display of a change that deleted an existing line or paragraph

In addition, a demo of the changes for the underlying comparison engine has been created.

Before you try out the demo to give us feedback, please note:

  • It's a work in progress, our QA engineers are currently using a list of comprehensive diffs to make sure the changes are consistent with the current version of the two-column diff experience or an improvement on the UI.
  • The demo page does NOT include all final UI changes but can give testers a good sense of how the completed two-column diff experience will end up looking.
  • To use the demo, paste the same text into the two boxes and modify the text in the right box. The diff under it will show what changed.

We'd love to hear your feedback on our talk page!

Next Steps

  • Accessibility of Design Colors: Our designer is working closely with our Design Systems team to determine the accessibility of the designs. We anticipate having to change the shade of them to a slight degree to make it more accessible but the colors will remain similar to the blue and yellow currently displayed on two-column and inline diffs.
  • Release plan: We are working out a release plan and a timeline of next steps and will be including this in our next project updates! Releasing changes to the underlying engine on the diff follows a different process than traditional releases in Mediawiki software so we will be sure to update you with steps and details next time.

We also want to include big thank you in this update to a non-Community Tech staff member, Tim Starling, who graciously stepped up to help us with the underlying changes in the C++ engine of wikidiff2. We are always happy to receive support fulfilling wishes from other members at the Foundation that have the expertise necessary to fulfill a wish even if they are not in the Community Tech team.

We're looking forward to hearing from all of you!

Open Questions from first update: We want to hear from you!

  • Are you interested in conducing user research on the new proposed interface to diff paragraph splits? If so, will you please post that you're interested in the Talk Page?
  • What other pain points manifest themselves when you view the diff?
  • How might we address the root pain points that address the confusion around paragraph splits?
  • How does the use of color indicate which content is added, removed, or stayed the same?

March 7, 2023: Community Wishlist Survey 2023 results published

The Community Wishlist Survey 2023 edition has been concluded. We have published the results of the survey and will provide an update on what is next in April 2023.

私たちがすること

私たちは主にコミュニティ要望調査に取り組んでいます。年に一度のプロジェクトであり、ウィキメディアのすべてのウィキから、編集者が最も変更の実現を望む課題を集めます。

私たちは、積極的な貢献者の役に立ち、比較的小さなタスクに取り組んでいます。特に、私たちは以下のような人々を支援します。

  • ウィキメディアのプロジェクトの管理や情報収集と整理にあたる人たち。
  • テンプレート、モジュール、ガジェット、利用者スクリプト、ボットなど、ウィキのための技術的機能にたずさわる人たち。

ときには、他のプロジェクトに取り組むこともあります。これは、要望調査では充分に支持されなかった小規模グループを支援するために行っています。

定期的に「ウィッシャソン」にも参加しています。

範囲

対象となるタスクには次のものが含まれます。

  • ガジェット、ボット、ウィザードを作成して、ユーザーがこれまでに実施した作業を支援すること
  • すでにあるガジェットやボットを修正して、より多くのプロジェクトで使えるようにすること
  • コミュニティが作成し使用頻度が高いコード(ガジェットとユーザースクリプト)を変換し MediaWiki ソフトウェアに組み込めるようにすること
  • ウィキメディアのプロジェクト群で役立つツールを作ること
  • 熟練の利用者向けのツールで昔からあって重要度が高いものの問題を解決すること、たとえば不正行為フィルタ AbuseFilter あるいは出典ボットなど
  • これらのツールをもっと有効に活用できるように、より優れた解説文書を書くこと

以下のタスクは範囲に含まれません

  • 他のWMFチームから見捨てられたり放棄されたプロジェクトの保守。
  • WMFチームの内部ニーズのサポート。
  • コモンズを構造化メタデータを使うように変換したり全く新しいウォッチリストのインターフェースを作成したりといったような大規模、長期的な開発プロジェクト。
  • すべてのコミュニティの技術的リクエストについての窓口になること。
  • Toolforgeを管理する、サイトのパフォーマンスを改善する、新しいウィキを作成する、IRCチャンネルを管理する、などといったようなシステム管理者的なタスク。

チームの現在の作業のより詳細な内訳については、Phabricatorでカンバンボードをご確認ください。

チーム


コラボレーション

コミュニティ技術チームはWikimedia Deutschlandのコミュニティ技術チーム - Technischer Communitybedarf (TCB) - と同様の任務を持ち、ドイツのウィキメディアコミュニティのために技術支援とソフトウェア開発を提供するチームです。私たちはチーム間で重複するプロジェクトで彼らと協力し、技術評価やコードレビューで互いに支援し合う予定です。また、優先度の高いコミュニティ依頼がその範囲内にある場合は、他のWMF開発チームと協力する予定です。このような場合、他のチームのリーダーと協力して、スケジュール、期待値、優先度、所有権について交渉します。私たちはまた、ウィキメディアのボランティア開発者とともに働き、支援することに多くの時間を費やします。

We uphold the civility standards set by the Terms of Use. We observe and maintain the code of conduct for Wikimedia technical spaces in our interactions, and ask that all contributors to Community Tech spaces do the same.

他のチームが私たちに連絡する方法は?

IRCの#wikimedia-commtech接続あるいはSlackの#talk-to-commtechチャンネルで、私たちの誰にでも個別に遠慮なくご連絡ください。

コミュニティ技術との関わり

私たちはPhabricatorで作業をトリアージおよび追跡しています。年次のコミュニティ技術要望調査以外では、以下のPhabricatorテンプレートを機能のリクエストや私たちが保守しているツールについてのバグを記録するために使用してください:

We review and triage new requests on a biweekly cadence.

ガイドライン

私たちは次のことを重視します。

  • 大きなインパクトがあるプロジェクトに取り組む
  • 多くの言語で書かれた大きなウィキから小さなウィキまで支援する
  • オープンでしっかりコミュニケーションをとる
  • 人々の要求や関心に対応する
  • 落ち着いて礼儀正しく、他者の善意を想定する

We're a small team, and there's a lot to do! We want to be as helpful and effective as we can, so we can't take everything on. Saying no to requests that we can't help with is an important part of our job, because it frees up time and energy for the requests that we can help with.

But "no" is hard to hear sometimes, so here are some guidelines about working and communicating with the Community Tech team.

  • Please be calm and civil, and assume good faith on our part. We care about the projects too.
  • We love our jobs and we work hard, but we don't work 24/7, and we can't guarantee an immediate response.
  • If a specific person or issue is taking an outsized percentage of our on-wiki time, that takes time and attention away from other people. We'll sometimes have to close a conversation, and say that we can't spend more time on a particular subject.
  • We can't take on projects that are currently on another product team's roadmap, or a project that directly conflicts with another team's work.
  • If there's an issue with another product team's work, we can direct you to the appropriate person to talk to.
  • We can't answer questions about staffing issues, or confidential matters.

私たちの価値と使命を決定するプロセス

In a collaborative session we all came together as a team to work towards being able to formulate our mission statement. To get there we first tried to think about which values we most care about individually to then see where they overlap, because we wanted to make sure that they are truly with us as a group of humans.

Three values stood out to us, which are: Knowledge, Kindness and Collaboration

Values statements itself are pretty broad and can be interpreted differently so we discussed them thoroughly to understand what behaviours they actually translate to, we’ll summarise here quickly what we mentioned:

なぜ知識を気にかけるのですか?

We do not want to be protective of our knowledge. If we discover something or implement something new we would like to write about it, let others know compassionately. If we make a decision, document it and explain the reasons. This is especially important because we want to be welcoming people to join the movement as new contributors or team mates.

Why do we care about Kindness?

We are conscious that we can never know what struggles others might be facing, always remember that we may not be aware of the whole picture. By being considerate and courteous to one another we ensure that we all feel included and encouraged to work more openly with one another. In addition to that being kind can mean being clear about if and how we can help or resolve a problem.

Why do we care about Collaboration?

Collaboration is the backbone to what we do and fosters innovation by combining ideas from different viewpoints. When giving explanations we want to be detailed and link to more info wherever possible, to make sure our explanations are meaningful to others. We welcome and actively seek ideas & feedback and questions from each other, WMF, and the community.

Mission statement

Having our values and beliefs in mind we further thought about what our mission statement might be. What are our responsibilities towards the movement, the community and towards each other and what connects us to the CommTech team. Are we just building some tools or is there any greater duty that motivates our work? This one summarised our opinions best:

We surface the movement's technical platform needs and build and support needed tools with engaged contributors.

As we want to contribute to the increase of the movement’s inclusiveness and growth, we surface the needs of the contributors, as long a they are of technical nature. Some of the tools we build ourselves, while we communicate others to the foundation to increase awareness of these needs across different teams.

戦略

One of the challenges our team faces is that we touch many different codebases and existing tools, that we don’t know well, therefore we currently have two main initiatives:

コラボのイニシアティブ

The need to collaborate and work closely with others at higher frequency than other teams is quite evident as we frequently build on top of other team’s work. If we touch existing codebases we need to make sure our tools are implemented in a way that matches their way to work and works towards the same goals.

The goal of this initiative is to improve knowledge sharing and collaboration across teams and within teams and find ways to check in with other devs before implementing work to make sure we do not build things from scratch that have previously been implemented. In addition to that we know we can build more innovative solutions by allowing for more collaboration. We thought of ways to encourage for more cross team collaboration for engineers i.e. by encouraging temporary exchange for engineers across teams, by reserving weekly internal collaborative programming sessions that engineers from other teams can visit and add to the agenda of these sessions.

Every quarter, since April 2022, we have an internal hackathon where we work on a series of proposals from this years wishlist and invite other teams to join us for a week. Often times specialists for certain fields are already existent in other teams and working on different projects for a week can increase the sense of belonging within the engineering team as a whole and have a positive impact on levels of collaboration in the future.

メンテナンスのイニシアティブ

当チームが管理するプロジェクトの一覧がどんどん拡大するにつれて、本来の優先事項に集中しにくくなってきました。

We do want to provide maintenance for our work, but want more structure for how we provide it. This year we reviewed our approach to maintenance and restructured our strategy towards maintenance. Here are the outcomes of this discussion here.

これらの変更の実施方法を内部で決めて、意思決定の過程を記録に残しました

説明文書作りのイニシアティブ

他のチームの作業を理解しようと、当チームでは目新しいコードベースにしばしば目を通しています。優れた解説文書とは、導入の詳細ばかりか他チームほかの制作物の目標や困難点をわかりやすく伝えるために不可欠です。本当に質の高い解説文書はどう書けば良いか、当チームは一丸となって先例になろうと志していて、(制作物の)初期導入より前に解説文書を書き、さらに作業進行と連動させて回を重ね、他のチームに更新を伝えていきたいものです。そのために、他のチームでそれぞれの制作物をどう解説しているのか注目して調べており、他のチームのやり方と共通の方法を見つけようとしています。解説文書はコードのすぐそばに置くのが良いと考えます。

コラボ作業を介してプログラムのセッションを進行する場合に使えるよう、ガイドに推奨事項をまとめておきました。

After researching different approaches for how to advance the way we document our work we have come across documentation-driven development, which seems to meet our needs in respect to how we value docs. We are experimenting with this approach with our current wish Better diff and already enjoyed it's benefits as we are more aligned on what we are working towards and can get feedback from users before implementation.

ユーザーガイド

出典用のテンプレート

  • Preferred Name:
  • How to talk to me:
  • (Optional) Pronouns:
  • (Optional) Things I like:
  • (Optional) Things I’m bad at:
  • (Optional) Annoying things I do:
  • (Optional) How to cheer me up when I am grumpy:
  • (Optional) Hot takes:
  • (Optional) Anything else you should know about me:

次の利用者ガイドをご参照ください。

User guides from former team members

その他の情報

サブページの一覧

Pages with the prefix 'Community Tech/ja' in the 'default' and 'Talk' namespaces:

Talk: