The participants of the survey are the members of the Wikimedia Toolforge project and Cloud VPS project administrators. 1825 participants were contacted via email. The emails were harvested from the Cloud Services' LDAP system ("developer accounts") and the Wikitech database. The final list was created by finding the union of the members of the Toolforge project and all users with "administrator" rights on one or more Cloud VPS projects. Users who have opted-out of email contact by other users in their Wikitech preferences or the survey specific opt-out page were excluded. Specific opt-outs for the Annual Survey can be made by users at wikitech:Annual Toolforge Survey/Opt out.
137 email recipients participated in the survey which represents 7.5% of those who were contacted.
The survey included several free form response sections. Survey participants were told that we would only publicly share their responses or survey results in aggregate or anonymized form.
If we could improve one thing in Toolforge in the next year, what should that be?
Responses to this question were varied, here is a summary of the comments clustered in different areas:
Improving documentation for beginners
Updating and removing outdated documentation
Better documentation for batch jobs / cron workflows
More responsive help desk
Help to beginners, people getting started
Centralized support site/forum
Development / Production environment parity for developing
Cross DB joins
Stability (breaking changes)
Usage for jobs is hard
Language / Version support
Ruby on Rails support
Logs and emails from cron jobs
Health checks and alerts
Show general service availability
If we could improve one thing in Cloud VPS in the next year, what should that be?
Thank you for those who answered positive comments and praise, it is very much appreciated.
There are less responses in this question, so the summary will be less detailed.
Better deployment workflows
Managed Kubernetes clusters
If you would like to share more about your experience finding, reading, or maintaining technical documentation on Wikitech, please do so here.
Hard to understand
Beginner documentation is very hard to understand
Needs more graphics
Cloud VPS docs are harder to understand than Toolforge's
What should I use? What is supported?
Reference lists for features, instead of all tutorials
More documentation about effective workflows
Out of date
Self-study is very hard, complicated to navigate the docs (guided-study is not so bad)
If you have any other comments, please share them with us here.
There were many praise responses, thanks a lot, they are very much appreciated.
Besides those, there were some comments about language/framework support, using propietary software for this surveys instead of OSS, and a variety of comments about topics mentioned in the other freeform questions.
Is there anything you have tried but not been able to do in Toolforge?
The responses here were very varied, the ones mentioned several times were:
Improve language support and use newer versions of languages and applications
Memory intensive work on Toolforge. People end up moving to Cloud VPS for these
Remote access issues (SSH, SFTP, etc.)
Analysis work and very CPU/IO intensive programs
Problems with blocked IPs
The rest were single comments and in interest of anonymity won't be detailed here.