Contributor technical overview #1768
Merged
Conversation
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.
Following a prompt from @mayank-mundhra-2012 over at #1741, I've decided to write a proper technical guide before jumping into closing PRs and issues.
At least 3 people reached out in various mediums telling me they'd be happy to contribute, and IMHO the main barrier for onboarding them is a lack of exhaustive, contributor-oriented material. This is my attempt at resolving the issue, and once it is done I hope to be more oriented towards actually fixing stuff rather than documenting them.
For everyone who's waiting - my apologies, but if this is a community-driven project, collaboration-enabling material is just as important as writing code, and I feel this is the right decision.