--- Comment #14 from Tisza Gergő <> ---
(In reply to Nemo from comment #12)
> I'm sorry but you clearly didn't even read what you're commenting: just look
> at bug 54197 comment 0; and you mention LiquidThreads as example, well
> LiquidThreads deploys have been frozen (wontfix'ed) for years.

bug 54197 means that archiving does not work reliably; that is a non-issue if
you don't mind archiving being disabled in the first place.

LiquidThreads is wontfixed because it is being superseded by Flow; also, unlike
AFT, it does modify core features (specifically how talk page content is
stored), so having to convert a wiki from LQT to Flow (or even just backing out
of LQT) is a significant maintenance burden. Backing out of AFT is just a
trivial config change.

(In reply to Bawolff (Brian Wolff) from comment #13)
> Bugs (or at least important ones) in most legacy extensions without
> developers assigned to them tend to get fixed by platform team or interested
> random volunteers in my experience. I don't think its fair to compare AFT's
> status to your average not actively developed extensions (Except maybe LQT,
> its status is probably similar to that)

The video extensions for example have not been actively developed for a while
(by the WMF, anyway), and I would guess they are more complex than AFT, but I'm
sure no one thinks that a good reason to disable them.

The way I see it, worst case there will be serious bugs and no one will fix
them, in which case the extension can still be turned off at that point; given
that it uses a separate table, it's unlikely that any problem it causes would
persist after that. Best case, there is no such bug and a bunch of wikis get a
useful tool they wanted, for free.

You are receiving this mail because:
You are the assignee for the bug.
You are on the CC list for the bug.
Wikibugs-l mailing list

Reply via email to