346 karma · joined February 23, 2013
* figure out if you can use git-request-pull or git-send-email * sign up for a mailing list (which, depending on the mailing list software the project uses, can take anywhere between a few seconds and annoyingly large amounts of minutes) * optionally figure out how to not receive the whole traffic of the ML or set up custom email filters * figure out if you have to CC the people responsible for the area of the code you're going to send a patch for (which might be written down in a wiki, some CONTRIBUTING file or somewhere else) * figure out if the project wants an extra cover letter for the patch series or not (and optionally search the man pages for how to write one).
With GitHub, I just use [hub](https://hub.github.com/) or an Emacs package or plugins for other editors to
* fork the repository * (without additional tools, I now have to add my newly created remote) * push to my own remote * create the pull request after reading CONTRIBUTING<tab>
which so far has been the exact same workflow for every project I've seen (ymmv of course).
http://fsharp.org/about/learning.html does not list them, and going from http://fsharp.org/about/index.html via the "Language Reference" link to https://msdn.microsoft.com/en-us/library/dd233181.aspx doesn't list RWFP in the sidebar anymore.
[0] https://chrome.google.com/webstore/detail/ipvfoo/ecanpcehffn... [1] https://addons.mozilla.org/de/firefox/addon/ipvfox/