[Overview] Chapter 2

[bartvanb]

Desired solution

TODO:

• [ ] Powerpoint slides
• [ ] Missing image of PETOps cycle
• [x] Key points need to be added
• [x] Unique selling points of vantage6: All of the bullet points are not unique. The combination of them is.
• [x] Unique selling points of vantage6: I would rename this section to "Why choose vantage6?"
• [x] Unique selling points of vantage6: "vantage6 is unique as it provides":
• [x] "Contains algorithms stored in images which can" -> "Contains algorithms stored in container images which can" (images can be seen as pixels by this part of the audience)
• [x] The vantage6 infrastructure: Mention the relationship between Algorithm store and Docker registry
• [x] The vantage6 infrastructure: "For more details see the technical documentation of the node." -> insert the link to the documentation
• [x] The vantage6 infrastructure: Mention that the node processes tasks in parallel
• [x] "central server" - > vantage6 server. We are trying to move away from that term because it adds to the confusion of the central part of the algorithm.
• [x] Mention encryption (see this comment)

Discuss:

• [x] How algorithms run in vantage6: Great exercise :) Can we do the example without equations? Or at leas help them a little bit more in case they are not familiar with the notation?
• [x] After reviewing the entire workshop material, I believe this chapter should begin with a description of the key v6-specific concepts. As it is now, there are multiple technical discussions that make reference to such concepts, and without this introduction, these lack context. For instance, most sections in this chapter refer to stuff that is related to collaborations or studies (concepts with a very specific interpretation in the context of v6), but at this point, participants don't know what those actually are. Maybe the high-level concept map and concept descriptions given in Chapter 3 should be moved here?
• [ ] Add future changes to chapters

[dsmits]

Some more feedback for chapter 2: #67

[wbaccinelli]

After reviewing the entire workshop material, I believe this chapter should begin with a description of the key v6-specific concepts. As it is now, there are multiple technical discussions that make reference to such concepts, and without this introduction, these lack context. For instance, most sections in this chapter refer to stuff that is related to collaborations or studies (concepts with a very specific interpretation in the context of v6), but at this point, participants don't know what those actually are. Maybe the high-level concept map and concept descriptions given in Chapter 3 should be moved here?

@bartvanb I think you're right. Looking at it now, I also think that the ""v6 administration" concepts might conceptually be part of the v6 basics in any case. @hcadavid how do you see moving the introduction of these concepts here in chapter 2 from chapter 3?

[wbaccinelli]

Add future changes to chapters

I don't remember exactly what we decided to do with the future developments section. @frankcorneliusmartin did we decide to remove it?

[hcadavid]

Hi @wbaccinelli, it makes sense to me (actually the comment you quoted was mine :)). I just pushed a PR of chapter 3 with a more 'user friendly' introduction to these concepts.

[bartvanb]

I don't remember exactly what we decided to do with the future developments section. @frankcorneliusmartin did we decide to remove it?

Frank is now on holiday but I think I talked with him about this and we assumed it was staying here

[wbaccinelli]

I don't remember exactly what we decided to do with the future developments section. @frankcorneliusmartin did we decide to remove it?

Frank is now on holiday but I think I talked with him about this and we assumed it was staying here

Alright, than I propose move these sections like this:

• Policies -> chapter 6
• Model repository -> chapter 6 or 7
• Build services -> chapter 7

What do you think @bartvanb?

[wbaccinelli]

Missing image of PETOps cycle

This is also for @frankcorneliusmartin (after the holiday).