Update FAQ (#8773)

Add a Q on the scope of our issue tracker, and remove a legacy Q.

1 files changed, 17 insertions, 10 deletions

diff --git a/docs/faq.rst b/docs/faq.rst
index 1bbf5eb4b..ac7f4152c 100644
--- a/docs/faq.rst
+++ b/docs/faq.rst
@@ -1,6 +1,22 @@
 Frequently asked questions
 ==========================
 
+What issues can you help with in your issue tracker?
+----------------------------------------------------
+
+The primary purpose of our issue tracker is to enable us to identify and
+resolve bugs and feature requests in ``cryptography``, so any time a user
+files a bug, we start by asking: Is this a ``cryptography`` bug, or is it a
+bug somewhere else?
+
+That said, we do our best to help users to debug issues that are in their code
+or environments. Please note, however, that there's a limit to our ability to
+assist users in resolving problems that are specific to their environments,
+particularly when we have no way to reproduce the issue.
+
+Lastly, we're not able to provide support for general Python or Python
+packaging issues.
+
 .. _faq-howto-handle-deprecation-warning:
 
 I cannot suppress the deprecation warning that ``cryptography`` emits on import
@@ -102,15 +118,6 @@ If you have no other libraries using OpenSSL in your process, or they do not
 appear to be at fault, it's possible that this is a bug in ``cryptography``.
 Please file an `issue`_ with instructions on how to reproduce it.
 
-error: ``-Werror=sign-conversion``: No option ``-Wsign-conversion`` during installation
----------------------------------------------------------------------------------------
-
-The compiler you are using is too old and not supported by ``cryptography``.
-Please upgrade to a more recent version. If you are running OpenBSD 6.1 or
-earlier the default compiler is extremely old. Use ``pkg_add`` to install a
-newer ``gcc`` and then install ``cryptography`` using
-``CC=/path/to/newer/gcc pip install cryptography``.
-
 Installing cryptography with OpenSSL 0.9.8, 1.0.0, 1.0.1, 1.0.2, 1.1.0 fails
 ----------------------------------------------------------------------------
 
@@ -154,7 +161,7 @@ Why can't I import my PEM file?
 -------------------------------
 
 PEM is a format (defined by several RFCs, but originally :rfc:`1421`) for
-encoding keys, certificates and others cryptographic data into a regular form.
+encoding keys, certificates, and others cryptographic data into a regular form.
 The data is encoded as base64 and wrapped with a header and footer.
 
 If you are having trouble importing PEM files, make sure your file fits