Page MenuHomePhabricator

Enable CampaignEvents extension on Meta-wiki
Open, In Progress, Needs TriagePublic

Description

Checklist

Note that some items were already completed for T318592 and are skipped here.

  • Passed reviews:
  • Create the schema
    • Schedule a dedicated window that does not conflict with other deployments - diff
    • Actually create the schema: mwscript sql.php --wiki=metawiki --cluster=extension1 --wikidb=wikishared /srv/mediawiki/php-1.40.0-wmf.11/extensions/CampaignEvents/db_patches/mysql/tables-generated.sql
  • Write config patches
    • Configure meta to use the wikishared DB
    • Enable the extension on meta
  • Schedule the config patches for deployment - diff
  • DEPLOY TEH THING
  • Add meta to the timezone script cron (T320403)

Acceptance Criteria

  • Enable the CampaignEvents extension on Meta-wiki
  • Test for the following basic actions:
    • Any user can create an event page in the event namespace
    • Organizers are a configurable user group
    • Only organizers who created an event page can enable registration
    • Organizer can specify event date, time, time zone, location, video conference link, chat group link
    • Organizer should see information at bottom of configuration form on what data is collected on participants and, if on a WMF project, reminder of WMF youth safety policy
    • Time zone of event is displayed as follows:
      • In person: as specified by organizer
    • Online & hybrid: time zone preference for logged in user, wiki default for logged out users
  • Organizer can edit registration information
  • Organizer can disable registration
    • Participant can join event by clicking on the 'Register' button
    • Participant must agree to terms of use and privacy policy (if on a WMF project)
    • Participant can choose between public and private registration
    • Visibility rules are as follows:
      • Organizer can see list of all participants
      • Participants can see their registration info and public participants
      • General users can see list of public participants
    • Confirmation email should be sent to participants after registering for event if:
      • They have email address associated with their account
      • They have not opted out of email communication via Preferences

Event Timeline

ifried updated the task description. (Show Details)

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

[operations/mediawiki-config@master] Configure the CampaignEvents ext to use the x1.wikishared db for meta

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

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

[operations/mediawiki-config@master] Enable the CampaignEvents extension on meta

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

Daimona changed the task status from Open to In Progress.Thu, Nov 24, 2:55 PM
Daimona updated the task description. (Show Details)
Daimona added a subscriber: Quiddity.

@Quiddity On second thought, do you think this should be in Tech News, since it's meta only? OTOH it's meant to be used by everyone, not just meta users. And on the other-other hand, initially only a predetermined list of users would be able to create events (T316227). I really don't know. If we do want to announce it, I think we could use something similar to what we used the last time (T318592#8367445). The deployment is scheduled for the 30th, so later next week.

@Daimona Good questions! My thoughts/questions:
It was mentioned in Tech/News/2022/45 3 weeks ago as being on the testwikis.
We do try to keep entries limited to those that are of interest to a very large number of readers/projects. (Rough inclusion criteria here)
We do also informally try to avoid too many repetitions of news about a specific thing. 1 or 2 is ideal, limiting any more to only major new changes.

For wording, and for timing: It's good to think about the goals of an announcement, and whether any necessary "more info" pages/docs are in place yet, and whether folks from the long-tail of "I have limited-time" might be better served by postponing any non-urgent announcements (and people with more time, or a known interest in the topic/feature, can often be reached in other more specific venues, e.g. mailinglists or WikiProject talkpages or chat-channels).

In sum: I'd suggest waiting a little while for this 2nd global notice about the feature (anywhere from 1 week to a few weeks), so that the early adopters/testers have time to help to create/polish/translate any user-docs, and there has been time to report (and perhaps resolve) any bugs/issues that didn't get noticed until the meta release and initial larger-scale test-usage & real-usage.
It's also easier to decide once you/we know the exact wording and links that are intended to be in the entry, so perhaps you/someone can draft that now/soon, and then we can include it in a future week's edition? HTH!

In sum: I'd suggest waiting a little while for this 2nd global notice about the feature (anywhere from 1 week to a few weeks), so that the early adopters/testers have time to help to create/polish/translate any user-docs, and there has been time to report (and perhaps resolve) any bugs/issues that didn't get noticed until the meta release and initial larger-scale test-usage & real-usage.
It's also easier to decide once you/we know the exact wording and links that are intended to be in the entry, so perhaps you/someone can draft that now/soon, and then we can include it in a future week's edition? HTH!

Thank you, makes sense to me! I will let @ifried weigh in on this once she's back. I was wondering if it might be a good idea to mention our upcoming office hours in the announcement (something along the lines of: "it will be deployed on meta, you can come to the office hours to learn more, ask questions etc.").

Thanks for the thoughts on this & the ping!

Yup, I understand the need to not over-message. One thing to consider, as Daimona mentioned, is that we may want to invite people to our upcoming office hours, which are on December 5 at 6 pm UTC and December 10 at 12 pm UTC. By the time of the office hours, the extension will be enabled on Meta-Wiki and we will be asking people if they want to be an early test organizer of the tool. The goals of the office hours are to demo the tool and collect usernames of those interested in being organizer testers.

I suppose the Tech News issue that comes out in 2 weeks will be on December 5th? If it will come out before 6 pm UTC that day, we can reach people before both office hours, so they could learn about the events and join, if interested.

Alternatively, we could post another announcement much later (for example, in February/March 2023) when we have released more features to the tool and have created some sort of organizer user group/right for its usage, but I don't know if that is too far in the future and will perhaps miss out on the window to invite people for feedback and testing earlier.

What do you think, @Quiddity? Curious to hear your thoughts! Thanks in advance.

Thanks, both! I'm a bit hesitant about such a broad announcement, given that the meta-wiki version won't immediately be open to widespread testing, and the meetings will presumably only be in English. I wonder if a more targeted message to specific pages/mailinglists/etc might be preferable?

However, if you're certain it needs to be included, we could include it this week once we have a message. If so, please could you propose wording for the message? At a rough-guess, it would be something like:

(In the "Future changes" section?)
The Event Registration tool will be enabled at Meta-wiki. There are two meetings with the team next week (in English) to demonstrate the tool, collect usernames for early access to test it, and to collect feedback, on 5 December at 6pm UTC and on 10 December at 12pm UTC.

Hello @Quiddity! To clarify, our office hours will have language support for Arabic, French, and Swahili, but regardless, your thinking makes sense and works for us. In that case, the team will focus on more targeted messaging for the release and office hours for now, and we can perhaps have a Tech News announcement once the tool is more broadly available to users after the early test phase on Meta-Wiki. Thanks!

ifried updated the task description. (Show Details)

Update: I removed the announcement in Tech News as part of the AC.