Merge the Contributors Meetup Async Update and the Core Contributor Check-in into one report

[cassiezamparini]

Description:

One issue that was not tackled during the Summit to Enhance the Core Contributor Experience was the potential merging of the Contributors Meetup Async Update and the Core Contributor Check-in into one report. We received some valuable feedback from the survey we sent out in 2024 and I think it would be beneficial to implement the feedback.

Feedback:

• 68.6% of CCs would like the "Contributors Meetup Async Update" and the "Core Contributor Check-in" to be merged into one report.

Contributors Meetup Async Update

Here are the requests:

• Improve the Working Group Updates section by making it:

  • Shorter
  • Less technical

• Improve the "Upcoming Events" section by:

  • Including milestones like the next planned release.
  • Including events in the community calendar.
  • Linking to Open edX events page.

• Improve the “Projects” section on the “Contributors Meetup Async Update” by (note: Members are confused why this section is “often” empty):

  • Including a list of current projects in a non-technical way.
  • Linking to info from the release planning spreadsheet.
  • Linking to platform-roadmap.

• Improve the “Next async update and meetup” by:

  • Updating the heading to "Get involved in the next Contributor Coordination Working Group meeting" and explain what the group actually does.
  • Ensuring draft agenda links to the most recent agenda, or possibly remove the link to reduce noise and add it to Slack like the other Working Groups do.
  • Possibly remove it to reduce noise as it’s on the Working Group Calendar.

Core Contributor Check-in

• Incorporate the updated questions as per this proposal.

Circulation

• Circulate update in Slack channels as well

[cassiezamparini]

@antoviaque and Natalia Chocontá (I can't seem to ping you on GitHub so will ping you in Slack about this issue):

What do you think of this potential task?

[antoviaque]

@cassiezamparini Looks like a good consolidation to me! 👍 And it might also be less work to have one report.

One remark is that I would try to focus the report on making it attractive to read, both in content and format. One way to change the perspective, both while elaborating the new format, and for people reading it afterwards, would be to change from a "report" format (which is rarely something attractive!) to a "newsletter" format.

[cassiezamparini]

Awesome @antoviaque...

I think one of the biggest things that I saw from the survey results is that 40% of people said they never see the report and would like it to be announced more broadly. The suggestions were the forum, slack and the CC mailing list. So I think that's low hanging fruit we can leverage. Plus I hope if more people see it more people will engage with the CC Checkin and see it's use in asking for help etc.

The results on whether it should be a newsletter were very divided almost 50-50. But I agree that this could be formatted in a better way. I'd be keen to take a stab at it and present an option to the community sometime. We'll also then need to appoint one person to run with this in future as Natalia does one and I do the other right now.

[cassiezamparini]

@jalondonot Could I ask you to ping Natalia about this thread? I can't seem to @ her on GitHub and would like her two cents as well.