Product Review is the process by which contributions are considered for inclusion in the Core Product. Contributions require product review if the subsequent PRs will result in a change, big or small, to the end-user experience. This includes learners, course authors, course teams, or course/instance administrators.
Does my contribution require Product Review?
If the answer is “yes” to any of the following questions, then your contribution requires Product Review.
Does this change or impact a feature that a learner would interact with?
Does this change or impact part of the authoring flow?
Does this change or impact the experience of configuring content or a course run?
Does the change or impact reporting?
Is this change related to Studio or Content Libraries?
Is this change related to the LMS?
Does this change impact the initial installation or the upgrade of the instance?
Does this change impact a course’s OLX?
When should I participate in the Product Review process?
The Product Review process must take place before PRs are submitted. The goal of the Product Review process is to ensure the contribution aligns with the overall strategic direction of the open source project and the community roadmap. It may result in recommended changes or adjustments in approach. The process is intended to be a two-way dialogue between the contributing organization and the Product Working Group, with the goal of landing on the best possible implementation to serve the greatest need for the majority of the community.
How do I participate in the Product Review process?