email@example.com is the best place to report bugs, submit patches and/or obtain support after you have searched the email archives and documentation.
No subscription will ever be required to email us
Cc: all participants in a thread or commit, as subscription is optional
Do not top post in replies
Quote as little as possible of the message you're replying to
Do not send HTML mail or images, they hurt reader privacy and will be flagged as spam
Anonymous and pseudonymous messages will ALWAYS be welcome
The email submission port (587) is enabled on the bogomips.org MX: bogomips.org/unicorn-public/20141004232241.GA23908@dcvr.yhbt.net/t/
We will never have a centralized or formal bug tracker. Instead we can interoperate with any bug tracker which can Cc: us plain-text to firstname.lastname@example.org This includes the Debian BTS at bugs.debian.org/unicorn and possibly others.
If your issue is of a sensitive nature or you're just shy in public, use anonymity tools such as Tor or Mixmaster; and rely on the public mail archives for responses. Be sure to scrub sensitive log messages and such.
If you don't get a response within a few days, we may have forgotten about it so feel free to ask again.
unicorn is sometimes affected by bugs in its dependencies. Bugs triggered by unicorn in mainline Ruby, rack, GNU C library (glibc), or the Linux kernel will be reported upstream and fixed.
For bugs in Ruby itself, we may forward bugs to bugs.ruby-lang.org/ and discuss+fix them on the ruby-core list at email@example.com Subscription to post is required to ruby-core, unfortunately: firstname.lastname@example.org?subject=subscribe Unofficial archives are available at: public-inbox.org/ruby-core/
For uncommon bugs in Rack, we may forward bugs to email@example.com and discuss there. Subscription (without any web UI or Google account) is possible via: firstname.lastname@example.org Note: not everyone can use the proprietary bug tracker used by Rack, but their mailing list remains operational. Unofficial archives are available at: public-inbox.org/rack-devel/
Uncommon bugs we encounter in the Linux kernel should be Cc:-ed to the Linux kernel mailing list (LKML) at email@example.com and subsystem maintainers such as firstname.lastname@example.org (for networking issues). It is expected practice to Cc: anybody involved with any problematic commits (including those in the Signed-off-by: and other trailer lines). No subscription is necessary, and the our mailing list follows the same conventions as LKML for interopability. Archives are available at lore.kernel.org/lkml/ There is a kernel.org Bugzilla instance, but it is ignored by most.
Likewise for any rare glibc bugs we might encounter, we should Cc: email@example.com Unofficial archives are available at: public-inbox.org/libc-alpha/ Keep in mind glibc upstream does use Bugzilla for tracking bugs: sourceware.org/bugzilla/
See the HACKING document (and additionally, the SubmittingPatches document distributed with git) on guidelines for patch submission.
Mailing list subscription is optional, so Cc: all participants.
You can follow along via NNTP (read-only):
Or Atom feeds:
https://bogomips.org/unicorn-public/new.atom http://ou63pmih66umazou.onion/unicorn-public/new.atom The HTML archives at https://bogomips.org/unicorn-public/ also has links to per-thread Atom feeds and downloadable mboxes.
mail archives: https://bogomips.org/unicorn-public/ nntp://news.public-inbox.org/inbox.comp.lang.ruby.unicorn nntp://news.gmane.org/gmane.comp.lang.ruby.unicorn.general public: firstname.lastname@example.org source code: git clone https://bogomips.org/unicorn.git