Derk-Jan
On Wed, Mar 15, 2017 at 12:29 PM, you wrote:
You mean like here: https://www.mediawiki.org/wiki/Roadmap ?
No, because that page is not a roadmap but a list of pages none of which is a roadmap in the sense I stated, and I rather think you knew that when you referrd to it.
Where it is already posting it's annual and quarterly plans to as much detail as anyone is able to predict a roadmap ?
A roadmap in the sense I asked for does not need to be detailed. It does need to be clear and comprehensible. It looks out further than the end of the current work year. We know that there are longer terms technical plans and projects (around parsers, editors and Flow) than these plans which all seem to send within the next few months.
Of course, those who want to participate in governance should have the chance to involve themselves, and usually they do, but that's not most people.
I wish that were ture, but it has not been my experience.
It would be much better if we acknowledged such problems, rather than
insist that there is a solution that we haven't spotted yet in 15 years... And that's exactly where I hope this guidance is going to land. A reference where we can mutually formalise our expectations, limitations and aspirations.
This is exactly what I'm arguing for. But this guidance seems unlikely to achieve it.
"Rogol"