Fetching contributors…
Cannot retrieve contributors at this time
91 lines (68 sloc) 3.63 KB
= Issues is the best place to report bugs,
submit patches and/or obtain support after you have searched the
{email archives}[] and
* 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, it will be flagged as spam
* Anonymous and pseudonymous messages will always be welcome.
* The email submission port (587) is enabled on the MX:
If your issue is of a sensitive nature or you're just shy in public,
then feel free to email us privately at
instead and your issue will be handled discreetly.
If you don't get a response within a few days, we may have forgotten
about it so feel free to ask again.
== Bugs in related projects
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 and discuss+fix them on the ruby-core
list at
Subscription to post is required to ruby-core, unfortunately:
For uncommon bugs in Rack, we may forward bugs to and discuss there.
Subscription (without any web UI or Google account) is possible via:
Note: not everyone can use the proprietary bug tracker used by Rack,
but their mailing list remains operational.
Uncommon bugs we encounter in the Linux kernel should be Cc:-ed to the
Linux kernel mailing list (LKML) at
and subsystem maintainers such as
(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. There is a Bugzilla instance, but it is
ignored by most developers.
Likewise for any rare glibc bugs we might encounter, we should Cc:
Keep in mind glibc upstream does use Bugzilla for tracking bugs:
== Submitting Patches
See the HACKING document (and additionally, the
document distributed with git) on guidelines for patch submission.
== Contact Info
* public:
* private:
* nntp://
* nntp://
Mailing list subscription is optional, so Cc: all participants.
You can follow along via NNTP:
Or Atom feeds:
The HTML archives at
also has links to per-thread Atom feeds and downloadable
You may optionally subscribe via plain-text email:
(and confirming the auto-reply)