https://bugzilla.wikimedia.org/show_bug.cgi?id=13953

--- Comment #16 from Kunal Mehta (Legoktm) <[email protected]> ---
(In reply to comment #15)

> The separate extension would be very small, and essentially only call the
> core
> ResourceLoader and LB/DB_Multi interface and the CentralAuth interface. So
> there would be no added value in separating it because it has no re-usable
> components. And the components it uses that are re-usable are already
> available
> for other extensions to depend on in core or CentralAuth.

Having a small extension that serves a specific purpose isn't a problem IMO.

If your wiki uses a shared user table, or any other non-CA global
authentication configuration (LDAP possibly), then it's entirely re-usable. I'm
not aware of what in core that offers this feature, nor any other extensions
(excluding Skizzerz's extension mentioned above).

> I think we should either reject this feature, or add it to CentralAuth.

Rejecting this feature isn't an option ;)

> Also note that, like user and site css/js in core (wgAllowUserJs etc.), this
> is
> also behind a configuration flag. So any concerns an admin may have are
> addressed by that.

If split out to another extension, there is no need for a feature flag, you
either enable the extension or you don't.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
Wikibugs-l mailing list
[email protected]
https://lists.wikimedia.org/mailman/listinfo/wikibugs-l

Reply via email to