Skip to content

Summit : agenda update for summit 2024 #68

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Aug 13, 2024
Merged

Summit : agenda update for summit 2024 #68

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
144 changes: 93 additions & 51 deletions summit.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -129,69 +129,69 @@ <h2>Day 1 (Wednesday, September 4)</h2>
<td>10:30</td>
</tr>

<tr><td><i>Lunch</i></td><td></td><td>11:30</td></tr>

<tr>
<td>
<details>
<summary>Eiffel at Volvo</summary>
<summary>Signing of Eiffel events : Intro</summary>
<div>
<ul>
<li>Eiffel traceability enabler (VSF Product
Metrics)</li>
<li>Eiffel for triggering (VSF CI)</li>
<li>Eiffel as a bridge between companies (Volvo IT)</li>
</ul>
<p>
<b>Speakers:</b> TBD
Presentation of how you can use Eiffel event
signing to uphold the integrity of events and
authenticate their sender.
</p>
<p>
<b>Speakers:</b> Magnus Bäck
</p>
</div>
</details>
</td>
<td><span class="tag bd-success">Beginner</span></td>
<td>12:30</td>
<td>11:30</td>
</tr>

<tr><td><i>Break</i></td><td></td><td>14:00</td></tr>

<tr>
<td>
<details>
<summary>Signing of Eiffel events</summary>
<summary>Effective collaboration strategies among diverse groups</summary>
<div>
<p>
Presentation of how you can use Eiffel event
signing to uphold the integrity of events and
authenticate their sender.
Details TBD.
</p>
<p>
<b>Speakers:</b> Magnus Bäck
<b>Moderator:</b> TBD
</p>
</div>
</details>
</td>
<td><span class="tag bd-success">Beginner</span></td>
<td>14:30</td>
<td>12:00</td>
</tr>

<tr><td><i>Lunch</i></td><td></td><td>12:30</td></tr>

<tr>
<td>
<details>
<summary>Effective collaboration strategies among diverse groups</summary>
<summary>Eiffel at Volvo</summary>
<div>
<ul>
<li>Eiffel traceability enabler (VSF Product
Metrics)</li>
<li>Eiffel for triggering (VSF CI)</li>
<li>Eiffel as a bridge between companies (Volvo IT)</li>
</ul>
<p>
Workshop, details TBD.
</p>
<p>
<b>Moderator:</b> TBD
<b>Speakers:</b> TBD
</p>
</div>
</details>
</td>
<td><span class="tag bd-success">Beginner</span></td>
<td>15:00</td>
<td>13:30</td>
</tr>

<tr><td><i>Break</i></td><td></td><td>15:00</td></tr>

<tr>
<td>
<details>
Expand Down Expand Up @@ -311,7 +311,7 @@ <h2>Day 2 (Thursday, September 5)</h2>
<tr>
<td>
<details>
<summary>Event signing deep dive</summary>
<summary>Signing of Eiffel Events : Deep Dive</summary>
<div>
<p>
A continuation of the event signing session from
Expand All @@ -330,84 +330,126 @@ <h2>Day 2 (Thursday, September 5)</h2>
<tr>
<td>
<details>
<summary>Q&amp;A</summary>
<summary>
Alternative approaches to modeling Git submodules
</summary>
<div>
<p>
Bring your own questions or ideas to this open
session where you get a chance to stump the
experts or get feedback.
In what ways can Git submodules be modeled with
Eiffel?
</p>
<p>
<b>Moderator:</b> TBD
<b>Speaker:</b> TBD (Volvo)
</p>
</div>
</details>
</td>
<td><span class="tag bd-success" style="border: 1px solid blue !important;">Intermediate</span></td>
<td><span class="tag bd-error">Advanced</span></td>
<td>11:00</td>
</tr>

<tr><td><i>Lunch</i></td><td></td><td>11:30</td></tr>
<tr>
<td>
<details>
<summary>
Filtering Eiffel : Discussion
</summary>
<div>
<p>
When it is a lot of eiffel messages, how to make it possible to only listen to some?
</p>
<p>
<b>Speaker:</b> TBD
</p>
</div>
</details>
</td>
<td><span class="tag bd-error">Advanced</span></td>
<td>11:30</td>
</tr>

<tr>
<td>
<details>
<summary>
Using Eiffel to communicate with third-party
suppliers
Scaling Eiffel infrastructure
</summary>
<div>
<p>
How can third-party suppliers use Eiffel to
deliver code and binaries, and how can they be
given feedback on those deliveries?
When the load gets higher, how to scale?
</p>
<p>
<b>Speaker/moderator:</b> TBD (Volvo)
<b>Speaker:</b> TBD
</p>
</div>
</details>
</td>
<td><span class="tag bd-success" style="border: 1px solid blue !important;">Intermediate</span></td>
<td>12:30</td>
<td><span class="tag bd-error">Advanced</span></td>
<td>12:00</td>
</tr>

<tr><td><i>Break</i></td><td></td><td>14:00</td></tr>
<tr><td><i>Lunch</i></td><td></td><td>12:30</td></tr>

<tr>
<td>
<details>
<summary>Q&amp;A</summary>
<div>
<p>
Bring your own questions or ideas to this open
session where you get a chance to stump the
experts or get feedback.
</p>
<p>
<b>Moderator:</b> TBD
</p>
</div>
</details>
</td>
<td><span class="tag bd-success" style="border: 1px solid blue !important;">Intermediate</span></td>
<td>13:30</td>
</tr>

<tr>
<td>
<details>
<summary>
Alternative approaches to modeling Git submodules
Reserved place for more topics
</summary>
<div>
<p>
In what ways can Git submodules be modeled with
Eiffel?
TBD
</p>
<p>
<b>Speaker:</b> TBD (Volvo)
<b>Speaker/moderator:</b> TBD
</p>
</div>
</details>
</td>
<td><span class="tag bd-error">Advanced</span></td>
<td><span class="tag bd-success">TBD</span></td>
<td>14:30</td>
</tr>

<tr><td><i>Break</i></td><td></td><td>15:00</td></tr>

<tr>
<td>
<details>
<summary>TBD</summary>
<summary>
Reserved place for more topics
</summary>
<div>
<p>
<b>Speaker:</b> TBD
TBD
</p>
<p>
<b>Speaker/moderator:</b> TBD
</p>
</div>
</details>
</td>
<td><!--<span class="tag bd-success" style="border: 1px solid blue !important;">Intermediate</span>--></td>
<td>15:00</td>
<td><span class="tag bd-success">TBD</span></td>
<td>15:30</td>
</tr>

<tr>
Expand Down