How to overcome VB death?

So, according to this post https://devblogs.microsoft.com/vbteam/visual-basic-support-planned-for-net-5-0/ on Microsoft's Devblog, VB.NET will be added to .NET 5 in a limited scope, but that's that. There's gonna be no further development of the language. VB has never had so much noise around itself as C# had, yet features have been added and language kept evolving. So relative silence about new VB feature maybe was not a warning sign for many. But the truth is that we didn't get parity of some cool features of C# which can mage language interoperability a problem (e.g. method implementation in interfaces).

I'm starting this thread to figure out what can be done to keep the best (.NET) language from dying.

a) Is there anything that can be done to reverse MSs decision, at at lest keep Microsoft formally in change of evolving VB.NET language, although majority of the work can be done by community. This would be good to avoid fragmentation.

b) If we as community are not happy about MSs attitude to the language, is there anything that would legally (copyrights, licenses etc.) keep us from further evolving the language? By that I mean forking all the relevant repositories, and starting do develop the language further, under a new name, such as many times proposed B# and ship it as a VS extension, bunch of NuGet packages etc. Are all the bits even Open Source (compiler, VS templates, VS integration, VB runtime - what did I miss)?