Renaming the library

[Nek-12]

The library has outlived its name. Instead of being a simple MVI implementation, it is now a general-purpose, extendable architecture framework, and it has little in common with coroutines Flows anymore.

I'm afraid the name "FlowMVI" will not appeal to the larger audience and cause misunderstandings about the purpose of the library, e.g. making people think it's solely an Android UI-oriented library. The library can be used on the backend, in the data and even domain layers of any Kotlin app right now, it supports both MVVM+ styles and redux implementations. Besides that, the focus of this library is not on providing an architectural foundation anymore, but rather being a flexible business logic container with plug-in support.

That said, the rename will have big consequences:

• Package names have to be changed
• Artifact ID has to be changed
• docs need rewriting
• creative assets need reimplementation
• SEO has to be started from scratch
• public library indexes like klibs.io need to be updated manually (there are currently 4 I know need updating)
• articles (currently 4+) have to be updated
• Reddit posts etc. also need a mention as they play part in SEO
• telegram and slack channels need renames (which may not be fully possible)

I want to hear the community's opinion before I make the decision. If there's not enough data, so far I'm considering Kent as the most interesting new name.