- Esug-list - lists.esug.org

CFP - IWST 2017 - International Workshop on Smalltalk Technologies - Extension deadline

by Anne Etien

Dear Smalltakers, Deadline of IWST has been postponed to June 21th AoE. However, we ask you to submit at least an abstract for June 16th. Only papers submitted before this date could be modified until June 21th. Thanks in advance, Cheers, Jannik and Anne > Début du message réexpédié : > > De: <jannik.laval(a)gmail.com> > Objet: [Moose-dev] CFP - IWST 2017 - International Workshop on Smalltalk Technologies > Date: 13 avril 2017 10:59:00 UTC+2 > À: "'Moose-related development'" <moose-dev(a)list.inf.unibe.ch> > Répondre à: Moose-related development <moose-dev(a)list.inf.unibe.ch> > > CFP - IWST 2017 - International Workshop on Smalltalk Technologies > > [Please accept our apologies if you receive multiple copies of this call] > [Please send to interested colleagues / mailing-lists] > ************************************************************************************************************ > CALL FOR PAPERS > > IWST 2017 — International Workshop on Smalltalk Technologies > http://www.esug.org/wiki/pier/Conferences/2017/International-Workshop-IWST_… <http://www.esug.org/wiki/pier/Conferences/2017/International-Workshop-IWST_…> > > Maribor, Slovenia; Between September 4th to 8th, 2017 > ************************************************************************************************************ > > ------------------- > Goals and scopes > ------------------- > The goals of the workshop is to create a forum around advances or experience in Smalltalk and to trigger discussions and exchanges of ideas. The topics of your paper can be on all aspect of Smalltalk, theoretical as well as practical. Participants are invited to submit research articles or industrial papers. This year we want to open two different tracks: one research track and one industrial track with less scientific constraints. > > We expect papers of three kinds: > > Short position papers describing emerging ideas > Long research papers with deeper description of experiments and of research results. > Industrial papers with presentation of real and innovative Smalltalk applications; this kind of paper should enlighten why Smalltalk is really appropriate for your application. > We will not enforce any length restriction. > > -------------------- > Important Dates > -------------------- > Submission deadline: June 16th, 2017 > Notification deadline: July 21th, 2017 > Workshop : between September 4th and 8th, 2017 > All accepted papers will be published in ACM DL (To be confirmed) > > ------------------- > Topics > ------------------- > We welcome contributions on all aspects, theoretical as well as practical, of Smalltalk related topics such as: > > -Aspect-oriented programming, > -Design patterns, > -Experience reports, > -Frameworks, > -Implementation, new dialects or languages implemented in Smalltalk, > -Interaction with other languages, > -Meta-programming and Meta-modeling, > -Tools > > ------------------- > Best Paper Award > ------------------- > To encourage the submission of high-quality papers, the IWST organizing committee is very proud to announce a Best Paper Award for this edition of IWST. > > We thank the Lam Research Corporation for its financial contribution which makes it possible for prizes for the three best papers: 1000 USD for first place, 600 USD for second place and 400 USD for third place. > > The ranking will be decided by the program committee during the review process. The awards will be given during the ESUG conference social event. > > The Best Paper Award will take place only with a minimum of six submissions. Notice also that to be illegible, a paper must be presented at the workshop by one of the author and that the presenting author must be registered at the ESUG conference. > > ------------------- > Publication > ------------------- > Both submissions and final papers must be prepared using the ACM SIGPLAN 10 point format. Templates for Word and LaTeX are available at http://www.acm.org/sigs/sigplan/authorInformation.htm <http://www.acm.org/sigs/sigplan/authorInformation.htm>. This site also contains links to useful informations on how to write effective submissions. > > ------------------- > Submission > ------------------- > All submissions must be sent via easychair: https://easychair.org/conferences/?conf=iwst2017 <https://easychair.org/conferences/?conf=iwst2017> > > ------------------- > Program chairs > ------------------- > Anne Etien (Université de Lille 1, France) > Jannik Laval (Université Lyon 2 Lumière, France) > > > -- > ~~Jannik Laval~~ > Enseignant-chercheur > Responsable Pédagogique Licence Coordonnateur de Projet en Système d'Information > IUT Lumière <http://iut.univ-lyon2.fr/>, Université Lumière Lyon 2 <http://www.univ-lyon2.fr/> > laboratoire DISP <http://disp-lab.fr/> > +33 4 78 77 43 06 > http://www.jannik-laval.eu <http://www.jannik-laval.eu/> > http://www.phratch.com <http://www.phratch.com/> > http://www.approchealpes.info <http://www.approchealpes.info/> > > > <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> Garanti sans virus. www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> <x-msg://221/#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>_______________________________________________ > Moose-dev mailing list > Moose-dev(a)list.inf.unibe.ch <mailto:Moose-dev@list.inf.unibe.ch> > https://www.list.inf.unibe.ch/listinfo/moose-dev <https://www.list.inf.unibe.ch/listinfo/moose-dev>

June 12, 2017

Re: [Esug-list] Seeking support: Vote for Jigyasa Grover for Red Hat International Women in Open Source Academic Awards 2017

by Jigyasa Grover

Dear kingzcq Thanks for the acknowledgement, but the deadline to vote was March 6. Fortunately, I am blessed to have the community support and I won the *Red Hat Women in Open Source Award 2017*. Links: https://www.redhat.com/en/about/women-in-open-source http://www.siliconangle.tv/weekly-wit-5317-jigyasa-grover-women-who-code-an… Best Jigyasa Grover On Wed, Jun 7, 2017 at 12:59 PM, kingzcq [via Smalltalk] < ml+s1294792n4950101h76(a)n4.nabble.com> wrote: > Cool, i will vote! > My personal homepage: http://www.jiyu-acp.com/ > > > ------------------------------ > If you reply to this email, your message will be added to the discussion > below: > http://forum.world.st/Seeking-support-Vote-for-Jigyasa-Grover-for-Red-Hat- > International-Women-in-Open-Source-Academic-Awar7-tp4934826p4950101.html > To unsubscribe from Seeking support: Vote for Jigyasa Grover for Red Hat > International Women in Open Source Academic Awards 2017, click here > <http://forum.world.st/template/NamlServlet.jtp?macro=unsubscribe_by_code&no…> > . > NAML > <http://forum.world.st/template/NamlServlet.jtp?macro=macro_viewer&id=instan…> > -- View this message in context: http://forum.world.st/Seeking-support-Vote-for-Jigyasa-Grover-for-Red-Hat-I… Sent from the ESUG mailing list archive at Nabble.com.

June 7, 2017

Re: [Esug-list] [Moose-dev] CFP - IWST 2017 - Deadline 16th June

by Anne Etien

Dear Smalltalker colleagues, This is a kind reminder of IWST 2017 submission deadline that will occur on 16th June (next Friday). The ACM DL endorsement and the best papers awards by Lam Research Corporation have been confirmed. Two tracks (research and industrial) this year. All details can be found bellow. Don’t hesitate to submit a paper. Kind regards, Anne Etien Le 13 avr. 2017 à 10:59, jannik.laval(a)gmail.com a écrit : > CFP - IWST 2017 - International Workshop on Smalltalk Technologies > > [Please accept our apologies if you receive multiple copies of this call] > [Please send to interested colleagues / mailing-lists] > ************************************************************************************************************ > CALL FOR PAPERS > > IWST 2017 — International Workshop on Smalltalk Technologies > http://www.esug.org/wiki/pier/Conferences/2017/International-Workshop-IWST_… > > Maribor, Slovenia; Between September 4th to 8th, 2017 > ************************************************************************************************************ > > ------------------- > Goals and scopes > ------------------- > The goals of the workshop is to create a forum around advances or experience in Smalltalk and to trigger discussions and exchanges of ideas. The topics of your paper can be on all aspect of Smalltalk, theoretical as well as practical. Participants are invited to submit research articles or industrial papers. This year we want to open two different tracks: one research track and one industrial track with less scientific constraints. > > We expect papers of three kinds: > > Short position papers describing emerging ideas > Long research papers with deeper description of experiments and of research results. > Industrial papers with presentation of real and innovative Smalltalk applications; this kind of paper should enlighten why Smalltalk is really appropriate for your application. > We will not enforce any length restriction. > > -------------------- > Important Dates > -------------------- > Submission deadline: June 16th, 2017 > Notification deadline: July 21th, 2017 > Workshop : between September 4th and 8th, 2017 > All accepted papers will be published in ACM DL (To be confirmed) > > ------------------- > Topics > ------------------- > We welcome contributions on all aspects, theoretical as well as practical, of Smalltalk related topics such as: > > -Aspect-oriented programming, > -Design patterns, > -Experience reports, > -Frameworks, > -Implementation, new dialects or languages implemented in Smalltalk, > -Interaction with other languages, > -Meta-programming and Meta-modeling, > -Tools > > ------------------- > Best Paper Award > ------------------- > To encourage the submission of high-quality papers, the IWST organizing committee is very proud to announce a Best Paper Award for this edition of IWST. > > We thank the Lam Research Corporation for its financial contribution which makes it possible for prizes for the three best papers: 1000 USD for first place, 600 USD for second place and 400 USD for third place. > > The ranking will be decided by the program committee during the review process. The awards will be given during the ESUG conference social event. > > The Best Paper Award will take place only with a minimum of six submissions. Notice also that to be illegible, a paper must be presented at the workshop by one of the author and that the presenting author must be registered at the ESUG conference. > > ------------------- > Publication > ------------------- > Both submissions and final papers must be prepared using the ACM SIGPLAN 10 point format. Templates for Word and LaTeX are available athttp://www.acm.org/sigs/sigplan/authorInformation.htm. This site also contains links to useful informations on how to write effective submissions. > > ------------------- > Submission > ------------------- > All submissions must be sent via easychair: https://easychair.org/conferences/?conf=iwst2017 > > ------------------- > Program chairs > ------------------- > Anne Etien (Université de Lille 1, France) > Jannik Laval (Université Lyon 2 Lumière, France) > > > -- > ~~Jannik Laval~~ > Enseignant-chercheur > Responsable Pédagogique Licence Coordonnateur de Projet en Système d'Information > IUT Lumière, Université Lumière Lyon 2 > laboratoire DISP > +33 4 78 77 43 06 > http://www.jannik-laval.eu > http://www.phratch.com > http://www.approchealpes.info > > > Garanti sans virus. www.avast.com > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)list.inf.unibe.ch > https://www.list.inf.unibe.ch/listinfo/moose-dev

June 7, 2017

Re: [Esug-list] Esug-list Digest, Vol 85, Issue 5 - Pharo 6.0 Release

by mldavis＠chaparralwest.com

Congratulations, This is a beautiful achievement. I've been watching the progress and I am amazed at the wonderful job you have all accomplished. Thank you so very much. mike -----Original Message----- From: Esug-list [mailto:esug-list-bounces@lists.esug.org] On Behalf Of esug-list-request(a)lists.esug.org Sent: Tuesday, June 6, 2017 4:23 PM To: esug-list(a)lists.esug.org Subject: Esug-list Digest, Vol 85, Issue 5 Send Esug-list mailing list submissions to esug-list(a)lists.esug.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.esug.org/mailman/listinfo/esug-list_lists.esug.org or, via email, send a message with subject or body 'help' to esug-list-request(a)lists.esug.org You can reach the person managing the list at esug-list-owner(a)lists.esug.org When replying, please edit your Subject line so it is more specific than "Re: Contents of Esug-list digest..." Today's Topics: 1. [Pharo-dev] [ANN] Pharo 6.0 released! (Torsten Bergmann) 2. Re: [ANN] Pharo 6.0 released! (Bert Freudenberg) ---------------------------------------------------------------------- Message: 1 Date: Tue, 6 Jun 2017 19:49:27 +0200 From: "Torsten Bergmann" <astares(a)gmx.de> To: pharo-dev(a)lists.pharo.org Cc: "Any question about pharo is welcome" <pharo-users(a)lists.pharo.org>, "Pharo Development List" <pharo-dev(a)lists.pharo.org>, members-consortium(a)pharo.org, "Seaside - general discussion" <seaside(a)lists.squeakfoundation.org>, "list ESUG Mailing" <esug-list(a)lists.esug.org>, vm-dev(a)lists.squeakfoundation.org Subject: [Esug-list] [Pharo-dev] [ANN] Pharo 6.0 released! Message-ID: <trinity-120f5c33-f6c1-41c3-bdd8-8124ea5db683-1496771367608@3capp-gmx-bs19> Content-Type: text/plain; charset=UTF-8 Dear friends, Yes - really an impressive release. With many cleanups and new treasures in the image - but also many shiny new/updated external packages and projects (like Roassal, Polymath, Calypso browser, ... to name just a few). Thanks to all who helped - especially to the ones who cared and also worked on the not so interesting but often hard to solve issues or boring but necessary parts or infrastructure. The new git integration in Pharo and the included Iceberg tool will allow us to work with services like GitHub, GitLab, BitBucket - even own local git servers (for instance setups using Gogs.io). We can now manage project resources beside code, commit several packages at once and branch and merge as necessary. This really rocks! Many thanks also to all the contributors of the OpenSmalltalk initiative - it is also impressive how much progress was done on VM side. Also thanks to the ones writing new books, articles and tutorials so other can learn and enjoy such a fantastic dynamic and lively system. We still have a way to go for Pharo 7 and onwards. I'm eager to play with the new git based development process and interested on how we can manage to build our future Pharo based on the bootstrap efforts. Even when not finally there ... step by step it goes! Bye T. ? Gesendet:?Dienstag, 06. Juni 2017 um 17:11 Uhr Von:?"Esteban Lorenzano" <estebanlm(a)gmail.com> An:?"Any question about pharo is welcome" <pharo-users(a)lists.pharo.org>, "Pharo Development List" <pharo-dev(a)lists.pharo.org>, members-consortium(a)pharo.org, "Seaside - general discussion" <seaside(a)lists.squeakfoundation.org>, "list ESUG Mailing" <esug-list(a)lists.esug.org> Betreff:?[Pharo-dev] [ANN] Pharo 6.0 released! Dear World, ? The time has come for Pharo 6.0! ? Pharo is a pure object-oriented programming language and a powerful environment, focused on simplicity and immediate feedback. ? This is our most significant release yet. Here are some highlights: ? - Pharo is now provided in 64-bit version in Linux and OSX and brings even better performance and stability (beware, 64bits version is a new technology and a small amount of tests is still failing) - A new code changes management system named Epicea for easier reviewing and recovering of your code easily - Integrated support for Git through an easy-to-use tool for repositories and commits management named Iceberg (as a preview for Pharo 6, it will be the default in Pharo 7) - The unified foreign function interface (UnifiedFFI) for interfacing with the outside world is significantly improved - The PharoVM is now part of OpenSmalltalk initiative - Introduction of object immutability, alternative bytecode sets and block closures independent of outer context - Pharo can now be bootstrapped from source code managed by Git - Pharo modularity is improved - Pharo is faster - The Dark Theme was improved and set as default color theme of Pharo ? ? These are just the more prominent highlights, but the details are just as important. We have closed 1474 issues in Pharo 6.0 (a more complete changelog can be found at https://github.com/pharo-project/pharo-changelogs/blob/master/Pharo60ChangeL ogs.md).? ? While the technical improvements are significant (starting the transition to 64bits is a remarkable achievement), still the most impressive fact is that the new code that got in the main Pharo 6.0 image was contributed by more than 80 people. ? Pharo is more than code. It is an exciting project involving energetic people. We thank all the contributors of this release: ? Alberto Bacchelli, Alejandro Infante, Alexandre Bergel, Aliaksei Syrel, Alistair Grant, Andrei Chis, Ben Coman, Bernardo Contreras, Bernhard Pieber, Boris Spasojevic, Christophe Demarey, Clement Bera, Cyril Ferlicot, Dale Henrichs, Damien Cassou, Damien Pollet, Dave Lewis, Denis Kudriashov, Dirk Roeleveld, Eliot Miranda, Esteban Lorenzano, Esteban Maringolo, Evan Donahue, Federico Balaguer, Franck Warlouzet, Glenn Cavarle, Guillermo Polito, Gustavo Santos, Henrik Johansen, Henrik Nergaard, Hilaire Fernandes, Holger Hans, Jan Kurs, Jan van de Sandt, Johan Fabry, Juraj Kubelka, K. K. Subramaniam, Ken Causey, Kris Gybels, Lionel Akue, Luc Fabresse, Lucas Godoy, Marcus Denker, Mariano Martinez Peck, Marion Noirbent, Martin Dias, Max Leske, Maxime Roelandt, Merwan Ouddane, Matteo Bellotto, Miguel Campusano, Milton Mamani, Myroslava Romaniuk, Nicolai Hess, Nicolas Cellier, Nicolas Passerini, Norbert Hartl, Offray Luna, Pablo Tesone, Paul De Bruicker, Pavel Krivanek, Peter Uhnak, Philippe Back, Roger Stebler, Ronie Salgado, Sean DeNigris, Serge Stinckwich, Skip Lentz, Sophie Kaleba, Stefan Reichhart, Stephan Eggermont, Stephane Ducasse, Sven Van Caekenberghe, Thibault Arloing, Thibault Arloing, Thibault Raffaillac, Thierry Goubier, Thomas Heniart, Tommaso Dal Sasso, Torsten Bergmann, Tudor Girba, Udo Schneider, Valentin Ryckewaert, Vincent Blondeau, Werner Kassens, Yuriy Tymchuk ? (If you contributed with Pharo 6.0 development in any way and we missed your name, please send us a mail and we will add you). ? Enjoy! ? The Pharo Team ? Try Pharo: http://pharo.org/download[http://pharo.org/download] Learn Pharo: http://pharo.org/documentation[http://pharo.org/documentation] ------------------------------ Message: 2 Date: Wed, 7 Jun 2017 00:21:21 +0200 From: Bert Freudenberg <bert(a)freudenbergs.de> To: list ESUG Mailing <esug-list(a)lists.esug.org> Subject: Re: [Esug-list] [ANN] Pharo 6.0 released! Message-ID: <CACnEXeco7WNGQ-75HgWAcHCVkC76pU2VRr-ai7HyDrwDC_p1Zg(a)mail.gmail.com> Content-Type: text/plain; charset="utf-8" ?Congratulations! - Bert -? On Tue, Jun 6, 2017 at 5:11 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > Dear World, > > The time has come for Pharo 6.0! > > Pharo is a pure object-oriented programming language and a powerful > environment, focused on simplicity and immediate feedback. > > This is our most significant release yet. Here are some highlights: > > - Pharo is now provided in 64-bit version in Linux and OSX and brings > even better performance and stability (beware, 64bits version is a new > technology and a small amount of tests is still failing) > - A new code changes management system named Epicea for easier > reviewing and recovering of your code easily > - Integrated support for Git through an easy-to-use tool for > repositories and commits management named Iceberg (as a preview for > Pharo 6, it will be the default in Pharo 7) > - The unified foreign function interface (UnifiedFFI) for interfacing > with the outside world is significantly improved > - The PharoVM is now part of OpenSmalltalk initiative > - Introduction of object immutability, alternative bytecode sets and > block closures independent of outer context > - Pharo can now be bootstrapped from source code managed by Git > - Pharo modularity is improved > - Pharo is faster > - The Dark Theme was improved and set as default color theme of Pharo > > > These are just the more prominent highlights, but the details are just > as important. We have closed 1474 issues in Pharo 6.0 (a more complete > changelog can be found at https://github.com/pharo- > project/pharo-changelogs/blob/master/Pharo60ChangeLogs.md). > > While the technical improvements are significant (starting the > transition to 64bits is a remarkable achievement), still the most > impressive fact is that the new code that got in the main Pharo 6.0 > image was contributed by more than 80 people. > > Pharo is more than code. It is an exciting project involving energetic > people. We thank all the contributors of this release: > > Alberto Bacchelli, Alejandro Infante, Alexandre Bergel, Aliaksei > Syrel, Alistair Grant, Andrei Chis, Ben Coman, Bernardo Contreras, > Bernhard Pieber, Boris Spasojevic, Christophe Demarey, Clement Bera, > Cyril Ferlicot, Dale Henrichs, Damien Cassou, Damien Pollet, Dave > Lewis, Denis Kudriashov, Dirk Roeleveld, Eliot Miranda, Esteban > Lorenzano, Esteban Maringolo, Evan Donahue, Federico Balaguer, Franck > Warlouzet, Glenn Cavarle, Guillermo Polito, Gustavo Santos, Henrik > Johansen, Henrik Nergaard, Hilaire Fernandes, Holger Hans, Jan Kurs, > Jan van de Sandt, Johan Fabry, Juraj Kubelka, K. K. Subramaniam, Ken > Causey, Kris Gybels, Lionel Akue, Luc Fabresse, Lucas Godoy, Marcus > Denker, Mariano Martinez Peck, Marion Noirbent, Martin Dias, Max > Leske, Maxime Roelandt, Merwan Ouddane, Matteo Bellotto, Miguel > Campusano, Milton Mamani, Myroslava Romaniuk, Nicolai Hess, Nicolas > Cellier, Nicolas Passerini, Norbert Hartl, Offray Luna, Pablo Tesone, > Paul De Bruicker, Pavel Krivanek, Peter Uhnak, Philippe Back, Roger > Stebler, Ronie Salgado, Sean DeNigris, Serge Stinckwich, Skip Lentz, > Sophie Kaleba, Stefan Reichhart, Stephan Eggermont, Stephane Ducasse, > Sven Van Caekenberghe, Thibault Arloing, Thibault Arloing, Thibault > Raffaillac, Thierry Goubier, Thomas Heniart, Tommaso Dal Sasso, > Torsten Bergmann, Tudor Girba, Udo Schneider, Valentin Ryckewaert, > Vincent Blondeau, Werner Kassens, Yuriy Tymchuk > > (If you contributed with Pharo 6.0 development in any way and we > missed your name, please send us a mail and we will add you). > > Enjoy! > > The Pharo Team > > Try Pharo: http://pharo.org/download > Learn Pharo: http://pharo.org/documentation > > _______________________________________________ > Esug-list mailing list > Esug-list(a)lists.esug.org > http://lists.esug.org/mailman/listinfo/esug-list_lists.esug.org > >

June 7, 2017

Re: [Esug-list] [ANN] Pharo 6.0 released!

by Bert Freudenberg

Congratulations! - Bert - On Tue, Jun 6, 2017 at 5:11 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > Dear World, > > The time has come for Pharo 6.0! > > Pharo is a pure object-oriented programming language and a powerful > environment, focused on simplicity and immediate feedback. > > This is our most significant release yet. Here are some highlights: > > - Pharo is now provided in 64-bit version in Linux and OSX and brings even > better performance and stability (beware, 64bits version is a new > technology and a small amount of tests is still failing) > - A new code changes management system named Epicea for easier reviewing > and recovering of your code easily > - Integrated support for Git through an easy-to-use tool for repositories > and commits management named Iceberg (as a preview for Pharo 6, it will be > the default in Pharo 7) > - The unified foreign function interface (UnifiedFFI) for interfacing with > the outside world is significantly improved > - The PharoVM is now part of OpenSmalltalk initiative > - Introduction of object immutability, alternative bytecode sets and block > closures independent of outer context > - Pharo can now be bootstrapped from source code managed by Git > - Pharo modularity is improved > - Pharo is faster > - The Dark Theme was improved and set as default color theme of Pharo > > > These are just the more prominent highlights, but the details are just as > important. We have closed 1474 issues in Pharo 6.0 (a more complete > changelog can be found at https://github.com/pharo- > project/pharo-changelogs/blob/master/Pharo60ChangeLogs.md). > > While the technical improvements are significant (starting the transition > to 64bits is a remarkable achievement), still the most impressive fact is > that the new code that got in the main Pharo 6.0 image was contributed by > more than 80 people. > > Pharo is more than code. It is an exciting project involving energetic > people. We thank all the contributors of this release: > > Alberto Bacchelli, Alejandro Infante, Alexandre Bergel, Aliaksei Syrel, > Alistair Grant, Andrei Chis, Ben Coman, Bernardo Contreras, Bernhard > Pieber, Boris Spasojevic, Christophe Demarey, Clement Bera, Cyril Ferlicot, > Dale Henrichs, Damien Cassou, Damien Pollet, Dave Lewis, Denis Kudriashov, > Dirk Roeleveld, Eliot Miranda, Esteban Lorenzano, Esteban Maringolo, Evan > Donahue, Federico Balaguer, Franck Warlouzet, Glenn Cavarle, Guillermo > Polito, Gustavo Santos, Henrik Johansen, Henrik Nergaard, Hilaire > Fernandes, Holger Hans, Jan Kurs, Jan van de Sandt, Johan Fabry, Juraj > Kubelka, K. K. Subramaniam, Ken Causey, Kris Gybels, Lionel Akue, Luc > Fabresse, Lucas Godoy, Marcus Denker, Mariano Martinez Peck, Marion > Noirbent, Martin Dias, Max Leske, Maxime Roelandt, Merwan Ouddane, Matteo > Bellotto, Miguel Campusano, Milton Mamani, Myroslava Romaniuk, Nicolai > Hess, Nicolas Cellier, Nicolas Passerini, Norbert Hartl, Offray Luna, Pablo > Tesone, Paul De Bruicker, Pavel Krivanek, Peter Uhnak, Philippe Back, Roger > Stebler, Ronie Salgado, Sean DeNigris, Serge Stinckwich, Skip Lentz, Sophie > Kaleba, Stefan Reichhart, Stephan Eggermont, Stephane Ducasse, Sven Van > Caekenberghe, Thibault Arloing, Thibault Arloing, Thibault Raffaillac, > Thierry Goubier, Thomas Heniart, Tommaso Dal Sasso, Torsten Bergmann, Tudor > Girba, Udo Schneider, Valentin Ryckewaert, Vincent Blondeau, Werner > Kassens, Yuriy Tymchuk > > (If you contributed with Pharo 6.0 development in any way and we missed > your name, please send us a mail and we will add you). > > Enjoy! > > The Pharo Team > > Try Pharo: http://pharo.org/download > Learn Pharo: http://pharo.org/documentation > > _______________________________________________ > Esug-list mailing list > Esug-list(a)lists.esug.org > http://lists.esug.org/mailman/listinfo/esug-list_lists.esug.org > >

June 6, 2017

[Pharo-dev] [ANN] Pharo 6.0 released!

by Torsten Bergmann

Dear friends, Yes - really an impressive release. With many cleanups and new treasures in the image - but also many shiny new/updated external packages and projects (like Roassal, Polymath, Calypso browser, ... to name just a few). Thanks to all who helped - especially to the ones who cared and also worked on the not so interesting but often hard to solve issues or boring but necessary parts or infrastructure. The new git integration in Pharo and the included Iceberg tool will allow us to work with services like GitHub, GitLab, BitBucket - even own local git servers (for instance setups using Gogs.io). We can now manage project resources beside code, commit several packages at once and branch and merge as necessary. This really rocks! Many thanks also to all the contributors of the OpenSmalltalk initiative - it is also impressive how much progress was done on VM side. Also thanks to the ones writing new books, articles and tutorials so other can learn and enjoy such a fantastic dynamic and lively system. We still have a way to go for Pharo 7 and onwards. I'm eager to play with the new git based development process and interested on how we can manage to build our future Pharo based on the bootstrap efforts. Even when not finally there ... step by step it goes! Bye T. Gesendet: Dienstag, 06. Juni 2017 um 17:11 Uhr Von: "Esteban Lorenzano" <estebanlm(a)gmail.com> An: "Any question about pharo is welcome" <pharo-users(a)lists.pharo.org>, "Pharo Development List" <pharo-dev(a)lists.pharo.org>, members-consortium(a)pharo.org, "Seaside - general discussion" <seaside(a)lists.squeakfoundation.org>, "list ESUG Mailing" <esug-list(a)lists.esug.org> Betreff: [Pharo-dev] [ANN] Pharo 6.0 released! Dear World, The time has come for Pharo 6.0! Pharo is a pure object-oriented programming language and a powerful environment, focused on simplicity and immediate feedback. This is our most significant release yet. Here are some highlights: - Pharo is now provided in 64-bit version in Linux and OSX and brings even better performance and stability (beware, 64bits version is a new technology and a small amount of tests is still failing) - A new code changes management system named Epicea for easier reviewing and recovering of your code easily - Integrated support for Git through an easy-to-use tool for repositories and commits management named Iceberg (as a preview for Pharo 6, it will be the default in Pharo 7) - The unified foreign function interface (UnifiedFFI) for interfacing with the outside world is significantly improved - The PharoVM is now part of OpenSmalltalk initiative - Introduction of object immutability, alternative bytecode sets and block closures independent of outer context - Pharo can now be bootstrapped from source code managed by Git - Pharo modularity is improved - Pharo is faster - The Dark Theme was improved and set as default color theme of Pharo These are just the more prominent highlights, but the details are just as important. We have closed 1474 issues in Pharo 6.0 (a more complete changelog can be found at https://github.com/pharo-project/pharo-changelogs/blob/master/Pharo60Change…) While the technical improvements are significant (starting the transition to 64bits is a remarkable achievement), still the most impressive fact is that the new code that got in the main Pharo 6.0 image was contributed by more than 80 people. Pharo is more than code. It is an exciting project involving energetic people. We thank all the contributors of this release: Alberto Bacchelli, Alejandro Infante, Alexandre Bergel, Aliaksei Syrel, Alistair Grant, Andrei Chis, Ben Coman, Bernardo Contreras, Bernhard Pieber, Boris Spasojevic, Christophe Demarey, Clement Bera, Cyril Ferlicot, Dale Henrichs, Damien Cassou, Damien Pollet, Dave Lewis, Denis Kudriashov, Dirk Roeleveld, Eliot Miranda, Esteban Lorenzano, Esteban Maringolo, Evan Donahue, Federico Balaguer, Franck Warlouzet, Glenn Cavarle, Guillermo Polito, Gustavo Santos, Henrik Johansen, Henrik Nergaard, Hilaire Fernandes, Holger Hans, Jan Kurs, Jan van de Sandt, Johan Fabry, Juraj Kubelka, K. K. Subramaniam, Ken Causey, Kris Gybels, Lionel Akue, Luc Fabresse, Lucas Godoy, Marcus Denker, Mariano Martinez Peck, Marion Noirbent, Martin Dias, Max Leske, Maxime Roelandt, Merwan Ouddane, Matteo Bellotto, Miguel Campusano, Milton Mamani, Myroslava Romaniuk, Nicolai Hess, Nicolas Cellier, Nicolas Passerini, Norbert Hartl, Offray Luna, Pablo Tesone, Paul De Bruicker, Pavel Krivanek, Peter Uhnak, Philippe Back, Roger Stebler, Ronie Salgado, Sean DeNigris, Serge Stinckwich, Skip Lentz, Sophie Kaleba, Stefan Reichhart, Stephan Eggermont, Stephane Ducasse, Sven Van Caekenberghe, Thibault Arloing, Thibault Arloing, Thibault Raffaillac, Thierry Goubier, Thomas Heniart, Tommaso Dal Sasso, Torsten Bergmann, Tudor Girba, Udo Schneider, Valentin Ryckewaert, Vincent Blondeau, Werner Kassens, Yuriy Tymchuk (If you contributed with Pharo 6.0 development in any way and we missed your name, please send us a mail and we will add you). Enjoy! The Pharo Team Try Pharo: http://pharo.org/download[http://pharo.org/download] Learn Pharo: http://pharo.org/documentation[http://pharo.org/documentation]

June 6, 2017

Re: [Esug-list] [ANN] Pharo 6.0 released!

by Tudor Girba

Great work! Doru > On Jun 6, 2017, at 5:11 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > Dear World, > > The time has come for Pharo 6.0! > > Pharo is a pure object-oriented programming language and a powerful environment, focused on simplicity and immediate feedback. > > This is our most significant release yet. Here are some highlights: > > - Pharo is now provided in 64-bit version in Linux and OSX and brings even better performance and stability (beware, 64bits version is a new technology and a small amount of tests is still failing) > - A new code changes management system named Epicea for easier reviewing and recovering of your code easily > - Integrated support for Git through an easy-to-use tool for repositories and commits management named Iceberg (as a preview for Pharo 6, it will be the default in Pharo 7) > - The unified foreign function interface (UnifiedFFI) for interfacing with the outside world is significantly improved > - The PharoVM is now part of OpenSmalltalk initiative > - Introduction of object immutability, alternative bytecode sets and block closures independent of outer context > - Pharo can now be bootstrapped from source code managed by Git > - Pharo modularity is improved > - Pharo is faster > - The Dark Theme was improved and set as default color theme of Pharo > > <Pharo6.jpeg> > > These are just the more prominent highlights, but the details are just as important. We have closed 1474 issues in Pharo 6.0 (a more complete changelog can be found at https://github.com/pharo-project/pharo-changelogs/blob/master/Pharo60Change…) > > While the technical improvements are significant (starting the transition to 64bits is a remarkable achievement), still the most impressive fact is that the new code that got in the main Pharo 6.0 image was contributed by more than 80 people. > > Pharo is more than code. It is an exciting project involving energetic people. We thank all the contributors of this release: > > Alberto Bacchelli, Alejandro Infante, Alexandre Bergel, Aliaksei Syrel, Alistair Grant, Andrei Chis, Ben Coman, Bernardo Contreras, Bernhard Pieber, Boris Spasojevic, Christophe Demarey, Clement Bera, Cyril Ferlicot, Dale Henrichs, Damien Cassou, Damien Pollet, Dave Lewis, Denis Kudriashov, Dirk Roeleveld, Eliot Miranda, Esteban Lorenzano, Esteban Maringolo, Evan Donahue, Federico Balaguer, Franck Warlouzet, Glenn Cavarle, Guillermo Polito, Gustavo Santos, Henrik Johansen, Henrik Nergaard, Hilaire Fernandes, Holger Hans, Jan Kurs, Jan van de Sandt, Johan Fabry, Juraj Kubelka, K. K. Subramaniam, Ken Causey, Kris Gybels, Lionel Akue, Luc Fabresse, Lucas Godoy, Marcus Denker, Mariano Martinez Peck, Marion Noirbent, Martin Dias, Max Leske, Maxime Roelandt, Merwan Ouddane, Matteo Bellotto, Miguel Campusano, Milton Mamani, Myroslava Romaniuk, Nicolai Hess, Nicolas Cellier, Nicolas Passerini, Norbert Hartl, Offray Luna, Pablo Tesone, Paul De Bruicker, Pavel Krivanek, Peter Uhnak, Philippe Back, Roger Stebler, Ronie Salgado, Sean DeNigris, Serge Stinckwich, Skip Lentz, Sophie Kaleba, Stefan Reichhart, Stephan Eggermont, Stephane Ducasse, Sven Van Caekenberghe, Thibault Arloing, Thibault Arloing, Thibault Raffaillac, Thierry Goubier, Thomas Heniart, Tommaso Dal Sasso, Torsten Bergmann, Tudor Girba, Udo Schneider, Valentin Ryckewaert, Vincent Blondeau, Werner Kassens, Yuriy Tymchuk > > (If you contributed with Pharo 6.0 development in any way and we missed your name, please send us a mail and we will add you). > > Enjoy! > > The Pharo Team > > Try Pharo: http://pharo.org/download > Learn Pharo: http://pharo.org/documentation -- www.tudorgirba.com www.feenk.com “Software has no shape. Actually, it has no one shape. It has many."

June 6, 2017

[ANN] Pharo 6.0 released!

by Esteban Lorenzano

Dear World, The time has come for Pharo 6.0! Pharo is a pure object-oriented programming language and a powerful environment, focused on simplicity and immediate feedback. This is our most significant release yet. Here are some highlights: - Pharo is now provided in 64-bit version in Linux and OSX and brings even better performance and stability (beware, 64bits version is a new technology and a small amount of tests is still failing) - A new code changes management system named Epicea for easier reviewing and recovering of your code easily - Integrated support for Git through an easy-to-use tool for repositories and commits management named Iceberg (as a preview for Pharo 6, it will be the default in Pharo 7) - The unified foreign function interface (UnifiedFFI) for interfacing with the outside world is significantly improved - The PharoVM is now part of OpenSmalltalk initiative - Introduction of object immutability, alternative bytecode sets and block closures independent of outer context - Pharo can now be bootstrapped from source code managed by Git - Pharo modularity is improved - Pharo is faster - The Dark Theme was improved and set as default color theme of Pharo These are just the more prominent highlights, but the details are just as important. We have closed 1474 issues in Pharo 6.0 (a more complete changelog can be found at https://github.com/pharo-project/pharo-changelogs/blob/master/Pharo60Change…) While the technical improvements are significant (starting the transition to 64bits is a remarkable achievement), still the most impressive fact is that the new code that got in the main Pharo 6.0 image was contributed by more than 80 people. Pharo is more than code. It is an exciting project involving energetic people. We thank all the contributors of this release: Alberto Bacchelli, Alejandro Infante, Alexandre Bergel, Aliaksei Syrel, Alistair Grant, Andrei Chis, Ben Coman, Bernardo Contreras, Bernhard Pieber, Boris Spasojevic, Christophe Demarey, Clement Bera, Cyril Ferlicot, Dale Henrichs, Damien Cassou, Damien Pollet, Dave Lewis, Denis Kudriashov, Dirk Roeleveld, Eliot Miranda, Esteban Lorenzano, Esteban Maringolo, Evan Donahue, Federico Balaguer, Franck Warlouzet, Glenn Cavarle, Guillermo Polito, Gustavo Santos, Henrik Johansen, Henrik Nergaard, Hilaire Fernandes, Holger Hans, Jan Kurs, Jan van de Sandt, Johan Fabry, Juraj Kubelka, K. K. Subramaniam, Ken Causey, Kris Gybels, Lionel Akue, Luc Fabresse, Lucas Godoy, Marcus Denker, Mariano Martinez Peck, Marion Noirbent, Martin Dias, Max Leske, Maxime Roelandt, Merwan Ouddane, Matteo Bellotto, Miguel Campusano, Milton Mamani, Myroslava Romaniuk, Nicolai Hess, Nicolas Cellier, Nicolas Passerini, Norbert Hartl, Offray Luna, Pablo Tesone, Paul De Bruicker, Pavel Krivanek, Peter Uhnak, Philippe Back, Roger Stebler, Ronie Salgado, Sean DeNigris, Serge Stinckwich, Skip Lentz, Sophie Kaleba, Stefan Reichhart, Stephan Eggermont, Stephane Ducasse, Sven Van Caekenberghe, Thibault Arloing, Thibault Arloing, Thibault Raffaillac, Thierry Goubier, Thomas Heniart, Tommaso Dal Sasso, Torsten Bergmann, Tudor Girba, Udo Schneider, Valentin Ryckewaert, Vincent Blondeau, Werner Kassens, Yuriy Tymchuk (If you contributed with Pharo 6.0 development in any way and we missed your name, please send us a mail and we will add you). Enjoy! The Pharo Team Try Pharo: http://pharo.org/download Learn Pharo: http://pharo.org/documentation

June 6, 2017

Deadline Extension - SLE 2017 (10th ACM SIGPLAN International Conference on Software Language Engineering)

by Andrei Chis

======================================================================== **Call for Papers** - **Deadline Extension** **Abstract Submission**: Friday 9, June 2017 **Paper Submission**: Friday 16, June 2017 ======================================================================== 10th ACM SIGPLAN International Conference on Software Language Engineering (SLE 2017) 23-24 October 2017, Vancouver, Canada (Co-located with SPLASH 2017) General chair: Benoit Combemale, University of Rennes 1, France Program co-chairs: Marjan Mernik, University of Maribor, Slovenia Bernhard Rumpe, RWTH Aachen University, Germany Artifact evaluation chairs: Tanja Mayerhofer, TU Wien, Austria Laurence Tratt, King's College London, UK Keynote Speaker: Peter D. Mosses, Swansea University, UK (http://cs.swan.ac.uk/~cspdm/) http://conf.researchr.org/track/sle-2017/sle-2017-papers http://www.sleconf.org/2017 Follow us on twitter: https://twitter.com/sleconf ======================================================================== Software Language Engineering (SLE) is the application of systematic, disciplined, and measurable approaches to the development, use, deployment, and maintenance of software languages. The term "software language" is used broadly, and includes: general-purpose programming languages; domain-specific languages (e.g. BPMN, Simulink, Modelica); modeling and metamodeling languages (e.g. SysML and UML); data models and ontologies (e.g. XML-based and OWL-based languages and vocabularies). ### Important Dates Fri 9 Jun 2017 - Abstract Submission Fri 16 Jun 2017 - Paper Submission Fri 4 Aug 2017 - Author Notification Thu 10 Aug 2017 - Artifact Submission Fri 1 Sep 2017 - Artifact Notification Fri 8 Sep 2017 - Camera Ready Deadline Sun 22 Oct - SLE workshops Mon 23 Oct - Tue 24 Oct 2017 - SLE Conference ### Topics of Interest SLE aims to be broad-minded and inclusive about relevance and scope. We solicit high-quality contributions in areas ranging from theoretical and conceptual contributions to tools, techniques, and frameworks in the domain of language engineering. Topics relevant to SLE cover generic aspects of software languages development rather than aspects of engineering a specific language. In particular, SLE is interested in principled engineering approaches and techniques in the following areas: * Language Design and Implementation * Approaches and methodologies for language design * Static semantics (e.g., design rules, well-formedness constraints) * Techniques for behavioral / executable semantics * Generative approaches (incl. code synthesis, compilation) * Meta-languages, meta-tools, language workbenches * Language Validation * Verification and formal methods for languages * Testing techniques for languages * Simulation techniques for languages * Language Integration and Composition * Coordination of heterogeneous languages and tools * Mappings between languages (incl. transformation languages) * Traceability between languages * Deployment of languages to different platforms * Language Maintenance * Software language reuse * Language evolution * Language families and variability * Domain-specific approaches for any aspects of SLE (design, implementation, validation, maintenance) * Empirical evaluation and experience reports of language engineering tools * User studies evaluating usability * Performance benchmarks * Industrial applications ### Types of Submissions * **Research papers**: These should report a substantial research contribution to SLE or successful application of SLE techniques or both. Full paper submissions must not exceed 12 pages including bibliography in ACM SIGPLAN acmart conference style ( http://www.sigplan.org/Resources/Author/) * **Tool papers**: Because of SLE's interest in tools, we seek papers that present software tools related to the field of SLE. Selection criteria include originality of the tool, its innovative aspects, and relevance to SLE. Any of the SLE topics of interest are appropriate areas for tool demonstrations. Submissions must provide a tool description of 4 pages including bibliography in ACM SIGPLAN acmart conference style ( http://www.sigplan.org/Resources/Author/) and a demonstration outline including screenshots of up to 6 pages. Tool demonstrations must have the keywords “Tool Demo” or “Tool Demonstration” in the title. The 4-page tool description will, if the demonstration is accepted, be published in the proceedings. The 6-page demonstration outline will be used by the program committee only for evaluating the submission. * **Industrial papers**: These should describe real-world application scenarios of SLE in industry, explained in their context with an analysis of the challenges that were overcome and the lessons which the audience can learn from this experience. Industry paper submissions must not exceed 6 pages including bibliography in ACM SIGPLAN acmart conference style ( http://www.sigplan.org/Resources/Author/) * **New ideas / vision papers**: New ideas papers should describe new, non-conventional SLE research approaches that depart from standard practice. They are intended to describe well-defined research ideas that are at an early stage of investigation. Vision papers are intended to present new unifying theories about existing SLE research that can lead to the development of new technologies or approaches. New ideas / vision papers must not exceed 4 pages including bibliography in ACM SIGPLAN acmart conference style (http://www.sigplan.org/Resources/Author/) ### Artifact evaluation SLE will for the second year use an evaluation process for assessing the quality of artifacts on which papers are based. The aim of this evaluation process is to foster a culture of experimental reproducibility as well as a higher quality in the research area as a whole. Authors of papers accepted for SLE 2017 will be invited to submit artifacts. Any kind of artifact that is presented in the paper, supplements the paper with further details, or underlies the paper can be submitted. This includes, for instance, tools, grammars, metamodels, models, programs, algorithms, scripts, proofs, datasets, statistical tests, checklists, surveys, interview scripts, visualizations, annotated bibliographies, and tutorials. The submitted artifacts will be reviewed by a dedicated Artifact Evaluation Committee (AEC). Artifacts that live up to the expectations created by the paper will receive a badge of approval from the AEC. The approved artifacts will be invited for inclusion in the electronic conference proceedings published in the ACM Digital Library. This will ensure the permanent and durable storage of the artifacts alongside the published papers fostering the repeatability of experiments, enabling precise comparison with alternative approaches, and helping the dissemination of the author’s ideas in detail. Participating in the artifact evaluation and publishing approved artifacts in the ACM Digital Library is voluntary. However, we strongly encourage authors to consider this possibility as the availability of artifacts will greatly benefit readers of papers and increase the impact of the work. Note that the artifact evaluation cannot affect the acceptance of the paper, because it only happens after the decision about acceptance has been made. ### Publications All submitted papers will be reviewed by at least three members of the program committee. All accepted papers, including tool papers, industrial papers and new ideas / vision papers will be published in ACM Digital Library. Selected accepted papers will be invited to a special issue of the Computer Languages, Systems and Structures (COMLAN) journal. ### Awards * **Distinguished paper**: Award for most notable paper, as determined by the PC chairs based on the recommendations of the program committee. * **Distinguished reviewer**: Award for distinguished reviewer, as determined by the PC chairs using feedback from the authors. * **Distinguished artifact**: Award for the artifact most significantly exceeding expectations, as determined by the AEC chairs based on the recommendations of the artifact evaluation committee. ### Program Committee Marjan Mernik (co-chair), University of Maribor, Slovenia Bernhard Rumpe (co-chair), RWTH Aachen University, Germany Christian Berger, Chalmers, Sweden Mark van den Brand, TU Eindhoven, The Netherlands Ruth Breu, University of Innsbruck, Austria Jordi Cabot, ICREA, Spain Walter Cazzola, University of Milan, Italy Marsha Chechik, University of Toronto, Canada Tony Clark, Middlesex University, UK Tom Dinkelaker, Ericsson, Germany Bernd Fischer, Stellenbosch University, South Africa Sebastian Gerard, CEA, France Jeff Gray, University of Alabama, USA Esther Guerra, Autonomous University of Madrid, Spain Michael Homer, Victoria University of Wellington, New Zealand Ralf Lämmel, University of Koblenz-Landau, Germany Tihamer Levendovszky, Microsoft, USA Gunter Mussbacher, McGill University, Canada Terence Parr, University of San Francisco, USA Jaroslav Porubän, University of Košice, Slovakia Jan Ringert, Tel Aviv University, Israel Julia Rubin, University of British Columbia, Canada Tony Sloane, Macquarie University, Australia Eugene Syriani, University of Montreal, Canada Emma Söderberg, Google, Denmark Eric Van Wyk, University of Minnesota, USA Jurgen Vinju, CWI, Netherlands Eric Walkingshaw, Oregon State University, USA Andreas Wortmann, RWTH Aachen University, Germany Tian Zhang, Nanjing University, China ### Contact For any question, please contact the organizers via email: sle2017(a)inria.fr

June 5, 2017

3rd CfP: SLE 2017 (10th ACM SIGPLAN International Conference on Software Language Engineering)

by Andrei Chis

======================================================================== **Call for Papers** **Abstract submission**: Friday 2, Jun 2017 ======================================================================== 10th ACM SIGPLAN International Conference on Software Language Engineering (SLE 2017) 23-24 October 2017, Vancouver, Canada (Co-located with SPLASH 2017) General chair: Benoit Combemale, University of Rennes 1, France Program co-chairs: Marjan Mernik, University of Maribor, Slovenia Bernhard Rumpe, RWTH Aachen University, Germany Artifact evaluation chairs: Tanja Mayerhofer, TU Wien, Austria Laurence Tratt, King's College London, UK Keynote Speaker: Peter D. Mosses, Swansea University, UK (http://cs.swan.ac.uk/~cspdm/) http://conf.researchr.org/track/sle-2017/sle-2017-papers http://www.sleconf.org/2017 Follow us on twitter: https://twitter.com/sleconf ======================================================================== Software Language Engineering (SLE) is the application of systematic, disciplined, and measurable approaches to the development, use, deployment, and maintenance of software languages. The term "software language" is used broadly, and includes: general-purpose programming languages; domain-specific languages (e.g. BPMN, Simulink, Modelica); modeling and metamodeling languages (e.g. SysML and UML); data models and ontologies (e.g. XML-based and OWL-based languages and vocabularies). ### Important Dates Fri 2 Jun 2017 - Abstract Submission Fri 9 Jun 2017 - Paper Submission Fri 4 Aug 2017 - Author Notification Thu 10 Aug 2017 - Artifact Submission Fri 1 Sep 2017 - Artifact Notification Fri 8 Sep 2017 - Camera Ready Deadline Sun 22 Oct - SLE workshops Mon 23 Oct - Tue 24 Oct 2017 - SLE Conference ### Topics of Interest SLE aims to be broad-minded and inclusive about relevance and scope. We solicit high-quality contributions in areas ranging from theoretical and conceptual contributions to tools, techniques, and frameworks in the domain of language engineering. Topics relevant to SLE cover generic aspects of software languages development rather than aspects of engineering a specific language. In particular, SLE is interested in principled engineering approaches and techniques in the following areas: * Language Design and Implementation * Approaches and methodologies for language design * Static semantics (e.g., design rules, well-formedness constraints) * Techniques for behavioral / executable semantics * Generative approaches (incl. code synthesis, compilation) * Meta-languages, meta-tools, language workbenches * Language Validation * Verification and formal methods for languages * Testing techniques for languages * Simulation techniques for languages * Language Integration and Composition * Coordination of heterogeneous languages and tools * Mappings between languages (incl. transformation languages) * Traceability between languages * Deployment of languages to different platforms * Language Maintenance * Software language reuse * Language evolution * Language families and variability * Domain-specific approaches for any aspects of SLE (design, implementation, validation, maintenance) * Empirical evaluation and experience reports of language engineering tools * User studies evaluating usability * Performance benchmarks * Industrial applications ### Types of Submissions * **Research papers**: These should report a substantial research contribution to SLE or successful application of SLE techniques or both. Full paper submissions must not exceed 12 pages including bibliography in ACM SIGPLAN acmart conference style (http://www.sigplan.org/Resources/Author/) * **Tool papers**: Because of SLE's interest in tools, we seek papers that present software tools related to the field of SLE. Selection criteria include originality of the tool, its innovative aspects, and relevance to SLE. Any of the SLE topics of interest are appropriate areas for tool demonstrations. Submissions must provide a tool description of 4 pages including bibliography in ACM SIGPLAN acmart conference style (http://www.sigplan.org/Resources/Author/) and a demonstration outline including screenshots of up to 6 pages. Tool demonstrations must have the keywords “Tool Demo” or “Tool Demonstration” in the title. The 4-page tool description will, if the demonstration is accepted, be published in the proceedings. The 6-page demonstration outline will be used by the program committee only for evaluating the submission. * **Industrial papers**: These should describe real-world application scenarios of SLE in industry, explained in their context with an analysis of the challenges that were overcome and the lessons which the audience can learn from this experience. Industry paper submissions must not exceed 6 pages including bibliography in ACM SIGPLAN acmart conference style (http://www.sigplan.org/Resources/Author/) * **New ideas / vision papers**: New ideas papers should describe new, non-conventional SLE research approaches that depart from standard practice. They are intended to describe well-defined research ideas that are at an early stage of investigation. Vision papers are intended to present new unifying theories about existing SLE research that can lead to the development of new technologies or approaches. New ideas / vision papers must not exceed 4 pages including bibliography in ACM SIGPLAN acmart conference style (http://www.sigplan.org/Resources/Author/) ### Artifact evaluation SLE will for the second year use an evaluation process for assessing the quality of artifacts on which papers are based. The aim of this evaluation process is to foster a culture of experimental reproducibility as well as a higher quality in the research area as a whole. Authors of papers accepted for SLE 2017 will be invited to submit artifacts. Any kind of artifact that is presented in the paper, supplements the paper with further details, or underlies the paper can be submitted. This includes, for instance, tools, grammars, metamodels, models, programs, algorithms, scripts, proofs, datasets, statistical tests, checklists, surveys, interview scripts, visualizations, annotated bibliographies, and tutorials. The submitted artifacts will be reviewed by a dedicated Artifact Evaluation Committee (AEC). Artifacts that live up to the expectations created by the paper will receive a badge of approval from the AEC. The approved artifacts will be invited for inclusion in the electronic conference proceedings published in the ACM Digital Library. This will ensure the permanent and durable storage of the artifacts alongside the published papers fostering the repeatability of experiments, enabling precise comparison with alternative approaches, and helping the dissemination of the author’s ideas in detail. Participating in the artifact evaluation and publishing approved artifacts in the ACM Digital Library is voluntary. However, we strongly encourage authors to consider this possibility as the availability of artifacts will greatly benefit readers of papers and increase the impact of the work. Note that the artifact evaluation cannot affect the acceptance of the paper, because it only happens after the decision about acceptance has been made. ### Publications All submitted papers will be reviewed by at least three members of the program committee. All accepted papers, including tool papers, industrial papers and new ideas / vision papers will be published in ACM Digital Library. Selected accepted papers will be invited to a special issue of the Computer Languages, Systems and Structures (COMLAN) journal. ### Awards * **Distinguished paper**: Award for most notable paper, as determined by the PC chairs based on the recommendations of the program committee. * **Distinguished reviewer**: Award for distinguished reviewer, as determined by the PC chairs using feedback from the authors. * **Distinguished artifact**: Award for the artifact most significantly exceeding expectations, as determined by the AEC chairs based on the recommendations of the artifact evaluation committee. ### Program Committee Marjan Mernik (co-chair), University of Maribor, Slovenia Bernhard Rumpe (co-chair), RWTH Aachen University, Germany Christian Berger, Chalmers, Sweden Mark van den Brand, TU Eindhoven, The Netherlands Ruth Breu, University of Innsbruck, Austria Jordi Cabot, ICREA, Spain Walter Cazzola, University of Milan, Italy Marsha Chechik, University of Toronto, Canada Tony Clark, Middlesex University, UK Tom Dinkelaker, Ericsson, Germany Bernd Fischer, Stellenbosch University, South Africa Sebastian Gerard, CEA, France Jeff Gray, University of Alabama, USA Esther Guerra, Autonomous University of Madrid, Spain Michael Homer, Victoria University of Wellington, New Zealand Ralf Lämmel, University of Koblenz-Landau, Germany Tihamer Levendovszky, Microsoft, USA Gunter Mussbacher, McGill University, Canada Terence Parr, University of San Francisco, USA Jaroslav Porubän, University of Košice, Slovakia Jan Ringert, Tel Aviv University, Israel Julia Rubin, University of British Columbia, Canada Tony Sloane, Macquarie University, Australia Eugene Syriani, University of Montreal, Canada Emma Söderberg, Google, Denmark Eric Van Wyk, University of Minnesota, USA Jurgen Vinju, CWI, Netherlands Eric Walkingshaw, Oregon State University, USA Andreas Wortmann, RWTH Aachen University, Germany Tian Zhang, Nanjing University, China ### Contact For any question, please contact the organizers via email: sle2017(a)inria.fr

June 2, 2017