2023-02-06 BTR Meeting notes

 Date

Feb 6, 2023

 Participants

  • @Régis Behmo

  • @Jhony Avella

  • @Matjaz Gregoric

  • @John Swope

  • @Kyle McCormick

  • @Jorge Londoño

  • @Maksim Sokolskiy

  • @Peter Pinch

  • @Pierre Mailhot

  •  

 Goals

  • Address each one of the agenda items

 

Recording

 Discussion topics

Time

Item

Presenter

Notes

Time

Item

Presenter

Notes

5 minutes

Project board review

@Jorge Londoño

None seem to be critical for Olive.2 (Thu 09 Feb)

5 minutes

Previous meeting action points review

@Jorge Londoño

Accomplishments from past year:

Still out of date:

Palm retrospective:

 

 

5 minutes

Next release: Olive.2

@Jorge Londoño

Thu 09 Feb

Call together?

  • Not strictly necessary anymore since we have a core contributor role for the release manager that grants permissions

  • But Matjaz will do it anyway this time

10 minutes

Palm.1 testing plan overview

 

Cut = 09 Apr

Release = 09 Jun

Which MFEs are we including?

Test plan is ready, Jorge will reach out to Dean anyway in case

10 minutes

xblock-lti-consumer security

@Régis Behmo

We need to publish a security fix for xblock-lti-consumer (discussion)

15 minutes

Tutor plugin indexes

@Régis Behmo

Plugin indexes are about to be released: pull request. I’ll be happy to answer any question you have about them.

Overhang.IO indices:

 

 Action items

Confirming the release roles for Palm.1 - @Jorge Londoño
@Matjaz Gregoric will reach out to Giovanni to discuss the xblock-lti-consumer security fix matter and @Maksim Sokolskiy will reach out to Igor as well.
@Matjaz Gregoric will schedule a call for the Olive.2 release in case anyone from the BTR would like to join him. He’s going to share the details of the call in Slack.
Clarifying the next steps to start working on palm.1 - @Jorge Londoño
Open edX Con Friday’s session planning - @Jorge Londoño
Writing a post for the Open edX Con Award ceremony candidates selection - @Jorge Londoño
@Dean Jay Mathew will move the information in into this group’s home page in the wiki
Once the above info is in the wiki, @Sofiane Bebert will delete the info in the repo README to avoid duplication

 Decisions