Clarify the notion of steps

[Lukas Pühringer]

We have to clarify what the supply chain graph should look like and which steps are actually layout-worthy. Here are some question that arose during user testing:

• is cd <dir> a supply chain step?
• if cd <dir> is a step, then it should be a “non-modifying step”?
• if cd <dir> is a "non-modifying step" then it appears as a parallel activity in the D3 graph, which is really confusing
• can I concatenate commands (steps) with ; or &&
• if steps are all commands, can I add comments?
• how do I represent the step “look at Travis icon on GitHub” ?

[Lukas Pühringer]

We should probably re-think the extent of customizability on the first couple of pages (vcs, building, qa, packaging).

Currently a user:

1. chooses from a set of popular tools in the option grid (custom command is one of the choices), then
2. customizes the tool command inside the option grid (the form expands on click), then
3. either clicks "add and continue on next page" or "add and continue on this page", (which btw. was very confusing for our beta testers), then
4. in case the user stays, the steps can be further customized and re-ordered in the workflow section below the option grid, and
5. eventually the user can refine or completely change all the previously entered information on the software supply chain page

Maybe we should limit the user-interaction on those first pages to choosing from popular tools, or specifying that a custom command is used and only provide a customization UI on the software supply chain page?

[Justin Cappos]

What would happen if we just asked the user to run a command (to start a shell we capture things from) and then commit, build, test, package, etc. their software? Would this be easier?

…

On Wed, Sep 13, 2017 at 12:56 PM, lukpueh ***@***.***> wrote: We should probably re-think the extent of customizability on the first couple of pages (*vcs, building, qa, packaging*). Currently a user: 1. chooses from a set of popular tools in the option grid (*custom command* is one of the choices), then 2. customizes the tool command inside the option grid (the form expands on click), then 3. either clicks "*add and continue on next page*" or *"add and continue on this page"*, (which btw. was very confusing for our beta testers), then 4. in case the user stays, the steps can be further customized and re-ordered in the *workflow* section below the option grid, and 5. eventually the user can refine or completely change all the previously entered information on the *software supply chain* page Maybe we should limit the user-interaction on those first pages to choosing from popular tools, or specifying that a custom command is used and only provide a customization UI on the *software supply chain* page? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#25 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AA0XD6vK5SkM167gnzHi4M_0eA9XfYEGks5siAk5gaJpZM4PWYvc> .

[Lukas Pühringer]

Do you mean instead of the web wizard? Or as part of it?

[Lukas Pühringer]

It was noted by to different users that the Custom Command button was not clearly recognizable as an alternative choice to the suggested tools (e.g. #14 (comment)). We should fix this.