Miraheze-6-year/Survey

Similar to the 5-year survey results, we will compare this year’s results to last year’s results.

Readers
The number of readers who completed the survey is 101 (up from 89 last year). The most popular genre of wiki for readers are gaming wikis – coming in at 60% of respondents. Last year gaming wikis only represented 39% of all responses! 51% of respondents say they access Miraheze at least once a day – this is consistent with last year’s results.

36% of respondents know that Miraheze is funded by donations only, this is a decrease from 40% last year and from the year before of 52% Future provisions of Miraheze may depend on increasing this knowledge. 39% of respondents know Miraheze is running only by volunteers, this is also a decrease from last years’ figure of 43%. 47% of respondents are aware that they could volunteer to support Miraheze, which is up from 45%. 45% of respondents are aware of Miraheze’s strong privacy stance, which is up significant from 36% the year before. 10% can find Miraheze’s financial information – down from 35%.

First comparison data for new questions asked last year: 66% of respondents said they are satisfied with their interactions with the community (down from 69%) while 67% are satisfied with Site Reliability Engineering interactions (up from 65%). 81% of respondents are also happy with Miraheze’s uptime, up from 69%. 78% are happy with the speed of the service, up from 74%. Overall, 79% are happy with the overall experience – up from 75%. When asked about the interface, 97% said it was designed well for their purposes.
 * 12% of respondents know Miraheze registered as Miraheze Limited, down from 26% last year.
 * 16% aware of community-elected positions, down with 21%.

Editors
The number of editors who completed the survey is 40 (same as last year). Unlike last year, the most popular categories of wikis are gaming, politics, and art-based wikis each at 20%. Community wikis have gone down significantly in popularity over the last year from 38% to 2%. 58% of respondents say they edit Miraheze at least one a day – this is up from 35%.

48% of respondents know that Miraheze is funded by donations only, this is a decrease from 53% last year. 40% of respondents know Miraheze is running only by volunteers, this is a decrease from last years’ figure of 63%. 50% of respondents are aware that they could volunteer to support Miraheze, which is down from 60%. 58% of respondents are aware of Miraheze’s strong privacy stance, which is down from 73% the year before. 22% can find Miraheze’s financial information – down from 35%.

First comparison data for new questions asked last year: 60% of respondents said they are satisfied with their interactions with the community (down from 73%) while 63% are satisfied with Site Reliability Engineering interactions (down from 70%). 78% of respondents are also happy with Miraheze’s uptime, the same as last year. 83% are happy with the speed of the service, up from 73%. Overall, 78% are happy with the overall experience – down from 88%. When asked about the interface, 85% said it was designed well for their purposes.
 * 40% of respondents know Miraheze registered as Miraheze Limited, down from 43% last year.
 * 27% aware of community-elected positions, down with 33%.

Advanced Users
The number of advanced users who completed the survey is 110 (down from 111 last year). The most popular genre of wiki is gaming at 25%. 48% of respondents say they edit Miraheze at least one a day – this is down from 56%.

86% of respondents know that Miraheze is funded by donations only, this is an increase from 73% last year. 76% of respondents know Miraheze is running only by volunteers, this is a decrease from last years’ figure of 78%. 82% of respondents are aware that they could volunteer to support Miraheze, which is up from 68%. 85% of respondents are aware of Miraheze’s strong privacy stance, which is up from 73% the year before. 56% can find Miraheze’s financial information – up from 52%.

First comparison data for new questions asked last year: 76% of respondents said they are satisfied with their interactions with the community (down from 81%) while 75% are satisfied with Site Reliability Engineering interactions (down from 80%). 81% of respondents are also happy with Miraheze’s uptime, up from 75%. 95% are happy with the speed of the service, up from 73%. 86% were happy with the speed of wiki creation (up from 84%) and 50% were happy with task resolution (down from 51%). Overall, 93% are happy with the overall experience – up from 85%.
 * 68% of respondents know Miraheze registered as Miraheze Limited, up from 60% last year.
 * 51% aware of community-elected positions, up with 47%.

When asked about the interface, 95% said it was designed well for their purposes.

ManageWiki
76 Advanced users have used ManageWiki (69%). Of those who have:
 * 80% said it was easy to use. This is only slightly down from 81%.
 * 80% said it provided the flexibility they needed. This is up from 75%.
 * 83% said it provided a level of control they needed. This is up from 75%.
 * 84% said it made Miraheze unique. This is up from 74%.

Issues Identified

 * Dark Mode is a poor feature for maintaining image contrast
 * ManageWiki interface seems clunky – many steps for one change. Similarly, changes with the UX happen without notification and usually with a detrimental impact on communities
 * Caching updates take a long period of time
 * Slow access times from Asian countries
 * LaTeX support is poor
 * Volunteering opportunities are poorly advertised – most do not know they exist until they are already doing them

Suggestions

 * Add CirrusSearch
 * Mobile App
 * Monthly/Weekly update communications from SRE (plus maybe big community things too)

Misc Comments

 * Team-based drama has a negative impact on community perception (SRE)
 * Constantly telling users ‘We are volunteers’ when justifying no responses in the periods of weeks has a big negative impact on retention, recruitment and wellbeing of communities
 * Seemingly a ‘community’ vs ‘SRE’ stance, as the community are held accountable, but SRE are not by the same standards
 * Large changes are pushed without proper community engagement – sometimes leading to a large learning curve and instability caused by communities having to adapt to changes they find detrimental