On Aragon naming
Aragon naming can be confusing. Aragon was the original name for the dapp, and now Aragon means the project in general. We need to clarify naming and keep it consistent, since we do have a lot of components, and it can make people unclear about their relationship.
Those are projects that are horizontal to the whole ecosystem and not tied to only Aragon. Therefore it shouldn’t follow any Aragon naming scheme, although I’d incline to name them after birds.
Those right now are: Radspec and Lorikeet.
The naming scheme for developer tools would be aragon + acronym. So aragonXXX.
Currently there is not a name for all the dev tools we have built. aragonSDK would be their umbrella, and the primary brand for Aragon developers. It’s tagline would be everything you need to build apps that run on Aragon Core.
Makes sense to be called that way, because it’s the kernel + framework that all the Aragon ecosystem uses to work and inter-operate.
DAO Kits to Aragon templates
A kit is a set of tools. What DAO Kits do resembles a template more, so we should just call them Aragon Core templates, or templates.
aragon.js to aragonAPI
aragon.js has a dot, which isn’t used anywhere else in our naming, and also has an extension, which locks it down to a single programming language and isn’t used anywhere else in our naming neither.
aragonAPI describes better what this component does, and adheres to our naming scheme. Of course, this would be for the aragon.js client. For the server (or the wrapper as we call it) it could just be split off as part of Aragon Core, and it would have some internal name not exposed to the public so much.
APM to aragonPM
We don’t use acronyms anywhere else, so I feel bad about this one. Going on with our dev tool naming scheme, I’d say aragonPM would be the right one. Since there’s immediate interest in maybe working on this with other teams, I’d leave it as it is, not to rename twice.
aragonUI would be the thin layer on top of Lorikeet that is Aragon-focused and opinionated.
Aragon CLI to aragonCLI
With our dev tool naming scheme, I’d rename to aragonCLI. aragonCLI would be the command line tool developers use to build Aragon apps.
It’d be a good idea to split aragonCLI into two components: the CLI for developers, and the CLI to interact with DAOs (the
dao subcommand in the CLI right now). Unsure about the name yet, but it could just be the DAO CLI.
Aragon Core to Aragon
Aragon Core it’s confusing and breaks in the following scenarios:
He is an Aragon core contributor . Does that refer to a core contributor to Aragon, or a contributor to Aragon Core?
Aragon App could work, but it has flaws:
Aragon Core acts as a platform for Aragon apps, so calling the platform Aragon App would mean that it’s an app that runs apps (?)
I like That Planning Tab, I use the Aragon app . Does that refer to TPT’s Aragon app, or to the Aragon App?
Not a lot of people know what Aragon Core anyway, everyone calls it just Aragon. If there is confusion or more context needed, one could always specify the Aragon project or the Aragon client, when referring to one of them.
Feels like the name is understandable. I’d leave it as it is. It’s a DAO that conforms a network of DAOs.