No matter if using Drupal, or any other system, instead of some parts of the existing MediaWiki is a sane move to make with the regard to scalability etc (thanks @Tgr for suggestions where to start to measure this, BTW), I think @dbarratt has touched some important points. At least reading what he said got me thinking of some things I mention below, thanks @dbarratt!
I am not sure how those fit the general strategy discussions, but as we're not clear whether we go top-down or bottom-up, I am going to ramble a bit:
- While I understand concerns about drastic changes, it would be good to have a framework allowing to actually evaluate the "drasticity" and estimate the cost of possible options, whatever they are going to be. In other words, I am pretty sure Daniel is absolutely right when saying above "the migration cost seems absolutely forbidding", but then, do we think we (here "we" being the people who are supposed to know and decide) know what would be the migration cost that would be more appealing? And things like that.
- It seems to me that we should not think of possible changes as "we would rewrite parts A, B, C and MediaWiki but better", but rather think what do the users want to do, and what tools do they need to get it done. I strongly believe there are ways to improve/fix/etc some things without needing to re-write half of MediaWiki and falling into stop-other-development-for-three-but-in-practive-five-years refactoring, etc. And I also believe that the tool that might allow people do what they want is not necessarily always MediaWiki.
Fri, Jan 19
Thu, Jan 18
We've been thinking about combining, but then @Jonas brought up the possibility to abuse the summary and "hide" some bad edits. Given comment https://phabricator.wikimedia.org/T173744#3889897, it seems we're fine with going this path then.
All clear, will start working on this task!
Wed, Jan 17
Tue, Jan 16
Mon, Jan 15
Sat, Jan 13
Thu, Jan 11
meh. I meant, if we moved the task to run on PHP 7 machine, that would mean we could still get correct XML, right? I.e. it does not require PHP 5?
Assigning to @Lydia_Pintscher for now to fill in the parts missing the specs.
I am not sure if I am simply rephrasing what @Jdforrester-WMF asked above, but any way: Are we positive this issue would go away if we updated box the command runs to PHP 7?
The summary part has been moved to the separate task: T184702.
Wed, Jan 10
@Jonas brought an interesting issue which is of relevance here. The background is the decision documented in https://phabricator.wikimedia.org/T173744#3691083, which also applies for editing grammatical features. I'll let @Jonas elaborate more on the issue itself, as he's the person to explain this. Thanks!
@Lydia_Pintscher: please find below the cases I believe are possible