Problem/Motivation/Idea

After the event is done, we want to make sure we understand what went well and what didn't and figure out improvements for the next event. We can also promote that the event happened with some recaps (tweets/blogs) and such. And make sure that everyone has been credited for their work on the various issues.

Proposed resolution

Go through and update the tasks lists as needed.

Remaining tasks

  1. Go through all Drupal 10 compatibility issues to see if they should have been tagged for the event
  2. Gather statistics from the event
  3. Event "retro" at next Contribution Events Initiative meeting
  4. Figure out which documentation is usable as-is for future events or what changes to make
  5. Figure out how we can make these events regular
  6. Recap blog posts (TBD)
  7. Thank you tweets
  8. Double check credits on issues
  9. Credit mentors and participants
  10. Other (TBD)

Comments

kalabro created an issue. See original summary.

kalabro’s picture

Issue summary: View changes
kristen pol’s picture

kristen pol’s picture

Issue summary: View changes

Updated the summary based on the changes I did for the July issue:

https://www.drupal.org/project/contribution_events/issues/3300583#commen...

kristen pol’s picture

kristen pol’s picture

kristen pol’s picture

Issue summary: View changes
Status: Active » Fixed

Statistics are done so marking fixed.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.