Using a more canonical name: MicroCrate => micropython-cratedb

[amotl]

Hi Simon,

coming from using "microcrate" as a working title for this piece of software was a good decision. Now that I am reading the camel-case variant, it reminds me of old times where we needed to put in additional efforts later to get rid of the overloaded "crate" label, and we still haven't made it thoroughly through all the driver and adapter artefacts (repositories and packages) to rename it to "something-cratedb", or "cratedb-something", depending on upstream conventions.

In this spirit, I am now humbly asking you to use a more canonical name for the driver, both for the repository and for its canonical name (optimally identical), so that we don't need to adjust packaging and publishing later on, which always creates additional hassle.

What do you think about boring yet canonical "micropython-cratedb"?

With kind regards,
Andreas.

[simonprickett]

Sounds good - I'll rename this before we move it to the crate organization.

[simonprickett]

I'm not 100% on having "micropython" in the name... some platforms discourage this with package naming, for example in the JavaScript world having "node" or "js" in the name isn't encouraged (see npm package.json guidelines). I've asked the MicroPython community on their Discord and will see what the prevailing sentiment is before taking action here.

[amotl]

Hi Simon,

I'm not 100% on having "micropython" in the name.

I am not married to it, my intentions are solely to prevent NIH. I just figured that out by evidence:

• https://pypi.org/search/?q=circuitpython-
• https://pypi.org/search/?q=micropython-

Some platforms discourage this with package naming, so I've asked the MicroPython community on their Discord about it.

Excellent. Better safe than sorry, thank you!

With kind regards,
Andreas.

[simonprickett]

Community feedback backs up the choice of micropython-cratedb with micropython in the name as there's no canonical package index location for micropython packages. I'll move forwards with this.

[simonprickett]

Working on this in #16