Naming of Primary Table?

[nelsonic]

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" 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" 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. 💬