Open edX Contributors Meetup

Working Groups
43

I was under the weather on Monday and couldn’t attend the meeting. Thanks for making the recording available so soon after the meeting. I was able to catch up this morning.

1 Like
44

This is the recap from the meeting on 2021-02-08.

Video Recording

Participants

@Nicole_Kessler
@amy.e.brown
@nimisha
@nedbat
@pdpinch
@BbrSofiane
@idegtiarov
@antoviaque
@arbrandes

Topics

Details and chat logs on Trello (still).

Next meetup: Monday February 22nd at 15:00 UTC (Timezone converter)

Details and draft agenda on the Github board.

1 Like
45

Note to contributors! Next Monday’s meeting agenda has moved to GitHub (along with everything else):

Also, we’re now publishing the event in a public calendar so you can subscribe to it if you wish:

(This is why those of you who were already invited got a new invitation.)

1 Like
46

This is the recap from the meeting on 2021-02-22.

Video Recording

Participants

@Nicole_Kessler
@andres
@idegtiarov
@omar
@nedbat
@pdpinch
@BbrSofiane
@idegtiarov
@morenol
@antoviaque
@arbrandes
@nimisha
@sambapete

Topics

Details and chat logs on this meeting’s agenda.

Next meetup: Monday March 8th at 15:00 UTC (Timezone converter)

Details and draft agenda on the Github board.

2 Likes
47

This is the recap from the meeting on 2021-03-08.

Video Recording

Participants

@omar
@nedbat
@pdpinch
@BbrSofiane
@antoviaque
@arbrandes
@nimisha
@sambapete
@Felipe
@andres

Topics

Details and chat logs on this meeting’s agenda.

Next meetup: Monday March 22nd at 14:00 UTC (Timezone converter)

Details and draft agenda on the Github board.

1 Like
48

Please note that due to the northern hemisphere entering Daylight Savings Time soon, and the fact that (as far as I can tell) that’s where most attendees are joining from, I moved the meetup up one hour in UTC. So it’s now:

Monday March 22nd at 14:00 UTC (Timezone converter)

You may have gotten a new invite. If you have any objections, feel free to voice them below. If enough people think this is a bad idea, we’ll just go back to where it was before. :slight_smile:

(I also updated the agenda and the recap post above.)

49

@arbrandes I do have an objection yes - the meeting was already at 5am for me before, that would put it at 4am my time. And generally, to make sure people can plan correctly, I’d rather not shift the meeting around during timezone changes (which vary for plenty of countries anyway), but keep it at a fixed time UTC, and in any case discuss it with other attendees before making any changes.

50

@antoviaque, alright, fair enough. I agree in principle that meeting times should not change with DST, but I found that 15:00 UTC was going to be a problem for @nimisha, and, rather naively, did not take into account that even if most attendees are in the north, not all northern countries (or states) undergo a DST change.

So, since two very important participants have a scheduling difficulty… poll time:

At what recurring time should we hold the Contributor’s Meetup?
  • 15:00 UTC (the old time)
  • 14:00 UTC (the new one)

0 voters

Pinging the usual participants from the last few meetups:

@omar
@nedbat
@pdpinch
@BbrSofiane
@antoviaque
@nimisha
@sambapete
@Felipe
@andres
@Nicole_Kessler
@idegtiarov
@amy.e.brown
@marcotuts

51

I am fine with either time, but there isn’t a way to indicate that.

1 Like
52

Oops - I accidentally clicked on the poll. Please discount my vote above. I was looking to see if I could add another option.

It would be great for Xavier to continue to attend the meeting. If we make it at 14:00 UTC, I’ll need to catch up with the group afterward. (There is a standing meeting at that time with JP and other Eng directors.)

May I suggest another time: 17:00 UTC ?

  • This would be later in the morning for Xavier.
  • For ET folks it would go back and forth between the afternoon hours of: 12pm ET and 1pm ET over the course of the year.
  • I’m not sure how 17:00 UTC plays out for folks in other timezones though.
1 Like
53

Yes, if either @nimisha or me can’t make it, then none of the two times work imho – we both need to be in that meeting. Since it looks like we can’t avoid changing the meeting time at all, @arbrandes could we do a whenisgood.net poll with the whole week as a choice, to maximize the number of attendees too? If we move it piecemeal we’ll just keep bumping into meeting conflict from other people imho.

There are also a few people that hadn’t been able to join at the time from the Monday meeting recently, like @regis @idegtiarov @marcotuts @Nicole_Kessler @abstract-technology or @sambapete – it could be an occasion to get an occasion to find a time that works for you too?

2 Likes
54

Good points all around, and it seems the best solution is a new general poll, indeed. Here it is:

Contributor’s Meetup WhenIsGood Poll

As usual, please keep the following in mind, so we can maximize the “goodness” of the chosen time:

  1. Select your timezone.
  2. Paint over as large a range of dates and times as remotely possible - even if not necessarily comfortable.

You can keep track of results here. The chosen time will be converted to UTC so that subsequent DST changes don’t affect it. The decision will apply to the next meeting and subsequent ones.

Tagging potential attendees, again:

@omar
@nedbat
@pdpinch
@BbrSofiane
@antoviaque
@nimisha
@sambapete
@Felipe
@andres
@Nicole_Kessler
@idegtiarov
@amy.e.brown
@marcotuts
@abstract-technology
@regis
@nizar

1 Like
55

It seems like there is no single good time for everyone: the best we did is 8 out of 10 on:

  • Monday 14:00 UTC
  • Tuesday 14:00 or 15:00 UTC
  • Thursday 15:00 UTC

However, of these, only Tuesday at 15:00 UTC is suitable for both @antoviaque and @nimisha. Since they handle particularly critical aspects of this meeting, I’m going to make a judgement call and elect this as the time for the following ones.

In other words, the next meeting will be on:

Tuesday March 23rd at 15:00 UTC (Timezone converter)

You may get another invite as I change the calendar event. If you’re not explicitly invited, please refer to the agenda for calendar links. Thanks!

2 Likes
56

This is the recap from the meeting on 2021-03-23.

Video Recording

Participants

@antoviaque
@BbrSofiane
@idegtiarov
@nedbat
@Nicole_Kessler
@nimisha
@nizar
@pdpinch
@sambapete
@sarina

Topics

Details and chat logs on this meeting’s agenda.

Next meetup: Tuesday April 6th at 15:00 UTC (Timezone converter)

Details and draft agenda on the Github board.

1 Like
57

I was catching up with this meeting now and I’d like to clarify something about MDEs.

The work we did previous to Koa allows MFEs to be hosted in a single domain with different paths.

1 Like
58

This is the recap from the meeting on 2021-04-06.

Video Recording

Participants

@antoviaque
@BbrSofiane
@idegtiarov
@nedbat
@nimisha
@arbrandes
@pdpinch
@sambapete
@sarina
@pdpinch
@sambapete
@sarina
@andres

Topics

Details and chat logs on this meeting’s agenda.

Next meetup: Tuesday April 20th at 15:00 UTC (Timezone converter)

Details and draft agenda on the Github board.

1 Like
59

This is the recap from the meeting on 2021-04-20.

Video Recording

Participants

@antoviaque
@BbrSofiane
@nedbat
@arbrandes
@sambapete
@Zia_Fazal
@regis
@Felipe
@usman

Topics

Details and chat logs on this meeting’s agenda.

Next meetup: Tuesday May 4th at 15:00 UTC (Timezone converter)

Details and draft agenda on the Github board.

60

This is the recap from the meeting on 2021-05-04.

Video Recording

Participants

@Zia_Fazal
@braden
@BbrSofiane
@arbrandes
@sambapete
@antoviaque
@regis
@nedbat
@andres
@sarina
@nimisha
@pdpinch
@Felipe

Topics

Details and chat logs on this meeting’s agenda.

Next meetup: Tuesday May 18th at 15:00 UTC (Timezone converter)

Details and draft agenda on the Github board.

2 Likes
61

This is the recap from the meeting on 2021-05-18.

Video Recording

Participants

@BbrSofiane
@arbrandes
@antoviaque
@nedbat
@sarina
@pdpinch
@nimisha
@regis
@djoy
@idegtiarov

(Zoom doesn’t insert placeholders for videoless participants in the gallery recording. If you’re not on this list, this is why. Feel free to correct me!)

Topics

Details and chat logs on this meeting’s agenda.

Next meetup: Tuesday June 1st at 15:00 UTC (Timezone converter)

Details and draft agenda on the Github board.

1 Like
62

Sorry for not being able to attend this morning. I just finished reviewing the recording. I probably watched the last 15 minutes at least 3 times.

I need to explain a few things.

With regards to ecommerce and the Payment MFE. Because of political / institutional decisions, we had to develop our own payment processor connector for Netbanx / Paysafe way back in 2016 and install it as part of our fork for ecommerce. Of course, there were slight modifications to edx-platform, but nothing serious. I also have to point out that we do not use the edX basket because our implementation of Netbanx / Paysafe uses an hosted payment page. So, all credit card information is entered on the hosted payment page and the PCI component of the equation rests at Netbanx / Paysafe.

When I first tried lilac.master, the Payment MFE was still not available for the native installation. Since I was afraid that something wrong could happen, call it a hunch, I went ahead to see if the code was really deprecated between Koa and Lilac.

The first thing I really noticed were the calls to the new Profile MFE to see what is the state of a user’s identity validation. Going from there I was able to reverse engineer the calls and determine where I would need to change a line of code here and a line of code there to call ecommerce as usual and used the code we developed for Netbanx / Paysafe way back in 2016. The code was adapted from the code of the cybersource connector. We even adapted it to Python 3 when Python 3 was introduced into Open edX.

When I said there were 31 files to modify, those are 31 files in Lilac. Everything worked fine before Lilac. Sometimes I needed to change a line or two. Sometimes I need to reintroduce code that was removed from Lilac or even make sure the number of parameters on specific functions. It was a long evening. A lot of trials and errors.

In the end, I was able to change things so that I could still use the same behavior we had before Lilac but of course that now makes my Lilac fork absolutely incompatible with the Payment MFE. There would need to be a lot of additional code changes to make it a choice between using the old behavior or using the new Payment MFE behavior. Remember what I said about reusing functions from Koa and some functions not having the same number of parameters between Koa and Lilac. It really was an exercise in hacking the code.

I could point you to the 3 big commits I made in our fork to make the payment workflow work for us. I was waiting to revert those 3 commits in order to test the new Payment MFE. Those 3 commits allowed me to test everything else in our fork with Lilac without having to wait for the sudden appearance of the MFEs in the native installation. Finding out today that I cannot use the Payment MFE because I am not using Cybersource, Paypal or Stripe, well that is disappointing to say the least.

For the moment, I could go as is with Lilac and bite the bullet with my modifications until I can find a solution or we can find a solution as a community for all other payment processors. I am just worried there will be so much changes between Lilac and Maple that even rebasing my fork with maple.master will be an adventure in itself.

If you need more information or if you have comments, please do not hesitate to contact me.

Regards,
Pierre

2 Likes