FRB sources are compact. None of our telescopes have a resolution to see anything particularly interesting in a galaxy 9 billion light years away of that size. Any kind of afterglow on a stellar scale would just drown in the galaxy light.

I mean Soviet Union in 1938 was certainly the land of freedom of expression with no political ramifications whatsoever for anyone who wanted to use big state rubble on research projects. There's no doubt that NKVD would be entrusted with genuine political views and would be a more credible source on how a particular person might feel about Ukraine than their own daughter. Korolev's imprisonment on the charge of membership in an anti-revolutionary trotskist organization was just a paperwork toss up. 10 years of labour camp on Kolyma can just slip in a random folder if you don't have you coffee before you arrive in the office. Happens to the best of us, no biggie.

It's great that more and more developers think about licenses. Though, there's one aspect that I find... underdocumented.

From time to time there may arise a need to fork a project. Either changes are out of the scope of the original project and they wouldn't ever be accepted upstream, or the upstream maintainers are not as responsive as community requires or for whatever other reason there may be. It's counter-productive to keep the original name (and have basically two diverging projects with the same name) or have original authors listed as the maintainers to be bothered about bug/features in the project they don't maintain (I'm not talking here about attribution).

So what's the proper forking procedure? Is there any differences depending on the project license?