Talk pages consultation 2019/Participant group sign-up/zh

參與小組是2019年討論頁諮詢中幅射式結構的一個關鍵部分. MediaWiki.org為本計畫的主要Wiki網頁，以作為整個過程的中心樞紐. 為了讓各式各樣的維基媒體人能夠分享他們的想法，我們希望每個人都能夠在他們感到舒適的主要語言環境，討論關於Wiki討論系統的議題.


 * 参与小组（社區）名稱
 * 正式或非正式的名稱可以辨別每個參與小組. 這可以是既有的名稱（例如自治體名稱或維基媒體計畫名稱）或是針對本次諮詢所採用的新名稱.


 * 語系
 * 参与小组应该用他们认为最舒服的语言就有关讨论页面的事项进行讨论. 不过，最终报告请用英文书写.


 * 主要联系人
 * 參與小組可以依照他們的決定組織成大型或小型討論群組，但每個小組必須要在MediaWiki.org的中央討論群組有一名（或兩名）小組協調人員.
 * 該名用户需要读写英文. 我们将定期与该用户联系，以使过程尽可能简单.
 * 该用户承诺平等对待所有反馈和意见，并在最终报告中考虑它们.


 * 咨询小组方式
 * 部分小組會在他們的主要Wiki網站討論，其他小組可能會決定在其他網站（如許多社群習慣使用的社群網站），甚至可能會以面對面方式進行討論，例如編輯松.


 * 您将在哪里记录您的讨论？
 * 對於在Wiki網站上的討論，請提供本次討論的連結. 在（大型）Wiki網站建立一個獨立頁面可以協助您追蹤所有的回饋. 對於在Wiki網站以外的討論，請提供一份討論總結的書面報告連結. 這份報告可以用偏好語言撰寫，後續我們將會協助翻譯.

Phase 2

 * In its second phase, the consultation is focusing on conversation around trade-offs. Each participant of the group gives individual feedback related to the below questions:


 * 1) What do you think of the proposed product direction?
 * Context: The Wikimedia Foundation proposes building a new, clearer design on top of existing wikitext talk pages. It will offer simpler tools for replying, indentation and signatures. You could continue to use wikitext on talk pages, if you prefer that. It should also be possible to participate in a discussion without using wikitext.
 * Question: What do you think of this product direction?
 * 1) Marking separate discussions
 * Context: People want to watch individual sections on the talk page. They want better notifications, archiving, and search.  To do any of this, we may need to create a more structured definition of what counts as a single discussion. This may mean making changes to the wikitext conventions on a talk page. For example, we may create a new way that discussion headings look in wikitext, or a new link that you need to use to create, rename or split a thread.
 * Question: What are the pros and cons of that approach?
 * 1) Helping newcomers find the talk pages
 * Context: Newcomers have difficulty finding talk pages.  During user tests, only one person out of ten found the  tab. Most testers looked for a  tab on the opposite side of the page, where all of the other tabs and links are. Many people also expected to see links to discussions about specific sections in the article. We may want to move the link to the talk page to the opposite side of the article page.  We might add discussion functionality connected to individual sections.
 * Question: What are the pros and cons of making the connection between article content and discussions more visible?
 * 1) Where to show discussion tools
 * Context: Currently, many wikis have community discussion spaces in the project namespace (  or  ), rather than in a talk namespace (  or  ). The project namespace is often used for village pumps/cafés, noticeboards, and some workflows, such as Articles for deletion. The system will need to know where discussions happen, so that it can display the new tools in those discussions, and not display them on other pages. There are several potential ways to do this. One of them is to move all discussions to a talk namespace.
 * Question: What are the pros and cons of doing that?
 * 1) History tradeoffs
 * Context: Sometimes, you need to see the history of the entire page.  Other times, it would be more helpful to see the history of only a single discussion thread. It would be ideal if we could provide both, but we're not sure how to do that.
 * Question: What are the pros and cons of having a complete page history or a specific thread history?
 * 1) Metadata location
 * Context: Some wikis place templates at the top of article talk pages.  These may show instructions, warnings, or FAQs.  They may hold page quality information, link to relevant WikiProjects, or identify past activities.  Many new users are confused by finding non-discussion material at the top of an article talk page.  It would be helpful to move some or all of that content somewhere else on the page, or under a different tab.
 * Question: What are the pros and cons of that approach? Which templates are crucial for the proper use of a discussion page, and which could be moved somewhere else?
 * Every participant gives others the opportunity to express themselves. At the end, the feedback is documented.


 * When does the feedback collection end?
 * Community summaries for Phase 2 are due by June 15, 2019.

Under construction groups
This second table is for groups that are under creation. If your group is ready to receive feedback, please move it to the first table.

Phase 1

 * 在第一阶段，协商不是辩论或得到最终决定同意做什么/不做什么的过程. 小组中的每个参与者都提供个人反馈，您可以参考以下指南進行討論：
 * 當您想要與您的社群討論某個議題時，哪些工具對您來說覺得實用，哪些則會阻礙您的討論？
 * 討論頁對於新手而言有什麼用處，而阻礙新手討論的又是什麼？
 * 您所屬社群中的其他人关于对话页面有什么争执？
 * 您希望在討論頁能做到什麼，但因為技術限制而無法達成？
 * 您認為「Wiki式討論」要有哪些重要的樣貌？
 * 每个参与者都有机会表达自己的意見. 最后，所有回饋將會予以建檔（见下文）.


 * 何時結束收集回饋？
 * 第一階段的社群總結應於2019年4月6日發佈. 最佳的選擇是在3月31日結束討論，這樣就會有足夠時間分析與組織收集到的回饋.

参与小组
如果您有兴趣代表参与小组，请在下面注册：

Community summaries are due by April 6, 2019. We advise communities, especially the ones that would have had collected a lot of replies, to end the conversation by March 31.

We do not advise creating new groups now, unless you can get a significant amount of feedback before the due date.

Under construction groups
This second table is for groups that are under creation. If your group is ready to receive feedback, please move it to the first table.