Equipe Rédaction
- Pour l'état des projets actuels d'édition, voir Talk pages project/Updates et Vérification des modifications
|
Editing
Développer et améliorer les outils d'édition utilisés sur Wikimedia
|
Objectifs
L'équipe Rédaction fait partie du groupe Contributors. They work on tools for editing across MediaWiki, principally VisualEditor, DiscussionTools, and Vérification des modifications, but also maintaining other editors such as WikiEditor and CodeEditor, as well as specific tools like Cite, TemplateData and Citoid.
L'équipe travaille actuellement sur un ensemble d'améliorations pour VisualEditor appelé Vérification des modifications.
Strategically, the Editing team supports the Product department's "New Content" program, and, in turn, the Wikimedia Foundation's long-term goal of "Knowledge Equity". Those initiatives are about building strong communities that bring broad and deep content to people all over the world. One way to accomplish this is by improving the mobile editing experience to make it easier for someone to contribute productively to Wikimedia projects on a mobile device from a browser. Le but de ce travail est d'augmenter les modifications faites par mobile et d'améliorer la rétention des nouveaux contributeurs. Une façon pour nous de voir nos progrès est de suivre :
- the edit success rate per period for mobile visual edits
- the number of edits per period via mobile visual editing by newer editors (within their first 6 months after registration)
- the number of editors per period using mobile visual editing feature(s)
As we track our progress, we encourage a two-way dialogue with the community.
Les membres
-
Bárbara Martínez
Product Designer -
Caro Medelius
Software Engineer -
David Chan
Senior Software Engineer -
David Lynch
Senior Software Engineer -
Ed Sanders
Lead Engineer -
Marielle Volz
Software Engineer -
Megan Neisler
Data Analyst -
Peter Pelberg
Product Manager -
Quiddity
Movement Communications Specialist -
Sdkb
Movement Communications Specialist -
Valentino Cioffi
Software Engineer -
Valerie Puffet-Michel
Engineering Manager
Les projets
- On-wiki collaboration - From September 2019 to 2020-2022, the Editing team's priority is to help improve how contributors collaborate on-wiki by evolving existing talk pages to be more intuitive.
- Started in October 2022, Vérification des modifications is a set of improvements for the VisualEditor to help new volunteers understand and follow some of the policies and guidelines necessary to make constructive changes to Wikipedia projects.
Que signifie retenir les nouveaux contributeurs ?
For the purposes of this team, "new contributors" are people who have had a registered account on a wiki project for less than six months. Les "rétenir" signifie qu'ils font une première modification, it continuent à faire des modifications supplémentaires au fil du temps.
As we work, the Editing team will determine which types of retention are most important to track and to increase.
Historique
The WikiEditor extension provides an improved interface for editing wikitext. It is the wikitext editing interface that Wikipedia started using in 2010 for desktop users, so it is sometimes called the 2010 wikitext editor. The extension used to provide "Labs" features for "publication" and "preview" steps, but these are removed from REL1_31 onwards.
VisualEditor was built with the goal of removing avoidable technical impediments associated with Wikimedia's editing interface, as a necessary pre-condition for increasing the number of Wikimedia contributors. In addition to its word-processor-like visual editing mode, VisualEditor has a built-in wikitext mode, which is sometimes called the Éditeur de wikicode 2017. Research on VisualEditor usage can be found in the VisualEditor on mobile report (2018).
The CodeEditor extension extends the WikiEditor advanced editing toolbar with an embedded Ace editor widget, providing some handy features for user/site JS, CSS pages, and when Extension:Scribunto is also installed, for pages in Module. Currently, the extension is under development, and details of activation and functionality are subject to change.
The TemplateData extension introduces a tag and an API which together allow editors to specify how templates should be invoked.
This information is available as a nicely-formatted table for end-users, and as a JSON API, which enables other systems (e.g., VisualEditor) to build interfaces for working with templates and their parameters.
The Citoid node.js service generates citation data given a URL, DOI, ISBN, PMID, or PMCID. It has a companion extension, Citoid, which aims to provide use of the citoid service to VisualEditor. Bugs, issues, and suggestions for improvement can be added to the Citoid phabricator project.
Comment collaborer
Rester informé
- About the Suggestion Mode Project
- The best way to stay up to date about the project is by adding the Suggestion Mode page, Edit check page, and /Status/2026 page to your watchlist. The team will use these pages to share information about new feature development, deployment plans, and questions the team would value your input on.
- Spread the word
- Subscribe to the Editing newsletter to get occasional updates on your talk page.
- Sign up as a m:Technical Ambassador. Technical Ambassadors get information and share it with their home communities.
Partager votre expérience
- We want to hear what you think. Post your questions and comments to the correct page:
- Visual-based mobile editing — visual editing from the mobile site
- VisualEditor/Feedback — visual editing from the desktop site
- VisualEditor/Diffs — the diff tool
- Edit check – the tool that provides reactive feedback to what a new editor has just written, where engagement is required before publishing
- VisualEditor/Suggestion Mode – the tool that provides proactive feedback on what an editor is encountering in existing text, where engagement is optional
Envoyer vos demandes
We review and triage new requests on a biweekly cadence and do our best to address critical bugs as soon as possible.
- Report a bug or suggest a new feature
- Create a ticket in Phabricator and use the appropriate tag, e.g. #DiscussionTools or #VisualEditor or #Editcheck or #SuggestionMode. (see Phabricator/Aide and Comment signaler une anomalie du logiciel (bogue))
- Internally request work from the Editing Team
- If you work for WMF and want to request any work from the Editing team, please create a task in Phabricator (tag it with #Editing-team)
- If your team is blocked on a task, please ping us on Phabricator. Feel free to reach out on Slack too.
- Slack: #talk-to-editing (Slack channels are generally for WMF staff only with occasional exceptions for WMDE colleagues and contractors)
Comment écrire le code
Software developers and those aspiring to become ones can work on the source code of VisualEditor. The software overview, Comment devenir un hackeur de MediaWiki and the API documentation are helpful guides to get started. If you're active on Wikimedia projects, you might find it more convenient to develop gadgets or user scripts that extend VisualEditor.
VisualEditor developers on IRC via #mediawiki-visualeditor connecter.
Need a place to start? Check out:
Tableau principal de Phabricator
Sous-pages
- Editing team/Archive/Current priorities
- Editing team/Archive/Weekly triage meetings
- Editing team/Community Conversations
- Editing team/Community Conversations/Archives
- Editing team/Community Conversations/Archives/2022
- Editing team/Community Conversations/Archives/2023
- Editing team/Editing Team Archive
- Editing team/Editing Team Archive/Weekly triage meetings
- Editing team/Projects
- Editing team/Release timeline
- Editing team/Research
- Editing team/Research/References
- Editing team/team norms
