qna was created in T180662: Request creation of qna VPS project but in the end I never found the time to work on it and in the meanwhile work on Discourse has progressed so far that there is probably not much point in doing it any more, so I'm relinquishing it. See T181377#4844844 for more details.
Some VMs in the qna project have been used for Meza testing, that needs to be ported to its own project first.
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | Andrew | T212657 Close qna VPS project once Meza functionality has been ported to its own project | |||
| Resolved | • Bstorm | T212918 Request creation of meza VPS project |
Oh huh, looks like someone is using it for meza tests. Let's put this on hold while that's sorted out.
@CCicalese_WMF @Jamesmontalvo3 @Darenwelsh that's one of you, right? Are those boxes still needed? Would it be hard to move them to a dedicated meza project?
@Jamesmontalvo3 has been using qna. He has gotten meza to build a debian-based MediaWiki environment on VMs in this project. I have already been able to reproduce his success on a VM in my pluggableauth project. Continuing this work on a dedicated meza project should be possible.
Hello! The title of this looks like an action item ('delete qna project') but I'm not clear if that's right -- are you ready for me to delete the project or are there other things that need to happen first?
@Tgr, @Jamesmontalvo3, @Darenwelsh: 7 months later... meza is empty and qna is hosting 2 instances and 2 HTTP proxies. What's the status of migrating the work to its dedicated project?
(I'm less confident about the "not much point in doing it any more" part of the task description now, but definitely not something I'll have time to work on anytime soon.)
Mentioned in SAL (#wikimedia-cloud) [2019-12-31T12:35:14Z] <andrewbogott> deleting project as per T212657