Change or add user "Wargo" as a maintainer of instance holding Wikimedia Space (Discourse). This service seems abandoned but users liked it.
- Mentioned In
- T262275: Decide what to do with [read-only content on] discourse-mediawiki.wmflabs.org
- Mentioned Here
- T225081: Request creation of Discuss VPS project
T225082: Request creation of Blog VPS project
T235235: Document data backup and disaster recovery plan for https://space.wmflabs.org and https://discuss-space.wmflabs.org
A change in project admins is outside the scope of the Cloud-VPS (Project-requests) process. The Toolforge-standards-committee exists to handle this sort of thing in the Toolforge project, but only for abandoned tools. We don't have any similar system for Cloud-VPS projects today.
The Space components were originally requested as a temporary proof of concept area (T225081, T225082). The Discourse instance in question actually was created in the discourse Cloud VPS project, so @Samwilson, @Tgr, @Qgil, and the other admins in that project need to evaluate this request and determine if they are willing to take on another co-maintainer or make data dumps available to recreate the instance in another project with more narrow scope.
Hi @Wargo !
Just a quick note now to say that we will need to do some homework in order to have answers about a couple of important questions that at least I don't know the answer right now:
- As of now, whoever has admin rights in that Discourse instance has access to the email addresses of all the registered users. Until now admins (and instance owners) have been Foundation employees. What are the legal / privacy implications of volunteers taking over?
- Even if the legal / privacy aspects were solved and we would be able to transfer ownership to non-Foundation staff members, I guess the current Space users wouldn't be fine with us just giving the keys to whoever shows up first. Is there a need for some kind of community process to vet / approve who gets root access to the instance and/or admin rights to Discourse?
To be clear, none of these points are specific to Wargo or even specific to Discuss Space. I guess we would hit the same questions for anyone willing to take over the administration of any project.
PS: I think this discussion would have a much better context in Space itself! For most Space users Phabricator is not a familiar place to follow and participate.
Presumably the Cloud VPS TOU covers that?
Even if you've never explicitly named a volunteer as an admin of a specific
project within Cloud VPS, there will still be volunteers with root access
across *all* Cloud VPS projects.
There needs to be a clear plan that combines guidelines for granting administrator permissions to certain users and a process that protects the privacy of existing Space users (whose data can be accessed by admins).
As current maintainers of Discuss Space, we are not attached to any specific plan. Please discuss in the topic above, since this is where most Space users will see the discussion and be more likely to participate.
Made a proposal. Tl;dr: some of the current admins are interested in helping to run the site as volunteers (our involvement has always been in a volunteer capacity); provide a way for people who expected Space to be a WMF project and not a volunteer project to get all their data deleted (on an opt-in basis, so if you don't do anything your data gets deleted); agree on requirements for adding new admins after that (I'd imagine it would require a volunteer NDA).