TL;DR

We have a naming convention for repositories, and it is mercari-X-Y-Z.

More words

Naming convention is no just fancy thing to agree on and follow.

It creates some context. As result people will spend less time guessing.

This convention, as well, provides more natural expectations on package naming if we use scopes. And it is better to use scopes.

When we install the package:

npm i @mercari/eslint-config

We are able, without guessing, searching, or whatever extra effort navigate to

mercari-eslint-config
(or mercari/eslint-config, plz, read to the end)

on github.

PS

1. The fact the mercari group is, so i heard, for OSS efforts, should, not affect this idea.
2. Conventions contribute a little to overall structure, whereas neglecting of such contribute to overall chaos
3. We may decide, though, that mercari org is already part of the name of the project (and so it is in fact), then the name of the repo would be mercari/eslint-config and we do not need mercari-suffix or prefix. Maybe, that is the best option here. I would like to hear your opinion, @1000ch

/cc @hitima