So I spoke with Daniel Stone today about the infrastructure. He estimates it will be ready to deploy the website in 2-3 weeks, at the most. So I'd say the infrastructure will be there when we are ready.
In the new system, our website will be running in its own container managed by freedesktop's new Gitlab server. So what we need to do for the deploy is: 1. Fork mesa into a repo on Gitlab.com (https://gitlab.freedesktop.org). 2. Create a .gitlab-ci.yml file which compiles the website from the files. (https://docs.gitlab.com/ee/ci/yaml/). In order to get the files ready, we need to make sure that they are rebased on top of Mesa master and reviewed. I started rebasing here: https://cgit.freedesktop.org/~ldeks/mesa?h=website2. That preserves the git history well, but if it's not a big deal to everyone else, we could just rebase Jean's branch. I don't think much has changed. Thanks. Laura On Thu, Apr 5, 2018 at 11:18 AM, Emil Velikov <emil.l.veli...@gmail.com> wrote: > On 5 April 2018 at 19:10, Laura Ekstrand <la...@jlekstrand.net> wrote: > > Emil, > > > > Specifically, what infrastructure do you need? Gallium is already > carrying > > Sphinx around as a dependency. > > > The gallium docs are hosted on readthedocs.org. And I doubt we want to > move the main mesa3d.org website there ;-) > Currently mesa3d.org, most graphics stuff and others are on > freedesktop.org infrastructure. > > HTH > Emil > P.S. Can I buy you to use interleaved posting/plain text email, please? >
_______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
