Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

 Template

Please include:

  • Overview: 1-2 sentences that describe the project

  • Problem: 1-2 sentences that describe the primary user problem, challenge or barrier

  • Use cases: As a [course author author/instructor/learner], I need to be able to [do something] because/in order to [achieve a specific outcome].

  • Discovery approach: What questions would you ask to explore solutions to this problem?

Status

PROPOSAL / DRAFT

Contributing Team

Marco Morales , Sam Daitzman

Earlier Discovery

Project - Improved Mobile Discovery (FC-28a)

Linked Initiatives

[Mobile] Improved Mobile Discovery

Overview

This is a proposal to improve the Open edX platforms basic course enrollment views, how these are authored in Studio, allowing for improved mobile discovery and general improvements to enrollment and discovery which has remained static in the open edx core for 2013.

Overview

Coming Soon

This document was created using the OE Roadmap Submission item template , but it likely will benefit from being represented in the roadmap as a series of smaller efforts to make it easier to provide visibility on whatever fraction of this set of initiatives moves forward.

Abstract

…

Context & Background

  • Coming soon

Scope & Approach

The team at Schema Education has only just started scope and approach discovery review, and we are interested in collaborating with the community on next steps for this project, including potential sequencing & funding paths.

Value & Impact

Coming soon

Milestones and / or Epics

 Template Detail

Any relevant background information about the Initiative. What key pieces of information are important for newcomers to understand about the nature of the problem or pain point, the current user experience, etc. Please use the following format:

Milestone 1: [Title]

  • [1-2 sentence abstract. Include key user stories if appropriate]

  • [Impact metric]

  • [Link to Epic where it may exist in GH, jira, etc]

Initiative 1: Teams Modernization, Apps, and In-Context Use

This initiative is meant to span teams app infrastructure modernization, LTI app support for Teams, a v1 In-Context Teams sidebar alongside content, and other platform cleanup efforts. A full proposal page will be created for this effort soon.

Named Release

 Template Detail

First Named Release to include this initiative. Alphabetical named releases are generally cut in early April and early October. Based on the removal date, what named release would be the first without this code? Please reach out to the Build Test Release working group (#wg-build-test-release in Slack) if you're not sure. Use the letter, if you're not sure of the name.

This is TBD based on community interest and funding.

Timeline

 Template Detail

Recognizing that many Initiatives evolve incrementally, please include a brief scope of the Initiative timeline. Please include a target Named Release, with contingencies if necessary.

TBD

Proposed By

Marco Morales , and team @ Schema Education

  • No labels