Jump to content

Équipe rédaction/Conversations communautaires

From mediawiki.org
This page is a translated version of the page Editing team/Community Conversations and the translation is 97% complete.
Languages:

Bienvenue ! L'équipe rédaction utilise cette page pour documenter les résultats des discussions hébergées et faciliter la compréhension des besoins et des défis auxquels les contributeurs font face quand ils commencent à rédiger sur Wikipédia.

Prochaines discussions

A FAIRE :


Discussions passées

Aperçu

Les membres de l'équipe Edition ont rencontré des bénévoles de la Wikipédia anglaise dans un appel vocal sur Discord. Cette discussion était centrée sur Éditeur visuel/Mode suggestion . Plus précisément, le plan de diffusion de la fonctionnalité en tant qu'abonnement bêta dans les semaines à venir (T415320) et les mécanismes des commentaires (par exemple phab:T401739) que nous utiliserons pour affiner ensemble la fonctionnalités (et les suggestions apparaissant à l'intérieur).

Notes de discussion

  • En sachant que les bénévoles seront en mesure de configurer les Suggestions individuelles, les bénévoles expérimentés ont pensé offrir le mode Suggestion en tant que fonctionnalité bêta pour qu'il soit sûr et bienvenu
  • Nous devons envisager la manière d'éviter les cas où les suggestions pourraient s'envenimer et (ou) provoquer une guerre d'édition en continuant de faire apparaître les Suggestions même après qu'elles aient été annulées.
  • Les bénévoles ont exprimé leur enthousiasme pour le potentiel du mode suggestion pour intégrer des outils développés par la communauté dans l'expérience utilisateur principale.
  • Dans l'ensemble, les personnes présentes ont exprimé leur enthousiasme pour le mode Suggestion. Quelques idées pour des suggestions supplémentaires :
    • liens nus
    • courtes descriptions

Information
Date : at 17:00–18:00 UTC
Sujet : Vérification des modifications aide les nouveaux bénévoles à apporter des changements constructifs aux projets de Wikipédia en leur offrant des commentaires pratiques pendant leur édition. Cette conversation communautaire se concentrera sur une nouvelle fonctionnalité associée : le mode Suggestion. Ce mode suggère de manière proactive un ensemble croissant de changements actionnables (mais facultatifs) que les utilisateurs peuvent envisager prendre pour améliorer la qualité du contenu.
Lien de la vidéoconférence : https://wikimedia.zoom.us/j/87178187425?pwd=fj21l4y5Lffb2enjqIiwQbHNjinfN6.1
Langue principale de la réunion : anglais
Objectif

Découvrir les façons dont le mode Suggestion et le logiciel sous-jascent pourraient être développés à l'avenir.

S'inscrire (optionnel)

Mardi 10 juin 2025, environ 15 bénévoles actifs sur en.wiki ont rejoint le personnel de la WMF lors d'une réunion vocale sur Discord pour discuter du Contrôle du ton. Ce qui suit est une tentative initiale pour documenter les sujets évoqués par les bénévoles (et les opportunités qu'ils pourraient présenter) dans le forum Discord, tout comme ceux évoqués sur la discussion du wiki qui l'ont demandé et qui les suivent.

La discussion à propos de ce qui suit continue sur en.wiki.

Scenarii potentiels

Potential scenario Details Potential outcomes Opportunities [i]
Scenario A: Tone Check could nudge people away from more obvious peacock words (e.g. "iconic") and towards subtler forms of biased writing that are more difficult for the model and people to detect. People acting in bad faith might try to repeatedly change the wording of what they've written until they find a way to use language that's promotional, derogatory, or otherwise subjective while also being subtle/ambiguous enough for Tone Check NOT to activate.
  1. Tone Check inadvertently increases the amount of biased / non-encyclopedic content on Wikipedia.
  2. Tone Check could help people editing in bad faith obfuscate COI editing.
  1. Introduce a hidden tag that gets appended to edits Tone Check would become activated on before making the feature visible to people editing. This way, volunteers could see the edits and people Tone Check would activate it for, were it to be made available. Note: this functionality actively being worked on.
  2. Enable volunteers to prevent Tone Check from becoming activated on certain pages/categories where people tend to edit in bad faith more frequently. E.g. contentious topics, companies, public figures, conflicts, etc. Please add ideas/thoughts to T393820.
  3. Limit how many times Tone Check can be activated within a given edit (or for a given user within a certain time period) so people acting in bad faith can't use the feature to craft edits that could circumvent it.
  4. Enable volunteers to see the reason someone provided for declining to revise the tone of what they have written when Tone Check asks them to consider doing so. Please add ideas/thoughts to T395175.
  5. Enable volunteers to see specific words/phrases the model detects as being promotional, derogatory, or otherwise subjective, along with the model's confidence in such predictions, so that volunteers can consider integrating these patterns into existing moderation tools and workflows.
  6. ???
  7. ???
  8. ???

i. Note: These are the ideas mentioned so far. We need your help to identify additional ideas and, ultimately, evaluate the extent to which the "final" set of ideas will be effective at both supporting experienced and newcomers.

Scenario B: Moderator/patrollers/reviewers could become less effective at catching people attempting to add spam to Wikipedia because Tone Check could discourage them from inadvertently "outing" the mal-intent they are editing with. People editing with a conflict of interest (or other mal-intent) could leverage Tone Check to write in a promotional, derogatory, or otherwise subjective tone that is subtle enough for moderators/patrollers to potentially miss. This would, in effect, remove one of the key signals (tone) volunteers currently depend on to prioritize investigating potential COI and other forms of bad faith editing.
Scenario C: By building a model like the one underlying Tone Check, and making it available under an open source license, people could run the model locally and, in turn, use AI to generate non-neutral text that on-wiki tools might not detect.

Information
Date : at 18:00–19:00 UTC
Sujet : Edit check helps newer volunteers make constructive changes to Wikipedia projects by offering actionable feedback while they are editing. This community conversation will focus on a new check: Peacock Check. Peacock check will prompt people adding puffery or promotional terms to write in a neutral tone..
Lien de la vidéoconférence : https://wikimedia.zoom.us/j/86108522272
Langue principale de la réunion : English
Objectif

Discover ways the proposed Peacock Check user experience, and underlying machine learning model, could be improved.

S'inscrire (optionnel)
Mockup of Paste Check User Experience –

Information
Date : 17:30 UTC
Sujet : Edit check discussion with Open Foundation West Africa volunteers. This conversation is also open to any volunteer interested in the subject.
Lien de la vidéoconférence : https://wikimedia.zoom.us/j/85700503885
Langue principale de la réunion : English
Prise de notes
Objectif

Knowing more about Edit check: current checks and upcoming projects around copy/pasting, multi-checks and more!

S'inscrire (optionnel)

Notes

  • 13 bénévoles ont rejoint la Conversation communautaire du 29 octobre, dont une personne qui est toute nouvelle dans la rédaction de Wikipédia.
  • Of the ~5 volunteers who spoke during the meeting, all expressed enthusiasm for Edit Check and its potential to help newcomers feel encouraged and clear about how to contribute to Wikipedia.
  • In response to the first iteration of the Paste Check user experience we shared, volunteers noted:
    • The value of adding a confirmation step before the text people pasted into an article is deleted
    • It might be more intuitive to people who are new to frame the reason for Paste Check appearing as being about plagiarism.
    • How supported they felt by Edit Check expressing gratitude to people regardless of how they respond to the choice the Paste Check is presenting to them: Keep the content they pasted or Remove it
    • Knowing Paste Check exists helps them – as a reader – to feel more confident in what they read on Wikipedia.
  • One volunteer described Edit Check as "2-step verification for edits" which resonated with everyone present.

3 July 2024 Editing Team Community Meeting
Information
Date : 17:30 UTC
Sujet : Edit check : Expanding Edit Check
Lien de la vidéoconférence : Zoom
Langue principale de la réunion : English
Prise de notes
Objectif
  • CopyVio Check: learn what volunteers think of the proposed user experience for the initial version of the CopyVio Check
  • Real-time Checks : learn what volunteers think about a version of Edit Check that would show people feedback, in real-time.
S'inscrire (optionnel)

Notes

~10 English-speaking volunteers with varying levels of wiki-experience joined the 3 July 2024 conversation to discuss copyrights in the context of Edit Check.

The ideas that emerged during the meeting are documented below.

Reactions

  • Volunteers present were unanimously supportive of an Edit Check that would prompt newcomers to consider whether the content they are adding could create a copyright violation.
  • Several volunteers experienced with training newcomers were present, all of whom shared that the newcomers they've supported are NOT familiar with the concept of copyright
  • Voluneers were in agreement, that newcomers are willing to follow instructions that they perceive as being intended to help Wikipedia.
    • Reason being: the newcomers they are experienced supporting are often are arriving to contribute clear about Wikipedia's importance and motivated to help the project.
  • Volunteers emphasized that we need to continue assuming that the newcomers who will encounter Edit Check are likely to being seeing concepts/terms like copyright, reliability, neural point of view, etc. for the first time. As such, it's crucial that Edit Check use language and terminology that people are likely to recognize and understand.

Information
Date : 16:00 UTC (18:00 CEST)
Sujet : Edit check : nouveau prototype
Lien de la vidéoconférence : Zoom
Langue principale de la réunion : français
Objectif

Après le succès de Edit Check suggérant d'ajouter une référence, il est temps pour l'équipe Editing de confirmer le succès de ce système avec un nouveau prototype. Nous vous invitons à une conversation communautaire, où nous vous présenterons les résultats du check sur l'ajout de références, puis nous réfléchirons ensemble aux erreurs les plus communes des novices lors de l'édition, afin de réfléchir au prochain prototype.

S'inscrire (optionnel)

Notes

New Checks ideas:

  • Help in structuring an article
  • Helping to ensure text coherence and conciseness
  • Checking copy/paste
    • Some people take pieces of source material and paste them together, which is illegal (and demotivating, as these modifications are deleted). Checking that an action it's not a copy/paste could inform users of not doing it.
  • Suggest good sources when editing.
  • Edit Check currently identifies sources rejected by a community.
  • Find/Suggest previously used sources
    • Yes, if they are within the article. No, if they are elsewhere. And some sources that are suitable for an article are not necessarily suitable elsewhere.
  • Suggest modifications to articles from other editions of Wikipedia (translations; be careful to master this tool).

Some side notes:

  • "I was able to participate more easily when someone helped me."
  • You need to take your time reading the rules.
  • As long as you haven't gained any experience, you're not approved as an editor.
  • Beware of smaller wikis, which don't always have as many rules or templates to enable participation.

South Asia Open Community Call
12:30 UTC (18:00 UTC+05:30)
Presentation of Editing and Growth features.

Archives

Editing team Community Conversations: 2022, 2023, 2024

Retrieved from "https://www.mediawiki.org/w/index.php?title=Editing_team/Community_Conversations/fr&oldid=8397402"