Talk pages consultation 2019/mr

ही चर्चापान संबंधित सल्लामसलत जागतिक पातळीवर फेब्रुअरी ते जुन २०१९ दरम्यान आयोजित केली गेलेली आहे, याद्वारे विकि-विचारांचे लोक आणि विकिमिडीयन्स एकत्र येऊन विकिवरील संवादासाठी सुयोग्य अवजारे निर्माण केली जाऊ शकतील. या सल्लामसलतीमधून विकिमिडीयाच्या समुदायाकडून वेगवेगळ्या भागातून सुचना मागवल्या जाणार आहेत - वेगवेगळ्या प्रकल्पातून, वेगवेगळ्या भाषांमधून, आणि वेगवेगळ्या दृष्टीकोनातून - ज्यामुळे आमचे उत्पादक गट योग्य असे अवजार आणि त्याच्या सोयीसुविधा ठरवू शकतील आणि त्यावर ते येत्या वर्षात काम करू शकतील.

या सल्लामसलतीचे कारण
विकिमजकूराच्य सहाय्याने तयार केलेली चर्चापाने कोणत्याच सोफ्टवेयरने तयार केली जात नाहीत; ती वेगवेगळ्या लोकांनी आपाअपल्या सांस्कृतीक भांडवलाद्वारे/सोयीने तयार केलेली असतात ती नव्या संपादकांना अडचणीची आणि अनूभवी संपादकांना त्रासाची वाटत आलेली आहेत. अनुस्वार चिन्हांची संख्या ठरवून उत्तराची पातळी देणे, टिल्डा देऊन सह्या करणे, आपण चर्चा करत असलेल्या विभागाकडेच नव्हे तर पूर्ण पानाकडे लक्ष ठेवणे, उत्तर देण्यास योग्य दुवे नसणे. - अश्या अनेक अडचणी इथल्या प्रत्येकासाठी डोकेदु:खी ठरलेल्या आहेत.

त्याचबरोबर ह्या विकिमजकूर चर्चापानातून अनेक बाबी खूपच सुलभ होऊ शकतात हे ही तितकेच खरे आहे. मोकळ्या विकिमजकूर चर्चापानांच्या मदतीने अनेकांनी साचे आणि अनेक तंत्रे वापरून खूप सृजनशिल वापर करून संपादक मुक्तपणे संवाद साधतातही. ह्या चर्चा अगदीसहजपणे पाहिजे तशी रचताही येतात. पानाचा इतिहास, फरक आणि आवृत्त्या तपासून नक्की कोणी काय केले हे संपादकांना लागलीच समजायला मदत होते. ज्या सोयीनी आपल्याला गेली पंधरा वर्षे संवाद साधण्यास आणि लाखो लेखांचे संपादन करण्यास तसेच विश्वकोशाला हातभार लावण्यास मदत केली आहे त्या सोयीला अचानक असे निरुपयोगी ठरवण्यात काहीही हाशिल नाही.

या आधीही विकिमिडीया गटांनी संवादाच्या अवजारांवर काम केलेले आहे : (२०१० मधे सुरूवात झाली) आणि  (२०१२ मधे सुरूवात झाली). 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
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?