| Age | Commit message (Collapse) | Author | Lines |
|---|
|
Until now, we would immeditely jump from the part on answering the
project's questions to Git branches. But this isn't too useful for
someone who doesn't know Git! So to start the Git branching
discussion, now we first show a small image of the workflow with a
"today" printed over it. Then another one with a "tomorrow". In the
next slide we abstract them to circles with hashes!
|
|
The short version of the slides is now ready. There is a '\longformat'
macro that will significantly increase the number of slides, but not
substantially (they are just the incremental things).
Some minor modifications were also made in the long version.
|
|
A name was finally selected for Maneage, so the slides also needed to
be updated.
|
|
A verification step was recently added to the pipeline, so it was
necessary to add it here is well.
|
|
Since some of the audience is not yet fully familiar with Git, I
thought its necessary to remind them in the slide showing Git
branching, that every commit contains all aspects of the project.
|
|
Following the convention of the Make-demo plot (where green files are
input and blue files are built), the first graph's gray boxes were
also changed to blue.
Some other minor corrections were made.
|
|
To help the audience, the legend of the graph (the description at the
bottom of the page) now also says that the built files are shown in
the Makefiles that produces them.
|
|
As Raul pointed out, to avoid confusion for a color-blind audience, or
when its printed in black-and-white, its best to not just base the
source-build distinction in the graph based on color.
With this commit, the source files have sharp edges and the built
files have round edges.
|
|
Some minor modifications were made in the graph showing the
organization of the analysis with Make. Also, a `tex/preamble.tex' was
defined to simplify the main source.
|
|
With this copyright, a random viewer will know their rights regarding
these files (that they are free software and that they can modify them
and redistribute them).
|
|
Due to a typo (incorrect macro naming), the credits of the "verified"
stamp were not being shown in the slide. This has been corrected.
|
|
The fact that we only displayed the Git checksum before showing it in
the paper could be a little confusing to people not much familiar with
Git. So a commit checksum (taken randomly from the history of these
slides) was added to it.
Also, some minor changes were done here and there.
|
|
A sentence in the Git slides was slightly shortened to fit in the
width without breaking into two.
|
|
For EWASS, they recommended a 16:9 aspect ratio. This is becoming the
standard and after some tests, I saw felt that it does indeed show
better on modern monitors while also giving more horizontal space. The
slides are now changed to this aspect ratio and everything was
slightly modified to show nicely in it.
Also, an extra step was added to the Git demonstration steps to show
how progress on the project branch happens independently of progress
on the template.
|
|
After the previous experience of presenting the slides in Ghent, they
are reordered to be more clear and cause less confusion. In
particular, until this commit, I was describing the software build
steps in the end, so the audience mainly forgot about the analysis
steps and thought this template is just something like Docker or a
virtual machine.
With this commit, the steps are described in the same step that occur:
first how the software are built, then how the input data are
downloaded and finally how the software are run on the data and the
values are written into the paper.
|
|
A graph was added showing how Git branching and history are used to
verfiy the integrity of the result.
|
|
The slides were significantly upgraded to help in making a better
introduction and clearly demonstrating things for the users.
|
