Core Contributor Sprint Retro - March 18th-April 1st

[antoviaque (Xavier Antoviaque (OpenCraft) - opencraft.com/help)]

For this sprint’s retro recap, see also the excellent recap of some of the discussions points by @jalondonot in Open edX Contributors Meetup - #91 by jalondonot :

“I want more visibility into the development/support status of components, especially MFEs. If a legacy frontend is being rewritten as an MFE, I think there should be a DEPR ticket for the legacy frontend from the get-go.”

Conclusions:

• There is no clear nor a specific roadmap or approach for this but the issue is well identified and the working groups are open to any suggestions. The DEPR working group will discuss this at the next meeting to improve the visibility of what is being removed and what is replacing it.
• The process for deprecating should be revisited considering that the real community using Open edX around the world is larger than the one that is actively participating on the community channels.
• A deprecation digest might be a good idea. Improving the information radiators that are currently in place seems to be a good approach for this.
• Deprecations should be included in the roadmap and prioritized in terms of user and product impact

"Discuss posts (Core contributors sprint & meetup) have helpful information, but I haven’t found the time to read through them thoroughly. So I should include that as part of my CC tasks.

I reviewed a PR (since it fixed an issue I was having) and then realized it already had an assignee on the Jira board (I then @ the assignee to let him know). What should we do in that case?"

Conclusions:

• Tagging the assignee and letting her know you gave a review is the best approach for this scenario.