- Esug-list - lists.esug.org

Re: ESUG call for a conference chair

by Francisco Garau

Hey Stef, I understand your frustration, and I can only imagine the effort you've put into organizing ESUG conferences year after year. Even though I haven't participated as much as I would have liked in past conferences, I truly appreciate all the work and energy you've poured into the Smalltalk community—and you've never asked for anything in return. I probably won't be able to attend this year, but I'd be happy to help with the organization and coordination of the remaining tasks. I'll reach out to you privately to discuss how I can contribute. Thanks for everything you do. Francisco On Fri, 6 Feb 2026 at 06:35, stephane ducasse via Esug-list < esug-list(a)lists.esug.org> wrote: > Hello people > > Even if I loved ESUG conference and IWST is a major important step for > many > young Smalltalkers, I decided that I do not want to organise ESUG this > year. > So far I will continue the discussions with the local organiser for the > budget, set up the > information on the web site and I will contact the video guys but I think > that it will be the maximum > I will do. > > So let me know if some of you want to join the effort because > I’m exhausted and fed up also by all the free good energy that I spent > on Smalltalk survival. Sometimes I do not think that this is either > considered nor valuable. > > I have the impression that many people like to play in their > own little places and just like to eat cookies others put on the table. > I do not have free cookies anymore. > > Contact me privately if you want to help. > > S. > > _______________________________________________ > Esug-list mailing list -- esug-list(a)lists.esug.org > To unsubscribe send an email to esug-list-leave(a)lists.esug.org >

Feb. 6, 2026

ESUG call for a conference chair

by stephane ducasse

Hello people Even if I loved ESUG conference and IWST is a major important step for many young Smalltalkers, I decided that I do not want to organise ESUG this year. So far I will continue the discussions with the local organiser for the budget, set up the information on the web site and I will contact the video guys but I think that it will be the maximum I will do. So let me know if some of you want to join the effort because I’m exhausted and fed up also by all the free good energy that I spent on Smalltalk survival. Sometimes I do not think that this is either considered nor valuable. I have the impression that many people like to play in their own little places and just like to eat cookies others put on the table. I do not have free cookies anymore. Contact me privately if you want to help. S.

Feb. 6, 2026

Re: ESUG Mailinglist: Server work next 24h

by Marcus Denker

Hello, The list server update is done. Marcus > On 20 Jan 2026, at 21:06, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > Hi, > > We are updating the ESUG list server. > > Please wait with sending messages for ~24 hours > > I will send another mail when the change is done > > Marcus

Jan. 22, 2026

ESUG Mailinglist: Server work next 24h

by Marcus Denker

Hi, We are updating the ESUG list server. Please wait with sending messages for ~24 hours I will send another mail when the change is done Marcus

Jan. 20, 2026

UKSTUG Meeting: Kasper Østerbye - AI Inside Pharo - 28 January 2026

by UK Smalltalk

This talk explores what it means to work with AI from inside a live Pharo system rather than treating AI as an external chatbot. I will demonstrate experiments where AI models are invoked directly from the Playground, including a concrete implementation of conversation history (AIAHistory) and experiments across multiple models and providers. Rather than focusing on code generation, the emphasis is on workflows: how different conversation structures affect results, how styles and constraints can be imposed on generated comments, and how AI systems can be inspected for systematic errors and limitations. Examples include documentation support, UML generation (via PlantUML), and experiments in automated paper review. The talk is experimental in nature and rooted in Smalltalk’s strengths: reflection, live objects, and tools that are part of the system rather than bolted on. The goal is not to present a finished framework, but to share concrete insights, failures, and possibilities for AI as a native Pharo tool. Kasper Østerbye ( https://github.com/kasperosterbye ) is a retired computer science researcher with a long background in programming languages and live systems, including decades of work with Smalltalk and Pharo. He now explores how AI models can be integrated as native tools inside a running Pharo system, focusing on conversation structure, systematic failures, and tool design rather than automation alone. This will be an online meeting. If you'd like to join us, please sign up in advance on the meeting's Meetup page ( https://www.meetup.com/ukstug/events/311265921/ ) to receive the meeting details.

Jan. 15, 2026

Master Internship sponsorship

by Noury Bouraqadi

Hi, My lab has funding for several Master's degree internship positions. These are likely to be the first step to PhD positions. - Topics are related to Software Engineering with applications to Robotics, IoT, Digital Twins, and AI - Duration: 5 months - Funding: about 630 euros / month - Location: Douai, Lille area (30km), France Application: send me a CV with a short email introducing yourself and your background. Best, Noury Bouraqadi IMT Nord Europe France

Jan. 15, 2026

Re: [Pharo-users] Looking for Metacello beta testers

by stephaneducasse＠mailo.com

Hi domenico Yes we want to know if people can load their project using baselines. S On 29 Dec 2025 at 13:40 +0100, Domenico Cipriani via Esug-list <esug-list(a)lists.esug.org>, wrote: > Hello, I would like to help. > what should I do? Load all my packages in a new Pharo 14 alpha and check if everything works? > best. > d > > On Mon, Dec 29, 2025 at 9:56 AM stephane ducasse via Pharo-users <pharo-users(a)lists.pharo.org> wrote: > > Hello > > > > Under the radar, we are actively continiously cleaning Pharo deep core so that we can work > > on new features. > > > > For metacello, in Pharo 13 we introduced a strict mode (so that we can detect hidden dependencies), > > and other loading features to support module experimentations. It will make Pharo code more robust > > in the long term. > > > > Since a couple of months we are actively simplifying/cleaning Metacello (as the version available in Pharo) because we want to introduce new features such as the possibility to force the reload of baselines and others. > > > > Now the unit test coverage of metacello is quite low and we do not use/know all the features > > that are available and that you may rely on. > > > > So we would love to have beta testers that can just try to load their code in Pharo 14 alpha > > and report potential bugs or features drop we would have introduced. > > > > So do not hesitate and this is a nice way to help pharo > > > > S. > _______________________________________________ > Esug-list mailing list -- esug-list(a)lists.esug.org > To unsubscribe send an email to esug-list-leave(a)lists.esug.org >

Dec. 29, 2025

Re: [Pharo-users] Looking for Metacello beta testers

by Domenico Cipriani

Hello, I would like to help. what should I do? Load all my packages in a new Pharo 14 alpha and check if everything works? best. d On Mon, Dec 29, 2025 at 9:56 AM stephane ducasse via Pharo-users < pharo-users(a)lists.pharo.org> wrote: > Hello > > Under the radar, we are actively continiously cleaning Pharo deep core so > that we can work > on new features. > > For metacello, in Pharo 13 we introduced a strict mode (so that we can > detect hidden dependencies), > and other loading features to support module experimentations. It will > make Pharo code more robust > in the long term. > > Since a couple of months we are actively simplifying/cleaning Metacello > (as the version available in Pharo) because we want to introduce new > features such as the possibility to force the reload of baselines and > others. > > Now the unit test coverage of metacello is quite low and we do not > use/know all the features > that are available and that you may rely on. > > So we would love to have beta testers that can just try to load their code > in Pharo 14 alpha > and report potential bugs or features drop we would have introduced. > > So do not hesitate and this is a nice way to help pharo > > S.

Dec. 29, 2025

Looking for Metacello beta testers

by stephane ducasse

Hello Under the radar, we are actively continiously cleaning Pharo deep core so that we can work on new features. For metacello, in Pharo 13 we introduced a strict mode (so that we can detect hidden dependencies), and other loading features to support module experimentations. It will make Pharo code more robust in the long term. Since a couple of months we are actively simplifying/cleaning Metacello (as the version available in Pharo) because we want to introduce new features such as the possibility to force the reload of baselines and others. Now the unit test coverage of metacello is quite low and we do not use/know all the features that are available and that you may rely on. So we would love to have beta testers that can just try to load their code in Pharo 14 alpha and report potential bugs or features drop we would have introduced. So do not hesitate and this is a nice way to help pharo S.

Dec. 29, 2025

[DEBT 2026] Future Debugging Techniques Call for Papers, submission 7th of March 2026

by Steven Costiou

DEBT 2026: Call for Papers ================================================================================ DEBT 2026, Workshop co-located with ECOOP 2026, Brussels, Belgium Fourth Workshop on Future Debugging Techniques (https://2026.ecoop.org/home/debt-2026#Call-for-Papers) ================================================================================ Important Dates ----------------------- * Abstract submission deadline: Sat 28 Feb 2026 * Paper submission deadline: Sat 7 Mar 2026 * Author notification: Wed 15 Apr 2026 * Workshop: Monday 29 June 2026 ================================================================================ DEBT’26 is looking to advance state-of-the-art to debug modern software. We welcome researchers from all related areas aimed at helping with the hard task of diagnosing the root cause of bugs, including dynamic and static debugging techniques, online and postmortem debuggers, delta debugging, automatic bug finding, novel visualization techniques for debugging programs, etc. The workshop aims to gather the community and foster discussion from different perspectives. That is why we seek submissions in the form of papers as well as talks and tool demonstrations. The workshop is a venue for all approaches to debugging. A non-exclusive list of topics of interest is: * Debugging techniques, from static to dynamic techniques. * Innovative visualisation techniques. * Techniques targeted specific programming models and execution models (e.g., concurrent and parallel programming, microservices, distributed ledgers, web, etc. ) or hardware (e.g., debugging micro-controllers, mobile devices, Big Data applications, etc.). * Case studies and evaluation of such techniques, e.g., user studies on visualisation tools, debuggers, etc. * Surveys, taxonomies of bugs and bug patterns, and current practices/uses of debugging approaches. Papers must be formatted according to the guidelines for ACM sigplanpapers (\documentclass[sigplan,screen]{acmart}), seehttps://www.sigplan.org/Resources/Author/ <https://www.sigplan.org/Resources/Author/>for details. Submissions should be made via Easychair using the following link:https://easychair.org/conferences/?conf=debt2026 <https://easychair.org/conferences/?conf=debt2026> The accepted papers will be published in the ACM Digital Library, though authors will be able to opt out of this publication, if desired. At least one author of an accepted paper must register for the workshop and attend the event to present the work, and participate in the discussions. AUTHORS TAKE NOTE: The official publication date is the date the proceedings are made available in the ACM Digital Library. This date may be up to two weeks prior to the first day of your conference. The official publication date affects the deadline for any patent filings related to published work. Workshop Organizers --------------------------- * Burcu Kulahcioglu Ozkan, Delft University of Technology, Netherlands * Steven Costiou, Centre Inria de l’Université de Lille, France For more information see: https://2026.ecoop.org/home/debt-2026

Dec. 24, 2025