[geos-devel] PSC Vote: Host geos.osgeo.org on GH pages

Sandro Santilli strk at kbt.io
Tue Aug 24 09:22:28 PDT 2021


On Tue, Aug 24, 2021 at 07:55:41AM -0500, Howard Butler wrote:
> 
> 
> > On Aug 24, 2021, at 5:10 AM, Sandro Santilli <strk at kbt.io> wrote:
> > 
> >> You guys hate the evil GitHub empire, but the way to do this is to create a GitHub action that pushes the site whenever  the branch that contains the active docs is pushed. See PROJ, PDAL, GDAL, and others for examples of this pattern working successfully for large projects.
> > 
> > There's no hate on my side, just love for independence :)
> > 
> > I debate there's one "way to do this", luckly for all of us.
> 
> One of the many advantages of the GDAL, PDAL, and PROJ documentation setup is we practically never have to mess with it. It just works. When it doesn't work, or when someone wants to make a documentation contribution, anyone can do so with a pull request and iterate until they succeed. No special access or special knowledge required. 

"It just works" is not true, GitHub breaks too.
When it doesn't work, if it's GitHub we can only wait for them to fix
it, if it's our machines, we can do something.

About contribution: anyone could do pull requests and iterations on
Gitea as well, access needed in both cases (in the Gitea case it would
not be "special" as it would be the same one used to file tickets, in
the github case it would be "extra" account).

Knowledge required in both cases (knowledge about an opensource
technology in one case, about a closed source technology in the
other).

> Additionally, GEOS should house its documentation at a top level
> domain (like libgeos.org or something) rather than a subdomain of osgeo
> (ala geos.osgeo.org).

This is completely unrelated to the comparison of self-hosting vs.
proprietary-infra-hosting.

--strk;


More information about the geos-devel mailing list