intregrated comments in by Josh Boyer

1 files changed, 34 insertions, 0 deletions

diff --git a/HOWTO b/HOWTO
index 8c0a9ff555556..7c3d34079d5fa 100644
--- a/HOWTO
+++ b/HOWTO
@@ -240,6 +240,40 @@ Above all, please remember to show respect to other subscribers.
 Working with the community
 --------------------------
 
+The goal of the kernel community is to provide the best possible kernel
+there is.  When you submit a patch for acceptance, it will be reviewed
+on its technical merits and those alone.  So, what should you be
+expecting?
+  - criticism
+  - comments
+  - requests for change
+  - requests justification
+  - silence
+
+Remember, this is part of getting your patch into the kernel.  You have
+to be able to take criticism and comments about your patches, evaluate
+them at a technical level and either rework your patches or provide
+clear and concise reasoning as to why those changes should not be made.
+If there are no responses to your posting, wait a few days and try
+again, sometimes things get lost in the huge volume.
+
+What should you not do?
+  - expect your patch to be accepted without question
+  - become defensive
+  - ignore comments
+  - resubmit the patch without making any of the requested changes
+
+In a community that is looking for the best technical solution possible,
+there will always be differing opinions on how beneficial a patch is.
+You have to be cooperative, and willing to adapt your idea to fit within
+the kernel.  Or at least be willing to prove your idea is worth it.
+Remember, being wrong is acceptable as long as you are willing to work
+toward a solution that is right.
+
+
+Differences between the kernel community and corporate structures
+-----------------------------------------------------------------
+
 The kernel community works differently than most traditional corporate
 development environments.  Here are a list of things that you can try to
 do to try to avoid problems: