Prasad JB

Hi, I noticed multiple people have expressed interest in working on this. Since the website update involves WordPress and NumFOCUS staff coordination, I can help by: Preparing the updated GSoC...

Thanks for the clarification, @MridulS! I understand now that the website update is handled by NumFOCUS staff and isn’t something contributors can directly modify. If needed, I’m happy to assist...

Hi, I’d like to work on this issue. Could you please assign it to me?

Hi there! I’d love to help improve the clarity around the “Participant and Speaker Selection” section. Ensuring that wording is crystal clear can make the guidance more actionable for event...

Thanks for opening this @maheshkukreja and for the context @kwwall. I agree that a large code block might distract from the main CS - maybe a collapsible section or even...

Thanks for clarifying, @kwwall - that makes sense. Instead of focusing on specific tools like aspell, framing this in terms of string similarity metrics seems much more future-proof and language-agnostic....

Hi! 👋 I’d like to work on making `next dev` return a 405 status for non-GET/HEAD requests, matching `next start` behavior. My plan is to check the request method in...

Hi @rcomer, I understand your concern . This suggestion is genuine and not AI-generated. I’m trying to improve documentation for first-time contributors (since even I went through the same struggles)...

**Hi all**, PR #40 implements the README improvements suggested here (Git setup, fork & clone instructions, and a first PR example). Once it’s reviewed and merged, this issue can be...

I agree with @kwwall — splitting into multiple cheat sheets seems more maintainable in the long term, especially since the scope here (RAG infra, embeddings, supply-chain, runtime, compliance, etc.) is...