There is no roadmap indeed.
Good idea! And we could use the list of issues to get inspiration (or remember things that were forgotten Since Enough does not have employees and is volunteer based, it is difficult to predict who will do what. And therefore even more difficult to predict what will happen and when. But a first roadmap could simply be a set of goals with no specified timeline. It is useful to know how much progress was made on a given goal and I’d like to find that in a roadmap too.
Here is an example roadmap to illustrate what I’m proposing. This is just an idea I had this morning: don’t hesitate to criticize (or say it’s not what you had in mind at all).
@dachary & @pilous explore k3s/k8s
||Using k8s with Enough is a complete refactor, there is no plan to go in this direction
||Add integration tests to the CI
||Abandon adding integration tests to the CI
||Use Docker to run the CI
||Broke Docker CI when implementing backup restoration and upgrade tests
||Use molecule for integration tests
||Replace molecule with tox
It’s not much of a roadmap to be honest but it would help a newcomer figure out who’s going in which direction. However… since there are very few of us another way to figure that out could also be to ask. I can only answer for myself and here is what I have in mind. I’m unsure exactly what I will actually do. It depends how much time I’ll have, how motivated I’ll be and how interactions with other people will go.
In other words, my main areas of interest in the following months are interactions, user research, MOOCs and development (in no particular order).
Of course, Enough being horizontal and all, every participant is expected to have a different views, goals and roadmap for how they engage with it