diff options
| author | Thomas Schwinge <thomas@schwinge.name> | 2010-12-21 13:12:55 +0100 |
|---|---|---|
| committer | Thomas Schwinge <thomas@schwinge.name> | 2010-12-21 13:12:55 +0100 |
| commit | 8d2236f62fab87615dfd402ce1f3f261e5999a6d (patch) | |
| tree | cec199ab9f3bcab07e2d2eda829be9e9abb2bf8c | |
| parent | 69cb8fe70e84b0f20add39ba1d30a0742a8d7b38 (diff) | |
contributing: Small change.
| -rw-r--r-- | contributing.mdwn | 6 |
1 files changed, 4 insertions, 2 deletions
diff --git a/contributing.mdwn b/contributing.mdwn index 6ad4d709..01140927 100644 --- a/contributing.mdwn +++ b/contributing.mdwn @@ -120,7 +120,7 @@ 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 +few free minutes -- even less so without any previous [[kernel]] hacking experience. Likewise, the Linux kernel maintainers are stating the exactly same @@ -128,7 +128,9 @@ 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 +But of course, none of this is meant to be dismissive, or to scare you away -- +on the contrary: 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! +You'll *just* have to get excited about it! |