It's a valid question.
My opinions follow. I don't have all the information, so this should be taken as guesses.
I am one of the most active here right now. I can tell you that I check in at the LibrePilot slack.com page about every day and even though most of the developers that I see there are in European time zones, I catch one or two logged in sometimes (once or twice a week) when I am there. Truthfully, I don't see them posting much there. I would say there are probably 4 or 5 devs that I see this way.
There have been about 4 new bugs / features entered in tracking so far in 2020 and a different 4 bugs / features have been coded in 2020 with a pull request generated. There are about 15 total outstanding pull requests. There have not been enough devs who felt expert enough or who had the time ... to generate the necessary number of confidence votes for these pull requests to be merged into next. Thus the version of next that we have does not have this code in it.
The most recent version on the 'next' download page
https://librepilot.atlassian.net/wiki/spaces/LPDOC/pages/263913473/Next+Downloadsis r782
The current version of next source code is r796, but the 14 change sets from r782 to r796 are probably not very important to the average user (as documented elsewhere where I recently documented the differences).
I personally have some projects that I want to work on, but haven't spent much time. I suspect that several other devs are in a similar boat. I would have guessed that Covid-19 would have caused more dev-hours to be spent on LibrePilot, but personally I don't see it, but then I don't peruse the private code branches to see who may be doing what.
I haven't discussed what I have been playing with because I don't want to get anyone's hopes up. A couple useful things I have done this year are the CC3D save settings fix (firmware posted elsewhere) and an OpMap (GPS map) fix that allows you to replace map tiles where with the current code you can't replace tiles without starting over. These are not even in next yet. I would like to better understand and document heli setup. I would like to code a new fixed wing path follower that is easier to understand, tune, and use; and that can fly more radical flight plans if the airplane is capable of radical flight. Maybe AutoTune for fixed wing. Certainly at least for heli. In the more distant future, I would like to code computer vision as a GPS replacement and as obstacle / crash avoidance and auto-land. This is years worth of stuff.
In the old days we had a test team, but for the last several years we have just made available 'next' versions because we didn't have anyone with the spare time, energy, and desire to whip up the users into a test team and to get the devs to finalize the work they wanted to include.
So after all that, I must say that it could go either way or anything in between. The best would be a resurgence leading at least to more code and more next's. The worst would be a quick loss of servers and not enough interest to move to new servers.