Communicate current policy around accepting direct PRs from the community

[saengel]

Communicate current policy around accepting direct PRs from the community.

This has been approved by the engagement team.

[gitvelocity-reviewer]

📊 Code Quality Score: 1/100

Base Score 4 × ESF 0.1 = 0.4, rounded to 1

Category	Score	Factors
🔭 Scope	1/20	One file modified: README.mkd. Five lines added, no logic files touched.
🏗️ Architecture	0/20	No module boundary changed. No dependency or structural change.
⚙️ Implementation	0/20	No code logic. Two prose paragraphs added with one external hyperlink to developers.sefaria.org.
⚠️ Risk	1/20	The text sets contributor expectations publicly; a poorly worded policy could affect community relations, but the change is trivially reversible with a revert commit.
✅ Quality	2/15	No tests applicable to a documentation change. Prose is readable and the external link is present. No test accompanies it, nor is one expected.
🔒 Perf / Security	0/5	No performance or security work present.

Was this score accurate? 👍 Yes · 👎 No

How this was scored →

_{Scored by GitVelocity · How are scores calculated?}

[gitvelocity-reviewer]

📊 Code Quality Score: 1/100

5 (base) × 0.1 (Nano ESF) = 0.5, floored to 1

Category	Score	Factors
🔭 Scope	2/20	One file modified: README.mkd. The change adds 8 lines of prose to an existing section. No subsystems, APIs, or logic paths are touched.
🏗️ Architecture	0/20	No module boundary changed. No dependency added or removed.
⚙️ Implementation	0/20	The change consists entirely of prose text with no branching logic, algorithms, or state management.
⚠️ Risk	1/20	The section is publicly visible and communicates Sefaria's contribution policy to potential contributors. An inaccurate or unwelcoming message could affect community relations, but the file is trivially editable.
✅ Quality	2/15	No tests apply to a README change. The prose is internally consistent and links to the Powered by Sefaria developer docs page.
🔒 Perf / Security	0/5	No performance or security work is present in this change.

Was this score accurate? 👍 Yes · 👎 No

How this was scored →

_{Scored by GitVelocity · How are scores calculated?}