- Pharo-dev - lists.pharo.org

Fwd: IWST deadline extension
by Guillermo Polito March 28, 2025

March 28, 2025

Apologies for multiple receptions! > DÃ©but du message rÃ©expÃ©diÃ© : > > De: Guillermo Polito <guillermopolito(a)gmail.com> > Objet: IWST deadline extension > Date: 28 mars 2025 Ã 5:08:37â¯PM UTC+1 > Ã: Gordana Rakic via Esug-list <esug-list(a)lists.esug.org> > > Dear all, > > due to several requests, we have extended the submission deadlines for the call for presentations. > Please check the info below: > > -------- > > IWST is the International Workshop on Smalltalk Technologies. The goal of the workshop is to create a forum around contributions and experiences in building or using technologies related to Smalltalk. While the maturity of presented ideas and results is not crucial, their presentation is expected to trigger discussion and exchange of ideas. The topics of your paper can be on all aspects of Smalltalk, theoretical as well as practical. Authors are invited to submit research articles or industrial papers. > > https://esug.org/2025-Conference/IWST2025.html > > This year we will again have two different tracks: > > Two-Round Paper Submission. As in the previous year, submission will be in two rounds: > Extended abstracts are submitted to present at the conference > Later, full/short papers are submitted for proceedings publications > > Presenting Previously Published Works. We also invite authors of contributions related to IWST's topics, accepted for publication in Journals and Proceedings of top-rated international conferences within the previous 2 years, to submit an abstract and present their published results to the IWST workshop collocated with ESUG. Authors will be invited to present their paper after checking that the submission meets the above criteria. Having the submissions already reviewed and accepted by the peers, they will not be reviewed again for technical content. > Important Dates > > Extended abstract submission deadline: April 7th, 2025 > Already Published Papers Abstract submission deadline: April 7th, 2025 > Extended abstract notification deadline: April 14th, 2025 AoE > > Already Published Papers Abstract notifications: April 14th, 2025 AoE > Full/short paper submission deadline: May 19th, 2025 AoE > > Workshop: July 1-4, 2025 > > Best regards, > IWST team

1 0

Re: [Pharo-users] "Introducing Hera: Gherkin-style tests" â New blog post on all: objects all: theTime
by Koen De Hondt March 28, 2025

March 28, 2025

Hi Guille, > I wonder, are there any good practices/recommendations regarding how to share state between steps? I think there is basically no difference with a unit test. As I wrote in https://all-objects-all-the-time.st/#/blog/posts/10, under "Shared setup and teardownâ, there are a few different ways to cope with different state required by different tests on the same class. My advice would be to create a new class if tests require different state. So I would answer yes to your question "Should this scenario be in a separate feature (shared state?), and all states related to this be in the shared state?â While shared state may be confusing in a unit test, in Hera, and also in Cucumber for Ruby, people can use traits (or Ruby modules) to group steps that use the same state. That way, the different states required by different scenarios can be nicely separated. Even if there are no traits, like in VisualWorks, helper classes can be used to group steps, and instances of those helper classes can carry state. > What kind of heuristics do people use to say things like: > - ok, these two things will be two scenarios of the same feature > - and here, these two need to be in separate features That is a good question. Given that a feature contains different scenarios, people would typically group all scenarios together. But that is not required. You can have different features files in Cucumber that describe different aspects of the same feature (the âFeature:â line at the top would have the same name). In Hera, it would result in different feature methods on different classes. Splitting up a feature is also a way to keep the tests maintainable. > I imagine that a âpuristâ (:D) would try to make features more business-oriented. > But I cannot stop thinking that some âease of implementationâ can creep inside if they simplify the test writing. Yes, features are business-oriented, as they are used to describe acceptance criteria (that is why Heraâs test class is called HeraAcceptanceTest). I guess that with "ease of implementationâ you mean that people are tempted to write imperative-style steps, rather than declarative-style steps. For instance, one can write imperative-style steps like this: Given I am on the sign-in page When I enter my email address in the email field And I enter my password in the password field And I press the âSign inâ button Then I see the home page while a declarative style would result in: Given I am signed in where the latter makes abstraction of how signing in should be done. Letâs discuss more at the Pharo Sprint today. Thank you for the support and the good feedback. Best regards, Koen > On 10 Mar 2025, at 15:16, Guillermo Polito <guillermopolito(a)gmail.com> wrote: > > Hi Koen! > > This is nice indeed! > > I wonder, are there any good practices/recommendations regarding how to share state between steps? > > For example, > > Letâs say I have a scenario: > > - two browsers do not share state > given that I open *a browser* > and I open *another* browser > when I select Y on the first browser > then the first browser selected blah is X > > Should this scenario be in a separate feature (shared state?), and all states related to this be in the shared state? > > What kind of heuristics do people use to say things like: > - ok, these two things will be two scenarios of the same feature > - and here, these two need to be in separate features > > I imagine that a âpuristâ (:D) would try to make features more business-oriented. > But I cannot stop thinking that some âease of implementationâ can creep inside if they simplify the test writing. > > Do you have some experience on these things? > > G > >> Le 9 mars 2025 Ã 10:18â¯PM, Richard O'Keefe <raoknz(a)gmail.com> a Ã©crit : >> >> I was working on Gherkin-for-Smalltalk myself, but hadnât got nearly this far. You have taken a radically different approach from mine, and I have to say that yours is more Smalltalkish than mine. This is brilliant stuff and i look forward to the release. >> >> As one of my previous managers used to say, âyouâre a hero!â >> >> >> On Mon, 10 Mar 2025 at 8:20â¯AM, Koen De Hondt <koen(a)all-objects-all-the-time.st <mailto:koen@all-objects-all-the-time.st>> wrote: >>> Dear Pharo users and developers, >>> >>> In my series of blog posts on testing, I published a new post on tools for running Gherkin-style test scenarios in Pharo. See https://all-objects-all-the-time.st/#/blog/posts/13. It is an introduction. Future posts will dig into the details. >>> >>> As always, all feedback is welcome. >>> >>> Happy reading! >>> >>> Ciao, >>> Koen >>> >

1 0

"Introducing Hera: Gherkin-style tests" â New blog post on all: objects all: theTime
by Koen De Hondt March 19, 2025

March 19, 2025

Dear Pharo users and developers, In my series of blog posts on testing, I published a new post on tools for running Gherkin-style test scenarios in Pharo. See https://all-objects-all-the-time.st/#/blog/posts/13. It is an introduction. Future posts will dig into the details. As always, all feedback is welcome. Happy reading! Ciao, Koen

2 2

ESUG 2025 Registration opened
by stephane ducasse March 18, 2025

March 18, 2025

Hello Just a little email to announce that the registration for the conference is now opened. https://registration.esug.org/ESUG <https://registration.esug.org/ESUG> And do not forget to submit your talk. S > > ESUG 2025 Call for Presentations > from Tuesday 1st to 4 th of July 2025 > Gdansk Poland > https://esug.github.io <https://esug.github.io/> > https://esug.github.io/2025-Conference/conf2025.html > > > You can support the ESUG conference in many different ways: > - Sponsor the conference. New sponsoring packages are described at https://esug.org/become_sponsor.html > - Submit a talk, software to the award competition, or a paper to IWST https://esug.github.io/2025-Conference/IWST2025.html > - Attend the conference. We'd like to beat the previous record of attendance (180 people at Koln 2019)! > - Students can get free registration and hosting if they enroll in the the Student Volunteers program. See below. > > New this year: a 3 days lectures will be organised before the conference following the isLoop summerschool principle > https://isloop.pharo.org/ > > ## Developers Forum: International Smalltalk Developers Conference > > We are looking for YOUR experience on using Smalltalk. You will have 30 min for presentations and 45 min for hands-on tutorials. > The list of topics for the normal talks and tutorials includes, but is not limited to the following: > - XP practices, Development tools, Experience reports > - Model-driven development, Web development, Team management > - Meta-Modeling, Security, New libraries & frameworks > - Educational material, Embedded systems and robotics > - SOA and Web services, Interaction with other programming languages > - Teaching Pearls and Show us Your Business > > > We added two types of sessions in addition to the regular talks and ''Show us your project'' sessions. > - Show your business in a 10-minute session (Get prepared!!) > - Teaching pearls: we want some sessions on how to teach some design aspects. We want your tip and tricks to teach Smalltalk or OOP. > We expect to have several 10 to 15-minute sessions aggregated. > > ### How to submit? > > Make a Pull Request here https://github.com/ESUG/esug.github.io/tree/source/2025-Conference/talks > [Or but only if you are not connected to the worldâ¦ send an email to stephane.ducasse(a)inria.fr <mailto:stephane.ducasse@inria.fr>] > > Title: [ESUG 2025] Please follow the template below the email will be automatically processed! > Name: > Email: > Abstract: > Bio: > > ## Call for Student Volunteers > Student volunteers help keep the conference running smoothly; in return, they have free accommodations, while still having most of the time to enjoy the conference. > > Pay attention: the places are limited so do not wait till the last minute to apply. > > Conference details: > Send an email to Steven Costiou <steven.costiou at inria.fr <http://inria.fr/>> and Oleksandr Zaitsev <olk.zaytsev at gmail.com <http://gmail.com/>> with: > > title: [ESUG 2025 Student] > name, > gender, > university/school, > country, > email address > want to attend the isLoop lectures (https://isloop.pharo.org/) > short description of you and why you are interested in participating > > For which period is accommodation covered? Accommodation is covered from Monday 30 th June to 4th July 2025. > If you attend the isLoop lectures the saturday and sunday nights will be covered. > Students will be hosted in student rooms. ESUG additionally covers the lunches during the week and one dinner. > > This year the isLoop schools is organized the Satruday, Sunday and Monday before the conference (soon at https://isloop.pharo.org/) > > Duties include handling registration as people arrive at the conference, collecting presentation slides for ESUG right after the presentation is given, being present at an information desk to answer questions, and generally being helpful. Student volunteering makes the conference better, takes a fairly small amount of time, and doesn't significantly interfere with enjoying and learning from the conference. Please note, that this role requires discipline and constant attention to all attendees. > > Information about hotel > Student Volunteer rooms are booked at (to be announced). If you are a student volunteer, do not book yourself, we have arranged the booking already! > > > > > > > > > > StÃ©phane Ducasse > http://stephane.ducasse.free.fr <http://stephane.ducasse.free.fr/> > 06 30 93 66 73 > > "If you knew today was your last day on earth, what would you do differently? ....ESPECIALLY if, by doing something different, today might not be your last day on earth.â Calvin & Hobbes StÃ©phane Ducasse http://stephane.ducasse.free.fr 06 30 93 66 73 "If you knew today was your last day on earth, what would you do differently? ....ESPECIALLY if, by doing something different, today might not be your last day on earth.â Calvin & Hobbes

1 0

ESUG 2025 CFP
by stephane ducasse Feb. 26, 2025

Feb. 26, 2025

Please distribute! ESUG 2025 Call for Presentations from Tuesday 1st to 4 th of July 2025 Gdansk Poland https://esug.github.io https://esug.github.io/2025-Conference/conf2025.html You can support the ESUG conference in many different ways: - Sponsor the conference. New sponsoring packages are described at http://www.esug.org/supportesug/becomeasponsor/ - Submit a talk, software to the award competition, or a paper to IWST http://https://esug.github.io/2025-Conference/IWST2025.html - Attend the conference. We'd like to beat the previous record of attendance (180 people at Koln 2019)! - Students can get free registration and hosting if they enroll in the the Student Volunteers program. See below. New this year: a 3 days lectures will be organised before the conference following the isLoop summerschool principle https://isloop.pharo.org/ ## Developers Forum: International Smalltalk Developers Conference We are looking for YOUR experience on using Smalltalk. You will have 30 min for presentations and 45 min for hands-on tutorials. The list of topics for the normal talks and tutorials includes, but is not limited to the following: - XP practices, Development tools, Experience reports - Model-driven development, Web development, Team management - Meta-Modeling, Security, New libraries & frameworks - Educational material, Embedded systems and robotics - SOA and Web services, Interaction with other programming languages - Teaching Pearls and Show us Your Business We added two types of sessions in addition to the regular talks and ''Show us your project'' sessions. - Show your business in a 10-minute session (Get prepared!!) - Teaching pearls: we want some sessions on how to teach some design aspects. We want your tip and tricks to teach Smalltalk or OOP. We expect to have several 10 to 15-minute sessions aggregated. ### How to submit? Make a Pull Request here https://github.com/ESUG/esug.github.io/tree/source/2025-Conference/talks [Or but only if you are not connected to the worldâ¦ send an email to stephane.ducasse(a)inria.fr] Title: [ESUG 2025] Please follow the template below the email will be automatically processed! Name: Email: Abstract: Bio: ## Call for Student Volunteers Student volunteers help keep the conference running smoothly; in return, they have free accommodations, while still having most of the time to enjoy the conference. Pay attention: the places are limited so do not wait till the last minute to apply. Conference details: Send an email to Steven Costiou <steven.costiou at inria.fr> and Oleksandr Zaitsev <olk.zaytsev at gmail.com> with: title: [ESUG 2025 Student] name, gender, university/school, country, email address want to attend the isLoop lectures (https://isloop.pharo.org/) short description of you and why you are interested in participating For which period is accommodation covered? Accommodation is covered from Monday 30 th June to 4th July 2025. If you attend the isLoop lectures the saturday and sunday nights will be covered. Students will be hosted in student rooms. ESUG additionally covers the lunches during the week and one dinner. This year the isLoop schools is organized the Satruday, Sunday and Monday before the conference (soon at https://isloop.pharo.org/) Duties include handling registration as people arrive at the conference, collecting presentation slides for ESUG right after the presentation is given, being present at an information desk to answer questions, and generally being helpful. Student volunteering makes the conference better, takes a fairly small amount of time, and doesn't significantly interfere with enjoying and learning from the conference. Please note, that this role requires discipline and constant attention to all attendees. Information about hotel Student Volunteer rooms are booked at (to be announced). If you are a student volunteer, do not book yourself, we have arranged the booking already! StÃ©phane Ducasse http://stephane.ducasse.free.fr 06 30 93 66 73 "If you knew today was your last day on earth, what would you do differently? ....ESPECIALLY if, by doing something different, today might not be your last day on earth.â Calvin & Hobbes

1 1

Fostering a respectful Pharo Community
by Esteban Lorenzano Feb. 20, 2025

Feb. 20, 2025

Hello, Pharo is more than just a programming language and a development environmentâit is, above all, a community. As a community, we uphold certain values that form the foundation of our interactions, both technical and non-technical. We believe in human rights and the right of all individuals to live and grow in an environment that respects them, regardless of their choices. With that in mind, we adhere to the principle of the paradox of tolerance: while we welcome open discussions, we do not support intolerance, hate speech, or any attempts to introduce such attitudes into our community. We recognize that we are not just programmers but multidimensional social individuals, and discussions may (and must) sometimes extend beyond strictly technical topics. However, we expect these conversations to remain within the respectful boundaries that ensure a welcoming space for everyone. In this sense, we want to apologize to anyone that may have feel discomfort or concern by the previous discussion. Our goal is to foster an inclusive and supportive environment where all members feel safe and valued. Thank you for your understanding and for being part of Pharo. Esteban, on behalf of the Pharo Board

1 0

Pharo on Bluesky and Mastodon
by Marcus Denker Feb. 14, 2025

Feb. 14, 2025

Hello, Bluesky: https://bsky.app/profile/pharoproject.bsky.social We are on Mastodon, too (since 2018!) https://mastodon.social/@pharoproject Marcus

1 0

Pharo News of the Week 06/2025
by Marcus Denker Feb. 7, 2025

Feb. 7, 2025

# Pharo News of the Week 06/2025 - [ANN] GSoC 2025 Mentors/Topics needed: https://www.pharo.org/news/2025-01-30-GSOC2025.html - [ANN] We are now on bluesky: https://bsky.app/profile/pharoproject.bsky.social - [ANN] and of course mastodon since a long time: https://mastodon.social/@pharoproject If you want to add your news to this list, use this form: https://tinyurl.com/4c89buy4 # The week on the Pharo Issue Tracker # Pharo 11 - Update version in #documentBrowser for BaselineOfPharo for Pharo 11 to âv1.0.4â #17766 https://github.com/pharo-project/pharo/pull/17766 # Pharo 12 - Backport changes to not restore ffi methods if they are not installed #17780 https://github.com/pharo-project/pharo/pull/17780 # Fixes - Fix opening of the Dependency analyzer #17763 https://github.com/pharo-project/pharo/pull/17763 - Fix browsing of methods in Epicea #17764 https://github.com/pharo-project/pharo/pull/17764 - Do not resume running process #17777 https://github.com/pharo-project/pharo/pull/17777 - Fixing browse in KMDescriptionPresenter #17776 https://github.com/pharo-project/pharo/pull/17776 - Fix cursor navigation #17772 https://github.com/pharo-project/pharo/pull/17772 - Fix save image dialog default values #17767 https://github.com/pharo-project/pharo/pull/17767 - 17563-propertyAtput-looks-bogus, #17754 https://github.com/pharo-project/pharo/pull/17754 # Features - Addition of new setting for using SpClosedWindowListPresenter or not #17757 https://github.com/pharo-project/pharo/pull/17757 # Code Completion - Branch: addingSetterToCoHeuristic #17782 https://github.com/pharo-project/pharo/pull/17782 # VM - Remove debugging code #911 https://github.com/pharo-project/pharo-vm/pull/911 - Simplify signal handler space calculation: use SIGSTKSZ, posix defined #910 https://github.com/pharo-project/pharo-vm/pull/910 # Newtools - changed menu bug display and updated baseline #970 https://github.com/pharo-spec/NewTools/pull/970 - Update world menu entry for the finder #982 https://github.com/pharo-spec/NewTools/pull/982 - Fix selection in save file presenter #980 https://github.com/pharo-spec/NewTools/pull/980 - Unsubscribe if user dont want to use the presenter anymore #977 https://github.com/pharo-spec/NewTools/pull/977 - Started to pass the stApplication in the open method #976 https://github.com/pharo-spec/NewTools/pull/976 - Moved IRMethod extension to OCIRMethod #975 https://github.com/pharo-spec/NewTools/pull/975 - Memory leak fix #972 https://github.com/pharo-spec/NewTools/pull/972 - adds property to morph when closed and remove it when unhidden #971 https://github.com/pharo-spec/NewTools/pull/971 # Tests - Skipping two tests to get the green bar for now. #17743 https://github.com/pharo-project/pharo/pull/17743 - Fix and improve WindowAnnouncementTest #17773 https://github.com/pharo-project/pharo/pull/17773 - Fix testMethodsOfTheClassShouldNotBeRepeatedInItsSuperclasses #17769 https://github.com/pharo-project/pharo/pull/17769 # Website - Update community.md: add bluesky link #84 https://github.com/pharo-project/pharo-website/pull/84 # Cleanups - Branch: 17675-Opal-Extension-symbolic-to-Debugging-Core #17735 https://github.com/pharo-project/pharo/pull/17735 - Branch: 17672-Rename-formatter-in-EFtests-to-avoid-spurious-sender-clash #17736 https://github.com/pharo-project/pharo/pull/17736 - Remove String>>isValidSelector #17741 https://github.com/pharo-project/pharo/pull/17741 - 17746-remove-ClassdeprecationRefactorings, Fixes #17746 #17747 https://github.com/pharo-project/pharo/pull/17747 - 17742-isSelectorSymbol-should-be-renamed-isUsedAsSelectorSymbol #17748 https://github.com/pharo-project/pharo/pull/17748 - 17667-remove-display-of-empty-sharedVariables-from-class-default-tempâ¦ #17749 https://github.com/pharo-project/pharo/pull/17749 - Branch: 17750-FormasText-from-MD-to-Form, #17751 https://github.com/pharo-project/pharo/pull/17751 - Branch: FixKMLeftInstanceVariable, #17758 https://github.com/pharo-project/pharo/pull/17758 - Removed Stuff linked to the presenter #17761 https://github.com/pharo-project/pharo/pull/17761 - Clean tool registry2 #17765 https://github.com/pharo-project/pharo/pull/17765

1 0

Re: [Pharo-users] "Book release: Application Building with Spec 2.0" â New blog post on all: objects all: theTime
by stephane ducasse Feb. 6, 2025

Feb. 6, 2025

Thanks. I have some other books under preparation :) S > On 1 Feb 2025, at 23:51, Mark O'Donoghue <mark.odonoghue.2010(a)gmail.com> wrote: > > Congratulation Stephane on completing this book. > > I feel it is crucial. It removes a major hurdle for new, part time and/or returning programmers to get what they need with a UI for their Pharo programs. > > For me, it also helps me advocating for Pharo with my colleagues. > > Cheers > Mark > > On Sun, 2 Feb 2025, 12:07 am stephane ducasse, <stephane.ducasse(a)inria.fr <mailto:stephane.ducasse@inria.fr>> wrote: >> Thanks. >> Writing this book was a daunting huge difficult exhausting task that took me around 4 years or more. >> >> This publisher is managed using a not so great Php software and I can tell you that you can feel it when >> you have to manage the books. >> >> S >> >>> On 30 Jan 2025, at 17:51, giorgio ferraris <giorgio.ferraris(a)gmail.com <mailto:giorgio.ferraris@gmail.com>> wrote: >>> >>> hello!, >>> >>> Thank you for the answer, I ordered the book today, please note that it still seems that is written in French. >>> >>> happy smalltalking >>> >>> >>> giorgio >>> >>> On Thu, Nov 7, 2024 at 1:23â¯PM Koen De Hondt <koen(a)all-objects-all-the-time.st <mailto:koen@all-objects-all-the-time.st>> wrote: >>>> Hi Giorgio, >>>> >>>> Thank you for reporting the issue. >>>> >>>> Yes, it is an error. We saw it a few days ago, but it has not been fixed yet. >>>> >>>> Best regards, >>>> Koen >>>> >>>>> On 7 Nov 2024, at 12:27, giorgio ferraris <giorgio.ferraris(a)gmail.com <mailto:giorgio.ferraris@gmail.com>> wrote: >>>>> >>>>> hello, >>>>> >>>>> The Amazon site says that the language is French. Is that an error? >>>>> >>>>> thanks >>>>> >>>>> ciao >>>>> >>>>> giorgio >>>>> >>>>> <Screenshot 2024-11-07 at 12.25.47.png> >>>>> >>>>> On Thu, Nov 7, 2024 at 6:32â¯AM Koen De Hondt <koen(a)all-objects-all-the-time.st <mailto:koen@all-objects-all-the-time.st>> wrote: >>>>>> Dear Pharo users and developers, >>>>>> >>>>>> It required an enormous effort to review, rewrite, and extend it, but I am happy to announce that it is finally here: the book on application building in Pharo with Spec 2.0. >>>>>> >>>>>> I wrote a blog post about it <https://all-objects-all-the-time.st/#/blog/posts/9>. Happy reading! >>>>>> >>>>>> Ciao, >>>>>> Koen >>>> >> >> StÃ©phane Ducasse >> http://stephane.ducasse.free.fr <http://stephane.ducasse.free.fr/> >> 06 30 93 66 73 >> >> "If you knew today was your last day on earth, what would you do differently? ....ESPECIALLY if, by doing something different, today might not be your last day on earth.â Calvin & Hobbes >> >> >> >> >> StÃ©phane Ducasse http://stephane.ducasse.free.fr 06 30 93 66 73 "If you knew today was your last day on earth, what would you do differently? ....ESPECIALLY if, by doing something different, today might not be your last day on earth.â Calvin & Hobbes

1 0

Pharo Association 2024 Review
by tesonep＠gmail.com Feb. 5, 2025

Feb. 5, 2025

Dear Pharo Association members, Pharoers and Smalltalkers from all over the world We are writing you to thank you again for your support of the Pharo Association. With your help, we are able to perform a lot of activities to increase the impact of Pharo, enlarge its community and have a better programming life for everyone. For the people who are not members of the association, we take the opportunity to tell you all the accomplishments of the association last year and invite you to participate in any of the forms our association provides. We want to profit this time of the year to tell you the most important actions that the association has supported the last years. - *Infrastructure for Pharo: *as an association, we support the maintenance of the infrastructure used by Pharo. We provided the funds for the hosting of Pharo services (website, file server, mailing lists) and domains. Most of the services that we daily use are supported by your help. Thanks for allowing the community to use the Pharo Launcher or getting an image from ZeroConf. - *Conference Sponsoring:* we all love to go to nice conferences and much more if there is Pharo-related content on it. This year as it is tradition we supported the *ESUG 2024 *conference. Having a place to interchange and to publish all the advances in Pharo is key to its development. - *Summer School: *With the objective of extending the Pharo community, in 2024, we sponsored a summer school at Split, Croatia about advanced object-oriented design with Pharo. Due to the nice reception and results, this year we are again sponsoring a summer school in February at Montpellier. - *Pharo Music: *Smalltalk has been always a language close to the arts, and Pharo is not an exception. This year, we heavily sponsored the development of Phausto, Coypu and CoypuIDE. *Phausto <https://github.com/lucretiomsp/phausto>* is a library and API that allows to use the FAUST compiler and its libraries (Functional Audio Stream) inside Pharo. *Coypu <https://github.com/lucretiomsp/Coypu>* is a package with methods and classes for Pharo designed for programming music on-the-fly, and it has its *IDE <https://github.com/pharo-graphics/CoypuIDE>* developed in Bloc. This tools has been presented in numerous technical and musical conferences, and in all of them they have generated a lot of attention and interest. We are much than happy with the results we are obtaining. - *Student Sponsoring:* we sponsored the access of students using Pharo to Summer Schools and visits to labs. We sponsored also the food and drinks of small meetings where students can learn and play with Pharo. This sponsoring is particularly important because often the labs are not allowed to pay trips of students, limiting the access to international students. Because of that, we sponsored students from Argentina (2), Serbia, Madagascar (3), Chile, and Bolivia. Without your support we would not be able to plant Pharo seeds all over the world. Your help is base to increase the community and to help all the people interested in Pharo. - *Book Sponsoring: *During last year, we have sponsored the write of 4 new books about Pharo. These books covers subjects for newcomers and experts, going from the style of code, testing and UI creation. All the books are available to the community (*https://books.pharo.org/ <https://books.pharo.org/>*) and even you can get a physical copy. We consider that we need to provide the material to let all the people interested to grow in their Pharo experience. We want to thank you again for your support as all the support we are getting are from our members. We remember you that you can renew or increase your subscription at *https://association.pharo.org <https://association.pharo.org/>*. Your support is really important for us because it enables us to do actions that would be almost impossible to do. Finally we remember you that we are always open to listen your opinions and suggestions, and to receive requests for sponsoring or support at *association(a)pharo.org <association(a)pharo.org>*. Sorry if you have got this mails from different channels. Thank you so much again, and we desired you and excellent new year! *Pharo Association*

1 0