Add a contribution and credit policy

Bedstead has actually had external contributions, so it seems reasonably
to set out how I handle them.

This was inspired by Valerie Aurora and by the contributions and credits
policy guide created by members of the RIPE Open Source Working Group.

diff --git a/CONTRIBUTING b/CONTRIBUTING
new file mode 100644 (file)
index 0000000..bf4ab72
--- /dev/null
+++ b/CONTRIBUTING
@@ -0,0 +1,43 @@
+Contributing to Bedstead
+========================
+
+While Bedstead is ultimately a personal project, I do sometimes accept
+contributions from others.  If have something to contribute, please
+send it by email to <bjh21@bjh21.me.uk>.  Reports of problems with
+Bedstead should go to the same address.  Adding the glyphs you need is
+particularly encouraged.
+
+I pay attention to Bedstead only sporadically, so you might not get a
+reply immediately.  However, if I make a new release without replying
+to you that's probably a sign that I've overlooked your contribution
+and you should remind me about it.
+
+Credit
+------
+
+The authors of code and glyphs in Bedstead are listed in a comment at
+the top of bedstead.c.  If you're sending a patch, you might like to
+include an update to this comment so that you get credited properly.
+If any of your contribution is based on others' work, please indicate
+that as well.  If I construct a Git commit from your contribution,
+I'll put your name and email address in the "Author" field.
+
+All contributions of code and glyphs should be released under the CC0
+Public Domain Dedication.  If you're sending a patch, adding your name
+to the comment beginning "To the maximum extent possible under the
+law" will indicate that you intend to release your contribution under
+that dedication.
+
+If you make a suggestion that isn't a direct code contribution, or
+report a bug, I will usually credit you by name in any corresponding
+Git commit message.
+
+If you do not wish to be credited, please mention that when sending
+any contribution.
+
+If you are credited in bedstead.c and wish to change how you're
+credited, please let me know.  I will generally be happy to update the
+credit to whatever name you prefer.  Similarly, updates to the Git
+".mailmap" file are welcome.  Git is very resistant to rewriting
+history, though, so I will generally not change the credits in
+published commits or releases.