Core Contributor Sprint Retro - 1 October - 15 October

Working Groups Core Contributors
,
1

Full report

@antoviaque #working-groups:core-contributors

Find the full report in Listaflow for your convenience: https://www.listaflow.com/

There have been 497.75 hours worked on the last two weeks, up compared to 285.75 hours and 320 hours in the previous two sprints.

Calls for help/collaboration

Is there anything where you could use help from others? Or that you would like to collaborate on? User
- Vote at the TOC elections if you have registered!
- Please help test & provide feedback about the upstreaming course! See Course | 101 | OpenCraft Courses 		Xavier Antoviaque
* OEP-57 is in review, would love to hear more CCs’ opinions! https://openedx.atlassian.net/wiki/spaces/COMM/pages/3540713547/Open+edX+Proposal+57+Product+Offering
* We are still looking for a new Build-Test-Release Chairperson. If you are interested but don’t have Build-Test-Release experience, no problem, we’re happy to work with you and get you up to speed :slight_smile: Reach out to Sofiane, Ned, me, or #wg-build-test-release if you’re interested.		 Kyle McCormick
Want to send Kudos to Braden for rocking the replies on discuss.openedx.org! I clock 17 threads you’ve participated in since the beginning of October alone. So good! Jill Vogel
1. We could use more info from Data WG folks about the events they use in this ticket: Spike: Review and report on event_types in use in your organizations data pipeline · Issue #16 · openedx/data-wg · GitHub. 2. I would like to work with someone in the community on this ticket as well: Spike: Investigate mapping problem events to xAPI statements · Issue #15 · openedx/data-wg · GitHub Brian Mesick

What should be improved?

Retrospective - Improvements User
how do we know if a PR needs a product review? who should we ask or tag? this was raised in this thread. Maria Grimaldi
MFE support for the community is still and afterthough. We need to make it first class citizen Felipe Montoya
Retrospective - Blockers User
Still finding it very difficult to block out time for CC, in amongst client firefighting and scope changes. :frowning: Jill Vogel
We need to finalise the Listaflow strategy. We plan to invite Fox to the next marketing meeting to discuss directly with the group. Dean Jay Mathew

What went well these last two weeks / sprint?

Retrospective - What went well these last two weeks / sprint? User
- TOC wiki page went live without any hiccups.
- I learnt about a new Open edX role (Arbiter), and enjoyed performing my duties so far		 Ali Hugo
The upstreaming course reached a first important milestone - it has reached beta status, with the first full draft of the course ready for early testing. Xavier Antoviaque
The Built Test Release group have already published Olive and it went up on the first try! | Open edx olive Demo
Marketing are getting much closer to developing How To videos to accompany the new Open edX Documentation site.
 Dean Jay Mathew
Collaborating with Ned, Sarina, and Feanil. Carlos Muniz

Here are the calculations of total hours: Core Contributors - Sprint Planning & Retro - Google Sheets

1 Like
2

Thanks @Dean ! And I’m posting a recap & follow-up of the blockers above, from the discussions in the contributors meetup on Tuesday:

We need to finalise the Listaflow strategy. We plan to invite Fox to the next marketing meeting to discuss directly with the group. (@Dean)

There has been a meeting to figure it out yesterday, besides the discussions in Slack - see the summary & meeting recording in the ticket:

Note that there have also been a few suggestions to improve the notifications, descriptions and generally remove blockers for reporting:

how do we know if a PR needs a product review? who should we ask or tag? this was raised in this thread. (@mgmdi)

We discussed during the contributors meetup, and it’s a topic being investigated by the product working group. There currently isn’t a good answer on this yet, but see the ticket below for the details and current status of the discussion.

@jmakowski In the meantime, should you be the one being pinged on pull requests in cases like this? Or should this go to @Michelle_Philbrick & @itsjeyd as part of OSPR management & routing?

Still finding it very difficult to block out time for CC, in amongst client firefighting and scope changes. :frowning: (@jill)

This inevitably happens to all of us at some point – whether it’s because of client emergencies, personal life, vacation, etc. there will be sprints where we can’t do the time committed. A good way to deal with this is to build up some extra time when there are less constraints on our time – for example, for a 20h/month commitment, contributing 30h one month allows to do only 10h the next month. As long as it averages out correctly, and that it’s done ahead to avoid falling behind, it’s completely fine.

MFE support for the community is still and afterthough. We need to make it first class citizen (@arbrandes)

Yes, I think @Kelly_Buchanan is currently running into that issue while trying to plan for proper MFE support in the Open edX release for the credentials changes she’s planning now. @arbrandes you mentioned that you’re spearheading an effort to improve the situation, including providing better instructions for how to achieve proper MFE support. Do you have some links that people interested in this can have a look at? CC @regis as this is also related to Tutor.

2 Likes
3

As a matter of fact, yes! We now have a central checklist that sets the bar for MFEs to be included in a Tutor release:

https://openedx.atlassian.net/wiki/spaces/COMM/pages/3561521275/Requirements+for+an+MFE

This will hopefully make it easier to communicate what frontend developers need to do before the BTR group will accept an MFE for inclusion in a Tutor release.

Note that these are not yet official requirements outside the Build-Test-Release group. Those will come about as a part of the upcoming OEP-61. We don’t expect the above list to change much until then, though.

1 Like