Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

\uD83D\uDC65 Participants

🎥 Recording and Chat Log

Summary

Feedback Collection

The meeting began with a discussion about the need for improved methods to gather feedback from the Open edX community. Jorge Londoño initiated the conversation, noting that this was a follow-up from a previous agenda item about enhancing feedback mechanisms. Xavier Antoviaque highlighted that while the core contributors' survey provides some internal feedback, there is a need for broader outreach to better engage the entire user base, including instructors, students, and operators. He proposed integrating a feedback system into the Open edX platform, potentially customizing it based on the user's role to gather relevant feedback efficiently.

Cassie Zamparini suggested she might bring this topic to the product working group, considering her upcoming involvement due to her new role in the UX and UI working group. This led to a consensus that exploring how the product working group handles data collection could provide insights or strategies that could be adapted for broader community engagement.

Release Management and Retrospective Planning

Jorge Londoño discussed the upcoming retrospective for the Redwood release. He detailed his plan to conduct the retrospective in two stages: an asynchronous phase where he would gather initial feedback through a space in the BTR wiki on Confluence and a synchronous phase during a BTR meetup to review the results collectively. The objective was to identify and prioritize actionable improvements for future releases.

Review of Core Contributors' Engagement

The discussion briefly touched on core contributors' engagement, focusing on the maintenance of community repositories. Xavier and Jorge discussed the effectiveness of previous calls for contributor involvement, suggesting that clearer communication and perhaps a second call to action might increase engagement. They mentioned the necessity of checking current repository priorities and potential maintainers' readiness to take on responsibilities.

Misc

Several administrative items were discussed:

  • Cassie's role in collating feedback and improving documentation processes.

  • The ongoing need for better asynchronous work tools and practices, especially considering recent restrictions on AI usage.

  • Upcoming vacations and scheduling implications for the next meetings.

\uD83D\uDDE3 Discussion topics

...