#41 Please read this before opening up a new issue

[Anonymous]

Originally created by: samboy

Please read this ticket before opening up a new issue:

• All bug reports and comments need to comply with the code of conduct detailed in CODE_OF_CONDUCT.md. This is the same code of conduct used for Linux kernel development.
• Feature requests will be ignored. There are a lot of excellent other open-source DNS servers around today which were not around when I started MaraDNS in 2001: NSD, Unbound, and KnotDNS come to mind.
• MaraDNS is not bug-for-bug identical to BIND when resolving poorly configured domains; “This obscure domain does not resolve” bugs will probably be closed as WONTFIX. See https://github.com/samboy/MaraDNS/issues/31 https://github.com/samboy/MaraDNS/issues/26 https://github.com/samboy/MaraDNS/issues/8 https://github.com/samboy/MaraDNS/issues/54
• Asking for anything specified in an RFC that came out after 2010 is a feature request; MaraDNS was frozen in 2010.
• Distribution specific issues should not be filed here. Please contact the support team for the Linux distribution you are using if using a package from that distribution to install MaraDNS.
• Support requests will probably be ignored or closed NOTABUG.
• Compiler warnings will probably not be fixed. GCC Compiler errors will probably be fixed. Clang compiler errors might be fixed. TCC and MSVC compiler errors will probably not be fixed. Yes, I made a point, back in the 2000s and early 2010s, to have MaraDNS and Deadwood compile with no warnings when -Wall is set, but compilers change and what used to be perfectly good code can now generate warnings or errors. Keep in mind that Clang did not exist when I developed MaraDNS, and was not a mainstream compiler able to compile the Linux kernel when I developed Deadwood. The code is more likely to compile without warning using GCC.)
• Legitimate bug reports may be handled.
• Closed bug reports get locked seven days (or more) after the bug is closed. If an old bug was not properly closed, open up a new bug.
• Security bug reports will probably be handled. If the issue is one that you wish to keep confidential, please open up a ticket here in Github; make sure your Github profile has contact information or include contact information in the bug report. But really, you won’t find that kind of security bug in MaraDNS: MaraDNS has been around for nearly two decades and no one has ever found a bug in it which should have been kept confidential before I patched it (see http://maradns.samiam.org/security.html )
• Spam disguised as a MaraDNS issue will be deleted. If the ticket does not mention MaraDNS, I will assume the ticket is robot-generated spam, and will both delete and report the ticket.

I want to be inclusive, but I also have limited time to devote to MaraDNS.

[Anonymous]

Originally posted by: samboy

I strive to be inclusive, but I also have a lot on my plate right now.