Page MenuHomePhabricator

Introduce "Event" and "Event talk" namespaces
Open, Needs TriagePublic


These will be defined by the CampaignEvents extension; the names will be translatable. The outstanding question is whether we all agree on the name.

Background: In the future, we will have a special page for campaign events. This will be the type of page that all event pages using the registration tool will need to be, and it will also be the type of page that is created by a future event creation tool. The purpose of this ticket to determine the name of this special page.

Acceptance Criteria:

  • Determine the name for campaign event special pages

Event Timeline

Daimona renamed this task from [PLACEHOLDER] Introduce "Event" and "Event talk" namespaces to Introduce "Event" and "Event talk" namespaces.Mon, Dec 20, 2:33 PM
Daimona added a project: CampaignEvents.
Daimona updated the task description. (Show Details)
This comment was removed by cmelo.
cmelo changed the task status from Open to In Progress.Fri, Jan 7, 6:20 PM
cmelo changed the task status from In Progress to Open.
cmelo claimed this task.
cmelo removed cmelo as the assignee of this task.

Note: This is for the event pages, either creating by organizers or a future event creation tool.

I'm thinking CampaignEvents, since Events is really general and there are many non-campaign events that happen in them movement (such as conference, office hours, salons, etc). Before we make a final decision, I would like other opinions, including @fnartey, @IBrazal, @BVershbow_WMF, and @gonyeahialam.

I am talking to @fnartey now, and his preference is to use the generic term "Events." He says this is because, by using "Events," we can sometime in the future capture all the events happening in the Wikimedia movement. They may also want registration, calendar support, and other features we are building. One caveat he says is that it would only work for campaigns at first, but it would later allow us to have the mandate/vision to expand our tools to be more generalized for more movement activity. The con for this approach is that it would create confusion in the beginning (since they will think it covers all events). So, the team would need to explain to people what it means and how it will expand over time.

One thought @ifried has in response is that it may be expanding the scope of the team early on, and we just don't know yet if we will encompass so much in our team (rather than staying focused on campaigns specifically).

In our meeting today, @IBrazal said we should use 'CampaignEvents' because conference events may have different needs and use cases, and we should be explicit about who we are building for.

Also @fnartey asked if we can create a new namespace for events, so we can have things like:

  • Event:Campaign
  • Event: Conference