|
| 1 | +## How to contribute to F# |
| 2 | + |
| 3 | +See [contributing guide][fsharp-contributing-guide] for more info |
| 4 | + |
| 5 | +### First, check if this is the right repository |
| 6 | + |
| 7 | +The https://github.com/fsharp/fsharp repository is for cross platform packaging only. |
| 8 | +The development of the compiler and core library is at [Microsoft/visualfsharp][Microsoft/visualfsharp]. |
| 9 | + |
| 10 | +* **Is this a language suggestion?** Use the [F# Language User Voice](http://fslang.uservoice.com) |
| 11 | + |
| 12 | +* **Is the issue specific to F# on Mono/OSX/Linux?** This might be the right repository. |
| 13 | + |
| 14 | +* **Is the issue a bug in Mono?** Please report to [Mono Bugzilla](https://bugzilla.xamarin.com/) |
| 15 | + |
| 16 | +* **Is the issue specific to F# on Windows or Visual Studio?** Use the [Microsoft/visualfsharp][Microsoft/visualfsharp] repository |
| 17 | + |
| 18 | +* **Is the issue a general bug in the F# compiler/core library?** Use the [Microsoft/visualfsharp][Microsoft/visualfsharp] repository |
| 19 | + |
| 20 | +#### **Did you find a bug?** |
| 21 | + |
| 22 | +* **Ensure the bug was not already reported** by searching on GitHub under [Issues](https://github.com/fsharp/fsharp/issues) and in the [Microsoft/visualfsharp Issues](https://github.com/Microsoft/visualfsharp/issues). |
| 23 | + |
| 24 | +* If you're unable to find an open issue addressing the problem, [open a new one](https://github.com/fsharp/fsharp/issues/new). Be sure to include a **title and clear description**, as much relevant information as possible, and a **code sample** or an **executable test case** demonstrating the expected behavior that is not occurring. |
| 25 | + |
| 26 | +* For more detailed information on submitting a bug report and creating an issue, visit our [contributing guide][fsharp-contributing-guide]. |
| 27 | + |
| 28 | +#### **Did you write a patch that fixes a bug?** |
| 29 | + |
| 30 | +* Open a new GitHub pull request with the patch |
| 31 | + |
| 32 | +* Ensure the PR description clearly describes the problem and solution. Include the relevant issue number if applicable. |
| 33 | + |
| 34 | +#### **Do you intend to add a new feature or change an existing one?** |
| 35 | + |
| 36 | +* Is the issue about the future evolution of the F# Language or Core Library? Suggest your change in the [F# Language Design User Voice site](https://fslang.uservoice.com/forums/245727-f-language). |
| 37 | + After a feature/change is "approved-in-principle", it's discussed in the [F# language design repository](https://github.com/fsharp/FSharpLangDesign/issues) |
| 38 | + and implemented as Github pull request in the [Microsoft/visualfsharp][Microsoft/visualfsharp] repository |
| 39 | + |
| 40 | +* Otherwise, open a Github pull request |
| 41 | + |
| 42 | +#### **Do you have questions about the source code?** |
| 43 | + |
| 44 | +* Ask any question about how to use F# in the [F# mailing list](https://groups.google.com/forum/m/#!forum/fsharp-opensource) or on stackoverflow. |
| 45 | + |
| 46 | +* Check the Contribute section in the [fsharp.org site](http://fsharp.org/) for more info |
| 47 | + |
| 48 | +</br> |
| 49 | + |
| 50 | +Thanks! |
| 51 | + |
| 52 | +The [F# Core Engineering Group][fsg] (a technical working group of [The F# Software Foundation][fsf]) |
| 53 | + |
| 54 | + [fsg]: http://fsharp.github.io/ |
| 55 | + [fsf]: http://fsharp.org |
| 56 | + [Microsoft/visualfsharp]: https://github.com/Microsoft/visualfsharp |
| 57 | + [fsharp-contributing-guide]: http://fsharp.github.io/2014/06/18/fsharp-contributions.html |
| 58 | + |
0 commit comments