... | @@ -8,6 +8,9 @@ This page has pointers to information you'll need. |
... | @@ -8,6 +8,9 @@ This page has pointers to information you'll need. |
|
First, 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.
|
|
First, 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.
|
|
|
|
|
|
|
|
|
|
|
|
Subscribe to the [ cvs-ghc mailing list](http://www.haskell.org/mailman/listinfo/cvs-ghc). This list gets an email for every commit that is made, and reports generated by the automated nightly builders, and it is also the place to discuss ongoing development of GHC. The list is high volume, so you probably want to at least filter it into a separate folder/label.
|
|
|
|
|
|
|
|
|
|
These pages guide you step-by-step through making a contribution:
|
|
These pages guide you step-by-step through making a contribution:
|
|
|
|
|
|
- [How to fix a bug in GHC](working-conventions/fixing-bugs)
|
|
- [How to fix a bug in GHC](working-conventions/fixing-bugs)
|
... | | ... | |