Add a contributor on-ramp to CONTRIBUTING - #20
Merged
Conversation
The issue list is only an invitation if someone finds it. Adds a 'Where to start' section naming the three gaps that matter most for adoption (monotone constraints, stability monitoring, fair lending), the smaller entry points, and an explicit note that domain knowledge is as welcome as code — several issues need someone who has governed a scorecard in production more than someone who writes fast Python.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Twelve issues (#8–#19) now describe the gaps between where CompileML is and where a risk function could adopt it. This adds the pointer, because an issue list nobody finds is not an invitation.
Names the three that matter most (#8 monotone constraints, #9 stability monitoring, #10 fair lending), lists the smaller entry points, and says explicitly that domain knowledge is as welcome as code — several issues need someone who has governed a scorecard in production more than someone who writes fast Python.
Docs only.