Rename the project

[pierreozoux]

As discussed is #579, this project is a fork, and the people that created this project, and the company that is trying to sell hosting of a closed source fork of this project would like to keep the name HackMD (which I totally understand, it is a great name :) )

But still, using the same name is confusing for new people coming to this project.

I propose we change the name to make it clear, and I have the sense that there is consensus about that in #579 .

As you know, "There are 2 hard problems in computer science: cache invalidation, naming things, and off-by-1 errors." (Leon Bambrick)

So first, what is HackMD?

In my opinion, it is the greatest pad with md support. Another amazing feature is the possibility to make presentations with revealjs!
So somehow, I guess the name should carry the following:

• collaboration
• text edition
• md
• presentation
• pad (in reference to etherpad)
  This is the first assumption to choose the name, so if you feel there are other values you want to convey, share here!

Then, as a second round, we should try to give names, and as a third round, let's vote about names!

Here is one idea about the name:
ukuMD
ukubambisana is collaboration in zulu, we would see the reference to hackMD, and it sounds great :)

Just an idea, waiting to hear yours!

[almereyda]

Most people seem to call Etherpads and HackMD pads either Pads or Hackpads, and I feel it could be a good choice to stick to it. Yet what makes HackMD outstanding, an almost a proper real-time wiki, is its Markdown support.

• ukuMD sounds a littly cryptic and is almost unpronouncable.

To go on with the brainstorm, allow me to throw those into the round:

• Markpad
• Hackpad sic! People will call it like that either way.
• Notepad in reference to

Let's try to stick with a pronouncable name that keeps in the minds of the readers. Yet effect described in the first sentence of this comment will most likely persist to remain.

[ccoenen]

I don't follow your argument by which either one would have to be renamed.

I'm not opposed to this discussion, but I don't see much benefit just from a rename. Feel free to post suggestions, but they'd have to be darn good to be worth the effort.

[pierreozoux]

You agreed to say it is not an open core model, yet the names are CE and EE which is usually used for open core model.
This is misleading, and you'll see, a lot of users (people that care about using only FLOSS, like me) will be disappointed, realizing that it is not an open core model (not saying that is my favorite, but better than a fork).

I personally don't care, as I already know what to expect.

And to say it one more time, I totally respect your desire to make a living from your project, and I respect your decision in finding the best way to do so.

You just have to understand that there are users that seek to only use FLOSS.
And when we pick a software, we prefer to pick one that will be maintained for the coming years.
(And yes, I do prefer to pick FLOSS that is backed by a company that is making good money, it means the software will be maintained.)
And the signal you send by making a fork is making us think that this will not be maintained.

We are part of the community, we developed this package for libre.sh, our infrastructure. And that's why we care. We invested time in this (nothing compared to you, obviously). And maybe we'll have to start from scratch again trying to find a better alternative.

That's fine, it is life, not trying to put pressure on you and making you responsible for this. You made this beautiful open source project, and I take it as a gift, I don't expect anything from you besides that.
This is part of the game, and I accept the rules.

Back to the issue in itself, as @SISheogorath said, maybe HackMD/HackMDLibre is better.
I would take the responsibility to make the rename PR if you want.
I would even offer hosting for the libre demo version if you want, instead of heroku, then we would be a bit more part of the community :) ?

Or, let me try :) the best way to close this issue would be to choose an open core business model? :)

I know it is low priority and it feels bike shedding, but in my eyes, this is important too.
I let you close the issue if you feel it is irrelevant, I'm fine, you do as you want.

[ccoenen]

In case this was directed at me: I am doing a little moderation of issues or perhaps "community management" as some call it today. I contribute an occasional Pull Request but wasn't involved in the original development and I'm not involved in the EE in any way. The same goes for @SISheogorath as far as I know. In short: we don't have any say over the business model.

[SISheogorath]

Okay guys, let's keep calm and focused.

I think that the details of why everything is like it is right now are a bit too complex to point out here (before writing this answer, I tried and failed). The history why it is like it is right now is out of scope of this issue.

Let's check that's the purpose of this issue.
Problem:
There is Hackmd.io, HackMD EE and HackMD CE. The EE and CE confuses people, as it leads them to the false conclusion that this project is running the open core model.

Solution:
Removing CE and use another term to make it clear that CE is not .io and EE. Also it's not running the open core model.

What is out of scope?
All details why the model is like it is.

What is the purpose of this issue?
Finding a term or name that can be used instead of "CE" or "HackMD CE" so users no longer gets confused.

---

For all who are curious about why it is like it is, the community announcement explains very detailed, why this split was made. More details can be pointed out in a more interactive conversation like the Gitter or Matrix.org chat. I don't think there is really a point in writing all this down here as it's in various places, too, complex.

I hope, this helps to stay on our way to improve HackMD and find a solution that fits all interests :)

[almereyda]

So we are forking off and underline this step with a new name. Sounds good to me. Thanks to the originators for their code donation to the public, us. I'd still be happy about Notepad, then I also wouldn't feel too bad about building a real-time wiki from that. Assuming here we self-invoke as a group of maintainers of the originally donated code and therefore the question of this issue may rather be if we have any aims where to take this newborn and how it is delivered.

[Marwe]

mdpad or madpad come to my mind ;)

[RoyiAvital]

What about CollabPad?

Any chance offering this in the model of StackEdit?
With ability to Sync against Google Drive, OneDrive and DropBox?

Even better to have also Desktop version with ability to work against local md files.

Thank You.

[ccoenen]

Any chance offering this in the model of StackEdit? [...]

Please create a new issue for suggestions. Nobody will find it in here or get back to you about this. If you create a fresh issue for it, it has a much higher chance of being picked up by somebody!

[almereyda]

Mdpad and Madpad sound nice, yet not mass compatible, CollabPad a little dowdy to me.

From Node-world we know some versioning practice that develops the next major release on branches called next, and the ownCloud community recently forked into Nextcloud, why I propose ...

• Nextpad

which is simple, easy to remember and kind of suits the case.

Unfortunately this title is already taken by some Windows 10 program.

Did anyone propose

• Librepad

yet?

This term is only occupied by programming exercises and personal pet projects.

[ccoenen]

Personally, I find "libre" as part of a name very cumbersome. This may be because in germany nobody knows how to pronounce it.

[pierreozoux]

It comes from FLOSS: Free Libre Open Source Software. Libre is the new Open :)

[ccoenen]

which does not explain how to pronounce it.

[SISheogorath]

which does not explain how to pronounce it.

https://en.wiktionary.org/wiki/libre#Pronunciation

😉