What problem would this feature solve? ====================================== Setting up a Kuma build environment, while easier than in the past, is stil non-trivial and requires a lot of resources. This a large hurdle for potential contributors, especially if they do not have access to a development-class computer. Who has this problem? ===================== Core contributors to MDN How do you know that the users identified above have this problem? ================================================================== Anecdotal evidence from staff and volunteer developers. How are the users identified above solving this problem now? ============================================================ Following this 12?-step procedure: https://kuma.readthedocs.io/en/latest/installation.html Do you have any suggestions for solving the problem? Please explain in detail. ============================================================================== https://janitor.technology/ provides cloud-based development environments for open source projects, as well as support for typical operations, so users don't have to spend lots of time reading project-specific docs. Is there anything else we should know? ====================================== Contact email@example.com, who is the maintainer of the projecgt.
This is cross-filed at: https://github.com/JanitorTechnology/janitor/issues/24#issuecomment-306900988 I haven't used Janitor, but it sounds promising for many users (older equipment, Windows, low-bandwidth). One potential issue is that Kuma uses multiple docker containers for development, and Janitor uses Cloud9 instead. jgmize is proposing a Kubernetes implementation that would help: https://github.com/mozmeao/infra/issues/29 I believe this would be a large effort for staff, and it would need to be a quarterly deliverable to make it happen, so it will be a while. This would be a great community project, and would help many MDN contributors.
Whiteboard: [specification][type:feature] → [specification][type:feature][points:6+][lod:4+][patchwelcome]
You need to log in before you can comment on or make changes to this bug.