Weekly Standup (2026-07-13) #141

Activity

1. github-actions

   added

   Weekly StandupWeekly standup to coordinate stdlib activities and development.Weekly standup to coordinate stdlib activities and development.

   on Jul 13, 2026
2. github-actions

   assigned

   anandkaranubc

   ,

   batpigandme

   ,

   gururaj1512

   ,

   headlessNode

   ,

   kgryte

   ,

   Neerajpathak07

   and

   Planeshifter

   on Jul 13, 2026
3. batpigandme commented on Jul 13, 2026

   

   batpigandme

   on Jul 13, 2026

   Member

   More actions

   🙌 Thanks I'd like to give

   • @kgryte for helping me with my existential crisis cum blog-post draft.

   ✅ Updates from last week

   • Opened feat: add accessible footnotes and margin sidenotes www-dev-blog-theme#8 for the ghost theme footnotes/sidenotes work.
   • Kept iterating on the "Do You WANT Contributors?" draft—restructured to v0.2, fixed citations (Yang, Gourdol), added the origin-story graf, and worked through kent/venn/debian flow fixes.
   • Scoped standing up ghost-publish as its own project and added the ghost theme footnotes/sidenotes living doc.

   🕵️ Pull requests I reviewed

   • https://github.com/stdlib-js/blog-drafts/pull/12 which is gonna be 🔥, @gunjjoshi

   👩‍🎓 One thing I learned last week

   • Drafting the ghost-publish RFC, I learned where Ghost's own Content API draws its boundary: post data is a flat set of fields (html, feature_image_alt, og_*, etc.), with no field representing things like callout-card type or image-width variant—those editor affordances collapse into the opaque html string once rendered. That's the same line the RFC ends up drawing for what ghost-publish should and shouldn't try to do.

   🔭 My plan for the current week

   • Keep moving "Do You WANT Contributors?" toward a shareable draft that doesn't bring shame on my family, employer, or nation.
   • Stand up the ghost-publish project and push the style-pass plan forward.

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

   • I couldn't find a documented subset of the stdlib JS style guide scoped to non-monorepo code (e.g. JavaScript code that's part of stdlib blog theme), so I wrote one up as a gist: stdlib House Style for Non-Monorepo JS. Would 💖 love love feedback on this (since I am, admittedly, not a JavaScript person).

   🏝️ My availability for next week

   • I'll be around all week.
4. Sachinn-64 commented on Jul 13, 2026

   

   Sachinn-64

   on Jul 13, 2026

   Last edited by Sachinn-64

   Member

   More actions

   🙌 Thanks I'd like to give

   • @kgryte for reviewing the PRs, and to @kgryte and @gururaj1512 for passing my midterm evaluation.

   ✅ Updates from last week

   • I worked on renaming the transform packages to use the ctor conventions, feat: add plot/vega/transform/sample/ctor stdlib#13416, feat: add plot/vega/layout/ctor stdlib#13428

   🕵️ Pull requests I reviewed

   • I reviewed and provided feedback on the following PRs:

     • None

   🧑🎓 One thing I learned last week

   • I learned that the label transform helps place text labels automatically so they don’t overlap with other chart elements.

   🔭 My plan for the current week

   • I plan on working on assertion packages for label transform, plot/vega/transform/label/ctor, renaming the open PR's of transform to use the ctor convention.

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

   • Nothing at the moment.

   🏝️ My availability for next week

   • I'll be available.

   💬 Important items for discussion

   Nothing for now.
5. MeKaustubh07 commented on Jul 13, 2026

   

   MeKaustubh07

   on Jul 13, 2026

   Member

   More actions

   🙌 Thanks I'd like to give

   • @kgryte and @gunjjoshi for passing my midterm evaluation! I've taken careful note of all the feedback, suggestions, and improvements.

   ✅ Updates from last week

   • Refactored ~12 ndarray wrappers to use the matrix constructor instead of the raw new ndarray approach.
   • Refactored and added enum string resolution support for level 2 blas/base/* packages.

   🕵️ Pull requests I reviewed

   • I reviewed and provided feedback on the following PRs:
     • Various PRs for ndarray level 2 wrappers involving matrix operations.

   🧑‍🎓 One thing I learned last week

   • I deepened my understanding of the @stdlib/ndarray/matrix/ctor constructor and its internal abstractions. Specifically, I learned about the nuances of instantiating matrices using nested generic arrays versus flat ArrayBuffer inputs across different typed implementations (e.g., Complex64Matrix), and how to correctly typecast and resolve string enum constants (like uplo or trans) when bridging generic multi-dimensional array interfaces with underlying base BLAS functions.

   🔭 My plan for the current week

   • I plan on working on finishing the refactoring for the remaining 2-4 packages to use the matrix constructor.
   • As @kgryte suggested in the last standup, my current plate is mostly clear after these refactors, so I'm looking forward to handling work related to the blas/ext/base* packages.

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

   • None this week.

   🏝️ My availability for next week

   • I will be available throughout the entire week.

   💬 Important items for discussion

   • None for this week.
6. prajjwalbajpai commented on Jul 13, 2026

   

   prajjwalbajpai

   on Jul 13, 2026

   Member

   More actions

   🙌 Thanks I'd like to give

   • @aayush0325 for resolving multiple small and large issues I faced through the week.
   • @aayush0325 and @kgryte for passing my GSoC mid-term evaluation.

   ✅ Updates from last week

   • I worked on dlasq2 and dorgqr LAPACK routines.

   🕵️ Pull requests I reviewed

   None

   🧑🎓 One thing I learned last week

   • I learned that ULP difference does not work with different sign numbers. For example, near-zero values like 2.4e-17 and -4.6e-19 are both essentially zero but they differ by ~9e18 ULPs due to opposite signs.

   🔭 My plan for the current week

   • As the mid-term evaluation is over and now all the remaining routines are high-level and have multiple dependencies, it is a good time to spend this week to tidy up all of the PRs I have made since the start of this GSoC project. This would speed up the review process and will not cause too many files in the lib/ directory of upcoming PRs. I will keep posting about this on Zulip.

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

   • I had a hard time figuring out how to handle the tests with the above mentioned ULP testing issue.

   🏝️ My availability for next week

   • I'll be available.