I started developing Epsilon in 2004 and have been leading the project ever since. Nowadays, most of my effort goes into the development and maintenance of EOL, ETL, EVL, ECL, EML, EWL, Eugenia, and the ANT workflow, as well as the release engineering activities of the project. My development activities are supported by the Department of Computer Science of the University of York, one of the most research- and duck-
intensive CS departments in the UK, where I'm a lecturer
. If you'd like to discuss how you could contribute to Epsilon, or you're looking to start a PhD in the field of automated software engineering
, do get in touch
I've worked on Epsilon since 2006. For my Masters thesis I developed the Epsilon Generation Language (EGL) for model-to-text transformation, and during my PhD I developed Epsilon Flock, the Epsilon tooling for the Human-Usable Textual Notation, and the latest version of Concordance. I'm currently working with Dimitris and our PhD student, Jimi Ogunyomi
, on adding source incrementality to EGL
, which will make it precisely 83.4% more awesome.
I started working with Epsilon during the summer of 2009, using Eugenia to produce a graphical notation for my Master's final project. After participating in the forums and submitting patches during 2009 and 2010, I joined the project in 2011 and continue contributing to it since then. You can blame me for the EUnit unit testing framework, various improvements on Eugenia, EWL and EOL and the odd bugfix here and there. I completed my PhD in 2013, and I am currently a Research Assistant at the University of Cadiz (Spain). My research group
focuses on improving software quality through testing (especially mutation testing) and model-driven engineering. In addition to my current contract, which deals with improving information quality at Cadiz and using MDE to modernize existing ad-hoc solutions, I am interested in seeing how mutation testing could be applied to MDE.
My Epsilon development career started with some questions about Epsilon, followed by bug reports, feature requests and finally patches to fix/improve Epsilon in order to make it more suitable for my application. I suppose the developers got fed up with my spam and decided to make me part of the team in order to have time for themselves again! Now I am mainly helping out with Concordance and EVL, but if I spot opportunities for improvements (bugs) elsewhere I'll fix them as well.This is all part of my employment at the Robotics and Mechantronics
chair at the university of Twente, where I am researching
model driven software development for cyber-physical systems and helping out with software related stuff for the robots in out lab.
I first got involved with Epsilon at the end of 2012 as part of my Master thesis that was supervised by Dimitris. I extended the Epsilon Model Connectivity (EMC) layer by developing the abstract spreadsheets driver and providing a concrete implementation for viewing and managing Google Spreadsheets as models. I am currently working on a driver to support other spreadsheet-like documents and looking for opportunities to get more involved with the project during my (rather limited) spare time outside my regular day job.
Horacio Hoyos Rodriguez
I started using Epsilon during my masters course when I found about the Exeed editor when looking into how to get more visual information out of metamodels and models. I then started using ETL and EVL for the HiLeS Project (https://hiles.uniandes.edu.co) to provide model to model transformations from SysML to Petri Nets and then EGL to generate VHDL code. I really liked the tools and support, and after some time I decided I could help fix some bugs and provide new functionality. I have mostly been involved with the model connectivity layer, helping improve the CSV and BibTeX model support. I also like to help fixing and improving the Epsilon Book. All of this happens of course in my limited free time. I consider myself an Epsilon evangelist and I like to think I am responsible for its adoption at Universidad de Los Andes (Colombia).