Fixes #27 – updated top level README.md to include links to sub-projects. (#30)



* We don’t need zlib

* #27 top-level README now includes links to subprojects

As suggested by @mrutkows
diff --git a/README.md b/README.md
index e5f72a5..29d5feb 100644
--- a/README.md
+++ b/README.md
@@ -1,26 +1,15 @@
 Developer tools for OpenWhisk
 =============================
 
+This repository is part of [Apache OpenWhisk](http://openwhisk.org) and provides developer tools that help with local development, testing and operation of OpenWhisk.
 
-### Installing OpenWhisk
+## Subprojects
 
-* Using Docker-Compose. See the [README](docker-compose/README.md) for more details. 
- 
-  [![Build Status](https://travis-ci.org/openwhisk/openwhisk-devtools.svg?branch=master)](https://travis-ci.org/openwhisk/openwhisk-devtools)
-  
-  ```bash
-  cd docker-compose
-  make quick-start
-  ```
-  
-  This is useful for creating local development environments. 
-  The build downloads by default the latest code from the master branch, but it also allows developers to work with their local clones by providing the local path to the OpenWhisk repo:
-      
-  ```bash
-  PROJECT_HOME=/path/to/openwhisk make quick-start
-  ```    
+* [docker-compose](docker-compose/README.md) allows testing OpenWhisk locally, using Docker Compose. This is ideal if you are contributing to core development
+* [kubernetes](kubernetes/README.md) is a work in progress to allow local testing on a Kubernetes cluster.
+* [node-local](node-local/README.md) allows testing individual OpenWhisk functions locally, using only node.js. This is ideal if you are writing node.js functions to run in OpenWhisk, but need to emulate some of OpenWhisk's behavior in creating `params` and expecting promises.
 
-### Travis builds
+## Travis builds
 
 Each tool in this repository has to provide travis build scripts inside a `.travis` folder. 
 The folder should define 2 scripts: