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

teh · 2017-02-07T11:43:38Z

No description provided.

hyperthunk

This is great, thank you @teh! We've been discussing moving some of this to readthedocs, so the fixes should help with that too (though I'm seeing some rendering issues, but I think these were present already).

hyperthunk · 2017-02-09T11:14:43Z

documentation.md

 *task layer*, but takes a very different approach to that described
 in the original paper and implemented by the [remote][remote] package. In particular,
 we diverge from the original design and defer to many of the principles
 defined by Erlang's [Open Telecom Platform][OTP], taking in some well established
 Haskell concurrency design patterns along the way.

-In fact, [distributed-process-platform][distributed-process-platform] does not really consider the
+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,


s/.Platform//

hyperthunk · 2017-02-09T11:15:23Z

documentation.md

@@ -427,14 +427,14 @@ domain was more *haskell-ish* than working with bare send and receive primitives
 The `Async` sub-package also provides a type safe interface for receiving data,
 although it is limited to running a computation and waiting for its result.

-The [Control.Distributed.Processes.Platform.ManagedProcess][d-p-platform-ManagedProcess] API provides a
+The [Control.Distributed.Processes.Platform.ManagedProcess][d-p-client-server-ManagedProcess] API provides a


s/.Platform//

hyperthunk · 2017-02-09T11:16:08Z

index.md

@@ -19,8 +18,6 @@ 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 <a class="pull-right" href="http://hackage.haskell.org/platform" ><img src="http://hackage.haskell.org/platform/icons/button-64.png"></a>


Why are we getting rid of this bit?

Ah sorry, only meant to remove the link to haskell-platform. The button image is no longer there and I couldn't find a good replacement.

Okay that's fine.

hyperthunk · 2017-02-09T11:18:14Z

team.md

@@ -27,7 +27,7 @@ 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-platform][8];
+[Tim][6] is the primary author and maintainer of [disributed-process][8];


Let's remove this part, firstly it's not true (I'm only one of several authors and committers, and distributed-process is now under @facundominguez's maintainership), secondly we're not listing all the libraries. I think we just s/[distributed-process][0],numerous libraries in (... an effort to...)/

thoughts...?

I think if we will add a paragraph about platform and core - it will be easy to write. Something like:

Most of the packages are maintained my the haskell-distributed organization(?) that with people from Well Typed, Tweag, and (other companies that are involved) and individuals (names).
Main maintaiters are @facundominguez maintains core packages, @hyperthunk maintains platform packages.

Some libraries are maintained my third parties, most notably d-p-p2p.

hyperthunk · 2017-02-09T11:19:04Z

tutorials/3ch.md

@@ -366,17 +366,17 @@ process. The `ProcessInfo` type it returns contains the local node id and a list
 registered names, monitors and links for the process. The call returns `Nothing` if the
 process in question is not alive.

-### Monad Transformer Stacks 
+### Monad Transformer Stacks


We should add an issue (if not fixing here) to point out the risks of this approach - @qnikst can you advise the right text to put in please?

Everything is ok, until you make an instance of BaseControl to Process monad. And this is 3rd party package, that I hope mentions possible problems

Not sure what this means, needs a separate doc update from you I think

Okay let's do that separately, I'll open an issue.

qnikst

Some minor comments.

qnikst · 2017-02-09T12:29:37Z

documentation.md

@@ -31,7 +31,7 @@ Cloud Haskell comprises the following components, some of which are complete,
 others experimental.



We need to put among the lines that Cloud Haskell consists of 2 (3) big parts:

Core package distributed-process itself. Using this package on it's own may be enough to write any
functionality. This package considered most stable.

Platform packages. Platform packages are built on the top of core packages and are intended to provide an implementation of patterns that are similar to OTP library (is it library?) in Erlang.

3 because we have also network-transport layer for communication between nodes (though this may be ommited).
Also there is d-p-simplelocalnet, and d-p-p2p that are not core, but neither platform.

done, PTAL.

qnikst · 2017-02-09T12:33:09Z

team.md

@@ -27,7 +27,7 @@ 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-platform][8];
+[Tim][6] is the primary author and maintainer of [disributed-process][8];


I think if we will add a paragraph about platform and core - it will be easy to write. Something like:

Most of the packages are maintained my the haskell-distributed organization(?) that with people from Well Typed, Tweag, and (other companies that are involved) and individuals (names).
Main maintaiters are @facundominguez maintains core packages, @hyperthunk maintains platform packages.

Some libraries are maintained my third parties, most notably d-p-p2p.

qnikst · 2017-02-09T12:34:40Z

tutorials/3ch.md

@@ -366,17 +366,17 @@ process. The `ProcessInfo` type it returns contains the local node id and a list
 registered names, monitors and links for the process. The call returns `Nothing` if the
 process in question is not alive.

-### Monad Transformer Stacks 
+### Monad Transformer Stacks


Everything is ok, until you make an instance of BaseControl to Process monad. And this is 3rd party package, that I hope mentions possible problems

hyperthunk

LGTM - @qnikst ?

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

ee48a7c

teh force-pushed the master branch from 0da3c08 to ee48a7c Compare February 9, 2017 10:54

teh added 2 commits February 9, 2017 11:03

Opinionated: Remove changelog completely. It's way out of date.

a5312ac

Update copyright dates to look alive

f8cfb6b

teh mentioned this pull request Feb 9, 2017

Remove changelog #30

Merged

hyperthunk reviewed Feb 9, 2017

View reviewed changes

Fix references to Async

7cb09e7

qnikst reviewed Feb 9, 2017

View reviewed changes

More feedback

73e060e

hyperthunk approved these changes Feb 10, 2017

View reviewed changes

qnikst approved these changes Feb 12, 2017

View reviewed changes

hyperthunk merged commit 7e9e682 into haskell-distributed:master Feb 13, 2017

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

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

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

teh commented Feb 7, 2017

hyperthunk left a comment

hyperthunk Feb 9, 2017

hyperthunk Feb 9, 2017

teh Feb 9, 2017

hyperthunk Feb 9, 2017

teh Feb 9, 2017

hyperthunk Feb 10, 2017

hyperthunk Feb 9, 2017

qnikst Feb 9, 2017

teh Feb 9, 2017

hyperthunk Feb 9, 2017

qnikst Feb 9, 2017

teh Feb 9, 2017

hyperthunk Feb 10, 2017

qnikst left a comment

qnikst Feb 9, 2017

teh Feb 9, 2017

qnikst Feb 9, 2017

qnikst Feb 9, 2017

hyperthunk left a comment

		@@ -31,7 +31,7 @@ Cloud Haskell comprises the following components, some of which are complete,
		others experimental.

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

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

Conversation

teh commented Feb 7, 2017

hyperthunk left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

qnikst left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

hyperthunk left a comment

Choose a reason for hiding this comment