Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Changing the project name #48

Open
tycobbb opened this issue Jul 17, 2018 · 6 comments
Open

Changing the project name #48

tycobbb opened this issue Jul 17, 2018 · 6 comments

Comments

@tycobbb
Copy link

tycobbb commented Jul 17, 2018

First things first, I love the concept of this tool. However, because of its gendered name, I'm hesitant to include it in my own projects. Would the maintainers of this library be open to changing the name to something more inclusive?

Any steps, even small ones, that we can take as a community to create a more welcoming environment for new/oldcomers alike enrich our field. We can look to factory_bot for an example of why, even for popular, established projects, such changes are both important and meaningful.

To cast the first line, how about something like doctopus? It draws both on this project's flexible scripting options and on its embedded documentation.

@saschanaz
Copy link

doctopus unfortunately does not seem to be available. https://www.npmjs.com/package/doctopus

@j-f1
Copy link

j-f1 commented Aug 19, 2018

Here’s a list of words starting with m and ending with d (but not ed).

@agilgur5
Copy link

makedown might be interesting since this library is similar to a Makefile written with Markdown

@j-f1
Copy link

j-f1 commented Aug 31, 2018

made might work too — it’s a pun on make, it contains m and d, and it’s a homophone of maid.

@egoist
Copy link
Owner

egoist commented Sep 10, 2018

or madefile, if that's possible..

@tycobbb
Copy link
Author

tycobbb commented Sep 17, 2018

@egoist Is your concern finding a corresponding name for the config file? While Makedownfile doesn't exactly roll off the tongue, we could pick a transform like:

maid     -> makedown
Maidfile -> Makefile.md

It continues to reinforce the make legacy. I also think it's nice for files that are actually ruby/markdown/etc to use the correct extension, so that we get syntax highlighting for free. Extension-less config files require a special case in every editor I use, at least.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants