WordPress.org

Making WordPress.org

Opened 10 months ago

Last modified 10 months ago

#3592 new enhancement

Dashboard Event Widget: Display 5 meetups instead of 3

Reported by: Nao Owned by:
Milestone: Priority: normal
Component: API Keywords:
Cc:

Description

In the metropolitan Tokyo area, close to 10 events may be scheduled per month within the 400km range.

This means that users may not see a local meetup close to their home until when there are only 2 other events within the 400km range, even if the organizer schedules it a month ahead of the time.

Depending on the schedule, the timing could be a few weeks before the local event takes place.

I'd say it's unlikely users go to an event over 100 km away because they can find a closer event (unless it's a large one with lots of speakers or WordCamp). A 400km radius covers about a third of the country.

Ideal Solution for Our Case

Just writing this out, even though I understand our situation is an edge case.

Personally, I feel the right mix to be the following for the case of cities near Tokyo.

  • 1 upcoming WordCamp within the country (Once a WC is scheduled it stays until it's over)
  • 5 meetups within a 100km radius

But for other cities in Japan, a 200km radius may be more reasonable.

Compromised Solution

If tweaking the radius range (or making exceptions) per city/country is not feasible, I'd like to see more upcoming events in the widget. This change provides 1) an incentive for organizers to schedule their events ahead of the time 2) a chance for attendees to find out their nearby events.

How about showing 5 events instead of 3 when they exist? This change will not affect areas will less frequent meetups but will help those with several nearby meetups.

Keeping the 400km radius isn't ideal for my location, but I can live with it as long as more meetups are shown.

Attachments (3)

japan-400km.png (284.5 KB) - added by Nao 10 months ago.
Map of 400 km radius from Tokyo
100km-radius.png (207.6 KB) - added by Nao 10 months ago.
100km radius from Tokyo, Kawaguchi (Saitama Prefecture), Takasaki (Gunma Prefecture)
50km-radius.png (355.8 KB) - added by Nao 10 months ago.
50km radius from Tokyo, Kawaguchi (Saitama Prefecture), Takasaki (Gunma Prefecture)

Download all attachments as: .zip

Change History (11)

@Nao
10 months ago

Map of 400 km radius from Tokyo

This ticket was mentioned in Slack in #community-events by nao. View the logs.


10 months ago

This ticket was mentioned in Slack in #polyglots by nao. View the logs.


10 months ago

#3 @casiepa
10 months ago

How about making it parameters that a site admin can set?

  • Number of meetups to show (between 2 and 4)
  • Number of WordCamps to show (between 1 and 3)
  • Radius: 100km - 400km
  • Limit to country: Y/N

But the total of the first 2 can never be over 5

This ticket was mentioned in Slack in #polyglots by casiepa. View the logs.


10 months ago

#5 @nukaga
10 months ago

I agree that a site admin can set. The situation of the place where we live is various.

#6 in reply to: ↑ description @iandunn
10 months ago

  • Component changed from General to API
  • Priority changed from low to normal

Replying to Nao:

In the metropolitan Tokyo area, close to 10 events may be scheduled per month within the 400km range.

The 400km range is only for WordCamps, for meetups the range is 100k.

  • 1 upcoming WordCamp within the country (Once a WC is scheduled it stays until it's over)

The upcoming change to pin camps to the widget (#wp41112) should help with that.

How about showing 5 events instead of 3 when they exist? This change will not affect areas will less frequent meetups but will help those with several nearby meetups.

It could affect some infrequent meetups, if they setup recurring events several months into the future. We could avoid that by having the API only include meetups that are less than ~4 weeks away, though.

I still worry about adding too much clutter to the UI, though. In the original design, 3 was chosen specifically to try and balance the amount of information that users are presented with.

Just writing this out, even though I understand our situation is an edge case.

I think it's still worth considering, and it's very helpful to get feedback from various communities, since they're all so different.

I definitely agree that there isn't a good one-size-fits-all solution, but I also have a hard time finding an elegant solution for all (or even most) use cases that doesn't have considerable downsides (for UX, maintainability, complexity, etc).

I think it's also important to keep in mind that the original purpose of the widget wasn't to help insiders like us keep track of 100% of the events that we’re interested in; it was to introduce new people to their local WP community. If someone wants to keep to track of 100% of events, then there are probably better ways, like signing up for meetup.com email notifications.

If we can find elegant ways to make the list of events more relevant to the user, though, that's definitely worthwhile. Maybe the API can look at the total number of upcoming events, and if there are more than ~3 in the next ~2 weeks, then it would remove some of the farther events from the response, so that events closer to the user are given precedence.

Another idea would be to use a translated string to set the radius per locale, and then pass that value to the API. That way smaller countries with large populations and active communities could set different locales than larger countries where driving longer distances is common. Using a translated string would prevent us from having to build/maintain per-country logic in the API itself. The API would probably want to enforce a reasonable min/max value, though.

One downside to that approach is that the best value for a locale is subjective, and different translators might have conflicting opinions. That's not necessarily a huge problem, though, since the translation editors could help find a reasonable compromise.

Related #wp41442, #2998

#7 @Nao
10 months ago

Thanks @iandunn !

The 400km range is only for WordCamps, for meetups the range is 100k.

@casiepa and others mentioned this in Slack, thanks for confirming.

It could affect some infrequent meetups, if they setup recurring events several months into the future.

I didn't think of such a case. I agree that seeing 4+ upcoming meetups that are months away could be not so useful for users.

We could avoid that by having the API only include meetups that are less than ~4 weeks away, though.

I think it's also important to keep in mind that the original purpose of the widget wasn't to help insiders like us keep track of 100% of the events that we’re interested in; it was to introduce new people to their local WP community.

It was not my intention to keep track of all events (We already have WordPress Events Calendar for that in Japan). I get the feedback that the number of new attendees visibly increased for many meetup groups here, therefore the organizers are really eager to see their own event listed as soon as possible after scheduling one (they love this feature! and I think that's one of the reasons the number of meetups incresed this year).

Generally speaking, I'm not a huge fan of using translation string to set a value for default configuration, but it sounds like a possible good solution for this. One downside I can think of is that it doesn't really work for transplant users who are using WP in their native language (e.g. someone who lives in Germany but is from Australia, using WP in en_AU).

If we can find elegant ways to make the list of events more relevant to the user, though, that's definitely worthwhile. Maybe the API can look at the total number of upcoming events, and if there are more than ~3 in the next ~2 weeks, then it would remove some of the farther events from the response, so that events closer to the user are given precedence.

I like this too, and I think it will work for Japanese users if the threshold is set right. For me, 100km is a quite long distance to travel for a short meetup. I originally said 100k for Tokyo, but now that I see the map more closely, 50k is probably a more reasonable number.

As you said, the distance one's wiling to travel for a meeting can be very subjective. It will depend the public transportaiton system, car ownership, family and work situation, etc. I'm interested in hearing opinions from people in various situations.

@Nao
10 months ago

100km radius from Tokyo, Kawaguchi (Saitama Prefecture), Takasaki (Gunma Prefecture)

@Nao
10 months ago

50km radius from Tokyo, Kawaguchi (Saitama Prefecture), Takasaki (Gunma Prefecture)

#8 @dd32
10 months ago

It's worth noting that the radius is a box, not circular, so it's a box of 100km north/east/south/west of the central points. When you're looking at meetups which are at the NW/NE/SE/SW directions that means it's closer to 150KM radius.

I think the ideal solution for areas such as Japan where there's lots of events within a small radius is that the API continues to return data as it does, but the client-side code slims it down to only those which are relevant, for example, "Only show meetups within a 30km radius".

The API could also add the circular radius checks (and return any boxed area events if the circular radius doesn't return anything, to maintain current results) which may also help slightly in the case of Japan, as it seems the locations are more likely to be at those box corners.

Note: See TracTickets for help on using tickets.