[petsc-dev] workflow diagram

[Satish Balay]

On Wed, 30 Apr 2014, Jed Brown wrote:

> Satish Balay <balay at mcs.anl.gov> writes:
> > Perhaps if there arrows were flipped the confusion could be reduced?
> 
> What do you mean by "flipped"?

instead of  (a) ---> (b)

use:        (a) <--- (b)

The arrow represend 'parent' relationship anyway

The confusion with forward facing arrows occurs when its interpreted
as 'data flow' or something that has 'time-factor' associated with it.

[so you had to do the squigly lines - which - I think are not
conveying the relationship properly]

Satish

> > [Somehow the commits should be accentuated to the timescale - and not the arrows]
> 
> Hmm, I think the arrows are equally important because they describe the
> reasoning and social issues around collaborative development.  The
> commits will be somewhere in almost any workflow, but the benefit of
> this one is in the arrows.  At least that's how I think about it, and
> I'm not a category theorist ("there are only arrows").
>