Talk pages consultation 2019/fr

La Consultation concernant les pages de discussion est une consultation globale planifiée de février à juin 2019, pour amener les wikimédiens et les personnes ayant la culture wiki à définir ensemble de meilleurs outils pour la communication sur wiki. La consultation va récupérer les avis du plus grand nombre possible de parties différentes de la communauté Wikimedia – sur de multiples projects, dans diverses langues, et dans des perspectives multiples – pour définir une direction produit concernant un ensemble de fonctionalités de communication sur lesquelles une équipe de production pourra travailler durant l'année fiscale qui arrive.

But de la consultation
Une page de discussion en texte wiki n'est pas faite de logiciel; c'est un ensemble de conventions culturelles déroutant pour les nouveaux arrivants et ennuyeux pour les rédacteurs expérimentés. En comptant les deux points pour indenter une réponse proprement, en utilisant des tildes pour signer votre nom, en devant regarder une page entière de discussion au lieu de la section à laquelle vous participez, sans la présence facile d'un lien de réponse - tout ceci est un casse-tête pour chacun.

En même temps, il y a beaucoup de choses que les pages de discussion en texte wiki, font très bien. La fenêtre vide d'édition a donné aux utilisateurs la liberté d'inventer des modèles et des techniques qui sont très souples et adaptables. Les conversations peuvent être réorganisées à la volée. Utiliser les diffs et les relectures signifie que vous pouvez toujours voir ce qui a été fait sur une page, quand, et par qui. The functionality that helped people collaborate on millions of encyclopedia articles for fifteen years shouldn't be dismissed as old-fashioned and useless.

Wikimedia Foundation product teams have worked on communication tools before: (started in 2010) and  (started in 2012). Both of these projects have been used successfully on many wikis, although they've also both been heavily criticized, and neither has gained wide acceptance on many of the largest wikis.

We want all contributors to be able to talk to each other on the wikis – to ask questions, to resolve differences, to organize projects and to make decisions. Communication is essential for the depth and quality of our content, and the health of our communities. We believe that this is essential for us to reach our goal of providing free access to the sum of all human knowledge.

Résultat désiré de cette consultation
One sentence, one paragraph, and one document that describe the overall direction of what we will build.

By the end of this consultation, we'll have an overall product direction for a set of communication features that a product team will be able to work on in the coming fiscal year. We'll have a rough consensus that our contributors agree with that overall approach, including both new contributors and longtime veterans, in multiple languages and across multiple projects.

A la fin de la consultation, nous serons en mesure de répondre à ces questions :


 * Sommes-nous en train de créer une fonctionalité, ou plusieurs ?
 * Est-ce que nous améliorons les anciens systèmes, ou nous construisons un nouvel outil ?
 * How will we balance ease of use with the advanced feature set that our most complex use cases require?
 * Quelles sont les questions ouvertes importantes que l'équipe du produit devrait investiguer et tester ?

Le résultat ne sera pas une spécification de produit complète et détaillée. Detailed plans will be developed and revised by the product team over time, informed by design, testing and continued close partnership with our users. But we'll have a solid place to start, and we'll be confident that the team is on the right track.

To encourage trust and good faith, the consultation and ultimate product development will be entirely public and transparent. Chaque étape sera documentée sur le wiki.

Solutions possibles
Pour que ce processus puisse fonctionner, nous avons besoin d'être ouverts à tout type de direction.

Non-goals
While we are interested in all good ideas, and might take some up in future, some things are out of scope for the current project:


 * Off-wiki discussion platform – Discussions need to be on the wikis, using Wikimedia accounts.
 * Temporary content – Discussions need to be stored on wiki, so they can be found and referenced later.
 * Tools for a niche audience – Discussions are designed for everyone, with equity in mind. We're not building a tool only for a subset of users (e.g., experience, language, preferred device.)
 * A social network per se – Discussions on Wikimedia should primarily be in service of improving content on the wiki.
 * Real-time discussions – Real-time discussions have value, but our current focus is on asynchronous discussions for the reasons mentioned in points above.

Participate
We are currently collecting information about how editors and other contributors communicate. Please read this page and tell us about your experience with communication on wiki:

You can also help build the list of the many different ways people talk to each other.

Final decisions
The project is led by Danny Horn (Director of Product Management), Benoît Evellin (Community Relations Specialist), Sherry Snyder (Community Relations Specialist) and TMeadows (Logistics)

Information from multiple communities and other stakeholders is extremely important. We deeply believe that we can't make a good decision without listening to you and understanding your needs. However, the final decision about what software to support will be made by the Wikimedia Foundation, after due consideration of all the available information, our educational purpose, and the movement's 2030 strategic direction.

Decision criteria
While the Wikimedia Foundation will make the final decisions in the 2019 talk page consultation, we are entering this process with honest curiosity, no preconceived solutions, and we are legitimately seeking to comprehend the feedback we receive. That said, there will be many difficult discussions about trade-offs we need to make. When it comes time to make a decision, all valid options will be weighed by the following criteria:


 * Which option(s) most aligns with our values?
 * Which option is most in alignment with Strategic Direction of Knowledge Equity?
 * Which option serves the most users and use cases as opposed to niche users?
 * Which option will result in more accessible user experience, for anyone on any device?
 * Which option will result in a more sustainable product that will be resilient to changing technologies, evolving use cases, and user expectations?
 * Which option poses the least amount of risk to achieve our project goals?