Background: The participation team is using “pilots” to give resources to ideas for new projects. I’ve been working with @bking to figure out good pilots for Community Ops (IT). One that was obvious was WordPress (multi-tenant, multi-site, etc etc) and we started filling out the pilot template (the template makes the case for choosing the project).
Note: that doc is set to anyone with link can edit, so I won’t link to it from here, if you haven’t seen and you should be contributing to it, please ask me for the link.
There has been discussion on that doc about using the same infrastructure as Mozilla. This isn’t a discussion we’ve really had in full as when we started planning on offering WordPress as a service (WPaaS) to communities, that wasn’t necessarily an option.
There are definitely questions to answer about what would be gained or lost over using Mozilla’s infrastructure vs having our own offering. It is also a possibility that Mozilla is going to be moving to wordpress.com instead of hosting in house (I saw this referenced on Governance so I believe this is not secret). Would that affect how communities would feel about being hosted on the same infrastructure as MoCo?
We discussed this a bit at the collaboration meeting today, and captured the questions and thoughts we had in this pad - https://communityit.etherpad.mozilla.org/wordpress
Please feel free to continue this discussion in this thread as well as add any points you may have to the pad.