Naming of Primary Table?

# Why?

Naming things is _always_ difficult; it's virtually impossible to achieve universal agreement.
Thankfully this is not a "branding" exercise where "_all the **good names** are **taken**_".
We only need to discuss and _agree_ on what the most intuitive name for a "job to be done" is.

The name needs to work well in English (_obviously_) because _most_ software is written in English. But it also needs to be _unambiguous_ and _immediately obvious_ to people who are _not_ native english speakers; the vast majority of the world do _not_ speak English as their primary language.

# What?

The primary table is where the "items" of "things to be done" are stored.

It it a checklist **item**, a "**todo**" a "**task**" or something `else` entirely?

As _fluent_ english speakers, we _know_ what a "Todo list" is.
We _automatically_ translate it in our heads to "_list of things to be done_".

But Searching for the definition of the word "todo" on Google we see the `default` meaning is _not_ what we expect: https://www.google.com/search?q=define+todo

> "a commotion or fuss."

This got us wondering if there is a more intuitive name for the individual item in the collection.

## Context

It's worth _contextualising_ that our plan is _not_ to build a one-trick-pony product.
Our plan to build a _general_ purpose communication platform that individuals, teams and organisations can use maximise their personal and collective effectiveness. We feel that _starts_ with a way of tracking the tasks that need to be done and the time it takes to complete them. See:
But if we don't at least _think_ about where we want to go with the idea(s) there is very little chance of us _randomly_ building something great.

https://www.google.com/search?q=item

https://www.google.com/search?q=define+list

## Meta

I opened this issue because:
**a)** I like to consider how naming things affects the way people _think_ and _use_ things.
See: ["Super Mario Effect"](https://github.com/nelsonic/nelsonic.github.io/issues/713) calling something a "test" is _very_ different from calling it a "quest".
**b)** I don't like it when decisions are made in an opaque way.
I always try to document my thought process so that others can understand it
and if anyone can spot an area for improvement, share it with me.
I don't _want_ to be a ["**BDFL**"](https://en.wikipedia.org/wiki/Benevolent_dictator_for_life) on this or any other project , I just want to help get the @dwyl community _started_ and set the _example_ for "hyper transparency". That means taking the lead on opening the discussion, making the best decision given the time and information available, and being open to

## _Curious_ About Naming?

**99.9%** of people don't give much thought to naming things.
That's "OK" because they have other things to think about.

If you're reading this it's a sign that you're at least _curious_ about naming.
Even if you don't participate in the discussion you at least know that _someone_ `else`
has put some thought into it and you can refer others to where this is recorded.
If you are interested in this and _want_ to participate, please leave a comment blow. 💬