FAQ.adoc: Add 'Submission' section to the FAQ

There have been some questions about rejecting changes to the kernel.
Let's add a section that provides a _simple_ explanation of why we might
reject a community requested change.

For future readers (and as stated in the commit text):  We do not like
to reject contributions.  We consider any rejections to be a loss for
the overall community behind Centos Stream and RHEL, but unfortunately,
we are also resource constrained.

Signed-off-by: Prarit Bhargava <prarit@redhat.com>

Author: prarit

content/docs/FAQ.adoc

@@ -13,6 +13,20 @@ The most common questions related to contributing to Red Hat-based kernel projec
 
 {{< toc >}}
 
+== Submission Related Questions
+
+=== I submitted an MR but it was rejected for 'non-technical' issues.  Why did that happen and what does it mean?
+
+CentOS Stream, and by extension Red Hat, welcome all community requests and contributions to the CentOS Stream kernel.  Red Hat applies Development, QE, Documentation, and other resources to every change made to the CentOS Stream kernel to ensure the CentOS Stream and RHEL kernels are secure, highly available, and meet Red Hat's users’ requirements.  The maintainers may reject a change because they are aware of a lack of resources available to provide support for the change.  For example, a community user or SIG may request that a particular driver be enabled and Red Hat may not have access to hardware associated with the driver.  In this case, CentOS Stream and Red Hat cannot provide any guarantee on functionality to users, and as such the request would be rejected.  Please take a moment to understand: We do not like to reject contributions and consider any rejections to be a loss for the overall community behind CentOS Stream and RHEL, but unfortunately, we are also resource constrained.
+
+=== I can support the hardware or software that was rejected for 'non-technical' issues.  Isn't that enough?
+
+Unfortunately, no.  While we appreciate your enthusiasm and help, Red Hat has support requirements it must meet and a lack of ability to reproduce a problem will cause a delay in support for users and customers.
+
+=== Are there any other options to getting my changes into the Centos Stream kernel?
+
+Yes!  You can consider forming a Centos Stream SIG for your changes, or joining a similarly aligned existing SIG.
+
 == Formatting Related Questions
 :sectnums:
 === anchor:badformatting[] The formatting is bad, how do I fix it?