You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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!
Reacted by juliusbentz, TC Liu, rainerzufall, Kai, Ching367436 and Pierre Ozoux
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.
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.
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.
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.
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 :)
Reacted by Max Wu, Brandon Curtis and Alexander Pushkov
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.
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!
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.
CodiMD, based on the latin word codicellus (or codicillus) which means notepad (or notebpads), is maybe a good new name. Those who really read the description will get it and those who don't may think we tried to cutify "Code" or "Coder" which is in one or another way close to Hack or Hacker, which than again is close to HackMD ^^
It also fits into the trend to use wise looking latin words in free software projects without overused words like Libre.
Anyone against it?
Reacted by Dampfklon, Royi, Pedro Ferreira, Pierre Ozoux, Timothee Gosselin, TC Liu, Robin Rosenstock, davidak, 林博仁 Buo-ren Lin, Kai and 2 more
I like the direction of codi(cellus/cillus). It seems to be the diminuitive form of codex / caudex, so why not go with the "big" one? This also means book, writing but also caudex: "A caudex (plural: caudices) of a plant is a stem, but the term is also used to mean a rootstock and particularly a basal stem structure from which new growth arises."
putting it into the conversation test proposed above:
"You can look it up in (the) caudex"
"I sent you a link to the Party caudex"
"We're using (the) caudex to organize and the results will be mailed to each of you"
I'm also in with the codi direction, CodiMD sounds quite good and makes sense.
I also wanted to add that for me the renaming is kind of starting to be critical. I have quite a number of users that are starting to become confused about functionalities that hackmd.io offers and what they can get on the self-hosted version.
It feels like there is a community growing here, lets fork it ;)
I'm going to rename the project to CodiMD at the end of the week. Along with that, we either make a decision about switching away from GitHub or not (See #838).
At least that's my plan if there are no (significant) voices against it.
I'm still trying to figure out how CodiMD won over Hackpad.
I can't see my self filling any of the sentence proposed with CodiMD because:
CodiMD pronunciation:[ˈkoʊdɪ ɛm diː] it's cumbersome and the two MarkDown letters interrupt the word (and the sentence) flow, which leads to shortenings
Shortening CodiMD: Codi, which is very similar to Kodi the XBMC successor, which leads to confusion, beside the fact that, and that's just my taste, Codi doesn't sound cool.
The CodiMD word root: looks like a truncation of Coding, which is probably why the first time I've seen the repo name I've thought "Hey cool! A HackMD coding fork!". Obviously this was before finding this issue. Also, even if I dind't like it and I wasn't that good at it, I actually studied latin in high school for 5 years.
About Hackpad:
sounds incredibly cool 😎
"Wait a second, I wrote it on my hackpad" Hemingway
"Let's have a hackpad later and fix the speech" Successful startupper
"What? You don't know hackpad? It's like drive, but better" the cool kids at school
There are some options for the domain that don't cost an eye (174€ was the cheapest after a quick search for .md)
Sorry for being stupidly late, I totally lost the track on this project, I just loved it from the beginning (as probably you all) and would've loved to see it gain more traction because it's open, because of the features and the values and, why not, because it just sounds cool.
Activity
almereyda commentedon Feb 8, 2018
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.
ukuMDsounds a littly cryptic and is almost unpronouncable.To go on with the brainstorm, allow me to throw those into the round:
MarkpadHackpadsic! People will call it like that either way.Notepadin reference toLet'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 commentedon Feb 8, 2018
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 commentedon Feb 9, 2018
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 commentedon Feb 9, 2018
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 commentedon Feb 9, 2018
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 commentedon Feb 11, 2018
Marwe commentedon Feb 20, 2018
mdpadormadpadcome to my mind ;)RoyiAvital commentedon Feb 25, 2018
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
mdfiles.Thank You.
ccoenen commentedon Feb 25, 2018
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 commentedon Feb 27, 2018
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 ...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
yet?
This term is only occupied by programming exercises and personal pet projects.
ccoenen commentedon Feb 27, 2018
Personally, I find "libre" as part of a name very cumbersome. This may be because in germany nobody knows how to pronounce it.
pierreozoux commentedon Feb 27, 2018
It comes from FLOSS: Free Libre Open Source Software.
Libre is the new Open:)ccoenen commentedon Feb 27, 2018
which does not explain how to pronounce it.
SISheogorath commentedon Feb 27, 2018
https://en.wiktionary.org/wiki/libre#Pronunciation
😉
12 remaining items
zeigerpuppy commentedon May 10, 2018
If someone using Markdown is a "marker", why not MarkerPad?
ccoenen commentedon May 10, 2018
Textmarker?
almereyda commentedon May 11, 2018
pferreir commentedon Jun 5, 2018
HouseMD?
SISheogorath commentedon Jun 6, 2018
As I just thought a bit about it:
CodiMD, based on the latin word codicellus (or codicillus) which means notepad (or notebpads), is maybe a good new name. Those who really read the description will get it and those who don't may think we tried to cutify "Code" or "Coder" which is in one or another way close to Hack or Hacker, which than again is close to HackMD ^^
It also fits into the trend to use wise looking latin words in free software projects without overused words like Libre.
Anyone against it?
pferreir commentedon Jun 7, 2018
The only potential problem I can see is confusion with "Kodi", the media centre software. Otherwise, it sounds quite nice.
ccoenen commentedon Jun 8, 2018
I like the direction of codi(cellus/cillus). It seems to be the diminuitive form of codex / caudex, so why not go with the "big" one? This also means book, writing but also caudex: "A caudex (plural: caudices) of a plant is a stem, but the term is also used to mean a rootstock and particularly a basal stem structure from which new growth arises."
putting it into the conversation test proposed above:
As far as I can tell, no other project uses this word.
unteem commentedon Jun 18, 2018
I'm also in with the codi direction, CodiMD sounds quite good and makes sense.
I also wanted to add that for me the renaming is kind of starting to be critical. I have quite a number of users that are starting to become confused about functionalities that hackmd.io offers and what they can get on the self-hosted version.
It feels like there is a community growing here, lets fork it ;)
SISheogorath commentedon Jun 18, 2018
I'm going to rename the project to CodiMD at the end of the week. Along with that, we either make a decision about switching away from GitHub or not (See #838).
At least that's my plan if there are no (significant) voices against it.
SISheogorath commentedon Jun 22, 2018
I started the renaming in #850
edoardoo commentedon Dec 3, 2019
I'm still trying to figure out how CodiMD won over Hackpad.
I can't see my self filling any of the sentence proposed with CodiMD because:
[ˈkoʊdɪ ɛm diː]it's cumbersome and the two MarkDown letters interrupt the word (and the sentence) flow, which leads to shorteningsAbout Hackpad:
"Wait a second, I wrote it on my hackpad" Hemingway
"Let's have a hackpad later and fix the speech" Successful startupper
"What? You don't know hackpad? It's like drive, but better" the cool kids at school
Sorry for being stupidly late, I totally lost the track on this project, I just loved it from the beginning (as probably you all) and would've loved to see it gain more traction because it's open, because of the features and the values and, why not, because it just sounds cool.
ccoenen commentedon Dec 3, 2019
@edoardoo most of the people who discussed this are now over at https://github.com/hedgedoc/hedgedoc
Potherca commentedon Oct 7, 2021
For the sake of completion (or to complete the confusion), the name "Hackpad" was already established out there...
Hackpad is a 2014 fork of Etherpad (now https://github.com/ether/etherpad-lite) which was bought by Dropbox and open-sourced in 2015 at https://github.com/dropbox/hackpad. It was to shut down in 2017, in favor of what is now Dropbox Paper.