Skip to content

Regular Meeting frequency/time update #3503

Closed

Description

@UlisesGascon

We had discussed this in several places (slack, offline...) and I think make sense to create a proper issue to find a good time slot that works for most of us (cc: @nodejs/build).

Currently the Meetings are every few weeks (3 weeks if I remember well) in different days and timezones (Tuesdays as Wednesdays). Here are the last ones as example: #3500 and #3479.

I think currently one of them is quite out of the Americas/Europe timezone and the other one is quite early for Americas. Do we want to change them? What works best for you?

Activity

  1. sxa commented on Sep 27, 2023

    @sxa
    Member

    Taking into account a recent post on the build mailing list it makes sense to stop using the 2200 UTC slot now since that that is usually the most difficult one. The one in that slot that you referenced had three declines in it. And while the 1200UTC one is quite early (0800) for those in Eastern time, I would likely be unable to make it in the hour after that due to another recurring meeting (Two hours later might be ok though if that was desired)

  2. richardlau commented on Sep 27, 2023

    @richardlau
    Member

    +1 for dropping/moving the UTC 10pm Wednesday meeting -- those just are not happening. The last few I joined at that time were just @mhdawson and myself and the slot is inconvenient for both of us.

  3. MoLow commented on Sep 27, 2023

    @MoLow
    Member

    +1, times were not optimal for me either

  4. mhdawson commented on Sep 29, 2023

    @mhdawson
    Member

    +1, neither time works for me right now.

  5. UlisesGascon commented on Oct 19, 2023

    @UlisesGascon
    MemberAuthor

    Seems like we have agreed on the change. Should we use UTC Wed 12:00 (12:00 PM)?, so both meetings take place at the same time but on different weekdays?

    • UTC Wed 12:00 (12:00 PM)
    • UTC Tue 12:00 (12:00 PM)

    I think we can create a PR to implement this change and confirm if everyone agrees. I am not sure where this change needs to be made.

  6. targos commented on Oct 19, 2023

    @targos
    Member

    UTC 12:00 doesn't seem ideal. Close to lunch break in EU, very early in NA.

  7. UlisesGascon commented on Oct 23, 2023

    @UlisesGascon
    MemberAuthor

    @nodejs/build I created a poll with the UTC times to see what time works better for the team. Please vote 🙏

    https://poll-maker.com/poll4974500x0229494a-152

  8. sxa commented on Oct 23, 2023

    @sxa
    Member

    Wednesday afternoon is quite horrible for me with calls so chances are I'd miss many of them if that's when it was held. Also if it's fixed in UTC then regardless of which option I choose I'm going to have a definite regular conflict for six months of the year due to time zone differences.

  9. UlisesGascon commented on Oct 31, 2023

    @UlisesGascon
    MemberAuthor

    Seems like UTC 2 PM is the best slot based on the poll results. Should we do the change?

    Screenshot 2023-10-31 at 12 47 50
  10. MoLow commented on Oct 31, 2023

    @MoLow
    Member

    +1

  11. anonrig commented on Oct 31, 2023

    @anonrig
    Member

    +1 to UTC 2PM

  12. sxa commented on Oct 31, 2023

    @sxa
    Member

    I've just voted for 1200 and 1500UTC (which will work for 50% of the year!) which evens it out at 18% for all options other than 2PM which has 25%, but that slot would completely exclude me.
    What was the reason for moving it from Tuesday to Wednesday?

  13. targos commented on Oct 31, 2023

    @targos
    Member

    It's not moving from Tuesday to Wednesday. IIUC the proposal is to move the time, but keep alternating between Tuesdays and Wednesdays.

  14. sxa commented on Oct 31, 2023

    @sxa
    Member

    It's not moving from Tuesday to Wednesday. IIUC the proposal is to move the time, but keep alternating between Tuesdays and Wednesdays.

    Gotcha - I'd misinterpreted the earlier comment. I'll get to 50% of them then :-)

  15. UlisesGascon commented on Nov 7, 2023

    @UlisesGascon
    MemberAuthor

    @mhdawson do you know how to update the calendar and the issue generation? I am not sure where we need to do the change 🤔

  16. mhdawson commented on Nov 14, 2023

    @mhdawson
    Member

    To make sure I understand it should be UTC at 2PM UTC alternating between Tuesday and Wednesday every three weeks?

    If so I can go ahead and update the calendar to reflect that.

  17. mhdawson commented on Nov 17, 2023

    @mhdawson
    Member

    @UlisesGascon calendar is updated. Let me know if it does not look updated to you, otherwise we should be good to go.

  18. UlisesGascon commented on Nov 19, 2023

    @UlisesGascon
    MemberAuthor

    @UlisesGascon calendar is updated. Let me know if it does not look updated to you, otherwise we should be good to go.

    I can see the changes in the online version https://calendar.google.com/calendar/u/0/embed?src=nodejs.org_nr77ama8p7d7f9ajrpnu506c98@group.calendar.google.com 👍.

    I will close the issue then.

    Thanks a lot @mhdawson!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions