Merge pull request #29 from teh/master

Replace a few references to platform to the now more specific projects.

Author: hyperthunk

Diff for: documentation.md

@@ -28,12 +28,25 @@ on Cloud Haskell and this reimplementation, which is worth reading in conjunctio
 with the documentation and wiki pages on this website..
 
 Cloud Haskell comprises the following components, some of which are complete,
-others experimental.
+others experimental. There are three main parts:
 
-* [distributed-process][distributed-process]: Base concurrency and distribution support
-* [distributed-process-client-server][distributed-process-client-server]: Common client/server patterns like Erlang's `gen_server`
+#### The core libraries
+
+* [distributed-process][distributed-process]: Base concurrency and distribution support. It provides a number of primitives known from Erlang like `link` and `monitor`.
 * [distributed-static][distributed-static]: Support for static values
 * [rank1dynamic][rank1dynamic]: Like `Data.Dynamic` and `Data.Typeable` but supporting polymorphic values
+
+#### The platform libraries
+
+* [distributed-process-client-server][distributed-process-client-server]: Common client/server patterns like Erlang's `gen_server`
+* [distributed-process-async][distributed-process-async]: Future-style computations
+* [distributed-process-task][distributed-process-task]: A worker queue
+* [distributed-process-extras][distributed-process-extras]: Monitoring, logging, resolving names etc.
+* [distributed-process-registry][distributed-process-registry]: A key-value registry
+* [distributed-process-execution][distributed-process-execution]: Load regulation, work shedding, hand-off etc.
+
+#### The network layer
+
 * [network-transport][network-transport]: Generic `Network.Transport` API
 * [network-transport-tcp][network-transport-tcp]: TCP realisation of `Network.Transport`
 * [network-transport-inmemory][network-transport-inmemory]: In-memory realisation of `Network.Transport` (incomplete)
@@ -328,7 +341,7 @@ Haskell concurrency design patterns along the way.
 
 In fact, [distributed-process-async][distributed-process-async] does not really consider the
 *task layer* in great detail. We provide an API comparable to remote's
-`Promise` in `Control.Distributed.Process.Platform.Async`. This API however,
+`Promise` in `Control.Distributed.Process.Async`. This API however,
 is derived from Simon Marlow's [Control.Concurrent.Async][async] package, and is not
 limited to blocking queries on `Async` handles in the same way. Instead our
 [API][d-p-async-async] handles both blocking and non-blocking queries, polling
@@ -502,6 +515,10 @@ TBC
 [distributed-process]: https://github.com/haskell-distributed/distributed-process
 [distributed-process-client-server]: https://github.com/haskell-distributed/distributed-process-client-server
 [distributed-process-async]: https://github.com/haskell-distributed/distributed-process-async
+[distributed-process-execution]: https://github.com/haskell-distributed/distributed-process-execution
+[distributed-process-extras]: https://github.com/haskell-distributed/distributed-process-extras
+[distributed-process-task]: https://github.com/haskell-distributed/distributed-process-task
+[distributed-process-registry]: https://github.com/haskell-distributed/distributed-process-registry
 [distributed-static]: http://hackage.haskell.org/package/distributed-static
 [rank1dynamic]: http://hackage.haskell.org/package/rank1dynamic
 [network-transport]: http://hackage.haskell.org/package/network-transport

Diff for: index.md

@@ -18,6 +18,8 @@ Documentation is available on this site for HEAD, or
 [hackage](http://hackage.haskell.org/package/distributed-process) for the current and preceding versions of
 each library.
 
+### <a href="/rss.xml"><img src="/img/feed-icon-28x28.png"></a> Recent Activity
+
 <div class="content">
   <div class="related">
     <ul>

Diff for: team.md

@@ -27,9 +27,15 @@ of Cloud Haskell as a whole. [Edsko De Vries][13], a member of Well-Typed and th
 author of much of the new implementation we have today, is still closely involved
 as well.
 
-[Tim][6] is the primary author and maintainer of [disributed-process][8];
-an effort to port many of the benefits of Erlang's [Open Telecom Platform][10] to
-the Cloud Haskell ecosystem.
+Most of the packages are maintained by the haskell-distributed
+organization, with people from Well Typed, Tweag, and other companies
+that are involved.
+
+The core [disributed-process][8] library is maintained by
+[Facundo Domínguez][14], and the platform libaries are maintained by
+[Tim Watson][6].
+
+Some libraries are maintained my third parties, most notably d-p-p2p.
 
 [Jeff][7] is the author of [distributed-process-global][11], a re-implementation of
 Erlang's [global][12] (locking, registration and cluster management) API for
@@ -54,3 +60,4 @@ Duncan Coutts, Simon Marlow, Ryan Newton, Eric Kow, Adam Foltzer, Nicolas Wu
 [11]: https://github.com/jepst/distributed-process-global
 [12]: http://www.erlang.org/doc/man/global.html
 [13]: https://github.com/edsko
+[14]: https://github.com/facundominguez

Diff for: tutorials/4ch.md

@@ -342,7 +342,7 @@ data BlockingQueue a = BlockingQueue
 ### Making use of Async
 
 So **how** can we execute this `Closure (Process a)` without blocking the server
-process itself? We can use the `Control.Distributed.Process.Platform.Async` API
+process itself? We can use the `Control.Distributed.Process.Async` API
 to execute each task asynchronously and provide a means for waiting on the result.
 
 In order to use an `Async` handle to get the result of the computation once it's