hedgedoc/hedgedoc

Rename to HedgeDoc

davidmehren opened this issue · 15 comments

davidmehren commented

This is a tracking issue for everything that needs to be done to release 1.6.1 under the new 'HedgeDoc' branding.

SISheogorath commented

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.

ErikMichelson commented

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.

  • 👍6
danyork commented

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.

codimd-readme

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,

  • 👍9
FaZeBase commented

Name change reported to the Cloudron team.
https://git.cloudron.io/cloudron/codimd-app/-/issues/4

  • 👍1
  • ❤️1
slel commented

Can someone create demo.hedgedoc.org and make it redirect to demo.codimd.org for now?

DerMolly commented

https://demo.hedgedoc.org will work once we changed everything on the demo instance to be called HedgeDoc

utybo commented

Seems like hedgedoc.org is down or is that just me? nvm, everything is fine now, congrats to the team!

DerMolly commented

hedgedoc.org is currently not online. It will be once hedgedoc.github.io is finished and will link to that page.

SISheogorath commented

@CHBMB could you look into this for the linuxserver.io part?

gramakri commented

I maintain the Cloudron package and I have started the renaming, will leave a note here when done.

  • 👍5
gramakri commented

I have renamed our repo and fixed the app package. Once 1.7 is out, we can push it all out - https://git.cloudron.io/cloudron/hedgedoc-app/-/commit/d9dc9d155f111993edab4b106e66d80faa9ac0db . Is there a logo somewhere without the HedgeDoc text in it? I can try to cut it out from the svg in the demo site but couldn't find one without text.

SISheogorath commented

@gramakri there are logo variants without a name available in the logo repository: https://github.com/hedgedoc/hedgedoc-logo

gramakri commented

@SISheogorath thanks, updated the logo as well! We are good to go from cloudron side. Of course, I need to test out the 1.7 release upgrade itself once it's available.

  • 👍1
  • 🚀1
InnayTool commented

I think all renaming tasks are done!

  • 🎉2
  • 🚀1
SimJoSt commented

In the following repo the description (not the readme) is still mentioning CodiMD: https://github.com/hedgedoc/cli
Might be worth correcting, as Google has it still indexed that way as well 😄

  • 👍1