This help page needs to be updated. The reason given is: this manual may contain out of date information, examples or images. Please help update this help page to reflect recent events or newly available information. Relevant discussion may be found on the talk page. (February 2020) |
Everything so far in this book has been about you as an individual editor, working on your own, interacting with others only to discuss problems or changes to articles. But editors at Wikipedia also work together in groups, formal or informal. Not only is there strength in numbers, there's energy and fun. Such group work is one of the things that make Wikipedia as much an online community as it is an encyclopedia.
Most editors edit articles that particularly interest them: articles about television comedy shows; the region where they live; sports; areas of science or technology; history; multiplayer video games; and so on. If you're one of them, the next natural step is joining a topical area WikiProject—a group of editors working on a collection of articles related to the same topic. Or you may take pleasure in a specific kind of editing: fixing footnotes; improving lead paragraphs; or adding geographical coordinates to articles. There are also WikiProjects for editors with such interests.
Although working in WikiProjects is the most common kind of group effort in Wikipedia, there are others: Collaborations are where a group of editors works on a single article for a week, fortnight, or month, and then turns to the next article they choose, often within a broad topical area. Organizations are less formal and less numerous than WikiProjects. One-time initiatives form and end whenever editors see the need and other editors agree to help.
This chapter describes each of these group efforts, and shows you where to get more information about the groups that already exist. And if you don't find a group that covers something you're interested in, this chapter also tells you how to create a group focused on your interest.
There are basically two types of WikiProjects—topical ones that focus on a subset of articles in a particular area (like WikiProject Poker), and cross-cutting ones that could theoretically work on any article in Wikipedia (like WikiProject Guild of Copy Editors).
In all, there are over a thousand WikiProjects (there's no official count), of which about a third are labeled inactive. Over 80 percent of all WikiProjects are topical; the rest are cross-cutting.
WikiProjects that focus on a subset of Wikipedia articles are listed in the main directory, which you'll find at the page Wikipedia:WikiProject Council/Directory (shortcut: WP:PROJDIR). Four major subdirectories are linked to from there:
Each of the four major groupings has hundreds of different WikiProjects in it, but there are definitely gaps—that is, opportunities for additional WikiProjects. That's because there isn't any person or group at Wikipedia responsible for top-down organizing: Every WikiProject that exists is the result of individual editors deciding that they wanted to create it.
Often topical WikiProjects are coordinated with each other when there's potential overlap. Figure 9-2 shows an example.
The 150 or so cross-cutting WikiProjects focus on Wikipedia-wide issues, rather than on a subset of articles in a particular topical area. Most of these fit into two general categories:
And then there are the more or less one-of-a-kind WikiProjects, such as:
Cross-cutting WikiProjects are not just places to do types of work you enjoy, but they're also excellent places to discuss the finer nuances of article construction and how to get the most out of Wikipedia's powerful software tools. If you find a chapter of this book particularly interesting, and want to improve Wikipedia by working in that area, you'll probably find a matching WikiProject. (If not, consider creating one, as described in the section about creating WikiProjects.)
An August 2007 survey of random 100 articles found that more than half had a related WikiProject noted on their article talk page. Thirteen of those article talk pages had two or three associated WikiProjects, not just one. The good news: WikiProjects are important. More than half of articles in Wikipedia have at least one WikiProject interested in improving them. The bad news: Almost half of all articles in Wikipedia are WikiProject orphans—either outside of any existing WikiProject's scope, or undiscovered by the relevant WikiProject.
There's more evidence of the pervasiveness of WikiProjects: Statistics on all Wikipedia articles, as of October 2007, showed that 900,000 had been assessed for quality by WikiProjects (assessments range from stub to featured article), with another 300,000 or so still to be assessed.
Looking at the examples in the section about cross-cutting WikiProjects, it's clear that a WikiProject can aim to improve just about anything on Wikipedia. But the vast majority of WikiProjects focus on articles, and the majority of those focus on articles within a particular topical area. Understanding such WikiProjects will give you a good idea of WikiProjects as a whole.
The first and foremost goal of topical WikiProjects is to improve Wikipedia's coverage of articles within that topic. Most of that effort is aimed at existing articles, but WikiProjects are also involved in creating new articles where needed.
WikiProjects are no more than the sum of the work of participating editors, so a certain amount of effort must be put into recruiting editors and retaining the interest of participating editors. ( Finding other participants and encouraging participation goes into more detail.)
A second role of WikiProjects is to maintain portals, mini-Main Pages which are entry points for particular topics. For example, WikiProject Indonesia maintains the page Portal:Indonesia (shortcut: P:ID) and WikiProject Books and WikiProject Novels jointly maintain the page Portal:Literature.
A third WikiProjects role is to assess the quality of articles within their projects. As of October 2007, an estimated 800 WikiProjects had done assessments (quality of articles, importance of articles, and so on) within their topics. The Version 1.0 Editorial Team (shortcut: WP:1.0) uses these assessments to select articles, and in April 2007 released a collection of about 2,000 articles as Wikipedia version 0.5, on a set of CDs.
A WikiProject's size significantly affects a given project's activities. Some projects have hundreds of members and cover tens of thousands of articles; some have only a handful of members and less than a hundred articles. Task forces (or similar subgroupings) are critical for large projects, while small projects need to minimize administrative housekeeping, instead focusing on working on articles. Still, here are a few things that most projects can or should do:
If you're a member of a WikiProject and hear of something interesting that your project isn't doing, don't be shy about suggesting it on the main talk page of that WikiProject or on another, more relevant talk page within that project. You may end up doing most of the initial work yourself, so avoid suggesting something you don't have the time to work on alone or with one or two others. (If no one else is interested, it's not a crime to drop the idea.)
One way to find a WikiProject you'd be interested in joining is to go to an article of personal interest and check the article's talk page. If the article has a WikiProject banner, follow the link to that WikiProject, and see if you want to join.
The other way to find a WikiProject of interest is to use the page Wikipedia:WikiProject Council/Directory (shortcut: WP:PROJDIR). Start with one of the subdirectories, and drill down until you find something that looks interesting.
Keeping a WikiProject going can be a challenge. After all, Wikipedia editors are unpaid volunteers whose interests and free time can change, so attrition is normal. Successful WikiProjects need to both recruit new members and retain the interest of existing members. If you're in a WikiProject, it's in your best interest to help with both of these.
You might think that recruitment and retention are the responsibility of whoever is in charge of a WikiProject. But the whole point of WikiProjects—and Wikipedia—is that no one's in charge. The Wikipedia community strongly discourages voting, elected positions, and hierarchy; Wikipedia:What Wikipedia is not (shortcut: WP:NOT) clearly states that Wikipedia is neither a democracy nor a bureaucracy. (Some large WikiProjects have coordinators, but they're primarily responsible for administrative housekeeping.)
So if, for example, your WikiProject doesn't have a newsletter, and you want to write one, all you need to do is post to a talk page, saying that you're thinking about doing so, asking if anyone has an objection—or wants to help. If no one objects, then you're now the newsletter editor (or co-editor, if others are interested).
Here is a list of various WikiProjects with links to their participants and bot-generated list of active editors.
There are two standard ways to recruit new members for an ongoing WikiProject:
Less common methods include:
Many WikiProjects have their own welcome template, which is ideal to post to the user talk pages of editors who sign up. If there's no template, you can post a personal note. Making the new editor feel welcome helps encourage active participation.
A monthly newsletter updating editors on progress and plans can encourage editors to spend some time on the WikiProject. Mentioning new members by name is a great way to increase the enthusiasm level. If you want something more than a plain text newsletter, check out sample newsletters from a number of WikiProjects, collected at Wikipedia:WikiProject Council/Newsletters. (One sample is shown in Figure 9-6.)
An announcements page within the WikiProject can be a good way to encourage members to check in frequently. Just don't hide the page away somewhere without putting up clear links to it.
Finally, while it may sound a bit hokey, at least a few WikiProjects have created awards for high participation editors. Having such an award posted on the editor's user talk page is a pleasant surprise and provides reassurance that others in the group recognize the editor's efforts.
A collaboration involves a single article, chosen by editors working in the group doing the collaboration, where editors work on that article for a week, fortnight, or month, and then turn to the next chosen article.
You can see the list of existing collaborations at Wikipedia:Collaborations (shortcut: WP:CO), as shown in Figure 9-7.
Some collaborations involve several WikiProjects, and some are separate entities unconnected to any WikiProject. But most collaborations occur within an existing WikiProject. One reason is that recruiting new members to a collaboration can be difficult, since collaborations don't post templates on large numbers of article talk pages, as WikiProjects do.
Another factor in favor of single-WikiProject collaborations is the process for selecting a new article to collaborate on: Editors whose articles aren't chosen for collaboration may give up, while editors who do continue to push for a particular article to be the subject of the collaboration may find that when it's chosen, hardly anyone else wants to work on it. Drawing participation from a single WikiProject can minimize or compensate for such problems, since project members have a high interest level, and new members are always joining.
The process for starting a new collaboration is basically to create a new page with details about what you have in mind, and then advertise it. You'll find full details in the " Creating a new collaboration" section at Wikipedia:Collaborations.
Given the challenges of keeping the interest of editors, think twice before creating a collaboration outside a WikiProject. Rather, if you're a member of a WikiProject, test out the waters by posting a note on the talk page of that project. If you get only one or two other editors who show interest, perhaps you can collaborate informally, and try again in a few months, when you can point to a couple of successes.
You might want to start a new collaboration as a monthly thing, rather than weekly. That gives you and the other editors more time to make progress. Also, you might want to focus on articles that are relatively short, and not the subject of any ongoing editing battles. That increases the chances of substantial results.
If you've been reading your way steadily through this book, you probably already have a good sense that there are no absolute rules in a lot of Wikipedia areas. Groups of editors working together is one of those areas. Such activities can be much less formal than WikiProjects and ongoing, listed collaborations.
Wikipedia has a small number of organizations, several of which are mentioned in later chapters of this book. You can see the complete list via the shortcut CAT:ORG. For example, the Typo Team (shortcuts: WP:Typo and WP:Tyop), which began in November 2003 as the Wikipedia Typo Department, "is dedicated to making Wikipedia look more professional by correcting typos and misspellings." As well as an informal members list, the organization has a page containing pledges by a number of editors; for example, to fix all typos immediately.
Temporary, one-time, initiatives by a group of editors are even more informal than organizations. For example, in late August 2007, a proposal was posted at the Village Pump proposals page (shortcut: WP:VP/PR) to standardize the template messages that appear at the top of article pages. (These are templates indicating that the article needs cleanup, needs to be wikified, has its neutrality disputed, and so on.) Within about a month, interested editors had agreed on and implemented changes to all the top-of-page article message templates (sometimes called amboxes), and the initiative was basically over.
If you're inclined to propose a new initiative, task force, working group, or similar project, whether a new organization or a temporary initiative, the Village Pump proposals page is a good place to start. Read the information at the top of the page, and then follow the link to the page of perennial proposals (shortcut: WP:PEREN); you won't get much traction if you bring up something that experienced editors have seen several times before, or if you post to the wrong page. And also post to the talk pages of related instructional pages. For example, a discussion about template standardization occurred at a subpage of Wikipedia talk:Template messages before the first posting about the subject appeared at the Village Pump.
Finally, you can always create a subpage within your user space to start working on an initiative and trying to find other interested editors. In such a case, again, you can post to the talk (discussion) page of the relevant instructional page such as the page Wikipedia talk:Manual of Style, to see if anyone else is interested.
This help page needs to be updated. The reason given is: this manual may contain out of date information, examples or images. Please help update this help page to reflect recent events or newly available information. Relevant discussion may be found on the talk page. (February 2020) |
Everything so far in this book has been about you as an individual editor, working on your own, interacting with others only to discuss problems or changes to articles. But editors at Wikipedia also work together in groups, formal or informal. Not only is there strength in numbers, there's energy and fun. Such group work is one of the things that make Wikipedia as much an online community as it is an encyclopedia.
Most editors edit articles that particularly interest them: articles about television comedy shows; the region where they live; sports; areas of science or technology; history; multiplayer video games; and so on. If you're one of them, the next natural step is joining a topical area WikiProject—a group of editors working on a collection of articles related to the same topic. Or you may take pleasure in a specific kind of editing: fixing footnotes; improving lead paragraphs; or adding geographical coordinates to articles. There are also WikiProjects for editors with such interests.
Although working in WikiProjects is the most common kind of group effort in Wikipedia, there are others: Collaborations are where a group of editors works on a single article for a week, fortnight, or month, and then turns to the next article they choose, often within a broad topical area. Organizations are less formal and less numerous than WikiProjects. One-time initiatives form and end whenever editors see the need and other editors agree to help.
This chapter describes each of these group efforts, and shows you where to get more information about the groups that already exist. And if you don't find a group that covers something you're interested in, this chapter also tells you how to create a group focused on your interest.
There are basically two types of WikiProjects—topical ones that focus on a subset of articles in a particular area (like WikiProject Poker), and cross-cutting ones that could theoretically work on any article in Wikipedia (like WikiProject Guild of Copy Editors).
In all, there are over a thousand WikiProjects (there's no official count), of which about a third are labeled inactive. Over 80 percent of all WikiProjects are topical; the rest are cross-cutting.
WikiProjects that focus on a subset of Wikipedia articles are listed in the main directory, which you'll find at the page Wikipedia:WikiProject Council/Directory (shortcut: WP:PROJDIR). Four major subdirectories are linked to from there:
Each of the four major groupings has hundreds of different WikiProjects in it, but there are definitely gaps—that is, opportunities for additional WikiProjects. That's because there isn't any person or group at Wikipedia responsible for top-down organizing: Every WikiProject that exists is the result of individual editors deciding that they wanted to create it.
Often topical WikiProjects are coordinated with each other when there's potential overlap. Figure 9-2 shows an example.
The 150 or so cross-cutting WikiProjects focus on Wikipedia-wide issues, rather than on a subset of articles in a particular topical area. Most of these fit into two general categories:
And then there are the more or less one-of-a-kind WikiProjects, such as:
Cross-cutting WikiProjects are not just places to do types of work you enjoy, but they're also excellent places to discuss the finer nuances of article construction and how to get the most out of Wikipedia's powerful software tools. If you find a chapter of this book particularly interesting, and want to improve Wikipedia by working in that area, you'll probably find a matching WikiProject. (If not, consider creating one, as described in the section about creating WikiProjects.)
An August 2007 survey of random 100 articles found that more than half had a related WikiProject noted on their article talk page. Thirteen of those article talk pages had two or three associated WikiProjects, not just one. The good news: WikiProjects are important. More than half of articles in Wikipedia have at least one WikiProject interested in improving them. The bad news: Almost half of all articles in Wikipedia are WikiProject orphans—either outside of any existing WikiProject's scope, or undiscovered by the relevant WikiProject.
There's more evidence of the pervasiveness of WikiProjects: Statistics on all Wikipedia articles, as of October 2007, showed that 900,000 had been assessed for quality by WikiProjects (assessments range from stub to featured article), with another 300,000 or so still to be assessed.
Looking at the examples in the section about cross-cutting WikiProjects, it's clear that a WikiProject can aim to improve just about anything on Wikipedia. But the vast majority of WikiProjects focus on articles, and the majority of those focus on articles within a particular topical area. Understanding such WikiProjects will give you a good idea of WikiProjects as a whole.
The first and foremost goal of topical WikiProjects is to improve Wikipedia's coverage of articles within that topic. Most of that effort is aimed at existing articles, but WikiProjects are also involved in creating new articles where needed.
WikiProjects are no more than the sum of the work of participating editors, so a certain amount of effort must be put into recruiting editors and retaining the interest of participating editors. ( Finding other participants and encouraging participation goes into more detail.)
A second role of WikiProjects is to maintain portals, mini-Main Pages which are entry points for particular topics. For example, WikiProject Indonesia maintains the page Portal:Indonesia (shortcut: P:ID) and WikiProject Books and WikiProject Novels jointly maintain the page Portal:Literature.
A third WikiProjects role is to assess the quality of articles within their projects. As of October 2007, an estimated 800 WikiProjects had done assessments (quality of articles, importance of articles, and so on) within their topics. The Version 1.0 Editorial Team (shortcut: WP:1.0) uses these assessments to select articles, and in April 2007 released a collection of about 2,000 articles as Wikipedia version 0.5, on a set of CDs.
A WikiProject's size significantly affects a given project's activities. Some projects have hundreds of members and cover tens of thousands of articles; some have only a handful of members and less than a hundred articles. Task forces (or similar subgroupings) are critical for large projects, while small projects need to minimize administrative housekeeping, instead focusing on working on articles. Still, here are a few things that most projects can or should do:
If you're a member of a WikiProject and hear of something interesting that your project isn't doing, don't be shy about suggesting it on the main talk page of that WikiProject or on another, more relevant talk page within that project. You may end up doing most of the initial work yourself, so avoid suggesting something you don't have the time to work on alone or with one or two others. (If no one else is interested, it's not a crime to drop the idea.)
One way to find a WikiProject you'd be interested in joining is to go to an article of personal interest and check the article's talk page. If the article has a WikiProject banner, follow the link to that WikiProject, and see if you want to join.
The other way to find a WikiProject of interest is to use the page Wikipedia:WikiProject Council/Directory (shortcut: WP:PROJDIR). Start with one of the subdirectories, and drill down until you find something that looks interesting.
Keeping a WikiProject going can be a challenge. After all, Wikipedia editors are unpaid volunteers whose interests and free time can change, so attrition is normal. Successful WikiProjects need to both recruit new members and retain the interest of existing members. If you're in a WikiProject, it's in your best interest to help with both of these.
You might think that recruitment and retention are the responsibility of whoever is in charge of a WikiProject. But the whole point of WikiProjects—and Wikipedia—is that no one's in charge. The Wikipedia community strongly discourages voting, elected positions, and hierarchy; Wikipedia:What Wikipedia is not (shortcut: WP:NOT) clearly states that Wikipedia is neither a democracy nor a bureaucracy. (Some large WikiProjects have coordinators, but they're primarily responsible for administrative housekeeping.)
So if, for example, your WikiProject doesn't have a newsletter, and you want to write one, all you need to do is post to a talk page, saying that you're thinking about doing so, asking if anyone has an objection—or wants to help. If no one objects, then you're now the newsletter editor (or co-editor, if others are interested).
Here is a list of various WikiProjects with links to their participants and bot-generated list of active editors.
There are two standard ways to recruit new members for an ongoing WikiProject:
Less common methods include:
Many WikiProjects have their own welcome template, which is ideal to post to the user talk pages of editors who sign up. If there's no template, you can post a personal note. Making the new editor feel welcome helps encourage active participation.
A monthly newsletter updating editors on progress and plans can encourage editors to spend some time on the WikiProject. Mentioning new members by name is a great way to increase the enthusiasm level. If you want something more than a plain text newsletter, check out sample newsletters from a number of WikiProjects, collected at Wikipedia:WikiProject Council/Newsletters. (One sample is shown in Figure 9-6.)
An announcements page within the WikiProject can be a good way to encourage members to check in frequently. Just don't hide the page away somewhere without putting up clear links to it.
Finally, while it may sound a bit hokey, at least a few WikiProjects have created awards for high participation editors. Having such an award posted on the editor's user talk page is a pleasant surprise and provides reassurance that others in the group recognize the editor's efforts.
A collaboration involves a single article, chosen by editors working in the group doing the collaboration, where editors work on that article for a week, fortnight, or month, and then turn to the next chosen article.
You can see the list of existing collaborations at Wikipedia:Collaborations (shortcut: WP:CO), as shown in Figure 9-7.
Some collaborations involve several WikiProjects, and some are separate entities unconnected to any WikiProject. But most collaborations occur within an existing WikiProject. One reason is that recruiting new members to a collaboration can be difficult, since collaborations don't post templates on large numbers of article talk pages, as WikiProjects do.
Another factor in favor of single-WikiProject collaborations is the process for selecting a new article to collaborate on: Editors whose articles aren't chosen for collaboration may give up, while editors who do continue to push for a particular article to be the subject of the collaboration may find that when it's chosen, hardly anyone else wants to work on it. Drawing participation from a single WikiProject can minimize or compensate for such problems, since project members have a high interest level, and new members are always joining.
The process for starting a new collaboration is basically to create a new page with details about what you have in mind, and then advertise it. You'll find full details in the " Creating a new collaboration" section at Wikipedia:Collaborations.
Given the challenges of keeping the interest of editors, think twice before creating a collaboration outside a WikiProject. Rather, if you're a member of a WikiProject, test out the waters by posting a note on the talk page of that project. If you get only one or two other editors who show interest, perhaps you can collaborate informally, and try again in a few months, when you can point to a couple of successes.
You might want to start a new collaboration as a monthly thing, rather than weekly. That gives you and the other editors more time to make progress. Also, you might want to focus on articles that are relatively short, and not the subject of any ongoing editing battles. That increases the chances of substantial results.
If you've been reading your way steadily through this book, you probably already have a good sense that there are no absolute rules in a lot of Wikipedia areas. Groups of editors working together is one of those areas. Such activities can be much less formal than WikiProjects and ongoing, listed collaborations.
Wikipedia has a small number of organizations, several of which are mentioned in later chapters of this book. You can see the complete list via the shortcut CAT:ORG. For example, the Typo Team (shortcuts: WP:Typo and WP:Tyop), which began in November 2003 as the Wikipedia Typo Department, "is dedicated to making Wikipedia look more professional by correcting typos and misspellings." As well as an informal members list, the organization has a page containing pledges by a number of editors; for example, to fix all typos immediately.
Temporary, one-time, initiatives by a group of editors are even more informal than organizations. For example, in late August 2007, a proposal was posted at the Village Pump proposals page (shortcut: WP:VP/PR) to standardize the template messages that appear at the top of article pages. (These are templates indicating that the article needs cleanup, needs to be wikified, has its neutrality disputed, and so on.) Within about a month, interested editors had agreed on and implemented changes to all the top-of-page article message templates (sometimes called amboxes), and the initiative was basically over.
If you're inclined to propose a new initiative, task force, working group, or similar project, whether a new organization or a temporary initiative, the Village Pump proposals page is a good place to start. Read the information at the top of the page, and then follow the link to the page of perennial proposals (shortcut: WP:PEREN); you won't get much traction if you bring up something that experienced editors have seen several times before, or if you post to the wrong page. And also post to the talk pages of related instructional pages. For example, a discussion about template standardization occurred at a subpage of Wikipedia talk:Template messages before the first posting about the subject appeared at the Village Pump.
Finally, you can always create a subpage within your user space to start working on an initiative and trying to find other interested editors. In such a case, again, you can post to the talk (discussion) page of the relevant instructional page such as the page Wikipedia talk:Manual of Style, to see if anyone else is interested.