Eiffel Virtual Summit 2021.1
Welcome everyone to the Eiffel Virtual Summit 2021.1!
| Topic | Level | Start time | 
|---|---|---|
| Beginner | 09:00 | |
| Beginner | 09:30 | |
| Break | 10:30 | |
| Beginner | 11:00 | |
| Intermediate | 11:30 | |
| Lunch | 12:00 | |
                Technical Committee updates | 
              Beginner | 13:00 | 
| Beginner | 13:30 | |
                New routing key standard
                    Sepia has recently been updated to standardize
                    what RabbitMQ routing keys (topics) should be used
                    when publishing events. This'll enable consumers
                    to set up narrower subscriptions and not have to
                    throw many of the received messages. See
                    github.com/eiffel-community/eiffel-sepia#9.
                    
                     
                Speaker: Magnus Bäck  | 
              Beginner | 14:00 | 
| Break | 14:30 | |
                What's cooking in the community?
                    Many of us have Eiffel-related tools or
                    integrations in the works. This hour is dedicated
                    to 5–10 minute talks for showcasing ideas and
                    things that aren't ready for a full demo or
                    session but deserve to be shared for spreading
                    awareness and to collect early feedback.
                     
                We'll schedule these talks ad hoc but to make things easier we encourage you to contact eiffel-tc@googlegroups.com ahead of time and let us know about your talk. 
 Moderator: Emil Bäckmark  | 
              Intermediate | 15:00 | 
| Topic | Level | Start time | 
|---|---|---|
                Eiffel vs CDF SIG Events protocol on Cloudevents
                    What is the CD Foundation
                    (CDF) and how does the protocol under way by its
                    SIG events
                    relate to Eiffel?
                    
                     
                Speaker: Mattias Linnér  | 
              Advanced | 09:00 | 
                eiffel-broadcaster Jenkins plugin
                    A walkthrough of the features of the
                    eiffel-broadcaster
                    Jenkins plugin.
                    
                     
                Speaker: Magnus Bäck  | 
              Intermediate | 09:30 | 
| Intermediate | 10:00 | |
| Break | 10:30 | |
| Intermediate | 11:00 | |
| Intermediate | 11:30 | |
| Lunch | 12:00 | |
                Discussion: Source change events
                    The two Eiffel events for modelling source code changes,
                    SCC
                    and
                    SCS,
                    create some challenges when attempting to use them
                    to model a Git DAG. Let's talk about the
                    improvement proposal made in
                    github.com/eiffel-community/eiffel#261.
                    
                     
                Moderator: Sven Selberg  | 
              Advanced | 13:00 | 
                Discussion: Using Eiffel to implement event-triggered pipelines
                    While Eiffel could be used just for traceability
                    of existing pipelines it's also well-suited for
                    actual triggering of pipeline tasks. What what are
                    the challenges when doing this? How do you deal
                    with error when there's no single entity that
                    determines the pipeline graph and is responsible
                    for its execution?
                    
                     
                Moderator: Magnus Bäck  | 
              Intermediate | 14:00 | 
| Break | 14:30 | |
                Discussion: Extracting common structures
                    Today, all Eiffel events have their own entirely
                    independent schemas. And yet, surely everyone
                    assumes the meta
                    key's contents to be the same across
                    all events. There are other keys whose values
                    effectively have the same schema across more than
                    one event type. Is this the best we can do or
                    should we strive to change this and extract
                    common pieces into external structures that we can
                    reference in schema files?
                    
                     
                Moderator: Sven Selberg  | 
              Advanced | 15:00 |