[wp-meta] [Making WordPress.org] #703: Keep track of which WordCamps each profile has spoken at and organized

[Making WordPress.org]

#703: Keep track of which WordCamps each profile has spoken at and organized
----------------------+----------------------
  Reporter:  iandunn  |      Owner:
      Type:  defect   |     Status:  new
  Priority:  normal   |  Component:  Profiles
Resolution:           |   Keywords:
----------------------+----------------------

Comment (by coffee2code):

 @iandunn: Unfortunately, the BP groups feature does not have membership
 meta. However, the removal request could include the wordcamp_id as had
 been sent for the add-activity request (assuming the id represents a
 specific year WordCamp). `handle_wordcamp_association()` could be modified
 to check the activity stream to see if they were added as an
 organizer/speaker for a WordCamp != wordcamp_id. If they aren't reported
 as being an organizer/speaker for another event, remove the association.

 @Otto42: The association handler is pretty straightforward: if the service
 requests a user add or removal from an association, then it simply does
 that. Handlers are custom per-service, so the WordCamp handler could
 definitely be customized (as I noted to Ian).

 Could the badge be based solely on the activity log query you suggest
 rather than a group association? Sure, but we go down the path of having
 more custom run-time badge determination querying and logic. Will that
 query scale for how immense the activity log will get, or scale for
 handling of similar custom badge querying? Maybe. One goal I had was to
 prevent run-time determination of things that are known and relatively
 unchanging.

 Another way to approach this is to have the WordCamp activity handler also
 handle the association management. If we added the ability to send a
 remove (or undo) activity, then an previously reported activity entry
 could be removed from the activity stream and group association could be
 re-evaluated.

 All the suggestions mentioned heretofore presume we know the full
 organizer/speaker activity history (or that we retroactively add them).

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