Create a roadmap #10

Roadmap draft for collaborative editing at https://pad.gusted.xyz/pn49roTKSE2kQYtxXwyMiQ#

As someone discovering the fork, knowing it is all new, I would like to know where it is headed, even if very high level. The roadmap could be goals to achieve, for instance:

• Adding user documentation
• User Research on federated issues
• Monthly reporting
• Establishing a well-being team and a moderation team

In other words:

• Writing code
• Prepare well to write code that is meaningful to users
• Communicate with the outside world
• Improve the diversity and preserve an inclusive environment

the HedgeDoc timeline which describes how it came into existence cited by @realaravinth is nice looking. Not exactly a roadmap though.

You could use such roadmap with branching for the different project tracks if you like such approach i.e. Product, Community, Development

Other tracks (e.g. Research, Project, Process) or different sets are possible.

I do not understand what the "In other words" bullet list means, btw. First one I get.. they are Roadmap deliverables.

By "In other words" I meant that they fall in these categories. A better formulation would have been:

The categories that would make sense to me to group those deliverables would be something like:

• Writing code
• Prepare well to write code that is meaningful to users
• Communicate with the outside world
• Improve the diversity and preserve an inclusive environment

Ah, I see. Can try to make them single words, then they can be labels. E.g.

• Coding
• Quality
• Communication
• Well-being

For me the second bullet point sounds more like "specification" than "quality".

I wonder if there is a generic term grouping good practices such as User Research, specifications or UX design. Everything that's not directly related to code but is input for the developer. 🤔

It was suggested that a Roadmap should be based on User Research instead of invented by the people involved in the fork. A task was created for this purpose.

I wonder if there is a generic term grouping good practices such as User Research, specifications or UX design. Everything that's not directly related to code but is input for the developer. 🤔

https://en.wikipedia.org/wiki/Human-centered_design comes close?

Hey people! I haven't (yet) read all the comments here and the roadmap draft, but wanting to mention #136 because it's a (very important and powerful, I believe) foundation on which we'd be building our roadmap.

I was wondering, whether it makes sense to continue working on a roadmap once the grants with NLnet are finalised. Part of those will be a breakdown of the tasks to be completed within the grant.