Community update — July 2: new contributors, loop-context, Cursor/Windsurf examples #130
Replies: 2 comments
-
|
📣 Announcement refreshed — full contributor call-to-action with this week's merges (#127–#131), help-wanted table, and @harshjainnn hold note. New here? Read the top post ↑ then pick an issue and comment I'll take this. Maintainers: please pin this discussion in GitHub UI (Discussions → ⋯ → Pin) if not already pinned. |
Beta Was this translation helpful? Give feedback.
-
|
Cross-posted to Substack / social — if you arrived from there, welcome. 👋 Start here: pick an issue from the table in the post above, comment "I'll take this", and we'll assign you (same-day review on stories + adopters when possible). Fastest wins:
Questions? Reply in this thread. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Loop engineering is open for contributors. If you want a scoped first PR (~10 min to ~1 hr), this is the place to start.
Shipped this week
good first issuemerge — Aider appendix in primitives matrixloop-context— memory manager + circuit breaker (tool README)Thank you @roian6 and @harshjainnn for picking up work from the contributor quickstart.
In flight (contributor-led — we wait on you)
@harshjainnn — #126 / #114. Your initiative started Windsurf coverage. Reply on the PR when ready — close with credit or rebase and extend. No maintainer action until you chime in.
Help wanted — pick one, comment "I'll take this"
loop-init --toolvaluesFull
good first issuebacklog →How to get merged fast
Questions? Reply here · Q&A category · Add your loop (#92)
Beta Was this translation helpful? Give feedback.
All reactions