OpenedX releases
Going from 4 months → 6 months
Waffle switches/flags/samples
Why we don't like them
It’s dumb that the configuration is in our database.
Hard to debug
Hard to manage/duplicate
There is now no validation or review before making a change.
Often they don’t have good docs on how to manage them.
Often don’t have many people who know how they’re supposed to work.
Even if we had manual review, review of django-admin UI is not as good as reviewing code or config.
Some reasons why waffle is nice.
Sometimes we want to roll-out low risk things and changing settings via remote config is WAY slower and has more overhead.
Really useful for quickly flipping and testing a configuration before ripping the flags out.
Things we’re doing that should help?
Toggle Documentation Improvements
Should this be required?
We could be reducing complexity of the waffle things by building/simplify better waffle base classes.
Other Notes
Making more abstraction layers on top of waffle/django might not be a great idea.
However if we are constantly fighting our flag framework.
Let pyupgrade switch %-formatting and {}-formatting to f-strings?
f-strings are usually easier to read, any objections to moving to this?
How does this work with translations?
is the "optimization" faster than both %-formatted and str.format or just one?
Jeremy thinks yes.
Dave
Open edX contributions:
What’s eduNEXT?
Open edX company based in Colombia, doing some blended development work for us
Do we merge any PRs from any open edx contributors? Or is there some flag that identifies the GitHub user that we can take contributions from?
What is blended development and what is the typical workflow for blended development tickets What are teams'/developers' responsibilities towards OpenEdx/blended development tickets?
Rebranding edX.org and its i18n implications
Manage space
Manage content
Integrations