[wp-meta] [Making WordPress.org] #2994: Make WordCamps sticky in the Events API

[Making WordPress.org]

#2994: Make WordCamps sticky in the Events API
-------------------------+-----------------------
 Reporter:  iandunn      |       Owner:  iandunn
     Type:  enhancement  |      Status:  accepted
 Priority:  normal       |   Milestone:
Component:  API          |  Resolution:
 Keywords:               |
-------------------------+-----------------------

Comment (by iandunn):

 Replying to [comment:3 casiepa]:
 > Not sure who would be allowed to put the sticky or how that would work.

 I'm not picturing any human interaction, the "stickyness" would just be
 determined by the API and the Core client, similar to your proposal.

 > My proposal would be like:
 > - The box shows 3 events.
 > - List all WordCamps in the next 3 months.
 > - If there are 2 or more WordCamps, only take the 2 earliest ones and
 show them together with the 1  upcoming meetup, ordered by date.
 > - If there is only 1 WordCamp, show in date order, together with 2
 upcoming meetups
 > - If there are no WordCamps, show 3 meetups.

 That's pretty close to what I was thinking. The only thing I'd maybe want
 to change would be how it handles 2+ camps.

 I worry about about showing 2 camps and only 1 meetup, since there are
 some cities that have several meetup events per week. If only 1 is
 displayed, that could have the unintended side-effect of some of those
 events only showing up for a day or two.

 I wonder if it'd be ok to increase the total # of events to `4` if there
 are 2+ upcoming WordCamps in the area? So, we'd show 2 meetups and 2
 WordCamps. That won't be very common, so I don't think having the extra
 row would add too much clutter. That would allow there to still be at
 least 2 meetups at all times. cc @mapk

 Another alternative would be to only have 1 sticky camp at a time. Either
 the one that's closest geographically, or the one whose date is nearest.
 I'd lean towards the one that's closest geographically. I think allowing
 `4` events sounds like a better option to me personally, though.

--
Ticket URL: <https://meta.trac.wordpress.org/ticket/2994#comment:4>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org