1 files changed, 23 insertions, 2 deletions

diff --git a/contributing.mdwn b/contributing.mdwn
index 3a713520..5d68f4ce 100644
--- a/contributing.mdwn
+++ b/contributing.mdwn
@@ -6,8 +6,8 @@ id="license" text="Permission is granted to copy, distribute and/or modify this
 document under the terms of the GNU Free Documentation License, Version 1.2 or
 any later version published by the Free Software Foundation; with no Invariant
 Sections, no Front-Cover Texts, and no Back-Cover Texts.  A copy of the license
-is included in the section entitled
-[[GNU Free Documentation License|/fdl]]."]]"""]]
+is included in the section entitled [[GNU Free Documentation
+License|/fdl]]."]]"""]]
 
 So, you are interested in contributing to the GNU Hurd project?
 
@@ -110,3 +110,24 @@ documentation pointers given in the previous section.  Also read through the
 
 Please send email to the [[mailing lists/l4-hurd]] mailing list for discussing
 this post-Mach system design.
+
+
+# Final Words -- Difficulties
+
+Please note that doing substantial contributions to a project as big and as
+encompassing as the GNU Hurd is not a trivial task.  For working on the GNU
+Hurd's inner guts and getting useful work done, you have to plan for a
+many-months learning experience which will need sufficient self-motivation.
+Working on an advanced operating system kernel isn't something you can do in a
+few free minutes -- even less so without any previous kernel hacking
+experience.
+
+Likewise, the Linux kernel maintainers are stating the exactly same
+difficulties, which is well presented by Jonathan Corbet in his 2010 Linux
+Kernel Summit report for the opening sessions about [*welcoming of
+newcomers*](http://lwn.net/Articles/412639/).
+
+But of course, none of this is meant to be dismissive, so just [[start
+using|hurd/running]] the GNU Hurd, and either notice yourself what's not
+working as expected, or have a look at one of the [[Open Issues]], and we shall
+see if you'll evolve to be the next core Hurd hacker!