Naming: agree marketplace is weak, some starting ideas
Section: Open questions, point 4 (Naming)
"Marketplace" is generic and SEO-poor, and the install-command name needs to avoid conflicts with existing CLIs... Open.
Agreed, marketplace isn't great. I don't have a final answer, but here are two I keep coming back to:
- nanostore. Ties straight into the Nano brand. Downside is it doesn't describe what the thing does that well, and "store" hints at buying, which cuts against us never taking a cut.
- SkillForest. I like this one, it's a bit novel and it matches the Forest naming we use on other projects.
Two things I think we should keep in mind whatever we pick:
- Avoid names that imply buying or selling. Both marketplace and store carry a checkout vibe, and the doc is clear we never take a cut, so a name that doesn't promise commerce keeps us honest.
- This is really two names, the project and the install command. The command still has to dodge the taken ones like
nano, pkg and agent, so even if the project lands on nanostore or SkillForest the command name is a separate call.
Ask: Can we treat marketplace as a placeholder and start a shortlist? nanostore and SkillForest are my starting ideas, and I'd want us to settle the install command name separately from the project name.
Naming: agree marketplace is weak, some starting ideas
Section: Open questions, point 4 (Naming)
Agreed, marketplace isn't great. I don't have a final answer, but here are two I keep coming back to:
Two things I think we should keep in mind whatever we pick:
nano,pkgandagent, so even if the project lands on nanostore or SkillForest the command name is a separate call.Ask: Can we treat marketplace as a placeholder and start a shortlist? nanostore and SkillForest are my starting ideas, and I'd want us to settle the install command name separately from the project name.