... | ... | @@ -27,7 +27,7 @@ GHC is a BSD-licensed open-source project, and we welcome your help in making it |
|
|
- **Testing against Hackage**: Patches that change the language GHC accepts may want to test against a subset of Hackage, kept up-to-date with GHC HEAD. See the [head.hackage repo](https://gitlab.haskell.org/ghc/head.hackage) for more information.
|
|
|
- **Licensing**: make sure you are familiar with GHC's [Licensing](licensing). Unless you say otherwise, we will assume that if you submit a contribution to GHC, then you intend to supply it to us under the same license as the existing code. However, we do not ask for copyright attribution; you retain copyright on any contributions you make, so feel free to add your copyright to the top of any file in which you make non-trivial changes.
|
|
|
- **For boot libraries**: GHC ships with a number of [boot libraries](commentary/libraries/version-history) maintained outside of GHC itself. Maintainers of such libraries should read [WorkingConventions/BootLibraries](working-conventions/boot-libraries) for guidance on how to maintain their libraries.
|
|
|
- **Tracking fixes across branches**:
|
|
|
- **Tracking fixes across branches**:
|
|
|
1. Find the issue, which should have a reference to the merge requests which fixed it
|
|
|
2. From the merge request, find the final commit SHA from Marge's comment
|
|
|
3. Look for references to that commit SHA in the appropriate branch.
|
... | ... | @@ -64,7 +64,7 @@ If you want to get a taste for possible starting tasks, the ~newcomer label coll |
|
|
### Advice
|
|
|
|
|
|
- Read up on the steps you are expected to take for [contributing a patch to GHC](/Contributing-a-Patch).
|
|
|
- Need help? You can email the [ghc-devs](http://www.haskell.org/mailman/listinfo/ghc-devs) list, or ask on IRC in `#ghc`.
|
|
|
- Need help? You can email the [ghc-devs](http://www.haskell.org/mailman/listinfo/ghc-devs) list, or ask on Matrix in [GHC room](https://matrix.to/#/#GHC:matrix.org).
|
|
|
- Don't get scared. GHC is a big codebase, but it makes sense when you stare at it long enough!
|
|
|
- You can [change](https://gitlab.haskell.org/help/user/profile/index?target=\_blank#change-the-email-displayed-on-your-commits) in your profile your commit email to private, e.g. `00001-username@users.gitlab.noreply.gitlab.haskell.org`.
|
|
|
- Don't hesitate to ask questions. We have all been beginners at some point and understand that diving in to GHC can be a challenge. Asking questions will help you make better use of your hacking time.
|
... | ... | |