चर्चापान विषयक सल्लामसलत २०१९
ही चर्चापान संबंधित सल्लामसलत जागतिक पातळीवर फेब्रुअरी ते जुन २०१९ दरम्यान आयोजित केली गेलेली आहे, याद्वारे विकि-विचारांचे लोक आणि विकिमिडीयन्स एकत्र येऊन विकिवरील संवादासाठी सुयोग्य अवजारे निर्माण केली जाऊ शकतील. या सल्लामसलतीमधून विकिमिडीयाच्या समुदायाकडून वेगवेगळ्या भागातून सुचना मागवल्या जाणार आहेत - वेगवेगळ्या प्रकल्पातून, वेगवेगळ्या भाषांमधून, आणि वेगवेगळ्या दृष्टीकोनातून - ज्यामुळे आमचे उत्पादक गट योग्य असे अवजार आणि त्याच्या सोयीसुविधा ठरवू शकतील आणि त्यावर ते येत्या वर्षात काम करू शकतील.
या सल्लामसलतीचे कारण
विकिमजकूराच्य सहाय्याने तयार केलेली चर्चापाने कोणत्याच सोफ्टवेयरने तयार केली जात नाहीत; ती वेगवेगळ्या लोकांनी आपाअपल्या सांस्कृतीक भांडवलाद्वारे/सोयीने तयार केलेली असतात ती नव्या संपादकांना अडचणीची आणि अनूभवी संपादकांना त्रासाची वाटत आलेली आहेत. अनुस्वार चिन्हांची संख्या ठरवून उत्तराची पातळी देणे, टिल्डा देऊन सह्या करणे, आपण चर्चा करत असलेल्या विभागाकडेच नव्हे तर पूर्ण पानाकडे लक्ष ठेवणे, उत्तर देण्यास योग्य दुवे नसणे. - अश्या अनेक अडचणी इथल्या प्रत्येकासाठी डोकेदु:खी ठरलेल्या आहेत.
त्याचबरोबर ह्या विकिमजकूर चर्चापानातून अनेक बाबी खूपच सुलभ होऊ शकतात हे ही तितकेच खरे आहे. मोकळ्या विकिमजकूर चर्चापानांच्या मदतीने अनेकांनी साचे आणि अनेक तंत्रे वापरून खूप सृजनशिल वापर करून संपादक मुक्तपणे संवाद साधतातही. ह्या चर्चा अगदीसहजपणे पाहिजे तशी रचताही येतात. पानाचा इतिहास, फरक आणि आवृत्त्या तपासून नक्की कोणी काय केले हे संपादकांना लागलीच समजायला मदत होते. ज्या सोयीनी आपल्याला गेली पंधरा वर्षे संवाद साधण्यास आणि लाखो लेखांचे संपादन करण्यास तसेच विश्वकोशाला हातभार लावण्यास मदत केली आहे त्या सोयीला अचानक असे निरुपयोगी ठरवण्यात काहीही हाशिल नाही.
या आधीही विकिमिडीया गटांनी संवादाच्या अवजारांवर काम केलेले आहे : LiquidThreads (२०१० मधे सुरूवात झाली) आणि प्रवाही/सुरचित चर्चा (२०१२ मधे सुरूवात झाली). 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.
For this process to work, we need to be open to all kinds of directions.
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.
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:
- Translate key elements of the Phase 1 report.
- Sign up your group to participate in Phase 2.
- Create a local consultation to answer the Phase 2 questions.
- Ask your community for feedback.
It is also possible to comment on MediaWiki.org.
This consultation will have a "hub-and-spoke" structure, with a central hub located here on mediawiki.org ("Talk Page Consultation central"). Over the course of the consultation, multiple participant groups will have discussions on other wikis and in off-wiki settings, and then contribute notes and findings back to TPC central. Some participant groups will participate through the whole process, others may participate for a limited time (especially if they're in real life/meet-ups). Everyone can follow along and participate at TPC central (language permitting).
Phase 0: Planning Done
This was the planning phase. During this phase, we:
- Publicly announced the project (banner info here), and invited questions and ideas from the Wikimedia community
- Set up TPC central documentation structure; current notes were featured on the main TPC page, while historical staff notes could be found here and here
- Created a list of wikis and user groups for initial outreach and invited groups to sign up
- Established code of conduct guidelines
- Carried out retrospective process for StructuredDiscussions/Flow, Liquid Threads and wikitext workflows, collect important documentation
- Reached out to participant groups
- Invited volunteers to facilitate discussions and participate in other ways
- Created the schedule for the project
Phase 1: Collect information Done
Source: TPC Feedback from volunteer participant groups and individuals
When: Mid-March - April; Community summaries posted by April 6, 2019
During this phase we solicited open feedback from a wide range of individuals and groups about their experiences with talk pages or alternative tools. Questions were:
- When you want to discuss a topic with your community, what tools work for you, and what problems block you? Why?
- How do newcomers use talk pages, and what blocks them from using it?
- What do others struggle with in your community about talk pages?
- What do you wish you could do on talk pages, but can't due to the technical limitations?
The information collection started when the first message was sent. Interested users could check if a group existed for their language.
Wrapping up the conversations Done
Community summaries were due by April 6, 2019. We advised communities, especially the ones that would have had collected a lot of replies, to end the conversation by March 31. That way, volunteers making the wrapping-up had time to make it.
Since this consultation was based on a different consultation process than how consultations are defined by local rules, those rules regarding how to close conversations were not applied.
Phase 2: Trade-offs and prioritization Done
Source: Phase 1 report, built from from the feedback received from volunteer participant groups and individuals.
When: Starts in mid May
Some ideas generated during Phase 1 may be mutually exclusive. Some ideas might work better for some purposes or some kinds of users. We'll have to talk about which problems are more urgent, which projects are most closely aligned with the overall needs and goals of the movement, and which ideas we should focus on first.
Discussions about these trade-offs will be moderated by the Wikimedia Foundation, guided by our decision criteria, listed below. We advise that they happen on wiki, like for Phase 1. As such, communities can sign-up on the group sign-up page under the new Phase 2 section, similarly to how they did for Phase 1.
We invited everyone back to review the emerging direction for this project during Phase 2.
Space for unexpected discoveries
Within the scope of this project, all the options are on the table. There are no hidden agendas. We don't know all the things, and we don't know what we might learn. We need to accept these "unknown unknowns".
The schedule of this consultation may change because of these unexpected discoveries.
Wrapping up the conversations
Community summaries are due by June 24, 2019 (formerly June 15). We advise communities, especially the ones that have to collect a lot of replies, to end the conversation by June 10. That way, volunteers making the wrapping-up have time to make it.
Since this consultation is based on a different consultation process than how consultations are defined by local rules, those rules regarding how to close conversations are not applied.
Status report: Wrapping up Phase 1
Thanks to everyone who's participated in the Talk Pages Consultation so far! We're wrapping up the discussions for Phase 1 and compiling all the results, which will lead into the start of Phase 2 in May.
The purpose of Phase 1 has been to collect as much information as we can about how people use talk pages, documenting the advantages and challenges, and generating ideas for making improvements. We've also collected information about communication tools that people are using now, both on-wiki and off-wiki. People have hosted group discussions on more than 15 wikis and at events, and we've also received individual feedback from many people. You can see the summaries of the wiki discussions here, which has links to the original discussions.
In addition, as part of Phase 1, we're currently running some user tests with people who are active Wikipedia readers and would like to become editors, in order to document what it's like for them to communicate on-wiki. The tests are just starting now; we'll post results over the next couple of weeks.
For the rest of April, the team is working on bringing together all the information and ideas that you've provided. We're reading all of the discussions, summaries and feedback, and putting it together into a big report that we'll publish at the beginning of May. The report will reflect all of the major themes from the discussions, so we all have a shared understanding of the issues that have been raised. It will also include a list of all the things that people want to accomplish on talk pages. (People in software development call these "user stories"; you can see the current draft list here).
Once we publish that report and people have had a chance to look at it and respond, we'll start Phase 2 in May. This is the "tradeoffs" phase, where we'll ask more specific questions about how to balance different user stories. The discussions we have in Phase 2 will help us to put together ideas to propose for a product direction in Phase 3. (You can see some early notes on the tradeoffs phase here.)
We'll post more updates on the Talk pages consultation 2019 page, as we work on the Phase 1 report together, with links to the current work. We're excited and inspired by all of the ideas that people have posted so far; thank you for being a part of this project! -- DannyH (WMF) (talk) 16:08, 17 April 2019 (UTC)
August 7, 2019
This marks the official last meeting of the TPC group. A debrief meeting will occur the first week of September that also covers Wikimania.
The Phase 2 report is largely written. What remains is to retrieve quotes used in the report in their original language, expand on some details, and ready for translation. Translation will be an ongoing process after the report is published; the process could take months simply because this report does not have a required feedback portion connected to it. To be clear, though, people are welcome to leave feedback if they desire. The report is slated for publication this coming Monday, August 19th, at the latest. That will also be when the official announcement is made.
The team is currently working on the TPC Wikimania presentation. Next steps for those interested will be to read the report, watch the main project page for announcements, and sign up for updates (details forthcoming).
The TPC seems to have been successful in its stated goals, foremost of which was to remain transparent and listen to and gather feedback from communities to develop a plan of action. That's not to say improvements couldn't be done; as this was the first such venture using this methodology, there were some hiccups. That being said, this may be a model used going forth when it comes to large changes.
See updates from before August, 2019 at Talk pages consultation 2019/Status updates.
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.
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?