Weekly Standup (2026-01-05)

[github-actions]

🎉 Weekly Standup 🎉

An async stand-up to provide status reports on what you've been up to the previous week, what your plan is for the upcoming week, and to request help for things you are working on.

Copy and paste the template below, and answer questions as needed!

**🙌 Thanks I'd like to give**

- <name> helped me out with...

**✅ Updates from last week**

- I worked on <link-to-pull-request>

**🔭 My plan for the current week**

- I plan on working on...

**🙏 Challenges that I've faced and things I'd like help with**

- I had a hard time figuring out...

**🏝️ My availability for next week**

- I'll be off on <date>

**💬 Important items for discussion**

- I have a question about <issue-or-pull-request>...
- Can @<github_handle> comment on issue #NN?
- I opened #NN for discussion.
- I need to discuss...

🎯 Task Status

Please make sure pull request labels and draft status reflect the current status of your work!

[kgryte]

🙌 Thanks I'd like to give

• Shoutout to @batpigandme for helping with I-Corps preparation.

✅ Updates from last week

• Standard PR review.
• ndarray dtype migration.
• Adding additional complex number APIs in order to pave the way for ndarray/base/ternary.

🔭 My plan for the current week

• I need to revisit the plot refactor in order to help unblock @gururaj1512 et al so we can move that effort forward.
• Creating more good first issues and initial tasks.
• Prepping for increased GSoC arrivals.
• I-Corps preparation.
• Initial SPA for dev docs to unblock @batpigandme.

🙏 Challenges that I've faced and things I'd like help with

• There are some tricky bits in terms of timing for the dtype migration efforts. Namely, several packages will eventually need to be upgraded simultaneously in order to have a clean break to using dtype instances instead of string literals.

🏝️ My availability for next week

• I'll be around.

💬 Important items for discussion

• Nothing is top of mind for the moment other than the usual tasks and making headway in various areas.

[batpigandme]

🙌 Thanks I'd like to give

• @kgryte for stdlib-js/www@074493f, and letting me put off my full-blown conversion to a front-end web dev for another day 😅

✅ Updates from last week

• I-Corps prep bonanza: getting in touch with old contacts, "customer" discovery, etc.

🔭 My plan for the current week

• Outreach and scheduling for NSF interviews
• Getting docs into the new app

🙏 Challenges that I've faced and things I'd like help with

• Any thoughts on how to disable expected-html-sections lint rule for markdown files that aren't function READMEs. (You can see my failed attempt docs: draft AI usage guidelines stdlib#9459 (comment), and Athan's successful but verbose workaround in stdlib-js/stdlib@79520cc#diff-b335630551682c19a781afebcf4d07bf978fb1f8ac04c6bf87428ed5106870f5R23-L40)

🏝️ My availability for next week

• I'm here

💬 Important items for discussion

• Would love feedback/discussion on docs: draft AI usage guidelines stdlib#9459, especially building up patterns for Dos and Don'ts (cc @Planeshifter @headlessNode, if you have any patterns/rules from the METR study that might be useful, those could be good additions)
• Once we have ^^ in an okay place, can open up #ai-dev channel in Zulip