-
Notifications
You must be signed in to change notification settings - Fork 575
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
Schedule for LTS Meetings #6
Comments
I was keen to have one next week but so far haven't started a doodle and my schedule is slightly crazy as I move around the globe. The main blockers here are how busy both myself and @bnoordhuis are currently but this is important enough for ourselves and for our respective companies that we should be able to prioritise this. There is also some discussion of meeting in #5 too for reference. |
Ok, let me know if there's anything I can do to help facilitate getting things rolling. |
Doodle for scheduling: http://doodle.com/37rwvfupsnrawff6 |
Are the times in doodle localized? Or are they PDT? |
They should be PDT. |
Before we commit to a time, is there an agenda? |
Ok, so status update on this: @misterdjules suggested yesterday that the Call-Formerly-Known-As-The-Joyent-Node-TC-Weekly-Status-Call (thursday mornings at 9am pst) should transition into the nodejs/LTS call. We'll need to reschedule the time to better fit with @rvagg's schedule and others who are outside the US |
Also make sure you record this and we get it up on the soundcloud account :) |
@jasnell Any update on scheduling this call, or should be keep the Thursday/9am PDT time slot for the next one (this Thursday)? |
Now that @shigeki and @joaocgreis are part of joyent/node collaborators, they might want to attend at least some of these meetings, which makes finding a time slot that works across time zones even more important since they are in Japan and Portugal respectively. @jasnell @rvagg Is 1pm PDT a time slot that turned out to work best for most time zones? If so, then maybe let's see if that time slot works for any day of the week. |
Sure, may as well add another 6am to my calendar. Let's do this, thanks @misterdjules! |
Just added @shigeki and @joaocgreis as members of the LTS working group because they are collaborators in joyent/node. @jasnell @rvagg New doodle here only with the 1pm time slot for every day of the week but Wednesday (there's already the Node.js TSC weekly meeting on that day): http://doodle.com/myb9svwvuuake76x. @nodejs/lts Please fill out this doodle to let us know about your availability. If none of these time slots work for you, we'll come up with another set of time slots. |
Build is in that slot for Tuesday so that puts you and I out for that one for now. I can do any of the other options. |
@rvagg Good point, somehow I had missed that. Doodle edited. Thank you! |
Slots work for me but not this week ( 22nd is ok) |
At 1pm PDT I can attend only on Fridays, and even so not always. I can almost always attend meetings starting between 4am and 10am PDT (lasting until 11), later than that only Wednesdays and Fridays. Feel free to adjust the time as it's best for @shigeki since my input is still quite limited and I can always read the minutes. |
I wanted things to get started so I sent an invite for a meeting every Monday at 1pm PDT. @shigeki, is it a time that could work at least sometimes? We'll need your input on security related topics. We can always work from the minutes though. @joaocgreis I hope we can find a timing that works in the near future for you. As for @shigeki, in the meantime the minutes will allow you to follow what's being discussed in these meetings. If nobody has any major concern, then I suggest we start meeting this week, and move the joyent/node weekly call meeting to this one. |
Works for me. |
Ok with me as well |
@trevnorris @mhdawson Thank you! If anybody wants to be part of the meetings and did not receive an invitation, please let me know. Also, I've been trying to maintain an accurate list of people interested in LTS releases as the @nodejs/lts team. If you're not a member of this team and would like to participate in the LTS effort, please let me know too. |
I'm interested in joining for now in light of the release proposals set forth in nodejs/node#1997 and how LTS may interact in our current processes and potential future processes. |
I'm interested in the minutes. Will they be published in this repo (as an issue, wiki, ...) ? |
@drewfish Yes, they will be published. I would suggest to do that as a PR that gets merged into the repository's content, but that will need to be discussed too. |
It is a difficult time for me, but I'll attend when possible. Next Monday I can't make it. Thanks @misterdjules ! |
@Fishrock123 You've been added to the meeting invitation, thank you for the interest! |
@Fishrock123 Also added you to the list of members of the @nodejs/lts team. |
Closing this issue as we have our first meeting Monday June 29th 2015, and this meeting repeats every week. |
I don't think I'll actually make it to this, I'll probably be on the road. Next weeks, yes. |
What is the schedule for the LTS WG Meetings? We should get this kicked off soon.
The text was updated successfully, but these errors were encountered: