-
-
Notifications
You must be signed in to change notification settings - Fork 30
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
Weekly Team Meetings: Jan-Jun 2023 #170
Comments
January 4th, 2023Attendees
Agenda
Additional Discussion
|
January 11th, 2023
Agenda
Additional discussions
|
January 18th, 2023
Agenda
Additional discussionsNone |
January 25th, 2023
Agenda
Additional discussions |
February 1st, 2023
Agenda
Additional discussions
|
February 8th, 2023
Agenda
Issue triageWe started with 25 bugs tagged to milestone 4.0.0 without an assignee. "Assigned" in the list below means that we assigned the bug to at least one person, by the person's request. An assignee may assign the bug to another person.
Additional discussions(none) |
February 15th, 2023
Agenda
Additional discussionsIssue triageBefore the meeting, 19 issues were labeled with tag:Feature Parity. "Assigned" in the list below means that the issue is now assigned to one or more GitHub users.
After the meeting, 16 issues are labeled with Next week, we'll look at 4.0.0 issues tagged with |
February 22nd, 2023
Agenda
Additional discussionsResume using RTC for JupyterLab meetings starting next week (vote passed) Issue triageJupyterLab 4.0.0 enhancements — 26 items
|
March 1st, 2023
Agenda
Additional discussionsJupyterLab 4.0.0 bugs/enhancements
|
Hello Jupyter(Lab) community members: Before any other apologies, please excuse if this comment reaches your inbox/phone and causes a waste of your time. During the most recent JupyterLab Weekly Team Meeting, I pretty much jumped down another Jupyter community member's throat for a pretty straightforward question, and would like to apologize for making anyone feel like they don't have space and respect. This is not behavior I would like directed at myself, which should have been a clear indicator that it was not appropriate. It was wrong of me to react this way, and I'll be making an explicit effort to be more civil in my speech and words, both in person and in these online spaces where we build Jupyter, both the software and the community. The question (in question) touched a pretty raw nerve of mine, based on some (mostly online) interactions over the course of several years with other people in the broader scientific computing community not even present at the call, about which the person in question was not aware. I fully recognize reacting in this manner was unbecoming of a Jupyter community member, and if unable to respond in a civil, respectful manner, I should have declined to comment. While none of the above excuses my words or tone, I would like to hope that accepting and acknowledging this publicly is a better path than waiting for things to get worse over time. If anyone feels that my behavior yesterday (or at any other time) should have further repercussions, I would ask this not be belabored on this issue (again, to be respectful of others' time), but rather through the mechanisms described in the Jupyter Code of Conduct, which includes a way to raise any issues anonymously. Thank you again for your time. |
March 8th, 2023Note: This meeting will be held at 09:00 PDT (UTC−07:00) next week, 16:00 GMT/WET, 17:00 CET.
Agenda
Additional discussions
|
March 15th, 2023
Agenda
Additional discussion
Of the 72 open pull requests in JupyterLab, we closed 10; 62 remain.
|
March 22nd, 2023Note: Next week, European "summer time" (WEST/CEST/etc) begins, so for example, Paris will once again be 9 hours later than Seattle.
Agenda
Additional discussionRTC testing session. |
March 29th, 2023
Agenda
Additional discussion
Bugs reviewed:
|
April 5th, 2023
Agenda
Additional discussion4.0.0 beta update — 51 open issues |
April 12th, 2023
Agenda
Additional discussionRTC play notes:
4.0.0 triage update — assigned new owners for the remaining unassigned release blockers: |
April 19th, 2023
Agenda
Additional discussion[Mike] heads up, npm 4.0.0 review: 44 open issues in 4.0.0, of which 5 are tagged as release blockers
|
April 26th, 2023
Agenda
Additional Discussion
|
May 3rd, 2023
Agenda
Additional Discussion
|
May 17th, 2023
|
May 24th, 2023
Additional Discussion
|
May 31st, 2023
Additional Discussion |
June 7, 2023
|
June 14, 2023
Additional discussion |
June 21th, 2023
Additional discussion
|
June 28, 2023
... [Fred] I'll open an issue on those repositories to notify subscribers that may be willing to take over the maintenance with a two weeks notice. After this 2 weeks, if no reaction to the issue, I will update the project README to add a notice of archiving the code linking to the team-compass issue. And then archive the projects.
|
Thanks @afshin for uploading recordings to YouTube! I updated the issue description with 📺 links to videos, where available. |
Here is a record of the agenda/minutes for our weekly meeting. Everyone is welcome to join.
Let's avoid using this thread for discussion. If you'd like to discuss something in the minutes, open a separate issue and reference this thread.
Meeting Notes
The text was updated successfully, but these errors were encountered: