Talk pages consultation 2019/hi

विकीमीडिया और विकी-माइंडेड लोगों को विकी संचार के लिए बेहतर उपकरणों को परिभाषित करने के लिए फरवरी से जून 2019 तक  टॉक पेज कंसल्टिंग  एक वैश्विक परामर्श है। परामर्श विकिमीडिया समुदाय के कई अलग-अलग हिस्सों से संभव के रूप में इनपुट करेगा - कई परियोजनाओं पर, कई भाषाओं में, और कई दृष्टिकोणों के साथ - संचार सुविधाओं के एक सेट के लिए एक उत्पाद दिशा के साथ आने के लिए जो एक उत्पाद टीम सक्षम होगी आगामी वित्तीय वर्ष में काम करना।

परामर्श का उद्देश्य
एक विकिटेक्स टॉक पेज सॉफ्टवेयर से बाहर नहीं बनाया गया है; यह सांस्कृतिक सम्मेलनों का एक संग्रह है जो नए लोगों को चकित कर रहा है और अनुभवी संपादकों के लिए कष्टप्रद है। एक उत्तर को ठीक से इंगित करने के लिए कॉलन की गिनती करना, अपने नाम पर हस्ताक्षर करने के लिए टिल्ड्स का उपयोग करना, जिस अनुभाग में आप भाग ले रहे हैं उसके बजाय एक संपूर्ण उत्तर पृष्ठ देखना, एक आसान उत्तर लिंक नहीं होना - ये सभी के लिए सिरदर्द हैं

At the same time, there are many things that wikitext talk pages do well. The empty edit window has given people the freedom to invent templates and techniques that are extremely flexible and adaptable. Conversations can be reorganized on the fly. Using diffs and revisions means that you can always see what's been done on a page, when, and by whom. 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.

Desired result from this 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.

By the end of the consultation, we'll be able to answer these questions:


 * Are we building one feature, or more than one?
 * Are we improving previous systems, or building a new tool?
 * How will we balance ease of use with the advanced feature set that our most complex use cases require?
 * What are the important open questions that the product team should investigate and test?

The result will not be a complete, detailed product specification. 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. Every step will be documented on wiki.

Possible solutions
For this process to work, we need to be open to all kinds of directions.

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
The phase 1 report has been posted!

We are currently collecting responses to the Phase 2 trade-off questions, coming shortly. The end date for feedback is June 15.

Communities are invited to:
 * 1) Translate key elements of the Phase 1 report.
 * 2) Sign up your group to participate in Phase 2.
 * 3) Create a local consultation to answer the Phase 2 questions.
 * 4) Ask your community for feedback.

It is also possible to comment on MediaWiki.org.

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?