---
# System prepended metadata

title: Eiffel Community Meetup May 11–12

---

# Eiffel Community Meetup May 11–12

## Practicalities

May 11, 10:00–17:00
May 12, 08:00–15:00

[Axis Communications, Gränden 1, 223 69 Lund](https://goo.gl/maps/girDtexsHneLL5Th6)

## Preliminary agenda

The final agenda will be decided at the start of the meetup.

* Stricter Eiffel
* Methods of promoting Eiffel to a wider audience
    * How do we reach out to other companies and projects and get them interested in Eiffel?
* Lunch
* Discussion around deployment events
    * Eiffel provides events for the CI pipeline but kind of stops at the deployment phase. This is a discussion about whether we should have deployment events, should we use the existing ones in the [Eiffel operations extension](https://github.com/Ericsson/eiffel-operations-extension) or create our own.
* Discuss generic event listener aggregating data from multiple events
    * Event aggregation is done in Eiffel intelligence. If we were to extract that part of Eiffel intelligence, what do we want it to do? And would more people use it? Are there other smart ways to aggregate data from multiple events and trigger activities on it?
* Supply chain security

## Day 2

* Add a new link type to ArtC to describe relationships to other artifacts (1 h)
    * Proposed from Ericsson: Add a link type "RELATIONSHIP" with a *subType* field stating a particular SPDX relation, e.g. PROVIDED_DEPENDENCY_OF, DEPENDS_ON, etc.
* Discussion about activity event linking (30 min)
    * How do we link activity events together in a non-event-driven pipeline. This is a discussion on possibly adding a new link type for providing improved traceability between non-causal activities within a pipeline.
    * https://github.com/eiffel-community/eiffel/issues/227
* Aggregation (1 h)
* Discussion about source change events (1 h)
    * Today Eiffel provides source change events, but they are not optimal for describing the various states of a source code tree. Sven wrote an issue and have been active in several monthly meetings and discussions. At the community meetup we want to dive deeper into this and finally finish these discussions.
    * https://github.com/eiffel-community/eiffel/issues/261
* Discuss a better structured documentation of the protocol, with improved reasoning on design background etc (1 h)
    * E.g. the use of custom data
    * Where to document example event graphs etc
* Event categorization
    * Would we benefit from grouping our events into categories? If so: How should we group them? What are good names?
    * https://github.com/eiffel-community/eiffel/pull/297


* Migrating an organization to Eiffel
    * Separate remote meeting
* Presentation of new format for schemas and documentation
    * We have worked hard to create a new data format for representing schemas, including an ability to generate documentation from this common source. Magnus will present the work he has done and what we can do with it.
    * https://github.com/eiffel-community/eiffel/issues/282
* Presentation about CDEvents
    * Emil and Mattias will present what is going on at CDEvents. Are they our competitor, are they our replacement and what are they even doing over there?
    * Discuss events structure CDEvents vs Eiffel events
* Plan for summit in the autumn
    * In autumn (if nothing changes) there will be an Eiffel summit. Let us sit down as a community and plan for this summit.

## Actions

* Axis: Book room for ~24 people + one smaller room for breakouts
    * Day 1: Kelvin (12 people) 09:30–17:00
    * Day 2: Keops (18 people) 08:00–16:00
* Axis: Investigate food
* Axis: Book AW
    * Table for 8 reserved for 18:00 at [M.E.A.T.](https://www.meatgrill.se/) Can probably accommodate a few more people if we call ahead during the day.
