Actually you can reference i18n messages even if the extension isn't installed: https://www.mediawiki.org/w/index.php?title=Extension:CampaignEvents&diff=prev&oldid=6958874

I feel like installing an entire extension just to produce some documentation in a slightly clearer way is overkill.

In T383155#10438752, @Pppery wrote:

Actually you can reference i18n messages even if the extension isn't installed: https://www.mediawiki.org/w/index.php?title=Extension:CampaignEvents&diff=prev&oldid=6958874

Oh, nice! I never even though about trying that.

I feel like installing an entire extension just to produce some documentation in a slightly clearer way is overkill.

It's not just that. Once installed it can be used normally, which for mw.o would presumably mean, if someone wants to use it for organising technical events like hackathons. Whether someone would want to do that, I don't know, nor did I ask. I just created this task quickly so I don't forget about it.

Hi @Pppery! Thanks for the comments on the ticket. I would like to clarify that the primary benefit of enabling the CampaignEvents extension on Mediawiki.org is actually not documentation. The primary benefit is so that it would be easier for people to organize and promote events that take place on Mediawiki.org.

For example, take the Language and Product Localization Community meetings. These meetings happen on Mediawiki.org (in the sense that the event pages and organized activity around the event takes place on that wiki). The organizers already ask people to sign up on-wiki in order to participate. So, the organizers of this series of events could use Event Registration instead (a tool from the CampaignEvents extension), which provides more robust and user-friendly features for registering participants, collecting optional demographic information, and communicating with participants.

Furthermore, if the organizers used Event Registration, their event would automatically appear in the Collaboration List, which would allow them to promote the event to a larger audience.

Finally, the extension has another tool called Invitation Lists. This tool is most useful to wikis that have content drives and edit-a-thons, but it may be useful to some users of Mediawiki.org as well.

I hope this explanation provides more clarity and context, and I'm happy to answer any questions you may have about the extension.

This should still get a discussion of some sort at https://www.mediawiki.org/wiki/Project:Village_Pump, but at this point I have no objection.

What I was objecting to is the use of an extension as a dummy, which seemed to be what was being proposed here.

(T383155#10449533 was just the triggers that should have occurred when a task is in the "Blocked on community consensus" column, since the task was previously in an inconsistent state)

In T383155#10456382, @Pppery wrote:

What I was objecting to is the use of an extension as a dummy, which seemed to be what was being proposed here.

(T383155#10449533 was just the triggers that should have occurred when a task is in the "Blocked on community consensus" column, since the task was previously in an inconsistent state)

Yup, sorry, that's my fault. The idea was to consider mw.org as a candidate for future releases not just for the inherent advantages provided by the extension's features, but also for documentation; I saw it as a plus, not the main motivation. But indeed, that was not explained in the original task description. The reason being that I just went "oh let me quickly file a task before I forget" and then ran out for dinner :D

@Daimona, has there been a discussion in the community?

In T383155#11454613, @neriah wrote:

@Daimona, has there been a discussion in the community?

Oh, actually, this was done as part of T409760, which involved broader communication to all communities. So, I'm closing this now.