~petersanchez/wikimain

c88721d6f5b3f382be3fb6eb87ee9349ff7c911d — Peter Sanchez 11 months ago 1cba48c
Simple updates for contributing doc
1 files changed, 12 insertions(+), 3 deletions(-)

M contributing.md
M contributing.md => contributing.md +12 -3
@@ 11,12 11,15 @@ source projects. This may feel odd if you're used to the fork, clone, work,
submit pull request cycle but we think once you get the hang of it, you'll see
that this is a very fast way to contribute with very little blockers.

If it's good enough for the massive [Linux kernel][linux], [Git][], and
[Mercurial][hg] projects then it's good enough for us and our tiny ones.
If it's good enough for the massive [Linux kernel][linux], [Git][],
[Mercurial][hg], [PostgreSQL][pgsql], and [OpenBSD][obsd]  projects then it's
good enough for us and our tiny ones.

[linux]: https://www.kernel.org/doc/html/latest/process/submitting-patches.html
[git]: https://git-scm.com/docs/SubmittingPatches
[hg]: https://www.mercurial-scm.org/wiki/ContributingChanges
[pgsql]: https://wiki.postgresql.org/wiki/Submitting_a_Patch
[obsd]: https://www.openbsd.org/faq/faq5.html#Diff

## Before you contribute



@@ 233,11 236,17 @@ post discussing the differences. See that here:

https://begriffs.com/posts/2018-06-05-mailing-list-vs-github.html

Also Martijn Braam recently wrote a nice post about how he much prefers the
Martijn Braam recently wrote a nice post about how he much prefers the
email workflow since switching about a year ago:

https://blog.brixit.nl/git-email-flow-versus-github-flow/

Also, Vincent Lee recently wrote an article titled "What's Wrong With GitHub
Workflow?" that also goes into detail about the various issues with the typical
"Github style" workflow.

https://www.vincent-lee.net/blog/2022-02-28-github/

While it may seem like the whole world follows the GitHub workflow, we'd wager
that far more open source contributions happen via email than pull requests
every day.