Come up with a better name

[balupton]

I think the poor adoption with joe is largely due to it's terrible name. I'm open to suggestions.

[RobLoach]

SuddenlyVelociraptor.js

I've always gone under the thought that a name is simply a name. Its adoption has nothing to do with its name, it's just that there are so many different testing frameworks out there. Some are more popular than others, but that is not a marketing problem. What is Joe missing that the others provide? Could Joe better integrate with what's out there, and build upon what they do well? Describing it as a competitor to Mocha won't help, while being a compliment to it will.

But of course, if the name more explicitly stated what the package did, it might help people get a better idea of what it accomplishes. I'm still down with SuddenlyVelociraptor.js.

[christav]

The "sales pitch" for joe right now seems to consist of "It doesn't blow up like Mocha when you're defining tests dynamically." That's a pretty niche scenario.

Defining your project as "we're not that other guy", especially when the other guy is popular and generally gets the job done does not attract people. Concentrate on what joe is good at, not what mocha is bad at.

[mikeumus]

Concur with both points here from @RobLoach and @christav. Really from a branding/marketing perspective, Joe is a freaking awesome name and you have the NPM namespace. :smile:

[balupton]

From an SEO perspective it's a nightmare.

[balupton]

I can also imagine the problems if you have someone called joe on your team as well

[mikeumus]

Having a nice shiny ✨ website and visually showing the mocha comparison in a markety way.

[balupton]

@mikeumus @christav @RobLoach @bevry/extras-team What do people think of fairtrade? Anyone have any objections. I like it, as it stays within the chocolate/coffee/tea namespace, while providing more guarantees. Plus, fairtrade.test, fairtrade.suite make sense.

[pflannery]

@balupton I think fair trade isn't a bad name but I've always looked at fair trade relating to fairness across trade in general.

Its got me thinking how a person would test or choose their coffee or tea.

Some words I've put together are taste, aroma\smell, roast(ed), hot, blends, fresh, ripe, colour, drinking, cuppa joe, or cup\mug.

A project I worked on recently I named the ci build user "cijoe" as a bit of humour. Maybe joe just needs a little something to go with it.

[pflannery]

or maybe it just need a logo like:

:)

[timhuff]

I figured I'd drop my two cents here. I'm probably not going to use joe. Here's my current situation: I'm using mocha and want to generate tests using information pulled from my database. It seems your library suits my use case. I'm not yet positive about not using this tool but I'm hesitant for several reasons. For one, this is not a drop in replacement for mocha and I already have a decent number of tests written. Secondly, this is not an extension of mocha but rather a replacement for it. I'm hesitant to risk committing to such a fundamental tool in the hopes that it continues to be maintained (meanwhile mocha's not going anywhere soon). There's also the question of "does this play nicely with my other testing tools?". It'd be excellent if this tool simply modified mocha to not run until a callback, provided by describe, is called. Solves my problem and is only a minor departure from my existing testing ecosystem.

[balupton]

Mocha is not well designed, patching it is not possible. This tool will be maintained.

[balupton]

Maybe joe just needs a little something to go with it.

Yeah maybe. Although I'd still hate to have the name Joe at a company that uses joe :P

---

I've reserved the name fairtrade by cross-publishing joe to it. Will make the name change later on.

[balupton]

fairtest is also an option

[balupton]

kava is also an option, if I email the people behind the unused packages

https://en.wikipedia.org/wiki/Kava

However, it can be stated that in general noble kava produces a state of calmness, relaxation and well-being without diminishing cognitive performance.

[balupton]

Replaced

Joe is a javascript testing framework that actually works. Unlike Mocha, we won't die on you abruptly when executing dynamically created tests and are always able to associate the correct test to the correct corresponding test suite. Switching from Mocha is trivial and only takes a few minutes.

With

Joe is an accurate and powerful testing framework that can run on node and in the browser

In v2.0.1

[rdeforest]

New potential user here, providing my perspective. I was going to write a huge wall of text, but instead I'm putting it on your wiki (as "Notes on a possible project re-branding") so folks can hack at it instead of producing a long series of posts on this issue. Discussion should still happen here, but the results of the discussion should go on the wiki.

[balupton]

I've sent the following email to @samholmes to request the kava name.

Hi Sam,

With your blessing, I'd like to rename https://github.com/bevry/joe to kava — https://github.com/bevry/joe/issues/7 — and as such, publish to the npm package name `kava` which is currently under your control with an empty package https://www.npmjs.com/package/kava

Joe has been powering the tests of the Bevry ecosystem since 2012, and will continue doing so for the foreseeable future.

As per the process at https://docs.npmjs.com/misc/disputes you can approve this move by running:

npm owner add bevryme kava
npm owner add balupton kava
npm owner rm samholmes kava

Thank you for your consideration. I will happily mention your blessing if you wish in the changelog once the rename has completed.

Regards,
Benjamin Lupton
https://balupton.com

[balupton]

In the meantime, I will publish to @bevry/kava

[balupton]

@samholmes has graciously given us the package name kava.

A new release will go up in the coming week in the next batch of dev work.

[balupton]

Kava v3 has been released.