GitHub's Open Source Guidelines are chock full of good advice:
miniblog.
Related Posts
Bevy has an amazing approach to code review that requires two reviews by the community before a maintainer will review and merge.
"We let anyone submit PRs without vetting: why is the bar higher for reviewing?"
https://shaping.systems/blog/open-code-review/
I tried OpenClaw today and I was surprised by the short time horizon of conversations. Am I holding it wrong?
W: Summarise open issues on my GH repo.
O: (summary)
W: OK, remember how I want you to format content [..].
O: Noted.
W: Summarise the issues again.
O: What issues?
Some novel (to me) AI workflows from OpenAI in https://openai.com/index/open-source-codex-orchestration-symphony/
(1) Adding the ability for the LLM to create follow-up tasks in the issue tracker.
(2) Identifying weaknesses in the spec by implementing in several different languages.
