Future plans (Your help is wanted!)

[Andre601]

Hello everyone,

With this post would I like to take the oportunity to talk about the future of this project.
I want to make clear, that I've discussed this with oprypin and this post is made with his agreement.

We - meaning me and oprypin - know that the start of this fork wasn't the best to put it mildly.
Decisions were made that we later regretted, but we want to make clear that this wasn't done with any ill intent, but out of an effort to prevent MkDocs from slipping further into the unmaintained state it currently is in.

We know that we could've made a fork and separate project, but as some of you have pointed out such a move comes with possible conflicts.
If we are unable to reuse the existing mkdocs import while under a different project name, will it require project maintainers to either move away from MkDocs to our fork, stay with MkDocs, support both in some way, or abandon their project. None of these outcomes are really beneficial.

But at this point such a fork is pretty much unavoidable and we will have to bite the sour apple, if we want MkDocs to exist for the future.
However, this also gives us some oportunities to change things for the better.
One such thing is including the community a lot more in our future decisions.

Inclusion of the community, especially recently, has been lacking in various ways, and the current way of issue tracking for the v2 is even more concerning.
The community is what made MkDocs big. Without all the people that made themes, extensions, plugins or contributed to MkDocs directly, the project would've never reached the size and influence it now has.

But code isn't everything. Often times something as simple as providing feedback to a planned feature is enough to help shape a project.
That's why we want to try and include the community a lot more in future decision making, starting with the Project name itself!

It is clear that we cannot stick with mkdocs as the project name for the future. It's already taken and a different name is needed.
While we do already have some naming ideas, this is something we don't just want to decide over you. After all, the name is something you will need to deal with whenever you install the project, or read through docs.
Because of that are we asking YOU for your own ideas.
We will make a follow-up post where you will be able to submit your own idea for a project name to use.

We hope that this will be one of many future interactions with the community, as we want to make this a project for the community, by the community and every help from you, even simply suggesting stuff, helps.

We apreciate if you followed the activities in the main repository of the project by watching it, or by subscribing to individual issues, Pull requests and discussions.

Let's revive MkDocs!

[Andre601]

Name suggestions can be made in #5