Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Review meeting times #129

Closed
mhdawson opened this issue Mar 25, 2019 · 12 comments
Closed

Review meeting times #129

mhdawson opened this issue Mar 25, 2019 · 12 comments

Comments

@mhdawson
Copy link
Member

mhdawson commented Mar 25, 2019

Current meeting times are 9 EST and 2EST on Mondays.

Please comment/discuss if these times still work for the team?

Edit (mborins)

The Sheet: https://docs.google.com/spreadsheets/d/12e8lN9ywi-2kAtcW08WS3x3S-6TXiOO8_yxs3j0Sm2E/edit#gid=0

@keywordnew
Copy link
Member

keywordnew commented Mar 25, 2019

Suggestion to amplify issue #123 for more meeting chairs.

With the bootstrap meetings now intended to morph into CPC meetings over time, we'd benefit from improved timezone coverage. With chairs from different timezones we'd be able to better include people not in UTC-8 through UTC+6.

@keywordnew
Copy link
Member

2 EST still works for me :)

@mcollina
Copy link
Member

The time still work for me. Mondays are generically bad as I'm typically traveling to some place on Monday, and I end up being on flights.

Also, do we still need weekly bootstrap/CPC meetings?

@jorydotcom
Copy link
Contributor

Per our meeting today, I've updated James' awesome spreadsheet to start collecting availability for new times.

Please take a look at this google spreadsheet and add your availability for Tuesdays and Wednesdays - note that there are two sheets in the same doc.

@bnb
Copy link
Member

bnb commented Apr 15, 2019

We're setting a deadline of May 1st to close the spreadsheet above 👍

@mhdawson
Copy link
Member Author

I believe we agreed to change to 12 EST on Wednesdays at least for a start. One note is that 1/3 weeks it will overlap with the Node.js TSC meeting.

@mhdawson
Copy link
Member Author

I've updated the calendar to reflect the new time and updated the generator so that it should create the meeting issue next Monday.

@evenstensberg
Copy link
Member

Whichever time works for webpack, we're adaptive as long as it's european times

@joesepi
Copy link
Member

joesepi commented Jul 10, 2019

We have discussed this in the last couple meetings (every meeting?) and I suggested that I propose some time pairings. In the times I am suggesting, I aimed to keep them on the same day, but maybe others would prefer alternating days and times. Also, 1600 was best on both days, so I worked on pairings with that time (except one wildcard). All times below in UTC.

Please vote with emoji

Wednesday

emoji time1 (rank) time2 (rank)
👍 1600 (84) 1900 (81)
1400 (73) 2000 (79)

Tuesday

emoji time1 (rank) time2 (rank)
🚀 1600 (89) 2100 (84)
🎉 1600 (89) 1900 (80)
😄 1600 (89) 1800 (84)

@boneskull
Copy link

This might come in handy: https://www.timeanddate.com/worldclock/converter.html

@mhdawson
Copy link
Member Author

The TSC meeting shared Wed 16,19 we would just need to ensure we schedule so they oppose as insterad of lining up.

@joesepi
Copy link
Member

joesepi commented Jul 17, 2019

Documenting what was discussed and decided on at today's meeting.

We are moving the weekly Cross Project Council meeting to Tuesdays, alternating between 1600 and 1800 UTC, starting next Tuesday at 1800 UTC. 🎉

@brianwarner will work with @mhdawson to get calendar updated and such.

/cc @openjs-foundation/cpc-voting-members @openjs-foundation/cpc-regular-members

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

9 participants