维基百科:专题委员会/专题指引

維基百科專題（WikiProject）是想以合作方式改進維基百科者的團隊。維基百科專題並不是頁面的選集。成立一個對特定主題集中討論、協作的社群對許多人都有益。本篇維基專題指引記載了許多能更有效率組織志願者的方式。

以下列出了一些組織和運行維基百科的方法。根據個別的範圍、規模與活動特質差異，許多專題也自行發展出了一套不同的組織方式。若想找到最適合的方式，可透過在專題內進行具創意的實驗，或觀察其他成功的專題是如何做到的。本指南不可能收錄能讓每一個專題都成功發展的所有做法。

本指南的適用對象是以「主題性」的維基百科專題為主，也就是目標為「改進關於特定主題之條目內容」的專題。而其他維護性質的專題通常有自己不同的組織架構和活動內容，包括小作品分類、消歧義、清理等，因此以下列出的方法指引可能不適用於該類專題。

什麼是維基百科專題？

维基百科专题是以团队合作方式，专门管理维基百科上特定主题的一系列条目的编者团队。维基百科专题是一群人，而不是一组页面，一个学科领域，或一个分类。维基百科专题的页面不是一个直接编写条目的地方，而是帮助协调、讨论、组织此团队的活动，分享编条目的想法的地方。

维基百科专题也可能是建立对某个主题领域感兴趣的维基人之间的联系的焦点，以及该领域的更广泛的社群：建立合作关系，欢迎、指导新维基人等。在这方面，维基百科专题的作用可能与维基媒体分会的作用重叠。

维基百科专题的页面是在一个特定主题领域协作编辑的中心。编者可以制定标准，维护各种协作流程，跟踪需要完成的工作，并可以作为论坛，讨论某一主题的编者感兴趣的问题。

可是，是什么让维基百科专题工作的呢？鉴于上面的定义，人们很容易把维基百科专题看作其条目有关的活动的总和，或者认为它仅仅是一些“专门管理特定主题或特定类别主题的页面”的整体。然而经验表明，维基百科专题一定要超越一系列流程和指引的成功的。区别成功的维基百科之处不是称它为“维基百科专题”；相反，维基百科专题的功能更应是一群编者而非条目。

维基百科专题本质上是一种社会建构：它的成功取决于其作为朝着一个共同目标而努力的，有凝聚力的编者团队的能力。要维持一个成功的专题，成员们需要做的大部分工作（特别是质量评估和同行评审，但几乎除实际编写条目之外的任何事情）都是单调乏味的，而且往往既没有回报，也不受重视。为了高效，维基百科专题在项目的主题方面，不仅要发展兴趣，而且要促进成员间团队精神的形成。在团队保持凝聚力时，专题成员就会愿意参与不那么令人兴奋的工作，这样一个维基百科专题才能振作精神、确立方向，系统地而非偶然地产出优秀的条目。

主題協作

如果你只是因为要在少数页面间进行协作，想做一点主题协作，你会在下面的章节中找到有用的想法。（当任务组参与的时候特别有用。）

討論頁的資訊

当然，在讨论页协调事务时，应该遵循討論頁指導。

话虽如此，修改讨论页，把重点放在当前需要对该页面做出的改进（不限于你的主题协调，但肯定会包括它），是很有益处的。你会发现下面的链接有助于此：

• Wikipedia:整理討論
• Wikipedia:如何將討論頁存檔

在討論頁中進行主題協作

下面是如何在讨论页进行主题协调的一个范例。毫无疑问，还有其他的方式；如果你遇到别的适合你的方式，随时记录在这里。下面的例子使用了郁金香。

1. 在讨论:郁金香页面（这是为郁金香条目的主要页）张贴一份说明：
   1. 目标：努力让郁金香的不同品种都至少有一个初级条目。
   2. 任务列表：列出所有条目的维基内部链接，并鼓励人们将他们的名字放置到他们志愿编写的条目旁。你或许可以参照Wikipedia:需進行工作列表
2. 页面网络：使用Template:Topic co-ordination link，将其他讨论页链回你主页面的章节

已隱藏部分未翻譯部分，歡迎參與翻譯。

跨專題協作

標記條目

我該用專題橫幅或小作品模板？

WikiProject assessment banner tags and stub templates often seem to serve the same purpose, yet they have distinct functions. While a banner tag marks an article specifically for a WikiProject, the aim of stub templates is to mark small articles uniformly across the whole of Wikipedia. As such, there is a large effort to coordinate stub use across all WikiProjects and also those articles not covered by individual subject projects (this is the main reason why there is a semi-formal proposal process for stub templates and categories). Banner templates, on the other hand, can be altered as an individual WikiProject sees fit, and—since they can be used to tag all articles relating to a WikiProject, and not just stubs—they are the recommended tagging method for individual WikiProjects. See Wikipedia:Stub#Stub types, WikiProjects, and Assessment templates for more details.

專題橫幅的目的

While many editors think that member recruitment is the primary reason for placing a project banner on an article, they are actually used in many different contexts:

• The tags place articles into categories that project members use to find articles that they want to work on.
• The tags are used to check recent changes (a sort of watchlist for the articles the group cares about).
• They are used to produce statistical reports about the quality of articles, which allow the group to monitor their progress.
• The tags allow the WP:1.0 team's assessment process to measure the size/scope of projects and to rank articles for inclusion in offline releases of Wikipedia articles.
• Article Alerts uses information in the tags to produce an automatically updated list of WP:Articles for deletion, WP:Proposed deletions, and other time-sensitive news about tagged articles.
• Cleanup listings uses tags to produce a comprehensive list of all clean-up tags in a project's articles.
• Walls of Recognized Content uses tags to create lists of high-quality articles.
• and several other automated processes.

專題並不擁有條目

Many articles will be tagged by more than one WikiProject. This is particularly true of articles that deal with prominent people, as those articles may be tagged by WikiProjects for biography, their places of residence, their professional field, and any other activities they may engage in. Placement of any relevant banner should generally be accepted, as each project may have unique resources and be willing to improve and monitor the article. One group may not prohibit another group from showing an interest in an article.

However, on occasion, someone clearly places the wrong banner on an article. When this happens, it is polite to ask either that individual or that project why the banner was placed. Doing so reduces the likelihood of inter-project animosity, and also could potentially help the article in some way. For example, a project's scope may have expanded to include the article; they might now be willing to work on the article. Also, particularly when a bot is being used to tag articles, the article may have been tagged because it is miscategorized. In instances like these, like in all others, civility, respect for others, and clear, unambiguous communications are to be greatly valued.

In 2007, some editors agreed to limit "WikiProject country" banners on articles about a city, especially if the city has changed hands several times over the course of history: if there is disagreement, then only the Wikiproject for the city's current country will tag the article. For example, though the Germans occupied France during World War II, it would not be appropriate to put articles about French cities under WP:WikiProject Germany. For more information, see the 2007 consensus discussion.

條目編輯者並不擁有專題

Many editors place banners on behalf of a WikiProject that they are not members of. This practice is normally welcomed by WikiProjects as it brings to their attention new and interesting articles.

Please be judicious in making such placements by minimizing the number of outside banners that you place on an article and by carefully reviewing the scope of the project. Information about the project's scope is often available on the WikiProject's main page, and sometimes also on documentation associated with the template. If you are uncertain that the placement will be welcomed, then leave a note on the project's talk page instead of placing the banner yourself.

If you place a banner for an outside WikiProject, and a member of that project removes it, do not replace the banner. A WikiProject's members have the exclusive right to define the scope of their project, which includes defining an article as being outside the scope of the project. Similarly, if a WikiProject says that an article is within their scope, then you may not force them to remove the banner. No editor may prohibit a group of editors from showing their interest in an article per Wikipedia:Requests for comment/Wikiproject tags on biographies of living people.

過多的橫幅將造成困擾

All editors should avoid tagging an article with a disruptive number of WikiProject banners. Banners take up a significant amount of space on the talk page; this can be minimized by enclosing all banners in a template such as {{WikiProjectBanners}}, a shell that is compressed and, as indicated on its documentation and on the Talk page layout project page, should be used when there are more than about five project banners on the page or if there are many other headers in use. {{WikiProjectBannerShell}}, an uncompressed shell, is generally preferred when there are about three to five banners on the page.

WikiProject banners should not be used to duplicate the category system or portals. If an article is only tangentially related to the scope of another WikiProject, then please do not place that project's banner on the article. For example, washing toys for babies reduces transmission of some diseases, but the banners for WP:WikiProject Health, WP:WikiProject Biology, WP:WikiProject Virus and/or WP:WikiProject Medicine do not need to be spammed to Talk:Toy.

For projects involved in the WP:1.0 assessment program, every banner placed is a demand for an assessment according to the project's guidelines. It is more friendly to omit outside WikiProjects that you think will rate the article as low importance relative to their specific field.

專題間的合作

There may also arise situations in which it is beneficial for an article to be actively collaborated upon by multiple projects. A short article about a prominent scientist, for example, would probably benefit greatly from a project dealing with the scientist's discipline, his area of residence, biographies in general, and potentially even his time period. In instances like this, it may be a good idea to propose the article for the Wikipedia:Article Improvement Drive, and inform all of the relevant projects of the nomination. By so doing, it is more likely that the members of the individual projects will interact beneficially, which could improve their mutual opinions of each other and likelihood of further interaction. Also, clearly, having high-quality content inserted from all relevant sides cannot be bad for the development of the article. Even if not nominated for the Improvement Drive, it is always beneficial to contact other projects, and inform them about your project's desire to expand the article. That way, other projects can provide copyediting for grammar and conventions, reference materials, or general advice about how to improve the article.

You could also approach relevant projects directly for pages of interest to discuss collaboration. You can use {{CotM}} on article talk pages to highlight a joint Collaboration of the Month.

編輯建議頁面

Many large WikiProjects eventually collect some advice about how to apply Wikipedia's policies, guidelines, and essays to their specific subject area. This advice is often excellent, and may helpfully consolidate and explain the specific details of many site-wide policies that are the source of the most confusion among editors. (e.g., WikiProject Bibliographies)

Editors who are working on such an advice page are encouraged to carefully study the main policies, guidelines, Manual of Style, and relevant essays. The best advice pages do not conflict with the site-wide pages and avoid unnecessary duplications with site-wide pages. You can help editors by providing links to subject-specific templates, a list of information that editors should consider including in a given type of article, relevant examples, and clear explanations (e.g., reasons why editors recommend 'this' instead of 'that').

However, in a few cases, projects have wrongly used these pages as a means of asserting ownership over articles within their scope, such as insisting that all articles that interest the project must contain a criticism section or must not contain an infobox, and that editors of the article get no say in this because of a "consensus" within the project. An advice page written by several members of a project is no more binding on editors than an advice page written by any single individual editor. Any advice page that has not been formally approved by the community through the WP:PROPOSAL process has the actual status of an optional {{essay}}.

The following templates are available to WikiProjects for clarifying the distinction between WikiProject guidance and Wikipedia-wide guidelines:

• {{WikiProject style advice}}
• {{Wikiproject notability essay}}
• {{WikiProject content advice}}

專題委員會的角色

There may still arise situations when there is a seemingly intractable disagreement between projects. If that happens, you can ask for advice from the 专题委员会. This group contains people who have generally shown some ability at working with and in groups. In severe cases, using formal dispute resolution channels are available.

使用機器人來儲存工作

See also: Wikipedia:专题委员会/Guide/Technical notes#Automation

Tool	Supports task forces?
Article tagging tools: Several bots can automatically tag article talk pages with a WikiProject banner, as well as make some automatic assessments. See Category:WikiProject tagging bots for a list, as well as Category:Autoassessment bots.	是
Finding new pages: AlexNewArtBot generates a report listing newly-created articles that match criteria set by the project; this is particularly useful for catching new articles not categorised properly.	是
Tracking recognized content: User:JL-Bot generates a subpage listing the Recognized Content (Featured Articles, Good Articles, In The News, etc.) of a WikiProject. See User:JL-Bot/Project content for details.	是
Finding deletion and review discussions: AAlertBot generates daily reports of the deletion discussions (PROD, AfD, ...) and reviewing process (FAC, GAN, ...) related to the articles of a WikiProject. See WP:AALERTS for details.	是
Article statistics: WP 1.0 bot generates tables summarizing article quality and importance statistics. It also produces daily logs of the change in article quality/importance ratings, as well as renamings, and banner tagging/untagging.	是
Finding unreferenced BLPs: DASHBot/Wikiprojects generates a list of unreferenced biographies of living persons relevant to a project.	是
Clean up listings: Sign up Svick's tool to generate a list of all pages within your scope that contain maintenance tags.	是

如何處理不活躍的專題

  「WP:INACTIVEWP」重定向至此。关于a list of inactive WikiProjects，请见「Wikipedia:专题委员会/Inactive projects」。

辨認

Inactive wikiprojects will have {{inactive}} added, either directly or via the inactive parameter of {{Infobox WikiProject}}. There are several options in dealing with inactive wikiprojects. The usual procedure is to identify projects whose main page hasn't been substantively changed for several months, and whose talk page has received nothing other than routine or automated announcements, or unanswered queries from non-participants, for several months. Alternatively, you may wish to sort through the list of named participants, placing indefinitely blocked accounts and users who have made no edits to Wikipedia for long periods (e.g., over a year) under a separate heading (you may wish to notify the users that you have done so, in case they return). If no active members remain in the list, then the project is inactive.

復蘇

See also the related Wikipedia Signpost article

Any editor may revive an inactive WikiProject. There are a number of things you can do to help revive an inactive or semi-active project. If you come up with something new, please list it here!

1. Update the project page as appropriate: replace the inactive tag with {{semi-active}}, or remove the existing semi-active tag. Archive old clutter (clean and simple is better for attracting new members), use generic WikiProject templates appropriately to organise content (e.g., {{Infobox WikiProject}}) and make use of any helpful automation the project hasn't been using (see section above).
2. Provide clear suggestions on what members can do, using to-do lists, {{tasks}} and cleanup listings, and perhaps linking to relevant pages elsewhere. You can use the {{WikiProject help}} template, either directly or as inspiration.
3. Create any missing userbox, project banner, or user invite templates. See whether the assessment system for the project banner works, and fix it if not.
4. Notify existing participants of your efforts and invite them to contribute, to make suggestions, or to leave a note on the project's talk page about what they're currently editing.
5. To try to gain new participants, individually invite active users who have been substantively involved with the topic to join the project or watchlist its page. This can be done with a personal, handcrafted message or a standardized invitation template.
6. Use automation (see above) to ensure most if not all appropriate pages are tagged with the project banner, thus promoting the project to those who may be interested. (Don't go overboard with this... in general, don't tag a page not within the project's main category unless you could justify making it the project's Collaboration of the Month.)
7. Provide a Special:RecentChangesLinked link on the project page, using the project's article category. (For project Wikipedia:WikiProject X, this will generally be Category:X articles, Category:WikiProject X articles, or X work group articles. Try it and see.) This gives an easy way to see recent relevant talk page discussions. Example.
8. Seek out collaboration with related projects. Tell them that the project is active, invite them to help, and ask whether there is an article of mutual interest that both groups could collaborate on.
9. Notify the Wikipedia Signpost WikiProject desk of your attempt.
10. Respond promptly to queries and post occasional messages at the WikiProject's talk page to let people know what you're working on and how they can help.

If you have any questions about or related to technical issues, try the Help Desk.

其他選擇

If you (or someone else) has already done the above or it simply looks hopeless, consider one of these options:

1. Merger. Consider proposing a merger with another wikiproject. This might be a related project of a similar type, with the two projects being reconstituted as part of a new one. More commonly it might be that the inactive project could become a taskforce of a parent project. See here for instructions on notification and merging projects.
2. Mark as defunct. In some cases projects are simply superseded (e.g., merged elsewhere), have served their stated purpose, or have been inactive for so long that they are unlikely ever to be revived. These may be tagged as defunct rather than inactive; see the usage notes and guidelines at {{defunct}}. This tag should be used rather than {{historical}} which is reserved for failed proposals or deprecated processes.
3. Userfy. When project had only one active member or was never so active as to justify keeping it for the whole community to refer to, consider userfication of the project to the organizer's userspace. This is particularly useful for recently created projects that never got off the ground as it can avoid being bitey.
4. Deletion. In rare cases, deletion may be appropriate. This might be appropriate for completely inactive projects which have no substantive history and serve no residual purpose even without activity (e.g., due to automation or information presented). Projects must also meet the guidelines for being marked as defunct (see {{defunct}}, the template's documentation is here). WP:MFD is the appropriate forum to propose this.

If you are considering taking any significant steps in this area which others might object to, take care to give appropriate notice to all parties of your proposals (including the WikiProject Council). Often it will be feasible to notify all listed participants who have been active on Wikipedia in the recent past (even if not recently active on the project). If proposing a merger, be sure to propose this at the merger target and do not take approval for granted.

創立一個維基百科專題

在創立之前

该章节的建议主要用于刚起步——或者重新回归活跃——的专题，以及任何考虑创建新维基专题的编辑；不过，任何参与维基专题的人都有可能在其中找到些感兴趣的东西。

檢視現有的提案

这相当简单：去专题委员会提案，看看是否别人已经提案了。搜索全部存档（列于此处：未有存檔（建立））看看是否之前曾被提案。

通知相關的母專題

至少在你开始前，应该找出任何有关的专题。如果你有一个关于可行专题的好想法，那很可能其他人已经想到了，于是这个专题就已经存在。如果这真的是一个新想法，那有关专题的成员很可能会参与此专题，他们也许能帮你创建一个新专题。 请在做任何事之前之参照以下步骤：

1. 檢查 专题名录 看看你是否能識別哪些可能父母群像是專題"鬱金香"WikiProject Netherlands 相關內容可見 园艺与园林专题
2. 查看主题列表來找到對應主題 .
3. 查看讨论页找尋關鍵文章有無相關討論、標記。

如何處理資訊:

• 如果有相關的組已經存在，即使它是無效的，你應該編修該項目，而不是開始另一個可以用編輯進行修整工作
  • 果關於這個問題的工作需要更多討論，可能很多意見，則麼你可以組成立一個專案存放WP：專案組該項目
  • 你如果有子母群體存在，你應該優先在相關頁面討論
  • 許多專案都沒有被整合，如果相關的主題一個個散佈在其中，則可以善用子母群體的功能來連接彼此

如果沒有這麼多的專案主題，則你下一步則是創造一個新的維基專題

設定最適合的範圍

Next, identify the best scope for your project. Successful WikiProjects have a scope that is natural and broad enough to attract and sustain editor interest. For example, are 郁金香s too small a project scope, such that it might only ever have a few dozen articles and six project members (some of whom don't do much)? Either of those criteria should be enough to make you think that maybe a larger scope would be better. You might be able to get a more reasonably sized project by including the entire 百合科, which includes tulips, or all 花s, or the larger subject of gardening and horticulture.

The risks of a narrow scope are:

• Not enough people: Your group may die from administrative overload, and become one of the more than 300 不活跃专题.
• Not enough pages: People will quickly complete the work and get bored. Your project may die from administrative overload, and likewise become inactive.
• Too much overlap: If the scope is too closely related to an existing project, then having separate projects is usually inefficient and counterproductive, because you wind up dividing the few interested editors across multiple projects. This approach maximizes administrative hassles and minimizes collaboration. However, there is no rule that prohibits two separate groups of editors from being interested in the same articles.

How to estimate the number of pages in your proposed scope

1. Go to the main article. Click on "What links here", and see how many articles are connected to this one. This is probably your number, unless you limit the scope in some way (e.g., only including significant Tulip growers (not just fanciers) from before 1900 in the Biography category).
2. Look in the categories associated with your key articles. The proposed WikiProject Tulips, for example, would want to consider categories like Category:花卉 and Category:Tulipa.

Having considered the probable size of the scope, ask yourself, "Is this a 'natural' scope?" Will other people be able to easily understand what kind of articles the group is working on? WikiProjects are allowed to have strange, arbitrary, or unpredictable scopes ("Tulips, except for my least favorite species, plus my favorite photo software"), but we strongly recommend that you adjust or expand the scope to be more sensible.

At the end of this step, you should know approximately how many articles are likely to be within the project's scope, what the names of the key articles and categories are, and how to describe the scope briefly. That information will help you determine the best structure.

設定最適合的架構

Having identified the scope you want for your project, the next thing to consider is the best structure for the project. The typical structures are:

Topic coordination

This format is appropriate if you want to co-ordinate across about a dozen or so pages, or for temporary, one-time tasks. See the separate section below for details.

Task force

This format is appropriate if your scope involves a few dozen to a few hundred pages. A task force uses most of the administrative structure of their parent project, but works together as a smaller group. The fastest way to start a task force is to join the parent WikiProject(s), and ask if they can help you form a task force. Some WikiProjects have a more developed framework for dealing with sub-groups like task forces; others will be unfamiliar with them. However, most WikiProjects are happy to have someone who is keen to start a task force, even if the project doesn't currently have any task forces in place.

WikiProject

This format is best for topics with thousands, or at least several hundred, of pages in the proposed scope. You'll still want to investigate any related projects, because they may already have a task force covering the same topic.

Inter-WikiProject coordination

If your scope was too large, but you're still keen, you'll probably want, instead, to identify potential child WikiProjects, and try to help them co-ordinate; this doesn't require a WikiProject in itself. Talk to the potential child WikiProjects about co-ordination, and see what sort of response you get. Be careful not to try to dictate to them; they could be sensitive about your appearing out of nowhere and wanting to assimilate them. If this is the format you choose, the rest of this document, while good background reading, is not essential (although it may help you not to look like an idiot).

尋找可能加入的成員

维基百科专题是一群人，而不是帮助人们一起工作的条目或页面。你应该考虑是否有足够的人愿意共同努力，使这成为可能。你可能已经了解到一些感兴趣的人，或通过联系相关小组，在对你提议的小组为最高重要度的条目发布消息，或直接联系正在编写这个领域的编者来找到潜在的参与者。

維基專題

主页面：Wikipedia:专题委员会/指引/专题

{{WikiProject}}是一个用于创建新的维基百科专题主页的范例模板。 例如，假设你的新专题的名称为Foo。第一步就是创建“Wikipedia:Foo专题”页面，并输入文字{{subst:WikiProject|Foo}}来替换为此模板。保存后，这段代码会被替换成一个维基百科专题的框架，你需要根据你的需要进行调整、适应。有些的注释掉的元素需要取消注释，其他不需要的就可以删除或者注释掉了。注释文字里面也给出了一些指引。

工作组

主页面：Wikipedia:专题委员会/指引/工作组

工作组本质上是一个更大的维基百科专题的非独立小组，负责维基百科专题范围内的某些特定部分。例如，軍事專題的美国军事历史工作组处理一个特定国家的军事历史；而电子游戏专题的魔兽工作组负责一个单机游戏系列。

参见

• Wikipedia:Article alerts
• Wikipedia:专题委员会/专题指引/技术备忘
• Wikipedia:专题委员会/Banner standardisation
• Category:Generic WikiProject templates
• Wikipedia:Wikipedia Signpost, which has a weekly section on WikiProject news, with a featured project
• Wikipedia:专题委员会/Inactive projects (list of inactive projects), Category:不活跃专题 and :Category:Defunct WikiProjects
• Wikipedia:Wikipedia Signpost/2013-04-01/WikiProject report

维基百科專題列表

維基百科专题委员会

維基百科專題指引