On Sat, 18 Sep 2021 12:39:40 -0600 Bryan Petty wrote:
BP> On Sat, Sep 18, 2021 at 7:03 AM Igor Korot <
ikor...@gmail.com> wrote:
BP> > This is not the first outcry about the forum.
BP> > It looks like Bryan is very busy at work and don't have time to look at this.
BP>
BP> Yeah, I don't have nearly as much time or motivation to maintain these
BP> servers as I used to, and it really is a significant amount of work.
I understand this perfectly and I know (probably better than anybody else
considering the number of times I've bothered you during all these years)
how much time you've already spent on it -- and, of course, am very
thankful for it! The question is whether somebody else can help with it or
if we really need to migrate to some hosted solution. Of course, I'd rather
not start changing this now and concentrate on releasing 3.2 instead, but
OTOH it's probably never going to be a good time to do it anyhow, so maybe
we should do it now...
BP> There's tons of regular maintenance backlog to catch up with on this
BP> server, and I can imagine this error might just resolve itself
BP> entirely if I could find the time:
BP>
BP> 1. The server is running completely out of date (and EOL) Ubuntu with
BP> EOL PHP as well.
BP> 2. The next major version update available for the forums requires
BP> newer PHP than the server is running.
BP> 3. Upgrading the server not only requires upgrading phpBB on the
BP> forums, but also upgrading MediaWiki for the wiki at the same time,
BP> which is in the same situation as the forums.
BP>
BP> All of this is one large move that's likely to involve significant
BP> down time, and likely break a bunch of things that will require
BP> additional follow-up, and that's why none of it has happened yet, even
BP> though it's been necessary for a couple years now.
I wonder if we could create a new server (it's a VPS, isn't it?) and move
things there piece-wise?
BP> Of course, none of this is nearly as bad as the situation we're in
BP> with Trac, which I'd say is nearly dead in the water. The Trac project
BP> itself is barely "maintained" these days, and regardless, we've been
BP> stuck on a 1.0.x release that's over 4 years old now, since 1.1+ (and
BP> they're out with 1.4 now) breaks a handful of our extensions,
BP> including the core ones that have been very popular for many Trac
BP> sites that we use for user registration and authentication. Honestly,
BP> wx should just enable GitHub issues, and start migrating things over,
BP> so Trac can just be retired entirely.
I didn't want to have all our eggs in GitHub basket, but by now we have
not only Git there, but also 99% of the CI jobs, which are even more
critical, so I guess we could migrate from Trac to it too. Especially
because GitHub Issues gained some functionality since then, e.g. they now
allow setting milestone for the tickets which is quite useful. I wonder if
anybody here has any experience with Trac-to-GitHub migration? There seems
to be quite a number of tools for doing it.
Using the same logic, we might even migrate the forum to GitHub
discussions, but having barely used the former and never the latter I don't
know if it's really a good idea.
Finally, I wonder if we could host our documentation on GitHub Pages too?
VZ