Changing the project name

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.

[agilgur5]

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

[tycobbb]

@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.