I agree about docs as a tool for thought.

What about the other side of docs, keeping them up to date?

I don't really see that as a different thing. The docs and comments guide you when it comes to doing maintenance, so it's natural to use them to plan and think about the needed changes. They get updated almost as a side effect.

I guess the mindset I have internalized is that I don't really see doc writing/updating as a separate thing from coding. I do it out of habit and without really being aware of it. Or, more likely, I've just been doing this a very long time and have deeply ingrained habits.

There has been an influx of AI-generated bug reports to popular OSS projects. It's unclear if this is malicious or someone built a tool with good intention that is now causing maintainers to be inundated with issues.

Has anyone stumbled upon an AI tool that helps submit bug reports to OSS project?

https://www.theregister.com/2024/12/10/ai_slop_bug_reports/

Nvm turned out to be a GitHub issue

Just noticed 404s on dbt core - was this announced recently?

https://github.com/dbt-labs/dbt-core

probably just https://www.githubstatus.com/incidents/4349zxvb8stp

the future of OSS maintenance: https://dosu.dev/

Big fan of Aider.

We are interesting in integrating Aider as a tool for Dosu https://dosu.dev/ to help it navigate and modify a codebase on issues like this https://github.com/langchain-ai/langchain/issues/8263#issuec...

Thank you for the feedback! That's good to know

Just launched a new marketing site with fun animation that requires scrolljacking.

Do you think it's worth it?

don't see the point

Oh nice. It's been a while since I've used LaTeX, but ChatGPT is great with it :)

Agreed! The status meetings we've thought about are:

- Status of project - Summary of weekly work (retro) - Breakdown of work by project

Any status meetings we are missing?

Daily standup.