2025-08-20 BizDev WG Meeting

2025-08-20 BizDev WG Meeting

Agenda for Open edX Biz Dev Meeting

  • Meeting Details:
    Open edX WG-BizDev
    Wednesday, 20. August · 17:00 to 18:00
    Timezone: Europe/Berlin

  • Meeting Link: https://meet.google.com/xxd-cntx-mjv

  • Bring your creativity and energy - let’s make it count!

Please review this agenda, prepare in advance, and contribute your ideas beforehand.

Also refer to the meeting notes from previous BizDev meetup - https://openedx.atlassian.net/wiki/spaces/COMM/pages/5104795651

Objectives for Today:

Meeting Notes:

Facilitator: @Eden Huthmacher

Attendees: @Abdul Ahad, @Jaimin Pavashiya, @Angie Ruíz, @Eden Huthmacher, Giulio Caratelli, @Jorge Londoño, @Juan Camilo Montoya, @Mahnoor Sarwat, @Marco Morales, @Nadheem Abdulla, @Natalia Vynogradenko, @Omar Al-Ithawi, @Tahir Latif

Date: 20.08.2025

 


Meeting Recording, Chat, and Transcript

Recording : https://drive.google.com/file/d/1RRkiSgbjTqI6Qei1Fs6DP1HuF1BGA5Tl/view?usp=drive_link

Chat : https://drive.google.com/file/d/1hWvafiFceW3zXr77_Vt1DfcZzOJbSoRH/view?usp=drive_link

Transcript : https://drive.google.com/file/d/16UzoxaZZWgk1EtbUseG-axmv9GS1HVj_QhnkJDE4CRE/view?usp=drive_link


Meeting Highlights

1. Competitiveness of Open edX vs. Other LMS

  • Introduced discussion based on a recent slack channel post about Open edX’s competitive positioning against Moodle, Blackboard, and Canvas.

  • @Eden Huthmacherexplained context: post originated from @Nadheem Abdulla (via Ali from Saudi Arabia’s requested RFP).

  • @Nadheem Abdulla provided background:

    • Saudi Arabia issued a national RFP for LMS solutions.

    • The RFP evaluated Open edX but considered Canvas more suitable due to missing features.

    • Highlighted gaps in Open edX limiting adoption for university projects.

  • @Omar Al-Ithawi added:

    • Recalled 2024 Stellenbosch conference discussions about hybrid learning support.

    • Identified missing features: classroom awareness, instructor-student chat, attendance tracking, staff-graded assignments as core features.

    • Costs escalate when building these features project-by-project. Suggested addressing centrally.

    • Translation quality noted as strong, though with room for improvement.

  • @Marco Morales Feedback:

    • Importance of breaking down feedback into actionable proposals.

    • Cost of missing features is hard to measure; example: notifications feature took years to justify but is now essential.

    • @Eden Huthmacher emphasized need to channel discussions into the feature request process with Product WG.

    • Marco confirmed about a dozen feature requests submitted since new process started.

    • Recommended subdividing large feedback items into smaller, categorized requests.

2. Leveraging the Core Platform & Extensibility

  • @Nadheem Abdulla suggested:

    • Keep the core kernel strong and extensible.

    • Enable building specialized solutions (corporate training, K-12, workforce development) on top of it.

  • @Eden Huthmacher highlighted:

    • G2M report shows Open edX competitive advantage in non-credit & workforce development.

    • But extensibility needs significant improvement.

    • Example: K-12 asynchronous training in India - Open edX could serve similar niches if core extensibility is improved.

3. Group Updateshttps://openedx.atlassian.net/wiki/spaces/COMM/pages/5085364228

  • @Juan Camilo Montoya added:

    • Small meeting (4-5 people, incl. Elizabeth from ASU, Santiago, Felipe, Juan).

    • Felipe presented proof-of-concept accessibility framework for AI extensions.

    • Progress is steady but slow; balance needed between urgency of customer demand and careful, robust development.

  • @Jaimin Pavashiya shared:

4. Marketplace & Discoverability of Extensions

  • @Juan Camilo Montoya raised concern:

    • Current discoverability of extensions is poor.

    • Shared prototype of categorized, user-friendly marketplace interface.

    • Taxonomy: Platform modules, third-party integrations, native courseware components, third-party courseware tools.

    • Emphasized need for intuitive navigation for non-technical stakeholders (e.g., government officials, NGOs).

  • @Eden Huthmacher & @Mahnoor Sarwat explained:

    • Edly’s Tutor Deck system currently pulls metadata from GitHub to WordPress.

    • Plan: transfer to Open edX repo → create official marketplace.

    • Will include categorization and filters in metadata for improved navigation.

  • @Omar Al-Ithawi suggested:

    • Include icons, screenshots, pricing metadata.

    • Highlight missing dimension: paid plugins.

  • @Juan Camilo Montoya cautioned:

    • Against over-reliance on WordPress (limits future enhancements like ratings, payments, comments).

    • Recommended independent service.

  • @Eden Huthmacher countered:

    • WordPress integration offers quick implementation.

    • Ratings/comments could be phase two features.

  • @Tahir Latif reminded:

    • Past community discussions (e.g., Paris) showed concerns with rating systems (fairness, bias).

    • Suggested focusing on discovery first, ratings later.

  • Consensus:

    • Phase 1: Build marketplace with categories & metadata.

    • Phase 2: Explore enhancements (ratings, payments, advanced UX).

    • Ensure multi-stakeholder ownership, not concentrated under Edly.

5. Closing

  • @Eden Huthmacher emphasized:

    • No final decisions yet. Community feedback will shape marketplace direction.

    • Encouraged ongoing contributions via Slack or email.

Key Takeaways

  1. Competitiveness: Open edX still struggles against Canvas, Moodle, Blackboard in hybrid/university market; requires addressing missing core features.

  2. Extensibility Vision: Strengthen kernel and build modular solutions for various sectors.

  3. AI Efforts: Ongoing proof-of-concepts; balancing urgency with careful design.

  4. Extensions Marketplace: Consensus to improve discoverability, categorization, and user experience. Quick solution with WordPress, but long-term may need independent service.


NEXT MEETING:

Sep 10, 2025 - https://openedx.atlassian.net/wiki/spaces/COMM/pages/edit-v2/5203394564?draftShareId=b6921838-10cc-4749-8e3f-a47b354d69d2