Re: [9front] Expired SSL certificate

[Kurt H Maier <khm@sciops.net>]

On Sun, Apr 07, 2024 at 09:47:30AM -0700, Lyndon Nerenberg (VE7TFX/VE6BBM) wrote:
> 
> If the hg tree is dead and the commit history is also available
> in git, then yes, I would say decommissioning hg is the right
> thing to do.  That way, if newcomers are exploring for Plan 9
> code, they won't be mislead by ancient creaky code.

This is almost the case.  Two mitigating factors:  

1) 9front's sysupdate utility used to pull from this server, so we left
it online so people who sysupdate infrequently would still be able
to smoothly transition to git, and

2) 9front is not the only repository on the mercurial server, and
people can migrate off it at their own pace (or never, as far as I
care).

> This frustrated me with Plan9port for a long time.  37+ different
> repos ... which one do I believe?

There is no way to make everyone happy.  Even when we had one code
server there were still supergeniuses out there who could not
differentiate between the 9front repository (i.e. the one that had
'9front' in the name) and the other repositories (i.e. the ones that
did not have '9front' in the name).  It's a hard world out there.

The people who benefit from code.9front.org/hg remaining online get
those benefits regardless of the certificate status.  It's no concern of
anyone's else, since the website, documentation, and source code have
all been updated to point to git.9front.org.

khm