-
Notifications
You must be signed in to change notification settings - Fork 46
How often and when should we meet? #2
Comments
Hey @nodejs/modules I've created a doodle that includes all 24 hours for an entire week. Please fill out your availability for a bi-weekly recurring meeting https://doodle.com/poll/cqavkzwxtxzccs4z There will be an expectation of active attendance to these meetings. If there is a wide enough range of times due to time zones we may opt to have rotating times Please let me know if you think we should hold weekly meetings for the first month or two in order to properly bootstrap edit: Timezone is currently EST, this can be changed at the top of the page |
To clarify: this is general availability moving forward, not related to any specific dates in the range of 2/11 - 2/16? |
Indeed
…On Feb 5, 2018 5:10 PM, "Jordan Harband" ***@***.***> wrote:
To clarify: this is general availability moving forward, not related to
any specific dates in the range of 2/11 - 2/16?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#2 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAecV4Up05mFQtPtVL7ZrlDdnt4XPHdoks5tR3xlgaJpZM4R2aU5>
.
|
@MylesBorins are you going to call a first meeting? Is the meeting agenda specified anywhere already? |
We are going to have our first meeting Next Wednesday the 14th at 2pm EST So i've reviewed the agenda and have narrowed down the dates quite a bit!!! From 120 potential times we have narrowed the choice down to 10 finalists As we only had 19 participants I've created one more doodle to try and get people to hone in on the best time for the group at large https://doodle.com/poll/vdb8cgz48q3zzt2t @nodejs/modules please respond to this doodle by end of week next week. |
BTW, I recognize that these times are not necessarily the best for all time zones involved, if you cannot make any of these times and have concerns please let us know |
barring the unforeseen, i won't be able to make next wednesday due to work. |
@zackschuster I believe you can click on the time zone to change it to your local time |
@MylesBorins thanks, updated my responses. |
Sounds good to me |
I reached out to all individuals in the group via private email or DM to inform them that if they do not fill out the doodle by Friday they will be moved to observer status the only person I couldn't find contact info for was @devamaz. |
I've just closed the poll. Our next meeting will be Wednesday February 28th at 3pm EST (8pm GMT) and will be recurring every two weeks @mhdawson @bnb @jasnell @williamkapke would you be able to add this to the calendar? |
@MylesBorins done 👍 |
Closing this as the meeting is now on the calendar |
I don't see the meeting on the calendar |
Reopening, don't see it on cal either |
Thanks is the incorrect date. It should Wednesday the 28th (at that time)
and biweekly
…On Wed, Feb 21, 2018, 11:45 AM William Kapke ***@***.***> wrote:
Here's what I see (in PST)...
[image: image]
<https://user-images.githubusercontent.com/739813/36492983-55bd0edc-16e3-11e8-8dfd-8bf9cad80217.png>
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<#2 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAecVxk6mITczjfxUf5uOWvlaWiCtpuHks5tXEgSgaJpZM4R2aU5>
.
|
Apologies, changes it to the correct date. Could you double check, @MylesBorins? |
LGTM, closing again |
When do we get the link to the meeting please
…On 21 Feb 2018 6:13 p.m., "Myles Borins" ***@***.***> wrote:
LGTM, closing again
—
You are receiving this because you are on a team that was mentioned.
Reply to this email directly, view it on GitHub
<#2 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AE2tHiCoxwRSWAu6wOMl4f4BnC0QYXUUks5tXE7VgaJpZM4R2aU5>
.
|
@inidaname I will open an issue with all the details for the specific meeting on Monday, the link to join the meeting with come on Wednesday just before the meeting. The time is consistent, so you can either subscribe the the main calendar (https://nodejs.org/calendar) or alternatively add it to your own calendar (what I do) |
I think that Bi-Weekly would be a good cadence to start with. We can try and find a good time once we have some members
The text was updated successfully, but these errors were encountered: