One: Clarification of project/module names - ONE, nnfwapi, oneapi, onert, onecc, nnfw, nncc and nnas

[wateret]

I'm confused with these names after we renamed the repo name to "ONE".

ONE, oneapi, onert, onecc, nnfw, nncc and nnas

Here's the old names:

• nnfw(FrameWork) : runtime
• nncc(Compiler Collection) : compiler (already not used)
• nnas(Acceleration Solution) : The name for both runtime and compiler which should have been the repo name before renaming to ONE
• nnfw API : runtime API

% nnfw is the old repo name. This is because, long ago, this repo was just for runtime then nncc was merged into nnfw

And here's what I thought when we renamed this repo to ONE.

• ONE : The repo name
• oneapi : new name for nnfw api
• onert : new name for nnfw (also namespace name for runtime)
• onecc : new name for nncc
• nnfw : no longer used
• nncc : no longer used
• nnas : no longer used

Please correct me if I'm wrong.

Personally I prefer not using any of "nnXX" and we should rename those still being used in our repo.

[hyunsik-yoon]

+1. Agreed.

[lemmaa]

I don't know if we should change this entirely. Personally, I think that names such as _nnfw_, _nncc_, and _nnas_ are historical and meaningful. It is also much fancy for me.

I think ONE can exist only as a representative of the whole project. I also like _neurun_ better than _onert_. It's just that it was inevitably changed due to concerns over trademark rights, and it could be just _nnfw_ in simple.

To be honest, I don't like ONE so much, even tough I suggested this name. I just don't hate it. Maybe I'm hoping for a better name to come out and replace it easily.

I'm sorry if these comments have confused you. You can just ignore it. :)

[wateret]

@lemmaa What I'm worried about is that using all these words may confuse those who don't know about the history. For example:

• Now the runtime name is onert while compiler is still nncc (onecc is never used)
• We have commands(scripts) named nnas, nncc and nnfw (Looks like nnas shows only the scripts and CMake files)

I'm OK with staying with the names now. Then nnfw api will be here to stay and I won't change the prefixes to onert_ #244. However still I would like to get rid of nnas someday.

[seanshpark]

compiler is still nncc (onecc is never used)

At least I'm not using nncc. I'm using just word Compiler and the folder names like _luci_, _tflchef_ etc.

[hyunsik-yoon]

My personal preference is to keep only one name not to confuse newly joining developers also us (#244 is one example of our confusion).
If we use both, we have some rule (strict or not) when to use nnfw when to use one.

[wateret]

Conclusion for now:

• ONE : The repo name
• oneapi : new name for nnfw api
• onert : new name for nnfw (also namespace name for runtime)
• nnfw : still used
• nnfw api : still used (hard to change API prefixe nnfw_)