-
Notifications
You must be signed in to change notification settings - Fork 304
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
Jupyter Server weekly meetings #111
Comments
👍 |
👍
…Sent from my iPhone
On Oct 2, 2019, at 9:52 AM, Steven Silvester ***@***.***> wrote:
👍
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
@rgbkrk @captainsafia @betatim fyi Probably makes sense to give the Jupyter Steering Council a heads up on this meeting. |
@ellisonbg @fperez Would it be possible to have a weekly standing meeting calendar published somewhere? |
@willingc just like jupyterhub has a team compass (https://jupyterhub-team-compass.readthedocs.io/en/latest/meetings.html) and voila has another published calendar (https://voila-dashboards.github.io/), I suggested consolidating all the public meetings in one display on https://jupyter.org/community I am happy to make the change to the website, but super busy today. |
👍 on the meeting. |
@SylvainCorlay Thanks. That would be a great first start. |
@lresende may be interested as well. |
Would someone on the steering council be willing to share this meeting with the rest of the SC? 😃 I don't know how to email the whole group directly. I wasn't expecting this much interest 😆 Thank you, everyone, for responding quickly. We'll have our first meeting (next) Thursday, October 10th. Let's meet on the Cal Poly Zoom. See you all there! |
I can make 8 am. I'll stick it on the calendar. |
Works for me! See you next week. |
I'll put it on my calendar as well! |
Hi all, Just a reminder that we're meeting tomorrow, 8AM Pacific (or your timezone).
I'll moderate discussion and offer some recent background around the project. I look forward to seeing y'all there! 😎 |
@Zsailer Will there be a follow-up meeting this week? I realise we did not take time (it was not at the agenda anyway) to validate the weekly cadence. Whatever planning it is, it would be good to be posted to book our calendar. |
👍 Yes, I'll be hosting these meetings weekly at the same time. Thursdays at 8am, pacific. |
Has this week's meeting been yet? I feel like I might have gotten confused by the DST/timezones. |
@vidartf We have just finished. So now you have the same feeling as I had yesterday for the jlab meeting :) |
Hi all, I will be traveling during this week's (11/14) meeting time, so I won't be able to lead the meeting. I propose that we cancel this week's meeting, unless someone else would like to lead the call. |
Thanks, Zach - save travels...
…On Wed, Nov 13, 2019 at 8:56 AM Zachary Sailer ***@***.***> wrote:
Hi all,
I will be traveling during this week's (11/14) meeting time, so I won't be able to lead the meeting. I propose that we cancel this week's meeting, unless someone else would like to lead the call.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
--
Brian E. Granger
Principal Technical Program Manager, AWS AI Platform ([email protected])
On Leave - Professor of Physics and Data Science, Cal Poly
@ellisonbg on GitHub
|
closing this issue since we have a weekly meeting issue already. |
* revert health endpoint * Bump to 0.10.1
I'd like to propose a weekly meeting for Jupyter Server so we can synchronize and catalyze development. I'm posting this issue here to gauge interest. I'll follow up over email.
I propose Thursday's at 8AM Pacific (your timezone).
The first meeting wouldn't be until next week, October 10th. If this time doesn't work for most people, I'm flexible to adjust.
@kevin-bates @SylvainCorlay @maartenbreddels @blink1073 @echarles @jasongrout @ellisonbg @takluyver @minrk @vidartf @rgbkrk @mpacer @willingc @captainsafia @betatim @fperez
The text was updated successfully, but these errors were encountered: