This is a rather important topic in terms of its potential to break existing content and impact on the ways contributors and (human) editors work. It merits a project page here with a broad description of the goals and the ways it is proposed to achieve them. A Phabricator search page is not an adequate substitute. In particular I note that it is proposed to reduce the power of templates to make it easier for software (I assume VE is a main driver here) to handle them. This really needs community engagement -- there's a huge investment in template technology closely adapted to the current software and there needs to be a clear engagement with the community before major impacts on their ways of working. As I point out in another topic, the absence of a locus for community engagement is expected to be a blocker in and of itself.
Topic on Talk:Parsing
Understood. The evolving wikitext ideas are, at this time, still at an idea phase and you might have seen the notes at Parsing/Notes/Wikitext 2.0, Parsing/Notes/Wikitext 2.0/Strawman Spec ... those are not accepted ideas of what will happen, but more a proposal of what we might want to work towards in the long run. Even if that were the plan (which it is not, it is just my personal high-level proposal), it is not something that we will just flip the switch one day ... but something that we will incrementally work towards. And yes, I agree about the need for community conversation and engagement.
But, https://phabricator.wikimedia.org/T114445 is one of the first steps that is actually in an RFC phase.
Thank you. I see the Phabricator task has been open for a year now. Phabricator is not a suitable venue for a community engagement exercise, although it may be capable of sustaining informal staff discussions around an existing task. You really need to hold that engagement somewhere more suitable like here or Meta. Presumably you have the stakeholder mapping and communications plan ready to go?