Main blockers are currently the logo and maybe a slogan.

As soon as we have a logo, I think it makes sense to rename user-facing services and social media.

I want to raise a question: Do we want to keep the name for the backend-repo as "server" after transferring to the new namespace?

There are many opensource projects that follow the approach of using the name of the software for their primary repository too. If we did so too, it would be 'hedgedoc/hedgedoc'. The advantage of using the software name as repository name is that forks as well as the directory after cloning have a more meaningful name.

Hi. I just learned about CodiMD this week, as did, I suspect, a good number of other people, because the IETF switched from Etherpad to CodiMD for recording meeting notes for their sessions this week.[1] As I started to tell other people about (and tweet about) CodiMD, I was surprised to now learn it is changing its name again. I've read through the various issues and understand why. To help prepare people who might just be learning about CodiMD for the name change, may I suggest that you add a line to the top of the current README.md that says something like:

NOTE: CodiMD is in the process of changing its name to HedgeDoc.

That way you are getting people ready for all the changes you are outlining here.

Best wishes with the renaming - and thanks for developing such an incredibly useful tool!

[1] You can see this in action if you go to the IETF 108 meeting agenda and look on the right side where there is an icon of a square box and a pencil. The tooltip still says "Etherpad for notetakers", but when you click the link, you go to a CodiMD link,