Hello @gonyeahialam! Can you add the design example to this ticket, now that we have closed out the investigation and will begin the engineering work soon? Thank you in advance!

And @cmelo, the ticket is ready for you to review; thank you!

@ifried There doesn't seem to be a task for this user story - showing the wikis on the Eventdetails page:

As a participant, I want to be able to see the wiki(s) of the event when I view the EventDetails page or discover the event in other places, so I understand on which wiki(s) the event will be have an impact and which communities I can expect to interact with during the event.

Also are you thinking of showing this info on the event details dialog too

Discussed today at eng+design. A few ideas/thoughts:

• Maybe we should limit the number of wikis organizers can enter, at least for the MVP version. This would make it easier to display them.
• What to do with events that do not specify any wikis? And what about events that target all wikis (e.g., global campaigns)? For example, show a radio in the form like the following:

Is this event targeting specific wikis?
◯ No
◯ All wikis
◯ Specific wikis

Enter the wikis that the event will target
[___________________________________] <-- this is the field shown in the prototype, and would only be shown if "specific wikis" is selected above

• In the current specs, the icon for the list of wikis is the Wikimedia logo. This wouldn't work for third parties, so wondering if there's an alternative icon we could use here.

@Daimona What do you mean by third parties

In T366765#9950264, @gonyeahialam wrote:

@Daimona What do you mean by third parties

MediaWiki sites that are not hosted by the WMF (e.g., Fandom).

In T366765#9950520, @Daimona wrote:

In T366765#9950264, @gonyeahialam wrote:

@Daimona What do you mean by third parties

MediaWiki sites that are not hosted by the WMF (e.g., Fandom).

Are they going to be using our tool?

In T366765#9951014, @gonyeahialam wrote:

In T366765#9950520, @Daimona wrote:

In T366765#9950264, @gonyeahialam wrote:

@Daimona What do you mean by third parties

MediaWiki sites that are not hosted by the WMF (e.g., Fandom).

Are they going to be using our tool?

I don't know. But, it's going to be easier to adopt if it doesn't hardcode too much Wikimedia stuff. Note that, for the specific text we're talking about (as well as in general), we can have a WMF-specific version. But we still also need a generic version of it.

In T366765#9926888, @gonyeahialam wrote:

@ifried There doesn't seem to be a task for this user story - showing the wikis on the Eventdetails page:

Yup, there should be a task for that. I see you created one (T369182). Thank you! We can fill in more details on that later.

As a participant, I want to be able to see the wiki(s) of the event when I view the EventDetails page or discover the event in other places, so I understand on which wiki(s) the event will be have an impact and which communities I can expect to interact with during the event.

Also are you thinking of showing this info on the event details dialog too

I'm not so sure about this, since the dialog is already quite cluttered and some events target many wikis. I'm inclined to think no for now, and we should just focus on the EventDetails page. What do you think, @gonyeahialam?

In T366765#9949906, @Daimona wrote:

Discussed today at eng+design. A few ideas/thoughts:

• Maybe we should limit the number of wikis organizers can enter, at least for the MVP version. This would make it easier to display them.

Yes, I agree, and I actually wrote down that we should in T367224 (not sure if that was the best ticket to add that there should be a limit into the AC though). I don't know what the limit should be, but perhaps 100 wikis and I have pinged some community folks in the ticket to get their feedback.

• What to do with events that do not specify any wikis?
• And what about events that target all wikis (e.g., global campaigns)? For example, show a radio in the form like the following:

Is this event targeting specific wikis?
◯ No
◯ All wikis
◯ Specific wikis

Yup, good questions! My first thought was, "What kind of event targets no wikis and/or all wikis?" And I thought: Things like conferences, movement events, affiliate meetups, some hackathons, etc. So, I don't think "all wikis" applies to campaigns, really, but it does certainly for many other event types. Since we do want to allow flexibility for all event types, I do think it makes sense to have a global or all wikis option.

The next thing that I asked myself is: Can we consider "no wikis" as the same thing as "all wikis," or no? I don't think they are exactly the same thing, but if we're thinking about what information people want to know in the first place (i.e., is this event for my wiki, or no? can I join, or no?), then "all wikis" may be sufficient.

So, decision #1: We should have an "All wikis (anyone can join)" option. How does that sound?

The second question is whether it should be optional or required for an organizer to specify the wiki. Initially, I thought it should be optional, since some events do not really apply to a wiki. Now I am wondering if the "All wikis (anyone can join)" option covers all bases, so it would be best to make it required, so we get more complete data that way. I just don't know if there are certain issues users may encounter if we make it required that I am not thinking about, or if it's best for privacy/general freedoms of the user to make it optional. Curious to hear if @gonyeahialam, @Rmaung, @Iflorez, and @Sadads have opinions on this.

• In the current specs, the icon for the list of wikis is the Wikimedia logo. This wouldn't work for third parties, so wondering if there's an alternative icon we could use here.

Hmmm, I think this is a design question; cc @gonyeahialam.

I think @ifried conclusion that all wikis, or no target wikis is kindof similar in could leave to confusing mixed measurement. Maybe you could clarify this in two stages: is the event about editing the Wikis? Which wikis? (All, or specific wikis)

I think if this covers all use cases then we can make it required.

This is my current exploration based on the discussion above:

I question that comes up here is how will events not targeting any wikis be shown to editors on the event list.

Thanks for this thinking and feedback, @Sadads & @gonyeahialam.

• Yup, I think we can simplify it by asking: "Will participants contribute to specific wikis?" Then, the options can be No or Yes (and the Yes option would ask them to select the wikis). I don't think we need "Yes, all wikis."
• For events that were created in the past, this all depends on whether we make wiki of the event optional or required. I will check in with some internal teams to see what is best and then update this ticket.

@ifried For events in the past in which organizers could not specify which wiki the event targeted, 1 idea could be to have an 'unspecified filter' in the event list. This way users can choose to show such events or not.
Additionally, for such events, in place of the wikis tag that shows on the event list we can put an unspecified tag.

Also, if an event is created for example in swahili wikipedia but the Wikis was not specified by the organizer we can still show it when the swahili wikipedia filter is applied on the event list. This ensures the event isn't lost.

In T366765#9966846, @gonyeahialam wrote:

@ifried For events in the past in which organizers could not specify which wiki the event targeted, 1 idea could be to have an 'unspecified filter' in the event list. This way users can choose to show such events or not.
Additionally, for such events, in place of the wikis tag that shows on the event list we can put an unspecified tag.

We discussed this work in the team meeting today. I will share some of the questions that came up and some of my early thoughts about them below:

• Engineers recommend that the 'wiki' field is not optional because it would make it confusing when using the Collaboration List. For example, if someone filters for events that are for all wikis on the Collaboration List, some of those events may be truly for 'all wikis,' while other events will simply be categorized as 'all wikis' because the organizer missed/forgot/didn't feel like specifying the wikis. I think this makes sense, and I am happy to update the AC to reflect this. We also have some design concepts for how this should work.
• Someone brought up that we should ask if an event is about contribution -- and only then we ask if it has a target wiki. But what if there is a meeting to discuss Wikimedia Commons, or what if there is a community call for members of the Indic Wikisource community? In this case, either one wiki or a collection of a few wikis is still the focus, even if it is not about strictly contributing. So, perhaps one does not need to be dependent on the other.
• If we always require a wiki selection, then we need to ask: What about cases when the 'target wiki' is not super clear? For example, if there is an affiliate meeting (for example, Wikimedia Sweden), that affiliate may largely have members contribute on a specific wiki (such as, Swedish Wikipedia), but it not necessarily limited to that wiki (for example, they may also contribute to Wikidata, Wikimedia Commons, English Wikipedia, etc). In that case, "all wikis" doesn't sound quite right. Perhaps "no specific target wikis" might be more accurate. Meanwhile, there may be a restriction on language (such as the event taking place in Swedish) or on a community (the fact that it is for affiliate members). But those data points probably need to be separate tickets.
• The main use case, overall, is to make it people to find events that interest them in the Collaboration List. There are a few main parts of this:
  • Event type (‘contributing content’ ‘contributing photos’)
  • Target wikis
  • Community focus (language, region, affiliate)
  • Certain people (newcomers, organizers, translators)
• I think we can cover most use cases by focusing on 3 things at first: event type, event wiki(s), and if the event has newcomer support (which can we define as newcomer training and/or newcomer mentors -- and we consult with other teams to see what that would be). We can focus on one of these at time, but the three could be a powerful combination for an MVP to increase usability.
• A question about past events got raised. Basically, how do we handle them in the Collaboration List? Basically, if an event does not have wiki of the event attached to it, I guess we could either lump it into 'no specific wikis'/'all wikis' or have another tag for all events from before the wiki categorization was available. I think we should opt for the former, but allow organizers to edit and update their old events to specify the wiki, if they want.