Build/Test/Release Working Group Biweekly Meetup

Come and help us improve Open edX! :partying_face:

The Build/Test/Release Working Group is scheduling an online weekly meetup: the goal of this meetup is to collaboratively identify and resolve issues related to the Open edX named releases.

More precisely, we aim to:

  1. Identify issues with the existing and the future Open edX named releases, assign people to the resolution of these issues and make sure that they follow-up on their commitments.
  2. Help newcomers investigate issues by making them collaborate with mentors who know their way around Open edX.
  3. Discuss broader release questions and take decisions on them.

This is a great place to start if you don’t have much experience contributing to Open edX and are looking at levelling up :mushroom:. We would like you to help us resolve these issues. If need be, you will be paired with a more experienced Open edX developer who will help us resolve road blocks.

If you already have experience with Open edX and you would like to help newcomers get on board with Open edX development, please join this meetup :hugs:

See you soon!

:calendar: Calendar

Meetups are scheduled every on Monday every other week at 15:00 UTC, starting on Feb 1 2021. Here is the Google calendar.

Zoom link

Meetups will happen on Zoom: Meeting URL: Launch Meeting - Zoom

(Meeting ID: 898 7557 0381, Password: 046246)


The meetings seem to be at 12h00 PM West and 05h00 AM East in what I can see in the calendar for August 2020.

What timezone is being used? Being on the East Coast of North America, the West meeting seems more appropriate for me if the timezone being used is EST/EDT. Or is it UTC?

1 Like

Hey @sambapete! I tried very hard to get the timezone right, but I’m not 100% sure it worked as I wanted. I believe that Jira displays events in the timezone associated to your account:

From my perspective, tomorrow’s meeting is scheduled for 6 pm; this corresponds to 4 pm UTC ( and noon in Montreal. So yes, the West meeting should be best suited for you – but hey I don’t know maybe you have different sleep patterns :wink:

Will you be available at that schedule? We can change it for the next meetups if necessary.

I 'll be there. Thanks.

1 Like

Thanks to those who joined! Here is the recording of the meeting:

The next meeting is scheduled for August 17th at, 9 AM UTC (here is the Zoom link This time was selected such that more contributors from Asia could participate. I know there are many Open edX users and developers from India and China out there, and I’m eager to meet you all!

Thanks @regis! Added to my calendar. :slight_smile:

Tomorrow is the second bi-monthly meetup of the BTR working group: it will happen at 9am UTC and is especially aimed at contributors from the Eastern Hemisphere. If you are interested in contributing to the platform or you would like to report a bug with the current release, please join! We will also discuss the release schedule and what major changes you would like to see happen.

Here is the link to the working group page in Jira.

Here is the Zoom meeting url:

EDIT: here is the link to the recording:
It starts off in French – but fear not, we switch to English after a few minutes.
Once of the topics we discussed is the upcoming release schedule: the consensus is that a 6-month (but no less) release period is great if it provides more visibility and less surprises to the Open edX developers and platform maintainers.

1 Like

Today is Western Hemisphere meetup day! As usual, let’s meet at 4pm UTC:

On the agenda:

  • Address current and future issues with Juniper/Koa
  • Building and deploying MFEs
  • Building a continuous integration pipeline for Open edX
  • Writing contributor’s docs

See you then!

EDIT: if you missed the meetup, here is the link to the recording:


Today is meetup day for the Eastern Hemisphere! :earth_asia: See you in ten minutes :mantelpiece_clock: We’ll talk about the big topics of the moment, which are the upcoming Koa release and the integration of micro frontends (MFEs).

Join Zoom Meeting:
Meeting ID: 810 6221 8501

EDIT: no one showed up :crying_cat_face: Should I have given advanced notice? Should we move the meetup time? Is it clear that it’s possible to subscribe to the meetup calendar to receive notifications?

It’s also possible to download the .ics file and add it to Google Calendar for example. That’s what I did recently. Unfortunately the Eastern Hemisphere meetup is in the middle of my night sleep since I am usually part of the Western Hemisphere meetup.

I would recommend at least a 24 hours advanced notice. And since the meetings are usually on a Monday, I would recommend a 72 hours advanced notice so that people can see the notice on Friday.

I only saw your notice right now and I was not subscribed to the meetup calendar but I will do it now.
The only problem with downloading the ics is that nobody will be noticed if the meeting time change.

Don’t you think we can use a shared Google Calendar for the BTR working group events?

This sounds reasonable. I’ll do that from now on.

Personnaly, I’d rather avoid using Google products when I can. Basically, we should be able to share a link to the davcal calendar. @nedbat I understand nothing about Jira, can you please help? I’d like to:

If the latter is not possible, I’ll move the calendar so a self-hosted davcal-compatible server.

Hmm, there isn’t much good news here…

Looks like you can’t make calendars available anonymously.

The BTR project is a Jira next-gen project. It looks like it is not possible to make that viewable by anonymous users. :frowning:

I’m not sure how to do this…?

(insert here long Jira rant)

Alright, let’s get rid of this Jira calendar. Here is a more accessible version :calendar: :

There are two links at the top: Subscribe (a Webcal link) and Download (for the ICS file)

1 Like

Régis, I was able to download the ICS file, but it will not allow me to subscribe to the webcal link. Just thought I would let you know.

I cannot subscribe to it too.

@sambapete @toxinu Did you try this? It worked for me.

1 Like