Invitation: Dask Bi-weekly Maintenance Sync #324
Comments
|
Current attendees of this meeting (you know who you are) will meet today (May 23rd) to have a preparation sync in anticipation of a larger group attending next fortnight. |
|
Bumped date to June 13th to ensure @fjetter can make it. |
|
I've gone ahead and added a calendar invite. Feel free to modify/delete. I figured it was maybe annoying to figure out how the external calendar worked. |
|
We just finished the initial kickoff meeting for this new format and it went well! Here are a few notes. I spent a big chunk of the meeting on the preamble where I talked through this issue and set the scene. I'll probably paraphrase this in 30 seconds at the beginning of each call for a while, but the plan will be to keep the meeting short and sweet and focus on tasks that are falling between the cracks. @fjetter created a doc to track tasks and populated it with some things that need attention and @jrbourbeau shared a bunch of issues that need attention. Thanks both! It's likely that doc will be replaced with a project board in the future. We talked through a few tasks on this list, focusing on things that are high priority (such as PRs from first-time contributors that are overdue a review) and things that are falling between the cracks (such dask/dask-labextension#261 which is important to the community but is unclear who has the time and knowledge fix it). I'd love to see more faces at the call next time. If you regularly contribute to Dask and can spare a little time once a fortnight to help pick up something that is slipping through the cracks you would be most welcome! This format is also experimental so if you have thoughts or ideas about how we can continuously improve things I'll leave this issue open as a place to discuss that. See you all on the 27th! |
|
Thanks for organizing.
…On Tue, Jun 13, 2023 at 11:11 AM Jacob Tomlinson ***@***.***> wrote:
We just finished the initial kickoff meeting for this new format and it
went well! Here are a few notes.
I spent a big chunk of the meeting on the preamble where I talked through
this issue and set the scene. I'll probably paraphrase this in 30 seconds
at the beginning of each call for a while, but the plan will be to keep the
meeting short and sweet and focus on tasks that are falling between the
cracks.
@fjetter <https://github.com/fjetter> created a doc to track tasks
<https://docs.google.com/document/d/1bsdJf8Yt5FwC5KQqENczkg5XoUAjS2TvPhOOP2clBCQ/edit>
and populated it with some things that need attention and @jrbourbeau
<https://github.com/jrbourbeau> shared a bunch of issues that need
attention. Thanks both! It's likely that doc will be replaced with a
project board in the future.
We talked through a few tasks on this list, focusing on things that are
high priority (such as PRs from first-time contributors that are overdue a
review) and things that are falling between the cracks (such
dask/dask-labextension#261
<dask/dask-labextension#261> which is important
to the community but is unclear who has the time and knowledge fix it).
I'd love to see more faces at the call next time. If you regularly
contribute to Dask and can spare a little time once a fortnight to help
pick up something that is slipping through the cracks you would be most
welcome!
This format is also experimental so if you have thoughts or ideas about
how we can continuously improve things I'll leave this issue open as a
place to discuss that.
See you all on the 27th!
—
Reply to this email directly, view it on GitHub
<#324 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AACKZTDBB7G67KVWH5SX5UTXLCGJ7ANCNFSM6AAAAAAYL5HKKM>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
|
Reminder that this is happening again today! See you there. |
Hi Dask Community!
You may or may not be aware that Dask maintainers meet every Tuesday to discuss the maintenance of the various Dask projects.
We want to experiment with opening this call up to anyone who regularly contributes to Dask and has an interest in helping out with the maintenance of the projects.
The call will be 15-20 minutes every other Tuesday and repo maintainers will highlight high-priority tasks on the current maintenance backlog to active developers in the community. There will be an expectation for attendees to volunteer to pick up tasks that are highlighted.
Time/place
Scope
For now, we will focus on dask/dask and dask/distributed but may touch on auxiliary repos including dask/docker, dask/sphinx-theme, dask/dask-tutorial and dask/dask-examples. We are keeping deployment tools including dask-kubernetes, dask-jobqueue, etc and broader community projects including dask-sql, dask-awkward, xgboost, optuna, etc out of scope for the time being unless there is a serious breakage/blocker/escalation that needs to be addressed in the core projects.
The goal is for maintainers to communicate the following categories of tasks to folks who can pick them up:
Day-to-day tasks and business-as-usual activities shouldn't be discussed as that is already handled async on GitHub.
Who should attend
I would expect regular attendees to include anyone who considers themselves to be a Dask Core Developer and who regularly works on Dask, but anyone who wants to contribute to the maintenance of Dask is welcome.
Everyone should expect to leave with actions, if you don't want maintenance actions you are probably not the target audience.
If that's you, come join us!
The text was updated successfully, but these errors were encountered: