Eiffel Summit October 2016 Concluded

[Daniel Ståhl]

I am happy to announce that the Eiffel Summit of October 2016 has been concluded! A big thank you to all the great people and organizations who participated and helped shape it into a great event:

• Ericsson
• Saab
• Grundfos
• Praqma
• Tieto
  
• Linköping University
• Axis Communications
• Volvo
• Sectra
• Autoliv

Those who missed out, don't worry, judging from the engagement at this event there will be more to come :)

During the summit we covered the following topics:

• Recap of first meeting and what has happened since
• Introduction to the Eiffel repository on GitHub
• Crash course of the Eiffel protocol so far
• Demo/presentation of Ericsson work and plans
• Demo/presentation of Tieto work and plans
• Demo/presentation of Praqma work and plans
• Demo/presentation of Linköping University work and plans
• Contribution policy and coordination process. How do we collaborate as efficiently and effectively as possible?
• What happens next? What needs to be prioritized? Who will do it?
• Options for persistence solutions
• Remrem architecture
• Windfalls and pitfalls of Eiffel usage
  

Summary of conclusions, decisions and action points from the events:

• Work on Drop 4 of the protocol will continue.
• Extensions to the protocol and implementations will be linked from the central Eiffel repository on GitHub.
  
• The community will not formalize its collaboration model at this time. Each organization will be responsible for and wield complete power over any contribution it makes, as it sees fit (while the community retains any right to fork).
• The community will arrange new Eiffel Summits twice a year.
• The community will arrange online conferences for demos, discussions and experience reports as needed, aiming for once every 1-2 months.
• The community will create and use a Google group for communication in between summits and online conferences.
• The need for concrete implementations based on the Eiffel protocol as well as sandboxes and examples was recognized.
  

Short- to medium term prioritized work items were listed, and organizations signed up for driving work addressing the respective items:

• Protocol evolution [Ericsson]
• Getting started guide, GitHub landing page [Ericsson + Praqma]
• Screen casts [Ericsson + Praqma]
• Sandboxes and reference implementations [Ericsson + Praqma]
• Persistence [Axis]
• Visualization of low level event data [Tieto]
• Triggering mechanism based on events [Praqma]
• Easy event serialization, validation and publication [Ericsson]
• SCM plugin(s) [Praqma + Axis]

Some work items remain unclaimed, and are considered somewhat lower priority:

• High abstraction level analysis of events [Possibly Ericsson, currently uncertain]
• Triggering mechanism based on high level abstraction states
• Gradle plugin
• Composition composer
  

Suggested improvements for future Eiffel summits are:

• Appoint a dedicated secretary to take notes, which are posted to the Google group
• More concrete implementations, self-contained examples and use cases
• Make it a two-day event, starting later in the morning on day one and finishing earlier on day two
• More information on where the community and the framework are heading
• More in-depth architectural guide and discussions on architecture
• Larger conference space to make room for everyone! :)
  

[Andrey Devyatkin]

I would group unclaimed Gradle plugin and SCM plugin into common category called integrations

Then it would look like this

Integrations

• SCM
• BitBucket plugin (Praqma)
• Gerrit plugin (Axis + possibly Praqma, we discussed two possible ways of implementation - one is to send Gerrit stream events using RabbitMQ and then have an external service that could transform them to Eiffel messages or actual plugin. This is something that requires a separate discussion)
• GitHub enterprise integration (possibly Praqma if there is a demand for that)
• Build systems
• Gradle (Praqma is planning to develop a plugin its customers)
• Yocto (that would be a fun thing to do if there is a demand for that)
• More to come