This label doesn't seem to be clear/specific enough. I would suggest 'Event format', 'Attendance Format' or 'Participation Mode'. @ifried

Thanks for all of the ideas shared, @Daimona & @gonyeahialam!

Language stuff is so hard, especially when we consider the fact that whatever we choose will be translated into many languages. However, I think Participation options is the best. Here is what I think now about all of the options:

• Participation options: To me, this one is actually the most clear. It shows that we're focused on the ways (i.e., options) that people can participate (i.e., participants).
• Event format: To me, this is the second best of the options presented, but it's still pretty unclear. Event format could mean so many things, which could have more to do with the event than the type of participation.
• Attendance Format: To me, this one is a no. We only use the word "Participants" so far, so "Attendance" could be a bit confusing. Format is also vague, and it sounds like it could be related to something more like a plan/schedule/programming format.
• Participation Mode: To me, this one is a no. This is the least clear of all of the options to me. If I saw this alone, I would have no idea what it meant.

Change #1152266 had a related patch set uploaded (by Daimona Eaytoy; author: Daimona Eaytoy):

[mediawiki/extensions/CampaignEvents@master] Rename "meeting type" to "participation options" in internal code

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

Change #1152328 had a related patch set uploaded (by Daimona Eaytoy; author: Daimona Eaytoy):

[mediawiki/extensions/CampaignEvents@master] Rename "meeting type" to "participation options" in i18n

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

Change #1152329 had a related patch set uploaded (by Daimona Eaytoy; author: Daimona Eaytoy):

[mediawiki/extensions/CampaignEvents@master] Rename "meeting type" to "participation options" in user-facing code

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

Change #1152266 merged by jenkins-bot:

[mediawiki/extensions/CampaignEvents@master] Rename "meeting type" to "participation options" in internal code

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

Change #1152328 merged by jenkins-bot:

[mediawiki/extensions/CampaignEvents@master] Rename "meeting type" to "participation options" in i18n

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

Change #1152329 merged by jenkins-bot:

[mediawiki/extensions/CampaignEvents@master] Rename "meeting type" to "participation options" in user-facing code

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

Change #1156409 had a related patch set uploaded (by Daimona Eaytoy; author: Daimona Eaytoy):

[mediawiki/extensions/CampaignEvents@master] tables.json: add note on new terminology for participation options

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

Change #1156870 had a related patch set uploaded (by Daimona Eaytoy; author: Daimona Eaytoy):

[mediawiki/extensions/CampaignEvents@master] Update "event type" to "participation options" in confirmation e-mail

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

It just occurred to me that in several places, we refer to participation options as "Location":

• In the event page header, the accessibility label for the "mapPin" icon
• In the event page "more details" dialog, the section title for participation options
• Special:MyEvents has a "Location" column
  • It is also used as part of the message key, but not the message content, for various messages used in Special:MyEvents and Special:AllEvents
• Special:EventDetails has a "Location" section

I assume we should also change all these to "participation options", right?

Thanks for checking on this, @Daimona!

Yes, I think we should change it all to "Participation options." It has always seemed odd to me to use the label of "Location" for something like "Online event," so I think it is more fitting anyway and it goes with the new standard that we have implemented.

I approve of this change.

@ifried do you know about the events impact report? It's outside of our team / extension but wondering if that should be changed too or if it's still used?

@vaughnwalters, yes and good call-out! I will ping @Arinaigu in this ticket and on Slack so she's aware of the change. She and I have talked about in the past, but the update now is that it's actually happening. Thank you for the reminder!

Change #1156895 had a related patch set uploaded (by Daimona Eaytoy; author: Daimona Eaytoy):

[mediawiki/extensions/CampaignEvents@master] i18n: Rename "location" to "participation options"

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

Change #1156899 had a related patch set uploaded (by Daimona Eaytoy; author: Daimona Eaytoy):

[mediawiki/extensions/CampaignEvents@master] i18n: update qqq for messages recently renamed

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

Change #1156900 had a related patch set uploaded (by Daimona Eaytoy; author: Daimona Eaytoy):

[mediawiki/extensions/CampaignEvents@master] Update "location" to "participation options" where appropriate

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

Change #1156870 merged by jenkins-bot:

[mediawiki/extensions/CampaignEvents@master] Update "event type" to "participation options" in confirmation e-mail

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

Change #1156895 merged by jenkins-bot:

[mediawiki/extensions/CampaignEvents@master] i18n: Rename "location" to "participation options"

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

Change #1156900 merged by jenkins-bot:

[mediawiki/extensions/CampaignEvents@master] Update "location" to "participation options" where appropriate

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

Change #1156899 merged by jenkins-bot:

[mediawiki/extensions/CampaignEvents@master] i18n: update qqq for messages recently renamed

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

Change #1156409 merged by jenkins-bot:

[mediawiki/extensions/CampaignEvents@master] tables.json: add note on new terminology for participation options

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

Acceptance criteria

• "Meeting type" is renamed to "Participation options" in:
  • ✅ API parameters and response structures
  • ✅ Class, function, method, variable, property names etc.
  • ✅ User-visible elements (labels, sections, tooltips, accessibility text, etc.)

• ✅ In the registration confirmation email, "Event type" is renamed to "Participation options"
  • QA note: This was correctly renamed, this is a follow up task for the contents of participation options which are not displaying correctly T397546

• "Location" is renamed to "Participation options" in:
  • ✅ The accessibility label for the "mapPin" icon in the event page header
    
  • ✅ The section header in the event page "more details" dialog
    
  • ✅ The table column in Special:MyEvents
    
  • ✅ Various message keys (not content) used in Special:MyEvents and Special:AllEvents
    
    • ❓ QA note: I don't know how granular we want to be but in qqq.json there is still "campaignevents-eventpage-btn-manage": "Label of a button in the registration header and popup on event pages. Organizers can use the button to change the details of the event, like the start and end date or the location.", when that could be end date or participation options. Same thing in interface CampaignEventsGetEventDetailsHook in CampaignEventsGetEventDetailsHook.php in the comments for the params. I realize this is inconsequential because they're both helper texts, but calling it out here anyway.
  • ✅ The section header in Special:EventDetails
    

@Daimona this looks good to me. See my one annoying note above, and then if we want to ignore that, this can go to product sign off.

In T387493#10935727, @vaughnwalters wrote:

• ❓ QA note: I don't know how granular we want to be but in qqq.json there is still "campaignevents-eventpage-btn-manage": "Label of a button in the registration header and popup on event pages. Organizers can use the button to change the details of the event, like the start and end date or the location.", when that could be end date or participation options. Same thing in interface CampaignEventsGetEventDetailsHook in CampaignEventsGetEventDetailsHook.php in the comments for the params. I realize this is inconsequential because they're both helper texts, but calling it out here anyway.

These are deliberate. I did not change them because they're still correct if we assume "location" to mean "address + country". I thought about changing them anyway, but eventually I chose not to because if I think about an event in general, and what information could change, the "when" and the "where" are the first two things that come to mind.

In T387493#10935746, @Daimona wrote:

In T387493#10935727, @vaughnwalters wrote:

• ❓ QA note: I don't know how granular we want to be but in qqq.json there is still "campaignevents-eventpage-btn-manage": "Label of a button in the registration header and popup on event pages. Organizers can use the button to change the details of the event, like the start and end date or the location.", when that could be end date or participation options. Same thing in interface CampaignEventsGetEventDetailsHook in CampaignEventsGetEventDetailsHook.php in the comments for the params. I realize this is inconsequential because they're both helper texts, but calling it out here anyway.

These are deliberate. I did not change them because they're still correct if we assume "location" to mean "address + country". I thought about changing them anyway, but eventually I chose not to because if I think about an event in general, and what information could change, the "when" and the "where" are the first two things that come to mind.

Okay thanks for the explanation. Sending to product sign off.