Learning patterns/Let the community know
What problem does this solve?Edit
A party that no one attends isn't much of a party. A wikiproject with no active members is a dead project. A new tool is only useful if people know that it exists, and want to use it.
Careful planning and hard work are not enough. However awesome your project idea is, the success of your project depends at least in part on other people. A community project needs a community.
What is the solution?Edit
Figure out who you want to help with your project, and who you are doing it for: who is your target audience? Who has expertise that you can benefit from? Who shares your interests and might want to work with you?
Brainstorm ways of reaching these individuals and communities, and contact them with specific requests or general notifications. Especially during the formative stages of a project, there's really no such thing as too much feedback. Use multiple communication channels whenever possible: post to community noticeboards and email mailing lists, invite people to join social media groups for your project or event. Make sure that people have a way of contacting you back to ask questions or get involved. Keep a record of people who have expressed interest in your project, so that you can contact them again.
Include an outreach strategy in your project plan. Include your answers to the questions above, and your initial ideas for how to accomplish your participation goals. Be prepared to revisit this plan on a regular basis as you work on your project and ask yourself whether you have done enough outreach, and received enough responses, that you are still confident that your project will be successful.
- Let the right community know. If you want a certain type of person or community to get involved, reach out to them specifically. The WikiArS project reached out to aligned WikiProjects, to identify "image gaps" in their subject domains, rather than just posting notices to the Village Pump. On the other hand, the MediaWiki Data Browser project struggled to gain adoption among its intended user base in part because users were not aware of its existence.
- Let the community know at the right time. The PRChina project organized a series of 5 meetups on college campuses throughout China early on in the project. Holding these meetups early allowed this project to advertise its online resources among its target demographic and to brainstorm ideas for upcoming social media campaigns.
- Provide incentives. In WLMTH2014, we give small souvenirs/certificate as incentives for people to to volunteer their time to the contest.
- Use medias as a tool. Medias could be a good tool to spread the word outside of the Wikimedia movement. For projects like Wiki Loves Monuments or Wiki Loves Earth this is a key element. In these kind of projects we have to balance between the Wikimedia community and people outside the community.
- Use as many tools as you can. Don't be shy. Use all tools you have to reach the community out. A banner on Wikimedia projects is the most powerful tool we have to reach people out. Before creating a banner, ask the community how to create it and in which cases it is allowed. In case you can not use it, do not ignore the rules. You have other options. Other ways to reach people out are mailing lists, social networks, medias or village pumps and embassies at the projects. Before paying for an advert, be sure you have used all of them.
- Learn about which channel was most effective. If you use a registration form before the event or a survey after that, ask people how they find the event or project out. That will let you know which channer was better or had more impact to focus on it for next events or change your strategy.
- Post your event on Wikipedia:Meetups.
When to useEdit
- Like many Wikimedia processes, Individual Engagement Grants require community notification and discussion before a decision can be made. Being proactive about inviting people to discuss your project is likely to serve your project well. For IEG proposals, we suggest starting discussion by posting a notification in a venue appropriate to your project's target community - a Village Pump, mailing list, or wherever else people who will be interested or impacted by your project may gather. In the notification, include a link back to your grant proposal so they can learn more about the project and share feedback or endorsements if they want to.
- Jmorgan (WMF)
- eranroz (talk)
- Ravid ziv
- Leutha (talk)
- Very important part to any project that relies on a large community to support the project. Rebecca Cotton (talk) 21:37, 18 February 2015 (UTC)
- Inviting others to join in the party planning! DrMel (talk) 05:48, 1 April 2015 (UTC)
- --アンタナナ 19:44, 6 April 2015 (UTC)
- This is an important pattern for Grants:IEG/Revision scoring as a service, considering that the success of our project also depends on the participation of volunteer members of the communities (e.g. to label revisions which are used to train Machine Learning models). Helder
- The WIGI project, is creating a new tool and wants to let people know about it. We find that email and twitter are the best ways to get a word out. Also, don't forget blogging, we use our own notconfusing.com and are hoping also to be able to write a guest post at blog.wikimedia.org. Maximilianklein (talk) 22:09, 21 August 2015 (UTC)
- StrepHit has benefited a lot from early community outreach Hjfocs (talk) 14:25, 11 April 2016 (UTC)
- je cherches encore Papykabi (talk) 12:24, 9 June 2016 (UTC)
- Ana,GIS aislante saasaos altamisa — The preceding unsigned comment was added by 126.96.36.199 (talk)
- SuperHamster, on behalf of Wikipedia Connection
- Many good tips here – take notice of those who express an interest and keep them in the loop, you'll get invaluable help later. Unhammer (talk) 10:45, 13 June 2016 (UTC)
- Sejal Khatri
- In the Web2Cit project our Advisory Board is one of the ways we have to let the community know about relevant project news and events. Diegodlh (talk) 12:15, 28 March 2022 (UTC)
- Founding WMBE we had the problem that different groups preferred different channels - mailing list, social networks, wiki, direct messages. This lead to some misunderstandings between community members. We've decided that there must be central communication channel that is always updated and official to ensure information coherence. This channel should be accepted by most. Additional channels are necessary, but must act as "additional broadcasts" of the central information. For WMBE we decided to build up a front-end website to act as the core channel.
- The project "Script encoding proposals for Nepal" set up a webpage seeking viewpoints from the members of the user community in Nepal. This Nepal Bhasa Wikipedia page queried the community on their opinion regarding the need of getting their scripts into the international standard Unicode (which was a proposed Wikimedia project) . Once the project was approved and a meeting was set up, a supplemental Meeting page was added. It identified the meeting location, schedule, and links to documents. There was also some email interchange with others, notifying them of the meeting, but the email included a link to the Meeting page.
- At the photo contests grant reports of WLM Spain 14, WLM Spain 15 or WLE Spain+Portugal 15 you can find which tools Wikimedia Spain used to reach participants out.
- This is an important step when the success of a project also depends on the participation of volunteer members of the communities. In the case of the IEG revision scoring as a service, volunteers were contacted for labelling a big number of edits, something that would be harder to accomplish without their help.
- Outreaching very early to relevant communities has played a crucial role during the planning phase of the StrepHit IEG project: it has enabled very insightful discussions with people who provided active feedback. Moreover, it has helped the identification of key people: setting up face-to-face meetings with them has also proven incredibly constructive.
- For Wikipedia Connection's Art+Feminism 2016 Edit-A-Thon at the Ohio State University, we had to reach out to the Ohio State and Columbus community to find participants and gain exposure. Some of the steps we took from within the university were to personally invite art professors and ask them to invite others that may be interested; forward an informative email to various departmental listservs (e.g. art department, English department, journalism, etc.); and hang up fliers across campus, especially focused within art/language buildings and libraries. We also reached out to the greater Columbus community by locating and contacting various art groups, such as CAW! Columbus. Finally, we also engaged social media by making various posts from our Facebook page and paying to boost those posts to targeted people in the Columbus area who had an interest in art, Wikipedia, and Ohio State - this was effective at getting viewership, but not very effective at getting people to attend. Overall, our efforts to let the community know paid off to get people to both come and be aware of our event and organization.
- When we started thinking about the Pan-Scandinavian Machine-assisted Content Translation project, we didn't even know about IEG until we contacted other local Wikimedia members; these people later became important in both spreading the news and evaluating the system, and we tried keeping them in the loop while updating others from the same and related wikis.
- ↑ Individual Engagement Grants: 2013 Program report
- ↑ Individual Engagement Grant: Consolidate wikiArS to involve art schools. final report
- ↑ Individual Engagement Grant: MediaWiki data browser. final report
- ↑ Individual Engagement Grant: Build an effective method of publicity in PRChina. final report
- ↑ a b Grants:PEG/WM ES/Wiki Loves Monuments Spain 2014/Report
- ↑ Grants:IEG/StrepHit:_Wikidata_Statements_Validation_via_References/Midpoint
- ↑ Grants:IEG/StrepHit:_Wikidata_Statements_Validation_via_References/Final
- ↑ Grants:PEG/Wikipedia Connection/Semester Funding for Workshops and Events/Report
- ↑ Grants:IEG/Pan-Scandinavian_Machine-assisted_Content_Translation/Final