Dear (aspiring) GHC Hackers,
we are trying to improve the on-boarding experience for new GHC contributors. We are wary of the fact that long-term GHC contributors have a hard time estimating the amount of resistance a new contributor goes through. If you had a hard time getting started with GHC in the past, now there’s a chance for you to lend us a bit of your time to improve the experience for everyone.
Please go to Glasgow Haskell Compiler / GHC · GitLab and tell us:
- Did you find the contributing page (HACKING.md · master · Glasgow Haskell Compiler / GHC · GitLab)
- Did you find the instructions there helpful?
- Which of the instructions did not help you and you find redundant?
- If you have been contributing, which instructions were missing/ you had to discover through other means?
- Which other recommendations do you have to improve the developer documentation?
After following the instructions, which other hurdles are still there, i.e. which other parts of the contribution experience were lacking?
Have you been able to solve your problems?
Did you use any communication platforms to contact GHC devs? If so, which? Out of the following, which communication platform are you/were you comfortable with using for GHC purposes?
- The GHC Matrix
- The ghc-devs mailing list
- The GHC IRC
- The Haskell Discourse
- One of the other Haskell forums (please specify)
- Other (please specify)
You may answer in response to this mail to the ghc-devs mailing list or on this GHC issue: Improve onboarding experience for contributors (#26771) · Issues · Glasgow Haskell Compiler / GHC · GitLab.
Your answers and thoughts are greatly appreciated. Thank you so much.
PS: please refrain from ranting - keep the discussion constructive 