mirror of
https://bjh21.me.uk/bedstead/.git
synced 2026-07-09 05:23:06 -04:00
247ffb0a77
It's apparent that the idea that you should disclose the use of such tools is not as widespread as I'd thought, so I should make it explicit.
51 lines
2.2 KiB
Plaintext
51 lines
2.2 KiB
Plaintext
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.
|
|
|
|
If you've made significant use of an automated tool, such as a large
|
|
language model, static analyzer, or Emacs keyboard macro, in the
|
|
preparation of your contribution, please let me know. Similarly, let
|
|
me know if it's based on another person's work.
|
|
|
|
Credit
|
|
------
|
|
|
|
The authors of code and glyphs in Bedstead are listed in a comment at
|
|
the top of bedstead.c and in the HACKING file. If you're sending a
|
|
patch, you might like to include an update to these 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. If I do that, I'll put any parts of the commit
|
|
message that I write in square brackets.
|
|
|
|
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.
|