Page MenuHomePhabricator

Default ThanksSendToBots to true in extension
Open, LowPublic

Description

👀 What?

What is the problem?

  • Bot operators feel underappreciated and burnt out, communities lack metrics for prioritizing bot development, and newcomers are confused by the inconsistency in the users that one can thank.

What does the future look like if this is achieved?

  • Bot operators feel appreciated for their work.
  • Editors members can easily thank bot operators without needing the extra clicks of writing a WikiLove message.
  • Communities and technical contributors have easy access to metrics that can inform prioritization of bots and individual bot tasks.
  • Wikis have an increased sense of camaderie and fun.

🤔 Why?

📈 Alignment with Annual Plan

  • Supports OKR WE1-2 ("Complete improvements to four workflows that improve the experience of editors with extended rights") and OKR bucket 2 ("Signals & Data Services").

💭 Why are you bringing this decision to the Technical Forum?

  • This change for Wikimedia wikis was unanimously supported by participants in a global RfC; I am bringing this decision to the TDF for implementing the feature in the extension itself (by default).

Event Timeline

Cross ref - T205224: Revisit inability to thank bots, T341388: Allow thanking bots on Wikimedia wikis

rOMWC1111732c8e98: InitialiseSettings.php: Allow thanking bots enabled thanking bots for all WMF wikis...

It's a config value in the extension (ThanksSendToBots), and it's default to false. This is easily changed on a wiki, but this really doesn't feel like is a tech-decision-forum thing.

What are you actually requesting here, because "Allow thanking bots in Extension:Thanks" seems to be done?

If I am interrupting it correctly, the request is to set ThanksSendToBots to true by default in the extension itself.

@Frostly If I am correct, would "Default ThanksSendToBots to true" be a better title for this task?

Frostly renamed this task from Allow thanking bots in Extension:Thanks to Default ThanksSendToBots to true in extension.Jan 14 2024, 2:13 AM
Reedy triaged this task as Low priority.Jan 14 2024, 2:22 AM
Reedy edited projects, added good first task; removed tech-decision-forum.

Change 956049 had a related patch set uploaded (by EpicPupper; author: EpicPupper):

[mediawiki/extensions/Thanks@master] Allow thanking bots

https://gerrit.wikimedia.org/r/956049

@Reedy if this task is uncontroversial and does not require the TDF, happy to re-submit the change!

@Frostly, @HouseBlaster's recent config change already allows anyone to thank any bot on any Wikimedia wiki. (See this log action by me thanking your bot on enwiki).

I personally don't see a strong enough argument being made (or a consensus being shown) here for this feature to be enabled on all non-wikimedia wikis as well (which include the non-wikimedia Minecraft Wiki, Miraheze, Fandom, Arch Wiki, some random guy's $1.12/mo private wiki etc). I agree this is a fun feature to have, but I feel having it be off by default is the correct approach, since it can incur some amount of unwanted database usage, which might/might not be acceptable to a wiki operator.

I personally don't see a strong enough argument being made (or a consensus being shown) here for this feature to be enabled on all non-wikimedia wikis as well (which include the non-wikimedia Minecraft Wiki, Miraheze, Fandom, Arch Wiki, some random guy's $1.12/mo private wiki etc). I agree this is a fun feature to have, but I feel having it be off by default is the correct approach, since it can incur some amount of unwanted database usage, which might/might not be acceptable to a wiki operator.

Of course, it's also cheap for them to turn it off. They can even set $wgThanksSendToBots = false; well in advance of them deploying the code that includes it.

If this task was about removing the config flag, I would understand there is more scope/weight to decide if that was desired.

It's not uncommon for extensions to follow whatever Wikimedia wikis are using as their default.

I will note, that I don't really care much either way.

As well, I don’t see this change causing significantly more logs in the database :)