Project idea

The idea behind Toolsforge is nice but it also requires the tool creator to be a little bit more of a sysadmin to administer and deploy it to Toolsforge. I present a much more better platform that would be basing on Kubernetes (the same infra cluster Toolsforge rely on) with a Heroku-compatible deployment strategy. Basically how this works is similar to Heroku albeit we change something here: - Define project dependencies in a metadata (package.json, requirements.txt, etc.) - Full utilisation of the multi-container Pods concept. Addons can be defined as standard Docker images (ie, you can define the Docker Redis as an addon) - Private spaces would be a OpenStack Provisioned VM (if project author has WMF Cloud Services allocation) or anywhere where Kubernetes runs - Rich integration with WMF's LDAP and Toolsforge Diffuse repos along with GitHub integration. - Pipelines concept for CI/CD with an additional human approval system (i,e. Allows a more hierarchical flow for CD) This idea can be extended beyond the Wikimedia Foundation namespace too, its up to you how it would feel. If I would to call this, it would be called ToolPilot since basically we're just automating how tools are deployed in WMF.

TBA

TBA