Look for ones relevant to your area of expertise, and confirm that they're
unused, then submit patches for their removal. You can enlist them for
SWAT, or use the tag "cleanup" and I or others may deploy them for you.
I'll run the script again sometime later, but in the mean time, feel free
to edit the page to strike-out or remove entries that you've dealt with.
> I wrote a script to detect unused wmf-config code.  Specifically, unused
> settings and conditional blocks for configuration that no longer exists in
> The script cross-references any wg- identifiers in wmf-config with
> Legoktm's Codesearch tool  and reports those that have no matches
> outside wmf-config. 
I checked the CirrusSearch ones and most are indeed unused, except that
this one: CirrusSearchCrossProjectBlockScoreProfiles - seems to have a
mention as CirrusSearchCrossProjectBlockScorerProfiles - I wonder if
it's a typo.
Generally CirrusSearch uses some configs without 'wg' prefix, but in
this case it doesn't seem to be an issue.
The script looks for wg* variables assigned or read in wmf-config that
search results in any other Wikimedia git repo.
Normally, when a wg variable is assigned in wmf-config it is to set it to a
certain value, to be consumed by MediaWiki core (or an extension).
In the case of wgUseContributionTracking, it is not a MediaWiki setting.
Rather, it is an internal setting created in wmf-config/CommonSettings,
solely for to be used
The concept of temporary variables internal to wmf-config is quite common.
However, the script
won't (and shouldn't) find those normally because those variables are
conventionally prefixed "wmg",
instead of "wg". But, the ContributionTracking setting uses the "wg"
prefix. Hence, the false positive
because this is a "wg" setting referenced exclusively within wmf-config.