Create a detailed roadmap

[Seb-stian]

This issue should address the following problems:

• contributors have problem with identifying parts that are missing → it is difficult to assign tasks
• we have poor estimate of how much resources it will take to finish (certain parts of) Obsidian

We should work on a more detailed Roadmap that will list everything that needs to be implemented and our progression. It would be valuable to:

• put them in chronological order of when they should be implemented
• track progression
• keep estimates in eg. man-hours

I believe this will be beneficial to occasional contributors and the internal team alike.

We should discuss the form. A single markdown file in this repository may cut it, but it may also add extra noise. A separate repository would keep this one clean and open more oppurtunities, but also add a need of keeping it up to date (which we are historically bad at cough cough API documentation cough cough).

[Naamloos]

Agreed, but I do think that it might be better to not estimate how long a thing would take as that adds extra pressure to finish a task "on time".

[Seb-stian]

@Naamloos Good point. It'd be nice to have sense of getting closer to the goal though. Some metric to go by, other than:

• [ ] not done
• [ ] not done
• [X] done
• [X] done

Like for example: WORLD GENERATION

[Naamloos]

not a bad idea, that's fun

[ktalap]

So how is it going?