Connect with us

NEWS

WikiIndaba’s Survey Leaves Phone Editors Off the Build List

Wiki Mentor Africa’s 93-reply survey, published two days before WikiIndaba, shows 46 people use no tools and 70 hit device limits the named tracks barely touch.

Published

on

46 of 93 African Wikimedians in a Wiki Mentor Africa survey use no tools, gadgets or bots in their work. The analysis was published on 11 November 2026, two days before the WikiIndaba hackathon opens in Abidjan.

70 of 93 said a weak connection or a limited device already decides which tools they can touch. The named project rooms still skip mobile Commons upload and offline editing, the two problems people described in the most detail.

Forty-Six Respondents Do Not Use Tools at All

Wiki Mentor Africa ran the Technical Needs Survey for the hackathon planning committee. The programme’s stated job is pairing African developers with tool maintainers, and the form asked what people already use, what blocks them, and what they would like improved.

Ninety-three people in 12 countries answered between 8 September and 8 October 2026. Two replies arrived after a 7 October close and were kept. There is no response rate, because the organisers do not know how many people saw the form.

Forty-seven people said they use tools, gadgets or bots. Forty-six said they do not. Only 35 went on to name what they use, so the build list for Abidjan is being drawn from a minority of the sample.

TOOLS NAMED MORE THAN ONCE

  • Outreach Dashboard: Six mentions, tied for first, used to track campaigns and student work.
  • Content Translation: Six mentions, tied for first, used to move articles between language editions.
  • HotCat: Five mentions, a gadget for adding categories.
  • Event registration: Four mentions, used to sign people into campaigns.
  • XTools, QuickStatements, Spell4Wiki, Wikidata Query Service: Three mentions each.
  • Broomstick and ISA Tool: Two mentions each; several other tools appeared once.

Seven answers named phones or laptops rather than software. Two named AI assistants. The most-used tools in the sample are campaign dashboards and article translation, which is a different population from the 46 people who never listed a tool at all.

Two-Thirds of the Answers Came From Two Countries

Nigeria supplied 44 replies and the Democratic Republic of the Congo supplied 18. Together that is 62 of 93, or 67%. Six countries appear once each: Rwanda, Burundi, Senegal, Tunisia, Tanzania and Togo. People named 39 groups and could tick more than one.

The analysis itself warns that country-to-country gaps are not reliable. The main findings still held when Nigeria was removed: low connectivity stayed first at 53%, local language support was 41%, and Wikidata tools were third at 37%. Strip out the DRC as well and 31 replies remain, with language support and Wikidata tied for second at 42%.

Most people have been in the movement for 1 to 3 years (38), then 3 to 5 years (21). Seventeen have been in for less than a year, and 17 for more than five. Roles overlapped: 84 editors or content contributors, 27 event or community organisers, 13 technical contributors, and 6 affiliate leaders or board members.

Wikipedia was the home project for 43 people, Wikidata for 28, Wikimedia Commons for 11, and Wikiquote for 7. Wiktionary, Wikisource, Meta and MediaWiki had one each. The form reached working editors. It barely reached the people who keep the software running.

Eight to 10 Minutes for One Commons Photo

When the form asked for the biggest technical gap in a person’s own work, 44 picked low-connectivity and offline editing support and 43 picked local language support. Wikidata and data-quality tools came third, with 30. People could pick more than one, so the counts run past 93.

Seventy of 93, or 75%, said connectivity or device limits restrict which tools they can use. Thirty-five of those 70 also marked offline editing as a top gap. In the free-text comments, 9 of 52 mentioned mobile and 7 mentioned offline use, low bandwidth or a thin connection. The survey did not measure what share of each community edits from a phone.

for each photo, we must manually enter on Commons: the description in French, the categories (e.g. Lubumbashi, Katanga, Markets in DRC), and the GPS coordinates. With an unstable connection and from mobile, this can take 8 to 10 minutes per image.

Survey respondent, Democratic Republic of the Congo, Wiki Mentor Africa Technical Needs Survey

That person asked for a mobile feature or a small bot that would suggest a basic French description and relevant DRC categories at upload, and said it would take them from 10 photos per session to more than 50. A second DRC account, from Goma, said about 80% of contributors there work only on a phone with a limited connection, and that current tools are not built for that. The 80% figure is that person’s estimate, not a count from the form.

From Uganda, another reply said most editors work only from phones with unstable data and asked for lightweight tools that work on WhatsApp or low bandwidth, batch photo cleaning and upload, and support for Runyankore and other languages. An existing product already tries to cover the offline half of that complaint: WikiFundi, a Wiki in Africa project first released in January 2017, offers offline Wikipedia editing without internet from a small local server and a wifi hotspot. It did not appear among the tools people listed, and it is not on the hackathon’s named project list.

Language is the twin constraint. Forty-five of 93, or 48%, said they have avoided a tool because it, or its documentation, was not in their language. Languages named in the replies include Igbo, Igala, Hausa, Swahili, Lingala, Runyankore and French. A Nigeria respondent asked for a tool that can translate several articles on Igbo Wikipedia. A DRC respondent said Content Translation works poorly into French and even less into Swahili and Lingala. A Tunisia respondent wanted better topic search inside the translation tool. A Uganda respondent said some gadgets are not even switched on for small wikis, and that getting help is hard.

Which Projects Did WikiIndaba Pick?

The analysis is explicit that its five focus areas are suggestions, not survey results, and that each one is framed as improving something that already exists. That follows a May 2026 draft from the Product and Technology Advisory Council, which tells affiliates to start by finding and translating tools where possible rather than writing new ones.

The suggestions, in the order of the closed-question counts, were mobile and low-bandwidth use of existing tools; translation tooling for African languages; Wikidata and data-quality tools; event and contributor tracking; and help with references and citations. Twenty-two people also marked onboarding and training tools as a gap, which the analysis said may fit the prep sessions better than the build.

The Meta event page, by 12 November, had already named the rooms. Rather than starting from scratch, it says the event will support, improve and localise existing tools. The rooms that have pages and mentors are Pulac (lexeme-based translation with audio), a Wikidata Reference Validator that flags citation errors, a Community Activity Alerts Dashboard that tracks edits and editors, Source Wiki for checking whether sources hold up, and a fifth room for interface translation whose mentor line is still blank.

SURVEY GAPS AGAINST THE NAMED ROOMS

Survey signal Count Named hackathon room
Low connectivity / offline editing as a top gap 44 None named
Local language support as a top gap 43 Pulac; interface translation
Wikidata and data-quality tools as a top gap 30 Wikidata Reference Validator
Event and campaign organising tools as a top gap 18 Community Activity Alerts Dashboard
Reference and citation tasks in free text 7 Wikidata Reference Validator; Source Wiki
Commons upload, descriptions and categorisation in free text 7 None named

Pulac is a lexeme tool with text and audio, which lines up with two manual-task answers about Igbo lexeme pronunciations. It is not Content Translation, the article-scale tool six people already use and two people criticised. The reference rooms map cleanly onto a Nigeria request for a tool that “helps pinpoint errors in references so as to avoid members from being blocked.” The dashboard room is a cousin of Outreach Dashboard, the other six-mention tool, not a test of whether that dashboard works on a phone.

Mobile Commons upload, the 8 to 10 minute photo, and offline editing have no named room. ISA Tool, a mobile-first Commons tagging app that two people already use, is also absent from the list, even though Wiki Mentor Africa has run ISA hackathons before. The Friday programme does put the Wikimedia Foundation Editing team in the main room for a session on edit check and reference check, which is closer to the Nigeria blocking problem than to the Goma upload queue.

Editors Still Pass Tools by Word of Mouth

The discovery question was answered only by tool users, 46 of the 47. Twenty-three said they find tools through other editors or word of mouth. Seventeen said social media. Fifteen said Phabricator. ToolHub, the movement’s own catalogue, was named by 10. Nine said they do not look for tools at all.

That pattern is the quiet half of the 46 who use nothing. A gadget that never reaches a phone in Goma, or a dashboard that is never mentioned in a WhatsApp group, does not exist for those editors. Improving Outreach Dashboard or Pulac in a Google Meet room will not, on its own, change how the next 46 people hear that the tool is there.

Sixty of 93 named a manual task they would like a tool, bot or feature to take on. Seven of those were “none” or unclear. The other 53, coded one theme each, clustered on translation (9), references and citations (7), Commons upload and categorisation (7), and event and contributor tracking (6). Wikipedia categories, spelling and grammar, and Wikidata lexemes and queries had three each. Offline editing appeared once as a coded theme, even though it dominated the closed-question gaps, which is a reminder that people describe the same pain in different boxes.

Fifty-two people left a final comment; 26 were “no” or “nothing.” Nine asked for training, onboarding, documentation or beginner-friendly tools. One wrote that new contributors face a large gap in how to use technical tools and asked for dedicated training sessions and hands-on workshops. Another, in the DRC, wrote that hackathons could be connected to longer-term technical support so prototypes become tools communities actually keep.

Eighty-Three Offers of Help Rest on 13 Technical Contributors

Interest in the event is not the shortage. Eighty-seven people said yes to joining the WikiIndaba hackathon and/or the Wiki Mentor Africa End of Year Hack Challenge 2026, with 4 maybe and 2 no. On the separate question that began “If you have technical skills,” 83 said they would give time to develop or improve tools for the region, with 9 maybe and 1 no.

The form did not ask what those skills are. Thirteen people described themselves as technical contributors: 11 yes, 2 maybe. Among the other 80, 72 said yes, 7 maybe and 1 no. The analysis says the yes answers cannot be read as a count of available developers.

WHO THE FORM ACTUALLY REACHED

  • Sample: 93 self-selected replies from 12 countries, with no response rate.
  • Tool use: 47 use tools, 46 do not; 35 named a tool.
  • Builders on the form: 13 technical contributors, 11 of them willing to help.
  • Hands raised: 83 yes to giving time, including 72 people who did not call themselves technical.

The public posts around the conference on 12 November were travel notes, not tool complaints. Wikimedia South Africa wrote that Afrikaans Wikipedians are heading to WikiIndaba 2026. The 8 to 10 minute Commons upload did not show up in that feed. The people who can post a departure photo are not the same population as the people who asked for WhatsApp-weight upload tools.

Goma Gets a Room With Power and Internet

The hybrid hackathon in Abidjan runs from 13 to 15 November 2026 inside WikiIndaba, which Wikimedia Community User Group Côte d’Ivoire is hosting under the theme Africa’s Future: Knowledge Equity and Innovation. Working languages are French and English. The event page listed 389 participants. Benedict Udeh opens the hackathon at 13:30 UTC on 13 November. Tool pitches follow, then team formation. The showcase is 13:15 to 14:15 UTC on 15 November in the Akwaba ballroom, with remote dial-in.

Satellite sites are the other half of the design. Each one is billed as a room with internet and power for people who cannot be in Abidjan. Goma is on that list, at Afrix Global in Goma Commune, North Kivu, on 13 and 14 November, in the same city as the account that said about 80% of contributors work only on a phone. Nigeria has three listed sites, in Dutse, Abuja and Abia State, matching the country that filled 44 of 93 survey slots.

THE ROAD TO ABIDJAN

  1. 8 September 2026: Technical Needs Survey opens.
  2. 7 November 2026: Pre-hackathon preparation sessions.
  3. 10 November 2026: Project focus and satellite locations announced.
  4. 11 November 2026: Survey analysis published, 93 replies from 12 countries.
  5. 13 November 2026: Hackathon opens in Abidjan and at satellite sites including Goma.
  6. 14 November 2026: Internet scholarship window scheduled to close; satellite hosting continues.
  7. 15 November 2026: Teams present in the Akwaba ballroom.

Other listed satellites include Gaborone, Kigali, Arusha, Douala, plus Accra and Zanzibar still marked TBD. An internet scholarship application was left open through 14 November, which is a direct answer to the connection problem and not a software patch. The Goma room can put power and a link under people who already edit from phones. It cannot, in two days, cut an 8 to 10 minute Commons upload to something a session of 50 photos can survive, and it cannot put ToolHub in the WhatsApp thread where 23 of 46 tool users still hear about new software.

The form showed needs. It did not show which existing tools can be extended or who maintains them, and the analysis said that check still had to happen before the planning committee committed. The rooms that did get names lean toward lexemes, citation flags and activity alerts. The 46 people who use no tools, and the Goma and Uganda editors who described the phone as the whole workplace, remain the parties with the most to gain if a prototype leaves the ballroom with a maintainer attached.

Harry is the editor and lead writer of CUMBERNAULD MEDIA, which he runs as an independent publication after a decade in journalism spent moving from reporting to editing. His habit is to open the document before the summary of it. A company result is read from the filing rather than the press release, a court or regulatory decision from the judgment itself, a scientific finding from the paper and its methods section rather than the headline claim, and a sporting sanction from the governing body's own ruling. That approach shapes coverage across news, business and technology as much as science, sports and entertainment, and it carries into the lifestyle, travel, auto and gaming pages, where product specifications are checked against the manufacturer's sheet and, where possible, against Harry's own testing. Every number is checked before publication, and where a source's figures are disputed the story says so. Corrections follow a public policy and are marked on the page. Readers anywhere in the world who write in get a reply from him, and the address is support@cumbernauld-media.com.

Click to comment

Leave a Reply

Your email address will not be published. Required fields are marked *

Trending