Open edX Contributors Meetup

jalondonot · April 11, 2022, 4:04pm

Sorry for the delay! Here is the recap from the meeting we held on 2022-04-05.

Video Recording

ConMeetup-05-04-22
The chat log can be found on the meeting’s agenda .

Participants

@antoviaque
@arbrandes
Kelly Buchanan
@Felipe
@mgmdi
@sarina
Julia Zack
@jmakowski
@Dean
@estebanetcheverry
@nedbat
@idegtiarov
@feanil
@sambapete
@djoy
@Andres.Aulasneo

Meeting notes

2. Working Groups Follow-Ups:

Marketing (@jmakowski):
-Main focus on the Open edX Conference
-Ongoing tutorial videos for new users are expected to be ready by the end of April.
-Open edX survey: Deadline has been extended 2 weeks, until the half of April. The results will be shared during the Open edX Conference.
BTR (@nedbat):
-Getting ready for cutting the Nutmeg release on Monday, April 11th. Nutmeg is going to be released on June 9th.
-Request for help:
Dean is leading the testing effort. If you think you might be able to lend a hand, reach out to him!
Testing Open edX release
Frontend (@arbrandes):
-Recap from the last meeting.
-The Node 16 upgrade is ongoing. The MFEs that will be included in Nutmeg are ready for Node 16. Node 12 and Node 14 will still be supported in Nutmeg.
-A possible dependency licensing issue
-Request for help:
Ongoing MFEs survey: An official but informal survey on the state of MFEs
The survey will be open until April 22nd so please reach out to Adolfo if you have an interest in contributing to the survey.
Data:
-Unfortunately, no one from this working group attended the meetup. Hope to get your valuable insight in the next call @dave @mafermazu @jacatove @e0d @blarghmatey
DEPR (@feanil):
-All DEPR tickets have been migrated from Jira to GitHub.
-tCRIL and Racoongang will accelerate some of the DEPR work. This work will not impact the Nutmeg release.
-Mongo’s courses will no longer show up by default in Master.
Product (@jmakowski):
-First session during the conference. Hopefully, people that are not attending the conference will be able to join the session virtually! @jenna will provide the details.
-Open edX Roadmap first milestone. Getting an updated glimpse of the ongoing work all across the community:
Sign in to GitHub · GitHub
-There is a new Wikispace for product management!
https://openedx.atlassian.net/wiki/spaces/OEPM/overview?homepageId=3375235221

3. Events:

Open edX Conference: There will be a few talks that will be streamed. The details will be specified in the agenda of the event.

4. Projects:

Django events (@mgmdi - @Felipe): One PR at a time. 4 PRs to go out of the 7 PRs from the initial scope of the project.

5. Improvements and Calls/offers for help (@antoviaque)

“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?"