User problem:

There are many impactful campaigns in the Wikimedia movement, but there isn't currently an an easy way to join Wikimedia campaigns or learn about new campaigns/events/edit-a-thons.

User story:

As a Wikipedia Admin, I want to decide if my community should utilize the CampaignEvents extension and have the ability to customize settings.

As the Campaigns Team, I want to scale the CampaignEvents extension to all Wikipedias, because this set of tools will help campaign organizers and will continue to growth and improve if they are utilized.

Background:

If admins are able to simply enable the CampaignEvents extension in Community Configuration, then the Campaigns team can ship this new extension more quickly and admins can decide if it's a feature they think campaign organizers should have access to on their wiki.

To begin thinking about how we can integrate Community Configuration into the CampaignEvents extension, we will start by first conceptualizing what the ideal setup and user experience would be for wikis that are considering turning on the various features available in the CampaignEvents extension. This ticket represents a conversation we will have as a team, so we can track the conversation as it evolves.

What can be used as a design baseline:

Community Configuration designs

Examples of existing forms:

• https://en.wikipedia.org/wiki/Special:CommunityConfiguration/HelpPanel
• https://en.wikipedia.org/wiki/Special:CommunityConfiguration/Mentorship
• https://en.wikipedia.org/wiki/Special:CommunityConfiguration/GrowthHomepage
• https://en.wikipedia.org/wiki/Special:CommunityConfiguration/GrowthSuggestedEdits

Early thoughts on how this could work:

• Event Registration (turn on/off)
• Event list (turn on/off)
• Invitation Lists (turn on/off)
• Namespaces where event registration is permitted (event, other?)
• Which user groups can grant/revoke the organizer right

Open questions:

• Do we want to allow flexibility in who manages the event organizer right? Or how it is organized?
• Do we want to allow flexibility in which namespaces can have event registration on the page?
• Do we want to allow flexibility on whether to allow the event namespace to be added?
• Once enabled, do we provide the option to disable, or do we need to remove that option since it could lead to major user experience issues if the extension is disabled while it is already in use?