Contributors Meetup Async Update - Dec 6th - Dec 20th, 2024

Working Groups Core Contributors
,
1

Core Contributor Update: Dec 6th - Dec 20th, 2024

Use the jump links below to view the section that interests you:

  1. Working Groups Updates
  2. Events
  3. Projects
  4. Next async update and meetup

1. Working Groups Updates

Working Groups Calendar

1.1. BTR Working Group

Chair: @jalondonot

:paperclip: Latest news

1. Release Status

  • Forums V2 Issue Resolved:
    • All critical issues, including those related to Forums V2, have been merged and backported.
    • There are no remaining release blockers.
  • Testing and Known Issues:
    • All test cases in the test sheet have been reviewed, and failing tests have associated GitHub issues.
    • No new high-priority issues were identified.
    • Existing high-priority issues remain but do not block the release.
  • Release Notes:
    • Chris Patti confirmed the release notes are complete, with a minor date discrepancy being resolved.
    • The notes will be merged and will not delay the release.
  • Readiness for Tagging:
    • All team members confirmed readiness to tag.
    • The tagging ceremony was scheduled for 40 minutes after the meeting.

2. Post-Release Planning

  • Next Steps:
    • Weekly meetings will resume on January 6, 2025, to discuss retrospective feedback and address any post-release issues.
    • A retrospective document will be created for asynchronous input on improving the release process.
  • Community Roles:
    • Discussion on chair and role transitions:
    • Current reliance on volunteerism was noted as a bottleneck for filling roles.
    • A suggestion was made to introduce “shadow” positions where a volunteer actively supports and observes the role, creating a smoother transition.
    • Adolfo Brandes volunteered to continue hosting meetings until a new chair is identified.

3. Closing Remarks

  • The team celebrated reaching the final steps of the release process.
  • Everyone was invited to the tagging ceremony.

:memo: Meeting notes

1.2. Contributor Coordination Working Group

Chair: Jorge LondoĂąo

:arrow_down: Past meeting notes 2024-10-29 CC Working Group Meeting Notes

  • Next Steps
    1. Implement a simple polling system for voting, ensuring that only core contributors are eligible to vote.
    2. Cassie Zamparini to announce the voting schedule within the week to prepare contributors.
    3. Direct follow-up with proposers who need to clarify their summit proposals before voting.
    4. Plan to use the existing ticketing system for tracking project progress post-vote, ensuring all updates are meticulously documented.
    5. Encourage thorough testing and review of proposals by all core contributors.
      Meeting participants left with clear tasks and timelines, looking towards an efficient voting process and subsequent implementation of the summit’s outcomes.

:memo: Meeting notes

1.3. Data Working Group

Chair: @e0d & @blarghmatey

:arrow_down: Past meeting notes 2024-11-13 Meeting notes

:memo: Meeting notes

1.4. DEPR Working Group

Chair: @feanil

:paperclip: Latest news

:memo: Meeting notes

1.6. Tutor Users’ Group

Chair: Kyle McCormick

:arrow_down: Past meeting notes Tutor Users GW 2024-11-18

:memo: Meeting notes

1.7. Educators Working Group

Chair: @john_curricume

:arrow_down: Past meeting notes 2024-10-07 Educator WG

  • In this session of the Open edX Educators Working Group, Eric J. Larson discusses AI literacy, focusing on the distinction between AI capabilities and human-like reasoning. Participants, primarily educators, explore the implications of AI in education, emphasizing the potential and limitations of current AI technologies. Larson elaborates on his book ‘The Myth of Artificial Intelligence,’ highlighting the strengths and weaknesses of AI as an educational tool. They discuss issues such as hallucinations, the impact of AI on student learning, and the importance of maintaining critical and creative thinking. Larson promotes leveraging AI thoughtfully to complement human cognitive abilities, especially in educational settings, while acknowledging the inherent challenges and unpredictable errors of AI systems.

:memo: Meeting notes

1.8. Frontend Working Group

Chair: @arbrandes

:arrow_down: Past meeting notes 2024-10-24 Frontend Working Group Meeting Notes

  1. “Frontend Base” Initiative:
  • David Joy introduced a unified library to replace various frontend components, such as headers and footers, enhancing configurability and usability.
  1. Header Configurations:
  • New headers are configured through a “site config” file, enabling dynamic updates tailored to specific modules without major code changes.
  1. Footer Development:
  • A prototype for an adaptable footer was showcased, inspired by layouts like edx.org, offering structured link layouts and improved internationalization.
  1. Module Federation and App Configuration:
  • David presented three app configuration methods (internal apps, federated modules, and external apps) to support modular, flexible builds with potential default configurations for easier integration.
  1. Plugin and Module Slot Configurations:
  • The team discussed organizing plugins and modules for a balance between flexibility and simplicity, suggesting helper functions and default setups for easier configuration.
  1. Internationalization Improvements:
  • Updates were shared on language selection, leveraging browser APIs for language options based on configured translations, eliminating the need for large external libraries.

Outcomes and Next Steps:

  • The group expressed overall approval for the proposed configurations and recommended further testing to explore complex use cases.
  • David will summarize the current work and gather additional feedback on Discourse.
  • The team acknowledged the importance of balancing configurability with usability and agreed to continue refining the system.

:memo: Meeting notes

1.9. Large Instances Working Group

Chair: @braden & @Felipe

:paperclip: Latest news

eduNEXT

  • Felipe Montoya : We have started the process of migrating our production clusters to Harmony. Starting with smaller clusters and documenting the process, and opening PRs as we encounter issues.

OpenCraft

  • Braden MacDonald We’re preparing for Sumac upgrade - happy with removal of Elasticsearch and the fact that forum can now use MySQL as a backend instead of MongoDB.
  • GĂĄbor Boros has opened a PR to add Terraform code for AWS & DigitalOcean to Harmony.
  • Discussion between GĂĄbor Boros and Felipe Montoya agreed that we don’t need to have “one way” to deploy Harmony using Terraform - we can provide examples of how OpenCraft does it, how eduNEXT does it, etc. and people can mix and match, if that’s helpful.

RaccoonGang

  • Currently focused on migrating to Tutor for deployments, and encountering quite a few issues.

:memo: Meeting notes

1.10. Marketing Working Group

Chair: Eden Huthmacher

:arrow_down: Past meeting notes 2024-11-20 MWG Meeting Notes

:memo: Meeting notes

1.11. Maintainers

Chair: Feanil

:paperclip: Latest news

  • Next Maintenance Items:
    • Ticket up Testing with 5.0 and 5.1 so that it’s easier when we’re ready to move to 5.2
    • Do we need the new process documented?
      • We probably need this, and should be done as a part of setting up the Django 5.2 upgrade.
    • If tests are added for 5.1 today, we’ll have to go back and update to 5.2 later. We could let maintainers decided if they have capacity to do this or just wait till 5.2 lands.
  • Maintainers at Large
    • Single team, will be setup soon and then nominations can start coming in.

:memo: Meeting notes

1.12. Product Working Group

Chair: Jenna Makowski

:paperclip: Latest news

  • LTI
  • UX/UI Working Group
    • Coordination with Paragon Working Group
      • Discussion on collaborating with the Paragon Working Group in 2025 for shared topics, such as design tokens.
      • Design tokens have been integrated but require further clarification regarding mobile transformation and documentation.
    • Presentation by MarĂ­a de los Ángeles Aguilar
      • MarĂ­a presented a proposal for categorizing content components to enhance LTI UX.
      • A suggestion was made to align the proposal with sidebar patterns to improve usability across projects.
    • Feedback on Meeting Structure
      • Mixed feedback received regarding the frequency and timing of meetings.
      • Suggestions included:
        • Alternating meeting times monthly to accommodate different time zones.
        • Integrating design activities and brainstorming sessions into meetings for increased engagement.

:memo: Meeting notes

1.13. Security Working Group

Chair: Feanil Patel

:memo: Meeting notes

1.14. TOC

Chair: Ed Zarecor

Announcements

Partnership & New TOC Member
It was announced that a Memorandum of Understanding (MOU) had been signed with a large university, which involves them joining the Technical Oversight Committee (TOC) starting in the new year. The announcement of a new member from that organization joining the meetings from February was mentioned, and plans were in place to work with their communications team on a further public announcement.

Migration of 2U Engineers to the core contributor program
An update was provided regarding the migration of all 2U engineers to the core contributor program for obtaining permissions within the project. Existing permissions will be grandfathered into core contributor & maintainers status, but obtaining new permissions will require following the same standards as the rest of the community, going forward.
On the flip side, it will require the community to keep stepping up its contributions in core contributor & maintainers time, to compensate for the shift of responsibility to the community.
Aligning 2U engineers and practices with the community guidelines requires a fair amount of changes within 2U, the rough timeline for the completion of this migration is set for February.

2025 Conference Update

Information was shared about the progress of arranging the upcoming conference, emphasizing that the Call for Proposals (CFP) had closed, and the submissions were under review. It was mentioned that the selection process involved a juried review by community members and stakeholders using a tool called Sessionize. The results were expected to be finalized soon, with keynote announcements pending.

Sumac Release

Concurrently with the meeting, the Sumac release ceremony was being held, though it has since been delayed by a few days. This release is significant and incorporates new functionalities like a central content library, enhancing content reusability across courses. Draft release notes were shared, and community contributions to this release were acknowledged, appreciating last-minute fixes and enhancements.

Market Research

During the presentation of a market research analysis performed for Open edX, extensive discussions centered around identifying the most beneficial markets and strategic focus areas for Open edX. The dialogue primarily navigated through the merits and potential of targeting specific sectors such as community colleges, ministries, corporate training, and certain international educational initiatives.

Presentation

Market Identification

  • Introduced the core market segments that Open edX could serve effectively: community colleges, ministries, and employers.
  • Emphasized the growing need for upskilling across these segments, both in the U.S. and globally.
  • Highlighted the potential in non-credit educational programs which are rapidly growing and are underserved by current Learning Management Systems (LMS).

Go-To-Market Strategy

  • Suggested that a channel partner model should be the primary route to market rather than Open edX building out a large direct sales force.
  • Discussed the benefits of leveraging existing relationships that channel partners may have within the educational and corporate sectors.
  • Shared insights on the substantial investments typically required for go-to-market activities citing examples from other companies in the education industry.

Barriers and Opportunities

  • Acknowledged the technical challenges and support issues currently facing new users of Open edX, stressing the need for improvements to user experience and platform accessibility.
  • The discussion also covered the necessity of raising market awareness given the low existing visibility of Open edX among potential users and partners.

Strategic Partnerships and Engagements

  • Detailed current discussions with large international organizations, aimed at using Open edX for large-scale educational initiatives.
  • Expressed the need to identify and engage with more partners who can aid in distribution and localized support.

:memo: Meeting notes

1.15. Translation Working Group

Chair: Eden Huthmacher

:arrow_down: Past meeting notes 2024-11-06 Translation WG Meeting notes

:memo: Meeting notes

2. Events

  • Registration for the 2025 Open edX Conference is open! Join the Open edX Conference 2025 in the TĂŠlĂŠcom Paris, Polytechnic Institute of Paris
  • Call for Papers: Open edX Conference 2025: Proposals are due by December 4, 2024, with early feedback available for submissions before November 11.
  • Would anyone like to highlight any past or upcoming events? Let us know in the comments!

3. Projects

Are there any new or ongoing projects you’d like to discuss? Get the conversation started in the comments below.

4. Next async update and meetup

  • Tuesday November 24th - Join the meetup here!
  • Friday January 3rd - Async update
  • Details and draft agenda on Confluence

:speech_balloon: Anything to add?

If there’s anything else you’d like to mention, please let us know in the comments below.