Changes in README.md [1a4ec93f:de38873] in mainline

File:

• README.md (modified) (4 diffs)

README.md

@@ -10 +10 @@
 extensible, fault tolerant and easy to understand.
 
-![screenshot](http://www.helenos.org/raw-attachment/wiki/Screenshots/screenshot.png "Screenshot")
+![screenshot](http://www.helenos.org/raw-attachment/wiki/Screenshots/newgui-aio.png "Screenshot")
 
 HelenOS aims to be compatible with the C11 and C++14 standards, but does not
@@ -35 +35 @@
 
 In order to build HelenOS, one must first build the cross-compiler toolchain
-(either as a root or by specifying the `CROSS_PREFIX` environment variable)
-by running (example for the amd64 architecture, further list of targets can be
-found in the `default` directory):
+(the default installation location can be overridden by specifying the
+`CROSS_PREFIX` environment variable) by running (example for the amd64
+architecture, further list of targets can be found in the `default` directory):
 
 ```
@@ -61 +61 @@
 ```
 # sudo dnf group install 'Development Tools'
-# sudo dnf install wget texinfo libmpc-devel mpfr-devel gmp-devel PyYAML genisoimage flex bison
+# sudo dnf install wget texinfo PyYAML genisoimage flex bison
 ```
+
 In case the toolchain script won't work no matter how hard you try, let us know.
 Please supply as many relevant information (your OS and distribution, list of
@@ -129 +130 @@
 see the files in tools/conf.
 
+## Contributing
+
+There is a whole section of our wiki devoted to
+[how to contribute to HelenOS](http://www.helenos.org/wiki/HowToContribute).
+But to highlight the most important points, you should subscribe to
+our mailing list and if you have an idea for contributing, discuss it
+with us first so that we can agree upon the design.
+
+Especially if you are a first time contributor, blindingly shooting
+a pull request may result in it being closed on the grounds that it
+does not fit well within the grand scheme of things. That would not
+be efficient use of time.
+
+Communicating early and often is the key to successful acceptance of
+your patch/PR.
+
 ## License