How to Contribute to erlang/otp
A practical guide backed by erlang/otp's real pull-request history - not guesswork.
48%
PR merge rate
no recent data
First review
42%
First-timer success
A Tier
C-Rank
Your game plan
1
Pick a starter issue
erlang/otp currently labels 7 open issues as "good first issue". Start there - maintainers expect newcomers on those.
2
Time your pull request
Median first review lands within no recent data. Open your PR when maintainers are active rather than right before a weekend.
3
Keep it small and focused
Outside PRs to this repo are merged at a 48% rate. Small, well-described PRs that pass CI consistently outperform large ones.
4
Engage with review feedback
44 active maintainers review contributions here. Respond to comments promptly - responsiveness is the strongest predictor of getting merged.
Open good first issues
runtime_tools: scheduler weighted utilization ignores cgroup CPU quota
#11804Expose distribution queue sizes
#11803logger: logger_std_h runs file_check every 20 writes, regardless of file_check config
#11711odbcserver in OTP 29 is not installed when given --with-odbc switch
#11705logger: remove_handler writes back a stale handler list and can drop a concurrently added handler
#11660Looking for more? See best Erlang repos for beginners.