Planned contributor guidelines
Public
Planned contributor guidelines
Agent
Pi
Model
Claude Opus 4.5 (latest)
Started
Jan 16, 11:40 PM
Messages3
Downloads0
Clarified enforcement and communication policies.
PlanAsked about PR scope and issue referencing.
PlanInquired about code quality and style requirements.
Plan
we need a contributor md file, ask me questions what's most important. it needs to be concise. we are in the age of agents where people just throw PRs at the repo generated by coding agents without them understanding or reviewing their shit, this is the thing that is most unacceptable. agent assisted prs are fine. if you send your first PR, use your human voice. PRs should not have walls of text, but be concise in describing what problem they fix and how, or what feature they introduce and why its a good fit for pi and not an extension. i probably forgot other shit. i also want to outline consequences if people do not adhere to this. for bigger changes, people should hop onto the discord to discuss first (but no guarantees they will get an answer imediatey) i want this to be concise
The user wants to create a CONTRIBUTING.md file. They've given me some key points and want me to ask questions to fill in gaps. Let me summarize what they've told me:
Questions I should ask:
Got it. A few questions to fill in gaps:
Consequences - What happens when someone submits an obvious agent-dump PR? Auto-close without comment? Close with a canned response? Ban repeat offenders?
Discord link - What's the invite URL?
"Bigger changes" threshold - New features? Anything touching core APIs? Or just use judgment?
Issue requirement - Should PRs reference an existing issue, or is it okay to submit standalone fixes/features?
Code requirements - Point them to run npm run check and fix all errors? Any other technical gates?
License/CLA - Need contributors to agree to anything, or is it implicit (MIT)?
First-timers - Should they start with an issue discussion before opening a PR, or is a good PR fine as a first contribution?