@@ -263,13 +263,24 @@
+
Brought to you by
Advisory Board members:
- 
+ 
+
- 
+ 
+
-
+ 
+
+
+
+ +
Affiliate members:
+
+ 
+
+
+ Individual backers:
+
+
-
+
- Ondřej Španěl — https://www.orbisfabula.com/ +
@@ -283,6 +294,7 @@
Brought to you by
-
+
- Spotify
- Lunatech
- 47 Degrees
- Goldman Sachs diff --git a/events.html b/events.html index 46876030..38056f16 100644 --- a/events.html +++ b/events.html @@ -12,7 +12,7 @@
- {% assign events = site.data.events.scala_lunches.events %}
+
+ {% assign events = site.data.events.scala_lunches.events %}
+
Scala Lunches at EPFL
@@ -22,6 +22,12 @@ Scala Lunches at EPFL
{{site.data.events.scala_lunches.header}}
+ {% include event-block.html %}
+
+ Past Lunches
+ {% assign events = site.data.events.scala_lunches.past-events %}
{% include event-block.html %}
diff --git a/faqs.md b/faqs.md
index 4fab185b..37101e70 100644
--- a/faqs.md
+++ b/faqs.md
@@ -40,15 +40,13 @@ You may also be interested in
### Does the Scala Center control the development of Scala?
-No. Scala is developed by organizations and individual contributors all over the
-world. Lightbend (formerly Typesafe) will continue to maintain and evolve the
-stable Scala distribution.
+Not by itself. See our [Governance](https://www.scala-lang.org/governance/) page.
### Who owns Scala's code?
Scala is owned by EPFL. Contributors to Scala own their own contributions and
allow us to distribute that code under [Scala's Apache 2.0 License](http://scala-lang.org/license.html) by
-signing our [Contributors License Agreement (CLA)](https://www.lightbend.com/contribute/cla/scala).
+signing our [Contributors License Agreement (CLA)](https://contribute.akka.io/cla/scala).
### Have more questions?
diff --git a/jobs.md b/jobs.md
index 99916e7f..b0a5d99a 100644
--- a/jobs.md
+++ b/jobs.md
@@ -1,17 +1,3 @@
---
-layout: contact
+redirect_to: /
---
-
-## We're hiring!
-
-We're looking for motivated individuals to help us improve Scala's libraries and
-tools.
-
-Candidates must have a minimum of 3 years of experience developing in Scala, and
-have a demonstrated track record of communicating (written or talks) with the
-developer community. Several years experience participating in an open source
-community required.
-
-If getting paid to build up important community open source projects, and
-promoting, advancing, and supporting Scala, sounds like you, then drop us a line
-at scala.center@epfl.ch with your resume and GitHub profile.
diff --git a/minutes/_posts/2016-08-09-august-9-2016.md b/minutes/_posts/2016-08-09-august-9-2016.md
index aabc40dc..1c0d0b55 100644
--- a/minutes/_posts/2016-08-09-august-9-2016.md
+++ b/minutes/_posts/2016-08-09-august-9-2016.md
@@ -410,7 +410,7 @@ one spoke up strongly in favor.
#### ScalaBridge
Bill briefly described the new
-[ScalaBridge](http://www.scalabridge.org) effort. Its goal is
+ScalaBridge effort. Its goal is
"Building an inclusive Scala community with introductory programming
workshops for women", modeled on RailsBridge.
diff --git a/minutes/_posts/2017-12-01-december-1-2017.md b/minutes/_posts/2017-12-01-december-1-2017.md
index ac398dd1..5a52ddb5 100644
--- a/minutes/_posts/2017-12-01-december-1-2017.md
+++ b/minutes/_posts/2017-12-01-december-1-2017.md
@@ -198,7 +198,7 @@ when deciding whether to repeat in subsequent years.
Adriaan mentioned [Bridge Foundry](https://bridgefoundry.org) as a
worthy organization deserving sponsorship. They coordinate efforts
-such as [ScalaBridge](http://www.scalabridge.org), whose goal is
+such as ScalaBridge, whose goal is
"building an inclusive Scala community".
### Closing remarks
diff --git a/minutes/_posts/2023-07-26-july-26-2023.md b/minutes/_posts/2023-07-26-july-26-2023.md
index 3047fad9..a0dfbbac 100644
--- a/minutes/_posts/2023-07-26-july-26-2023.md
+++ b/minutes/_posts/2023-07-26-july-26-2023.md
@@ -48,6 +48,7 @@ Officers:
* also board member, representing Lunatech
* Darja Jovanovic (executive director), EPFL
* Julien Richard-Foy (technical director), EPFL
+* Martin Odersky (technical advisor), EPFL
* Seth Tisue (secretary), Lightbend
* also board member, representing Lightbend, subbing for Lukas Rytz
@@ -248,7 +249,7 @@ community page](https://scala-lang.org/community/).
### SCP-031: Ensure reachability of Scala websites
-The text of the Lukas and Seth's proposal is here:
+The text of Lukas and Seth's proposal is here:
* [SCP-031](https://github.com/scalacenter/advisoryboard/blob/main/proposals/031-scala-websites-vpn.md)
diff --git a/minutes/_posts/2023-10-17-october-17-2023.md b/minutes/_posts/2023-10-17-october-17-2023.md
index e959110d..0585b49a 100644
--- a/minutes/_posts/2023-10-17-october-17-2023.md
+++ b/minutes/_posts/2023-10-17-october-17-2023.md
@@ -40,6 +40,7 @@ Officers:
* also board member, representing Lunatech
* Darja Jovanovic (executive director), EPFL
* Sébastien Doeraene (interim technical director), EPFL
+* Martin Odersky (technical advisor), EPFL
* Seth Tisue (secretary), Lightbend
* also board member, representing Lightbend, subbing for Lukas Rytz
diff --git a/minutes/_posts/2024-02-07-february-7-2024.md b/minutes/_posts/2024-02-07-february-7-2024.md
new file mode 100644
index 00000000..612c7adf
--- /dev/null
+++ b/minutes/_posts/2024-02-07-february-7-2024.md
@@ -0,0 +1,167 @@
+---
+layout: contact
+---
+
+# Minutes of the 31st meeting of the Scala Center, Q4 2023
+
+Minutes are [archived](https://scala.epfl.ch/records.html) on the
+Scala Center website.
+
+## Summary
+
+The following agenda was distributed to attendees:
+[agenda](https://github.com/scalacenter/advisoryboard/blob/main/agendas/031-2023-q4.md).
+
+Center activities for the past quarter focused on Scala 3 features and
+compiler performance, Scala.js, the Scala Improvement Process, sbt 2,
+Scastie, Scala CLI, TASTy Query, Advent of Code, compiler sprees,
+Google Summer of Code, fundraising, and more.
+
+Details are below and in the Center's activity report:
+
+* [report](https://scala.epfl.ch/records/2023-Q4-activity-report.html)
+
+No new proposals were received this quarter.
+
+## Date, Time and Location
+
+The meeting took place virtually on Tuesday, February 7, 2024 at
+15:00 (UTC).
+
+Minutes were taken by Seth Tisue (secretary).
+
+## Attendees
+
+Officers:
+
+* Chris Kipp (chairperson)
+* Darja Jovanovic (executive director), EPFL
+* Sébastien Doeraene (interim technical director), EPFL
+* Martin Odersky (technical advisor), EPFL
+* Seth Tisue (secretary), Lightbend
+
+Board members:
+
+* Noel Markham, Xebia Functional
+* Paweł Marks, VirtusLab (subbing for Krzysztof Romanowski)
+* Claire McGinty, Spotify
+* Lukas Rytz, Lightbend
+* Daniela Sfregola, Morgan Stanley
+* Eugene Yokota, community representative
+
+## Technical report
+
+Seb, as interim technical director, summarized Scala Center activities
+since the last meeting. His remarks mainly consisted of brief
+highlights taken from the Center's more detailed Q4 quarterly activity
+report:
+
+* [report](https://scala.epfl.ch/records/2023-Q4-activity-report.html)
+
+And the Center's Q4 roadmap:
+
+* [roadmap](https://scala.epfl.ch/records/2023-Q4-roadmap.html)
+
+The following notes do not repeat the contents of the report and
+roadmap, but only supplement them.
+
+Martin offered congratulations to Eugene and the Center on getting sbt
+2.x initially compiling on Scala 3. Eugene mentioned that a number of
+"hacks" in the sbt codebase were no longer necessary on Scala 3, and
+that the new macro implementations were "safer" thanks to Scala 3.
+
+The Center declined to issue a ruling on whether Scala CLI is
+pronounced "Scala C.L.I." or "Scala Clee" :-)
+
+Chris asked about broader Scalafix improvements, as previously
+discussed in 2021 when
+[SCP-027](https://github.com/scalacenter/advisoryboard/blob/main/proposals/027-refactoring.md)
+was submitted. Seb said that hasn't been revisited recently but
+they'll take a second look if there is sufficient engineering time
+available this year.
+
+Seth observed that Scalafix seems underused in the community, and
+although it's not clear why. It could be because it's not well
+integrated enough with tooling, and/or insufficient documentation and
+publicity? And do people know where to find rules?
+
+Branching off the Scalafix discussion, Eugene observed that we don't
+have good centralized documentation and recommendations on what
+compiler flags are available and which ones should be enabled (in
+general, and also in specific scenarios such as cross-building).
+
+Chris praised the successful recent work on "quickfixes" in Scala 2.
+"I'm amazed how easy it is to trigger a quickfix and it makes me so
+happy every time it works." This connects to the Scalafix discussion
+because quickfixes and Scalafix overlap in purpose, and the compiler
+has information about user code that Scalafix may not.
+
+## Scala 2 report
+
+This was presented by Seth.
+
+At the time of the meeting, 2.12.19 was at the release-candidate
+stage, 2.13.13 was almost there, and the following forum threads were
+open for discussing the contents and timing of the two impending
+releases:
+
+* [Scala 2.13.13](https://contributors.scala-lang.org/t/scala-2-13-13-release-planning/6315)
+* [Scala 2.12.19](https://contributors.scala-lang.org/t/scala-2-12-19-release-planning/6216)
+
+After the meeting, the following threads were opened to discuss the
+next releases:
+
+* [Scala 2.12.20](https://contributors.scala-lang.org/t/scala-2-12-20-release-planning/6580)
+* [Scala 2.13.14](https://contributors.scala-lang.org/t/scala-2-13-14-release-planning/6581)
+
+The technical highlight of 2.13.13 is the introduction of
+`-Xsource:3-cross` as an alternative to `-Xsource:3`; the former is
+for crossbuilding, the latter for migration.
+
+## Community report
+
+Eugene led some brief discussion about the health of various segments
+of the community (Spark users, Typelevel, ZIO, Akka, and so forth).
+
+He also noted that his experience with co-organizing Scala Matsuri is
+that times are currently tough for conference organizers, especially
+in seeking sponsorship, likely because the job market in IT generally
+is weak, and sponsorship money is often motivated by recruiting.
+
+Darja said that she's very encouraged by all the signs she's seeing
+that conference and meetup activity are reviving, post-pandemic.
+
+Eugene also updated us on the health of the sbt plugin ecosystem.
+Many plugins have changed owners, dormant plugins are being revived,
+and many are now publishing to Maven Central. The Play and Pekko
+projects are among the drivers of this work.
+
+Chris asked the Center if a second community representative has
+been found yet. Darja says that a strong candidate has emerged
+and will hopefully join next quarter.
+
+## Management and financial report
+
+This was presented by Darja. Her report centered on fundraising. The
+Center is in need of new money, as a number of board members bowed out
+in 2023. The Center is pursuing various potential funding
+prospects. It seems that times are tough all over for open source
+funding. As part of bringing new members on board, some adjustments to
+the charter may be proposed, for example, to flexibly accommodate
+different sizes of company. Details remain to be seen.
+
+For practical reasons, and to the Center's regret, there is little
+likelihood of Scala Days happening in 2024. The Center is highly
+optimistic that it can be revived in 2025; doing that is a high
+priority. (There was a long discussion about various ways this
+might hypothetically play out.)
+
+There was also some discussion of what online services the Center
+should be using for publicity. One theme that came up is that some
+venues are better suited for interaction with the community, others
+best used only to broadcast announcements.
+
+## Conclusion
+
+We talked about what upcoming conferences we might see each other at,
+otherwise, see you online!
diff --git a/minutes/_posts/2024-04-25-april-25-2024.md b/minutes/_posts/2024-04-25-april-25-2024.md
new file mode 100644
index 00000000..c8dfd072
--- /dev/null
+++ b/minutes/_posts/2024-04-25-april-25-2024.md
@@ -0,0 +1,207 @@
+---
+layout: contact
+---
+
+# Minutes of the 32nd meeting of the Scala Center, Q1 2024
+
+Minutes are [archived](https://scala.epfl.ch/records.html) on the
+Scala Center website.
+
+## Summary
+
+The following agenda was distributed to attendees:
+[agenda](https://github.com/scalacenter/advisoryboard/blob/main/agendas/032-2024-q1.md).
+
+We were joined by two new board members, Dmitrii Naumenko (JetBrains)
+and Zainab Ali (community representative).
+
+Center activities for the past quarter focused on pipelined
+compilation (Scala 3), TASTy Reader (Scala 2), Scala.js minifier (2
+and 3), WebAssembly backend for Scala.js (2 and 3), Metals debugger (2
+and 3), presentation compiler (3), sbt 2.x (2 and 3), the Scala
+Ambassadors initiative, Google Summer of Code, conferences (Scala.IO
+and Scalar), compiler sprees, combating Scala website scammers,
+and fundraising.
+
+Details are below and in the Center's activity report:
+
+* [report](https://scala.epfl.ch/records/2024-Q1-activity-report.html)
+
+No new proposals were received this quarter.
+
+Other topics covered included Scala Days community discussions around
+"lean Scala" and "direct style" and related concepts, Scala LTS
+vs. Scala Next, the Scala Native 0.5 upgrade, and more.
+
+## Date, Time and Location
+
+The meeting took place virtually on Friday, April 25, 2024 at
+15:00 (UTC).
+
+Minutes were taken by Seth Tisue (secretary).
+
+## Attendees
+
+Officers:
+
+* Chris Kipp (chairperson)
+* Darja Jovanovic (executive director), EPFL
+* Sébastien Doeraene (interim technical director), EPFL
+* Martin Odersky (technical advisor), EPFL
+* Seth Tisue (secretary), Lightbend
+
+Board members:
+
+* Zainab Ali, community representative
+* Krzysztof Borowski, VirtusLab
+* Dmitrii Naumenko, JetBrains
+* Lukas Rytz, Lightbend
+* Daniela Sfregola, Morgan Stanley
+* Eugene Yokota, community representative
+
+Apologies:
+
+* Michel Davit, Spotify
+
+## Introduction
+
+Our two new board members introduced themselves.
+
+Dmitrii Naumenko will represent JetBrains, who have just finished
+joining the board. Dmitrii is the leader of the IntelliJ Scala plugin
+team there.
+
+Zainab Ali is a new community representative, serving alongside Eugene
+Yokota. She has been organizing the London Scala Users Group for the
+last five years or so. She describes herself as a functional Scala
+developer who does training in the functional space.
+
+## Technical report
+
+Seb, as interim technical director, summarized Scala Center activities
+since the last meeting. His remarks were based on the Center's more
+detailed Q1 quarterly activity report:
+
+* [report](https://scala.epfl.ch/records/2024-Q1-activity-report.html)
+
+And the Center's Q2 roadmap:
+
+* [roadmap](https://scala.epfl.ch/records/2024-Q2-roadmap.html)
+
+The following notes do not repeat the contents of the report and
+roadmap, but only supplement them.
+
+(No questions were asked about Seb's updates, so there are no further
+notes here.)
+
+## Management and financial report
+
+Darja presented this section.
+
+In February, the Center published their [2024
+roadmap](https://www.scala-lang.org/blog/2024/02/06/scala-center-2024-roadmap.html).
+
+The Center published two blog posts about scammers targeting Scala users:
+
+* https://scala-lang.org/blog/2024/03/01/fake-scala-courses.html
+* https://www.scala-lang.org/blog/2024/03/18/scam-response.html
+
+Combating these scams consumed considerable time and effort, but the
+good news is that the scamming activity did stop.
+
+At the Scalar conference in Warsaw, the Center organized a meeting of
+conference and meetup organizers and also launched the new [Scala
+Ambassadors program](https://scala-lang.org/blog/2024/03/28/ambassadors-initiative.html).
+
+The Center's participation in Google Summer of Code for 2024 is moving
+ahead.
+
+The Center's moderation team met in person in Lausanne to share knowledge
+and experiences and to discuss and strategize.
+
+The Center's governance project made progress which Darja summarized.
+That work was eventually completed later in the year, as described
+in this October 2024 blog post:
+
+* https://www.scala-lang.org/news/new-governance.html
+
+Several engineers completed their time at the Center and moved on:
+Anatolii Kmetiuk, Jamie Thompson, and Jedrzej Rochala. Seb will be
+teaching part-time at EPFL, so his effort level at the Center will be
+reduced to 50%. Hiring new engineers would require new funding.
+
+The Center's 2024 roadmap reflects the smaller size of the engineering
+team. Center staff will travel less unless the travel is sponsored.
+The Center will continue to "support, empower, and amplify" active
+Scala communities and community members to accomplish things that the
+Center itself cannot.
+
+The Center continues to collect income from its MOOCs, but the amount
+continues to gradually decline.
+
+Fundraising efforts are ongoing. Multiple leads are being pursued.
+
+The effort to revive Scala Days for 2025 is ongoing. In the meantime,
+the Scala website's [events page](https://www.scala-lang.org/events/)
+is kept up to date with upcoming events.
+
+## Scala 2 report
+
+This was presented by Lukas.
+
+Since the last meeting, Scala 2.12.19 and 2.13.13 were released,
+and 2.13.14 is almost ready. The 2.13.14 cycle was short because
+of a few regressions. 2.13.14 introduces `-Xsource-features`.
+
+Lukas contributed an sbt PR, now merged, which aligns sbt with
+[SIP-51](https://docs.scala-lang.org/sips/drop-stdlib-forwards-bin-compat.html),
+which will allow the Scala 2.13 standard library (which is also used
+by Scala 3) to make additions again. A process for that will need
+to be set up.
+
+## Community report
+
+This section was led by Eugene and Zainab.
+
+They said that in the community there is a great deal of discussion,
+some confusion and uncertainty, and even some tension around the
+following complex of issues and developments: effect systems, the
+advent of Project Loom, the concept of "direct style", and Martin's
+[blog post](https://odersky.github.io/blog/2024-04-11-post.html) about
+"lean Scala". Discussion involving nearly the entire board ensued.
+
+Eugene said there was also some confusion in the community about Scala
+LTS vs Scala Next. As will be described in the next minutes, Zainab
+later submitted a proposal asking the Center to provide clearer public
+guidance on this, and that proposal was completed by the publication
+of [this new page](https://scala-lang.org/development/).
+
+Zainab praised the organizers gathering at Scalar in Warsaw in March,
+which was "useful" in strengthening networking between conference and
+meetup organizers. In London they are hoping to do even more events
+besides just talks, such as workshops, open-source sprees, and katas.
+She also expressed hope that the Center's new [Scala
+Ambassadors](https://scala-lang.org/blog/2024/03/28/ambassadors-initiative.html)
+initiative will help onboard people who want to get more involved with
+community.
+
+Zainab mentioned that pushing the Scala Native 0.4 to 0.5 upgrade
+through the open source ecosystem has been difficult. In response, Seb
+recalled when Scala.js went from 0.6 to 1.0, a transition he described
+as "difficult and long", yet necessary. Scala Native 0.4 was 3 to 4
+years ago, so the big jump to 0.5 is now "unfortunately necessary",
+but the Native team "very much hopes" that this is "the last one
+before 1.0", which is probably "a few years down the line". Eugene
+added that setting up a Scala.js or Scala Native community build, like
+the existing JVM-centric Scala 2 and Scala 3 community builds, could
+really help (if resources could be found for such an effort). Seth
+added that library maintainers shouldn't be shy about requesting help
+from Scala Native enthusiasts, rather than feeling obligated to sort
+out problems themselves.
+
+## Conclusion
+
+Darja intends to organize an in-person advisory board meeting to be
+held at EPFL in the fall. Everyone on the board indicated they would
+make an effort to attend. (The in-person meeting did in fact occur, in
+September, and it will be covered in the next minutes.)
diff --git a/minutes/_posts/2024-09-05-september-5-2024.md b/minutes/_posts/2024-09-05-september-5-2024.md
new file mode 100644
index 00000000..54ee2f1c
--- /dev/null
+++ b/minutes/_posts/2024-09-05-september-5-2024.md
@@ -0,0 +1,206 @@
+---
+layout: contact
+---
+
+# Minutes of the 33rd meeting of the Scala Center, Q3 2024
+
+Minutes are [archived](https://scala.epfl.ch/records.html) on the
+Scala Center website.
+
+## Summary
+
+The meeting took place towards the end of Q3, so we considered it to
+be a combined meeting (with a combined report) covering both Q2 and
+Q3.
+
+Center activities for the past two quarters focused on maintaining
+and improving Scala 3, the adoption of Scala CLI as the new
+`scala` command, the WebAssembly backend for Scala.js, the
+Scala Improvement Process, the Scala Toolkit, the Metals debugger,
+Scaladex, sbt 2, documentation, Google Summer of Code, compiler
+sprees, fundraising, and more.
+
+Details are below and in the Center's activity report:
+
+* [report](https://scala.epfl.ch/records/2024-Q2-Q3-activity-report.html)
+
+Two new proposals were received:
+
+* [SCP-032](https://github.com/scalacenter/advisoryboard/blob/main/proposals/032-scala-version-guidance.md): Provide guidance on choosing between Scala LTS and Next
+* [SCP-033](https://github.com/scalacenter/advisoryboard/blob/main/proposals/033-deprecate-scala-ide.md): Deprecate Eclipse Scala IDE
+
+Both proposals were accepted by the board (and both were later
+completed, in October).
+
+Other topics covered included the long-term future of the Center.
+
+## Date, Time and Location
+
+The meeting took place at EPFL over two full days: Thursday and
+Friday, September 5-6, 2024.
+
+Minutes were taken by Seth Tisue (secretary) with the aid of
+Valérie Meillaud (Scala Center).
+
+## Attendees
+
+Officers:
+
+* Chris Kipp (chairperson)
+* Darja Jovanovic (executive director), EPFL
+* Sébastien Doeraene (interim technical director), EPFL
+* Martin Odersky (technical advisor), EPFL
+* Seth Tisue (secretary), Lightbend
+
+Board members:
+
+* Zainab Ali, community representative
+* Krzysztof Romanowski, VirtusLab (substituting for Krzysztof Borowski)
+* Dmitrii Naumenko, JetBrains
+* Lukas Rytz, Lightbend
+* Daniela Sfregola, Morgan Stanley
+
+Guests:
+
+* James Belsey, Morgan Stanley
+* Damian Mazurkiewicz, SiriusXM
+* Valérie Meillaud, Scala Center
+
+Apologies:
+
+* Eugene Yokota, community representative
+
+## Introduction
+
+This special in-person meeting lasted two full days.
+
+## Technical report
+
+Seb, as interim technical director, summarized Scala Center activities
+since the last meeting. His remarks were based on the Center's more
+detailed Q2+Q3 quarterly activity report:
+
+* [report](https://scala.epfl.ch/records/2024-Q2-Q3-activity-report.html)
+
+And the Center's Q4 roadmap:
+
+* [roadmap](https://scala.epfl.ch/records/2024-Q4-roadmap.html)
+
+The following notes do not repeat the contents of the report and
+roadmap, but only supplement them.
+
+An officer asked if there are still still two Bloops; Seb said no,
+that work is now completed on re-merging the fork that Scala CLI had
+been using.
+
+There was some discussion about IntelliJ support for Scala-CLI.
+(There is already some, and it is expected to improve. One particular
+area that hadn't been addressed yet at meeting time was folders
+full of independent scripts.)
+
+A board member asked if build pipelining would be enabled by default
+in sbt. Seb said perhaps eventually, but they aren't sufficiently
+confident in the quality yet.
+
+An officer asked who's running SIP (the Scala Improvement Process)
+now, with Toli having left the Center. It's Dimi Racordon from
+Martin's lab now; the web page will be updated to reflect that.
+
+A board member asked if there is a timeline when the first sbt 2 beta
+is expected. Seb said first half of 2025 is plausible but later in the
+year is likelier. There was some inconclusive discussion about the
+status of the build caching feature and whether that should be
+considered a blocker.
+
+A board member asked about whether sbt plugins will be able to
+cross-compile for sbt 1 and sbt 2, or whether they'd have to branch.
+Seb said cross-compiling will be supported.
+
+There was some discussion about adoption of Scala 3 at a company with
+a significant number of Scala developers. They are now using Scala 3
+features heavily, not just compiling old 2 code with the 3 compiler.
+It was emphasized that good IntelliJ support is of critical
+importance.
+
+### Scala 2 report
+
+This was presented by Lukas.
+
+Lukas said that the main themes are still aligning with Scala 3,
+warnings and lints especially under `-Xsource:3`. Some improvements
+shipped in 2.13.14, further changes coming in 2.13.15.
+
+About
+[SIP-51](https://docs.scala-lang.org/sips/drop-stdlib-forwards-bin-compat.html),
+Seth noted that 2.13.15 didn't break forward bincompat yet but 2.13.16
+might. (In the end, it got pushed off to 2.13.17.)
+
+## Community report
+
+This section was led by Zainab. (Eugene was unable to attend.)
+
+Discussion centered on meetups and hack days (or "sprees"),
+including how the pandemic set meetups and conferences back
+severely, and how recovery has been progressing.
+
+## SCP-032: Provide guidance on choosing between Scala LTS and Next
+
+The text of Zainab's proposal is here:
+
+* [SCP-032](https://github.com/scalacenter/advisoryboard/blob/main/proposals/032-scala-version-guidance.md): Provide guidance on choosing between Scala LTS and Next
+
+Discussion was brief, since the board sees the need, but there wasn't
+yet a draft text available to give feedback on.
+
+We neglected to hold a formal vote after the discussion, but we
+confirmed with the board afterwards that the proposal should be
+considered accepted by acclaim.
+
+(Later, in October 2024, the proposal was considered completed with
+the publication of [this
+page](https://www.scala-lang.org/development/).)
+
+## SCP-033: Deprecate Eclipse Scala IDE
+
+The text of Zainab's proposal is here:
+
+* [SCP-033](https://github.com/scalacenter/advisoryboard/blob/main/proposals/033-deprecate-scala-ide.md): Deprecate Eclipse Scala IDE
+
+The proposal was discussed by the board. An officer asked what the old
+site would redirect to. Seth said that scala-lang.org will soon have a
+new page dedicated specifically to Scala IDEs (namely IntelliJ and
+Metals) and the site will redirect to that.
+
+We neglected to hold a formal vote after the discussion, but we
+confirmed with the board afterwards that the proposal should be
+considered accepted by acclaim.
+
+(Later, in October 2024, the proposal was considered completed.)
+
+## Management report
+
+Darja began by reflecting on the Center's experiences over the past
+eight years, both its successes and accomplishments, and things that
+might change over the next eight years. She also updated the board on
+the budget situation and in-progress fundraising efforts.
+
+Discussion ensued about the Center's role, mission, structure, and
+long-term future.
+
+One theme that emerged was a desire for the Center to improve
+communication about everything going on under the Scala umbrella, not
+just at the Center itself, but also at LAMP, Akka, VirtusLab, and our
+collaborators. (After the meeting, this discussion led to the creation
+of new "Scala Highlights" newsletter; the [first
+issue](https://www.scala-lang.org/highlights/2025/02/06/highlights-2024.html)
+was published in February 2025.)
+
+There was also discussion about the Center's plans to revive Scala
+Days in 2025. (Later, after the meeting, plans were finalized and
+[August 2025 dates were
+announced](https://www.scala-lang.org/blog/2025/02/18/announcing-scala-days-2025.html).)
+
+## Conclusion
+
+The next meeting will be held online in January 2025 (or February, if
+necessary).
diff --git a/minutes/_posts/2025-02-05-february-5-2025.md b/minutes/_posts/2025-02-05-february-5-2025.md
new file mode 100644
index 00000000..0f605507
--- /dev/null
+++ b/minutes/_posts/2025-02-05-february-5-2025.md
@@ -0,0 +1,225 @@
+---
+layout: contact
+---
+
+# Minutes of the 34th meeting of the Scala Center, Q4 2024
+
+Minutes are [archived](https://scala.epfl.ch/records.html) on the
+Scala Center website.
+
+## Summary
+
+The following agenda was distributed to attendees:
+[agenda](https://github.com/scalacenter/advisoryboard/blob/main/agendas/034-2024-q4.md).
+
+Center activities for the past quarter focused on Scala 3 maintenance,
+the Scala 3 language specification, Scala.js maintenance, the Scala
+Improvement Process, sbt 2, the new Scala Highlights newsletter,
+Google of Summer Code, Scala Advent of Code, compiler sprees, Scala
+Days, and fundraising.
+
+Details are below and in the Center's activity report:
+
+* [report](https://scala.epfl.ch/records/2024-Q4-activity-report.html)
+
+One new proposal was received this quarter:
+
+* [SCP-034](https://github.com/scalacenter/advisoryboard/blob/main/proposals/034-artifact-publishing.md): Artifact publishing
+
+After discussion, the board decided to postpone any formal vote on it.
+
+Other topics covered included officer elections; officers remained
+unchanged.
+
+## Date, Time and Location
+
+The meeting took place virtually on Wednesday, February 5, 2025 at
+16:15 (UTC).
+
+Minutes were taken by Seth Tisue (secretary).
+
+## Attendees
+
+The company formerly known as Lightbend is now called Akka. Lukas
+Rytz is still the Akka representative, but he was unavailable for this
+meeting so Seth filled in.
+
+Officers:
+
+* Chris Kipp (chairperson), community
+* Darja Jovanovic (executive director), EPFL
+* Sébastien Doeraene (interim technical director), EPFL
+* Martin Odersky (technical advisor), EPFL
+* Seth Tisue (secretary), Akka
+
+Board members:
+
+* Zainab Ali, community representative
+* Krzysztof Romanowski, VirtusLab (substituting for Krzysztof Borowski)
+* Dmitrii Naumenko, JetBrains
+* Seth Tisue, Akka (substituting for Lukas Rytz)
+* Eugene Yokota, community representative
+
+Apologies:
+
+* Daniela Sfregola, Morgan Stanley
+
+## Technical report
+
+Séb, as interim technical director, summarized Scala Center activities
+since the last meeting. His remarks were based on the Center's more
+detailed Q4 quarterly activity report:
+
+* [report](https://scala.epfl.ch/records/2024-Q4-activity-report.html)
+
+And the Center's 2025 Q1 roadmap:
+
+* [roadmap](https://scala.epfl.ch/records/2025-Q1-roadmap.html)
+
+The following notes do not repeat the contents of the report and
+roadmap, but only supplement them.
+
+Séb noted that at its current staffing level the Center is currently
+doing at least as much organizing and community work as technical
+work.
+
+A board member asked where Scala.js's WebAssembly back end stands.
+Séb said that optimizing the back end is still pending. Closures in
+particular are not optimized yet. Martin added that stable exceptions
+support in WebAssembly in browsers is another pending issue preventing
+the Center's work on this from being quite ready yet for use in common
+scenarios.
+
+There was some technical discussion about how the Scala 3 debugger
+would be packaged to be consumed by IntelliJ and other tools. Also,
+an officer asked about the debugger code moving into the main Scala 3
+repo; does that mean that fixes require a new language release? Séb
+said yes, but that code is now stable enough now for it to be worth
+it.
+
+## Scala 2 report
+
+This was presented by Seth.
+
+Scala Newsletter is out today, and covers both Scala 3 and Scala 2.
+Let us know what you think, as this will be the template for future
+issues, which will be published quarterly.
+
+Since the last meeting, we published a blog post about our Scala 2
+maintenance plans. Note that 2.12 is now under minimal maintenance.
+
+Scala 2.13.15 and 2.13.16 came out since the last meeting. Changes
+were modest and focused on compatibility, on supporting Scala 3
+migration, and on improvements to warnings and linting. There have
+been no 2.13.16 regression reports, so if anyone was holding back on
+upgrading, I'd say go ahead.
+
+As usual, we've opened threads on the Contributors forum for
+discussing plans for the next releases:
+
+* [2.13.17](https://contributors.scala-lang.org/t/scala-2-13-17-release-planning/6994)
+* [2.12.21](https://contributors.scala-lang.org/t/scala-2-12-21-release-planning/6753)
+
+We plan for
+[SIP-51](https://docs.scala-lang.org/sips/drop-stdlib-forwards-bin-compat.html)
+(resuming making additions to the standard library) to be a theme
+for 2.13.17.
+
+An officer asked: if the primary motivation for maintaining 2.12 is sbt 1,
+does that mean that when sbt 2 comes out, 2.12 be EOLed? Seth
+responded: perhaps eventually, but not right away. We are assuming a
+longer timeframe since sbt 1 will remain in wide use for some time yet
+to come, even once sbt 2 is available.
+
+## SCP-034: Artifact publishing
+
+Eugene summarized [the
+proposal](https://github.com/scalacenter/advisoryboard/blob/main/proposals/034-artifact-publishing.md).
+
+Séb expressed support; "it seems like a sensible thing to do". One
+board member wondered if maintainers would be sufficiently motivated
+to migrate to a shared implementation. Another member asked if there's
+a particular current implementation that would be the basis of the
+shared one; there was no simple, single answer.
+
+The rest of the discussion centered on whether the Center would have
+enough engineering resources this year to lead this. In the end, the
+board decided not to formally vote on it now, but revisit the proposal
+later. Chris suggested that Eugene amend the proposal to reflect
+today's discussion.
+
+## Elections
+
+For chairperson, Chris Kipp indicated his willingness to continue as
+chair and was elected unanimously. (Chairs are not required to serve
+past one year, but a willing chair is welcome to serve for longer.)
+
+Also re-elected without any other nominations being made were Martin
+Odersky (technical advisor) and Seth Tisue (secretary).
+
+## Community report
+
+This section was led by Zainab and Eugene.
+
+Zainab said the London community is currently strong, with more events
+occurring, with attendance up as well. The London Scala group is now
+doing open-source hack days and women-in-Scala meetings, in addition
+to the usual meetups with speakers. ScalaBridge has received feedback
+that it could devote more time to setup and tooling, as that usually
+causes participants more trouble than the language itself.
+
+Eugene noted that X (aka Twitter) is no longer as universal a source
+of news and discussion; some users remain but others have dispersed to
+Bluesky and/or Mastodon. He said that as a result, the Scala Reddit is
+even more important to the community than before, and the discussions
+and engagement there have been strong recently (including topics about
+education and training).
+
+He also observed that there have been several extremely active
+language design discussions recently, such as the one about collection
+literals. There was some discussion among the board about how these
+proposals and discussions can best be framed and structured, to
+encourage high quality engagement and ensure that people feel heard.
+
+There was some also some discussion on how to better coordinate
+language changes with tooling maintainers, including the recent
+introduction of the concept of "preview" features as an intermediate
+state between "experimental" and completed.
+
+One board member expressed a wish for Scala people (perhaps even
+Center members) to more present at non-Scala conferences, representing
+Scala outside of our own community.
+
+There was some discussion around how having a smaller engineering
+staff may change community perception of the Center. There was general
+agreement that our publicity should focus on what advances are
+happening and not too much on exactly where they happened (except, of
+course, to give credit where credit is due!). That's part of the idea
+behind the new Scala Highlights newsletter, which is assembled by the
+Center, but isn't restricted to presenting the Center's own
+activities.
+
+## Management and financial report
+
+Darja said that a major piece of news since the last meeting was the
+publication in October of the new Scala governance and "development
+guarantees" documents, as described in [this blog
+post](https://www.scala-lang.org/news/new-governance.html).
+
+Also very important, the publication of the first issue of [Scala
+Highlights](https://www.scala-lang.org/highlights/2025/02/06/highlights-2024.html).
+The first issue covers all of 2024; future issues will have quarterly
+news.
+
+The Center's finances have improved thanks to one-time donations and
+assistance from several sources. Regardless, hiring additional staff
+would require additional funding. Fundraising efforts are ongoing.
+
+The Center is also still in the process of reviving Scala Days for
+later in 2025. (Later, after the meeting, plans were finalized and
+[August 2025 dates were announced](https://www.scala-lang.org/blog/2025/02/18/announcing-scala-days-2025.html).)
+
+## Conclusion
+
+The next meeting will be held online, probably in April. If possible,
+a late-summer or fall meeting will be held in-person at EPFL.
diff --git a/projects.md b/projects.md
index 4639cf37..5d7093bd 100644
--- a/projects.md
+++ b/projects.md
@@ -1,3 +1,3 @@
---
-redirect_to: /records/2024-Q2-roadmap.html
+redirect_to: /records/2025-Q1-roadmap.html
---
diff --git a/records.md b/records.md
index 71c2d090..e9ded117 100644
--- a/records.md
+++ b/records.md
@@ -14,6 +14,8 @@ Every quarter, the Scala Center publishes an activity report detailing the
work that has been achieved. You can find the roadmap for the current quarter
in the [Projects page]({% link projects.md %}).
+- [2024, Q4]({% link records/2024-Q4-activity-report.md %})
+- [2024, Q2-Q3]({% link records/2024-Q2-Q3-activity-report.md %})
- [2024, Q1]({% link records/2024-Q1-activity-report.md %})
- [2023, Q4]({% link records/2023-Q4-activity-report.md %})
- [2023, Q3]({% link records/2023-Q3-activity-report.md %})
@@ -38,6 +40,10 @@ in the [Projects page]({% link projects.md %}).
### Board meeting minutes
+- [February 5, 2025 - Thirty-Fourth SC Advisory Board Meeting](/minutes/2025/02/05/february-5-2025.html)
+- [September 5, 2024 - Thirty-Third SC Advisory Board Meeting](/minutes/2024/09/05/september-5-2024.html)
+- [April 25, 2024 - Thirty-Second SC Advisory Board Meeting](/minutes/2024/04/25/april-25-2024.html)
+- [February 7, 2024 - Thirty-First SC Advisory Board Meeting](/minutes/2024/02/07/february-7-2024.html)
- [October 17, 2023 - Thirtieth SC Advisory Board Meeting](/minutes/2023/10/17/october-17-2023.html)
- [July 26, 2023 - Twenty-Ninth SC Advisory Board Meeting](/minutes/2023/07/26/july-26-2023.html)
- [April 27, 2023 - Twenty-Eighth SC Advisory Board Meeting](/minutes/2023/04/27/april-27-2023.html)
diff --git a/records/2022-Q4-activity-report.md b/records/2022-Q4-activity-report.md
index 7562377a..1897e4e6 100644
--- a/records/2022-Q4-activity-report.md
+++ b/records/2022-Q4-activity-report.md
@@ -207,7 +207,7 @@ In Q4, we're finally opening it to the wider public. We've integrated the projec
The significance of the project is to ensure the long-term sustainability of Scala 3. Scala 3's team is smaller than corresponding teams of many other programming languages. We need to ensure that the project is not dependent on a small number of people, but rather on a large number of people who are interested in contributing to the compiler. Compiler Academy is one of the avenues that ensure a stream of new compiler enthusiasts.
-You can learn more about the Academy [here](https://compileracademy.carrd.co/). [Here](https://www.scala-lang.org/blog/2022/11/02/compiler-academy.html) is the blog post announcing opening it up.
+You can learn more about the Academy here (dead link: httpx://compileracademy.carrd.co/). [Here](https://www.scala-lang.org/blog/2022/11/02/compiler-academy.html) is the blog post announcing opening it up.
### Community Expansion
diff --git a/records/2023-Q1-activity-report.md b/records/2023-Q1-activity-report.md
index 7b56ddb3..bc8d57a0 100644
--- a/records/2023-Q1-activity-report.md
+++ b/records/2023-Q1-activity-report.md
@@ -42,8 +42,8 @@ We contributed PRs in the follow areas:
[dotty#17088](https://github.com/lampepfl/dotty/pull/17088)
Additionally, our collaborations with members of the community, either
-asynchronously or as part of the [Compiler
-Academy](https://compileracademy.carrd.co/), led to improvements
+asynchronously or as part of the Compiler
+Academy, led to improvements
in the following areas:
- Type inference
[dotty#17092](https://github.com/lampepfl/dotty/pull/17092)
diff --git a/records/2023-Q3-activity-report.md b/records/2023-Q3-activity-report.md
index 5d068be4..f5a83f50 100644
--- a/records/2023-Q3-activity-report.md
+++ b/records/2023-Q3-activity-report.md
@@ -11,12 +11,12 @@ Jamie Thompson, 100%;
Sébastien Doeraene, 100%;
Guillaume Martres, 100% until August 31, 20% since;
Julien Richard-Foy, 80% until August 31;
-Johanna Reichen: 80% until August 14;
Lucas Nouguier: 100% until August 31;
+Ayman Lamyaghri, intern July 3 - August 25.
Sylvie Buchard: 30% until August 31;
Valérie Meillaud: 30% since September 1;
-Shiv Verkaran: 80% since September 15.
-VirtusLab team: Jędrzej Rochala, 100%.
+Shiv Verkaran: 80% September 1 - October 12;
+VirtusLab team: Jędrzej Rochala, 100%
## At a Glance
{: .no_toc}
@@ -206,7 +206,7 @@ Relevant PRs: [scala/docs.scala-lang#2894](https://github.com/scala/docs.scala-l
In collaboration with Xebia Functional, we organized the Scala Days conference in Madrid and a number of co-located events around it:
-* [Scala Bridge](https://scaladays.org/madrid-2023/scala-bridge), lead by Zainab Ali and Noel Welsh - a Scala workshop for beginners to attract more newcomers without programming background to the Scala community.
+* [Scala Bridge](https://web.archive.org/web/20230922193146/https://scaladays.org/madrid-2023/scala-bridge), lead by Zainab Ali and Noel Welsh - a Scala workshop for beginners to attract more newcomers without programming background to the Scala community.
* [Scala Spree](https://github.com/scalacenter/sprees), lead by Jamie Thompson - a hackathon for the Scala developers to hack on OSS projects together with the maintainers of those projects.
* Tooling Summit, lead by Chris Kipp - a meeting of the Scala tooling stakeholders to get to the same page on the future of the Scala tooling ecosystem.
* In-person [SIP](https://docs.scala-lang.org/sips/process-specification.html) meeting, lead by Anatolii Kmetiuk, where the SIP committee members got a chance to speak to each other in person and otherwise do an ordinary SIP meeting.
diff --git a/records/2024-Q1-activity-report.md b/records/2024-Q1-activity-report.md
index 30fd71ce..e05d4f0d 100644
--- a/records/2024-Q1-activity-report.md
+++ b/records/2024-Q1-activity-report.md
@@ -175,17 +175,17 @@ We expect that these additional data will help us make Metals more robust in the
For Scala 2 and Scala 3 throughout.
-### Ambassador Program
+### Ambassador Initiative
-We incubated the [Scala Ambassador program](https://github.com/scalacenter/ambassadors).
-This is a program to foster a new generation of Scala community leaders, able to competently answer community questions.
+We incubated the [Scala Ambassador initiative](https://github.com/scalacenter/ambassadors).
+This initiative aims to foster a new generation of Scala community leaders, able to competently answer community questions.
Those people will also be empowered to organize local community events and otherwise help their local communities thrive.
-Currently, the program is in its early stages, as we welcome our first Ambassadors on an invitation basis.
-The program is meant to recognize and support the independent work of active community leaders.
+Currently, the initiative is in its early stages, as we welcome our first Ambassadors on an invitation basis.
+It is meant to recognize and support the independent work of active community leaders.
We publicly announced it at Scalar 2024 and [on our website](https://www.scala-lang.org/blog/2024/03/28/ambassadors-initiative.html).
-The ambassador program will strengthen the community, amplify the official story around Scala and increase activity in the local Scala communities.
+The ambassador initiative will strengthen the community, amplify the official story around Scala and increase activity in the local Scala communities.
### Google Summer of Code
diff --git a/records/2024-Q2-Q3-activity-report.md b/records/2024-Q2-Q3-activity-report.md
new file mode 100644
index 00000000..ba0b2ea9
--- /dev/null
+++ b/records/2024-Q2-Q3-activity-report.md
@@ -0,0 +1,207 @@
+---
+layout: contact
+title: Scala Center Activity Report for 2024 Q2-Q3
+---
+
+Scala Center team:
+Darja Jovanovic, 100%;
+Adrien Piquerez, 80%;
+Jamie Thompson, 100% until July 31st;
+Sébastien Doeraene, 100% until June 30th, 50% since then;
+Guillaume Martres, 20%;
+Valérie Meillaud: 30%.
+VirtusLab team: Gabriel Kepka, 100% since July 1st.
+
+## At a Glance
+{: .no_toc}
+
+* Table of Contents
+{:toc}
+
+
+## Language, Compiler, Standard Library
+
+### SIP 46 - bundle Scala CLI as the Scala command
+
+For Scala 3.
+
+Starting with Scala 3.5.0, Scala CLI is released in the binary distribution as the `scala` command (PR [scala/scala3#20351](https://github.com/scala/scala3/pull/20351) and PR [scala/scala3#20631](https://github.com/scala/scala3/pull/20631)).
+We adapted Scala CLI to support wrapping it in a script that overrides some default options, such as reading from a local classpath.
+
+We also fixed the coursier `install` command to support mixing both JVM and native launchers (PR [coursier/coursier#2975](https://github.com/coursier/coursier/pull/2975)).
+This ensured that earlier versions of Scala, including Scala 2, can be used with the newly distributed `scala` command.
+
+### SIP 57 - replace nonsensical `: @unchecked` with `.runtimeChecked`
+
+For Scala 3.
+
+We implemented [SIP 57](https://docs3.scala-lang.org/sips/replace-nonsensical-unchecked-annotation.html) in the PR [scala/scala3#20987](https://github.com/scala/scala3/pull/20987).
+It brings a safer and more intuitive way to disable pattern matching exhaustivity checks.
+The previous approach could lead to accidental unsoundness issues.
+
+### Maintainance of the Scala 3 Compiler
+
+For Scala 3.
+
+Every month, about 100 new issues are opened on [the Scala 3 repository](https://github.com/lampepfl/dotty/).
+The project welcomes any help it can get in triaging, bug-fixing, PR reviewing, etc.
+
+Our goal is to solve long-standing issues while keeping up with new ones.
+We also aim to get more people involved in working on the compiler to ensure the sustainability of the project.
+
+We contributed PRs for bug fixes in various areas, notably: `-Xcheck:unused`, annotations, match types, `lazy val`s, named tuples, and the TASTy format.
+
+### Improving Performance of the Scala 3 compiler
+
+For Scala 3.
+
+#### Support for pipelined concurrent compilation
+
+We cleaned up various aspects of the build pipelining implementation based on feedback from users.
+Notably, we now write the pipeline tasty in parallel, and detect missing macro dependencies while reporting to the user how to fix the problem (PR [scala/scala3#20139](https://github.com/scala/scala3/pull/20139)).
+
+#### Computing compilation metadata in parallel
+
+We concluded supervision of a student project to compute Zinc metadata in parallel to the compiler using TASTy Query.
+The experimental findings suggest that the TASTy Query library has adequate capabilities to perform the task, but has a slow startup due to classpath loading.
+We would likely need a layered classpath to share information between repeat compilations for the approach to yield real performance improvements.
+
+### Develocity setup
+
+For Scala 2 and Scala 3.
+
+Gradle is providing us with a [free instance of Develocity](https://develocity.scala-lang.org/) through their [open-source program](https://gradle.com/customers/oss-projects/).
+We are partnering with them to integrate Develocity in the Scala 3 compiler build ([#21386](https://github.com/scala/scala3/pull/21386), [#21479](https://github.com/scala/scala3/pull/21479)), with support for:
+
+- Publishing build scans from the CI
+- Automatic test retries and flakiness detection
+- Build caching (planned for the future)
+
+In parallel, Lukas Rytz from Lightbend started integrating Develocity in the Scala 2 compiler build ([#10848](https://github.com/scala/scala/pull/10848)).
+
+### WebAssembly backend for Scala.js
+
+For Scala 2 and 3.
+
+In Q1, we had developed a proof-of-concept implementation of WebAssembly backend for Scala.js, in collaboration with VirtusLab.
+In the past few months, we have polished it and [merged it into Scala.js upstream](https://github.com/scala-js/scala-js/pull/4988).
+Huge thanks go to Tobias Schlatter, co-maintainer of Scala.js, for *reviewing* that mega PR of 13,000 lines of code!
+
+In addition to the baseline implementation, we implemented several low-hanging fruit optimizations.
+Initial performance measurements are very encouraging, as they show that we can reach a 15% geomean speedup over Scala.js.
+We already merged most optimizations into Scala.js.
+
+The WebAssembly backend will be shipped as part of Scala.js 1.17.0.
+
+In order to further improve performance and code size, we will integrate with [`wasm-opt`](https://github.com/WebAssembly/binaryen), a Wasm-to-Wasm optimizer.
+We contributed [support for the new Wasm Exception Handling spec in `wasm-opt`](https://github.com/WebAssembly/binaryen/pull/6814), since our backend relies on it.
+
+In parallel, VirtusLab is experimenting with a variant of this backend that targets Wasm runtimes without JavaScript.
+This new target will significantly expand the reach of Scala as a language.
+
+### TASTy Reader for Scala 2
+
+For Scala 2.
+
+We added support in Scala 2.13.15 (PR [scala/scala#10811](https://github.com/scala/scala/pull/10811)) for TASTy produced by Scala 3.5.
+
+### Scala Improvement Process
+
+For Scala 3.
+
+The [Scala Improvement Process](https://docs.scala-lang.org/sips/) coordinates the evolution of the language.
+It ensures that the decisions are made by taking into account the needs of all the stakeholders of the language.
+
+## Developer Experience
+
+### Scala Toolkit
+
+For Scala 2 and Scala 3.
+
+We released 3 versions of the Toolkit:
+
+- [0.3.0](https://github.com/scala/toolkit/releases/tag/0.3.0): the final version supporting Scala Native 0.4
+- [0.4.0](https://github.com/scala/toolkit/releases/tag/0.4.0): dropped support for Scala Native 0.4, and added support for Scala Native 0.5
+- [0.5.0](https://github.com/scala/toolkit/releases/tag/0.5.0): updated library versions
+
+### Documentation
+
+For Scala 2 and Scala 3.
+
+We wrote a tutorial on building web servers with Cask, to add to the collection of Toolkit tutorials.
+We started adapting the documentation to use `scala-cli` as the new Scala runner, since Scala 3.5.0 is now released.
+
+We also worked on documenting features not yet included in the documentation, such as binding patterns to variables in pattern matching.
+
+### Debugger in Metals
+
+#### The Scala 2 expression compiler
+
+For Scala 2 only.
+
+In the past, we dedicated significantly more time in developing the Scala 3 expression compiler compared to the Scala 2 one.
+The Scala 2 expression evaluator barely worked in simple cases, but it could not handle more complex source files.
+To resolve this, we rewrote the Scala 2 expression compiler from scratch ([#701](https://github.com/scalacenter/scala-debug-adapter/pull/701)), mirroring the Scala 3 implementation.
+The two expression compilers are now aligned closely enough to share the same test suite and be simultaneously maintained.
+
+#### The Scala 3 binary decoder
+
+For Scala 3 only.
+
+We developed the Scala 3 binary decoder to decode stack traces, and printing fully-typed method signatures in the debugger.
+In this quarter we extracted it to its own repository ([scalacenter/scala3-binary-decoder](https://github.com/scalacenter/scala3-binary-decoder)), in order to spread its usage to other tools of the ecosystem, such as Scastie and Scala CLI.
+
+Additionally, we made significant progress on decoding fields ([#2](https://github.com/scalacenter/scala3-binary-decoder/pull/2)) and variables ([#3](https://github.com/scalacenter/scala3-binary-decoder/pull/3)), which will be useful for the debugger.
+
+### Scaladex
+
+As part of GSoC, we mentored two Scaladex projects:
+
+* We added an intermediate artifacts page, to list the artifacts of a project by name, ordered by the latest version. For instance, see [cats/artifacts](https://index.scala-lang.org/typelevel/cats/artifacts).
+* We extracted additional information from POM files: version scheme, full Scala version and developers. For instance, see [cats/artifacts/cats-core/2.12.0](https://index.scala-lang.org/typelevel/cats/artifacts/cats-core/2.12.0).
+
+### sbt
+
+For Scala 2 and Scala 3.
+
+In addition to addressing various bugs ([#1140](https://github.com/sbt/zinc/pull/1382), [#7568](https://github.com/sbt/sbt/pull/7568)), we actively participated in the development of sbt 2, led by Eugene Yokota.
+We centered our efforts on stability ([#7522](https://github.com/sbt/sbt/pull/7522), [#7538](https://github.com/sbt/sbt/pull/7538)) and error reporting ([#7539](https://github.com/sbt/sbt/pull/7539)).
+Additionally we investigated straight-to-JAR compilation, which aims to boost performance on Windows and streamline the implementation of cached compilation ([#7592](https://github.com/sbt/sbt/pull/7592)).
+
+## Community and Contributor Experience
+
+For Scala 2 and Scala 3 throughout.
+
+### Google Summer of Code
+
+Google Summer of Code (GSoC) has been a long-standing vehicle for the Scala Center to attract newcomers to the Scala OSS world.
+
+The Scala Center acts as an organization shepherding the projects related to Scala.
+As such, we perform administrative tasks and mentor several projects.
+
+The program for this year is coming to an end.
+All of this year's 10 projects passed their midterm evaluation several weeks ago.
+Final evaluations of students are in progress.
+
+Find our more about the various projects on [the GSoC page for the Scala Center](https://summerofcode.withgoogle.com/programs/2024/organizations/scala-center).
+
+### Scala Matsuri 2024
+
+We presented a talk about build tooling and build performance.
+In the talk, we first explained how Scala build tools work.
+We then reported on the progress we made in Pipelining and Progress tracking.
+Finally, we reviewed the concepts of offloading work via parallel compilation.
+
+### Compiler Sprees
+
+We maintained our involvement in the [Scala 3 Compiler Academy Issue Spree](https://www.scala-lang.org/blog/2022/11/02/compiler-academy.html).
+
+Since its inception, the compiler spree has helped close [more then a hundred issues](https://github.com/lampepfl/dotty/issues?q=is%3Aissue+sort%3Aupdated-desc+label%3ASpree+is%3Aclosed) with the help of over 80 contributors.
+
+## Scala Center Administration
+
+### Sovereign Tech Fund
+
+We applied for a large grant from the [Sovereign Tech Fund](https://www.sovereigntechfund.de/) (STF), a governmental German fund that "supports the development, improvement, and maintenance of open digital infrastructure."
+The STF has significantly contributed to the maintenance of several other open-source programming languages in the past, such as Ruby, Python and Node.js.
+We are hopeful that they will choose to support Scala as well.
diff --git a/records/2024-Q4-activity-report.md b/records/2024-Q4-activity-report.md
new file mode 100644
index 00000000..9c3f376e
--- /dev/null
+++ b/records/2024-Q4-activity-report.md
@@ -0,0 +1,147 @@
+---
+layout: contact
+title: Scala Center Activity Report for 2024 Q4
+---
+
+Scala Center team:
+Darja Jovanovic, 100%;
+Adrien Piquerez, 80%;
+Sébastien Doeraene, 50%;
+Guillaume Martres, 20%;
+Valérie Meillaud: 30%.
+VirtusLab team: Gabriel Kepka, 100%.
+
+## At a Glance
+{: .no_toc}
+
+* Table of Contents
+{:toc}
+
+
+## Language, Compiler, Standard Library
+
+### Maintainance of the Scala 3 Compiler
+
+For Scala 3.
+
+Every month, about 100 new issues are opened on [the Scala 3 repository](https://github.com/scala/scala3).
+The project welcomes any help it can get in triaging, bug-fixing, PR reviewing, etc.
+
+Our goal is to solve long-standing issues while keeping up with new ones.
+We also aim to get more people involved in working on the compiler to ensure the sustainability of the project.
+
+We contributed PRs for bug fixes in various areas, notably match types.
+We also invested more in reviewing PRs from external and internal contributors alike.
+
+### Scala.js maintenance
+
+For Scala 2 and 3.
+
+At the beginning of the quarter, we released [Scala.js 1.17.0](https://www.scala-js.org/news/2024/09/28/announcing-scalajs-1.17.0/).
+It features the initial implementation of the [experimental WebAssembly backend](https://www.scala-js.org/doc/project/webassembly.html) that we worked on during the previous quarter.
+
+This quarter, we only performed behind-the-scenes maintenance of Scala.js: internal cleanups that will ease future developments.
+We added support for recent Scala 2.x releases, which included a last-minute patch for Scala 2.13.16, shipped as part of [Scala.js 1.18.2](https://www.scala-js.org/news/2025/01/23/announcing-scalajs-1.18.2/).
+
+### Scala Improvement Process
+
+For Scala 3.
+
+The [Scala Improvement Process](https://docs.scala-lang.org/sips/) coordinates the evolution of the language.
+It ensures that the decisions are made by taking into account the needs of all the stakeholders of the language.
+
+## Developer Experience
+
+### Scala Toolkit
+
+For Scala 2 and Scala 3.
+
+We released a new version of the Toolkit:
+
+- [0.6.0](https://github.com/scala/toolkit/releases/tag/0.6.0): updated library versions
+
+### Documentation
+
+For Scala 2 and Scala 3.
+
+After the release of Scala 3.5.0, we updated the documentation website to use `scala-cli` as the entry point to the language.
+
+We continued our work to simplify the documentation structure.
+In particular, the Scala 3 book now contains at least as much information as the Scala 2 book.
+Since the Scala 3 book actually documents Scala 2 as much as Scala 3 (with systematic version tabs), we plan to retire the Scala 2 book.
+
+We also worked on documenting features not yet included in the documentation, such as `boundary`/`break`.
+
+### sbt
+
+For Scala 2 and Scala 3.
+
+We continued our efforts to stabilize sbt 2.x.
+In addition, we contributed several optimizations ([#7879](https://github.com/sbt/sbt/pull/7879), [#7880](https://github.com/sbt/sbt/pull/7880), [#7882](https://github.com/sbt/sbt/pull/7882)), which will make it significantly faster to load than sbt 1.x and consume less memory.
+
+### Scala 3 specification
+
+For Scala 3.
+
+We finished the following areas of the Scala 3 specification:
+
+* for comprehensions
+* match types
+
+## Community and Contributor Experience
+
+For Scala 2 and Scala 3 throughout.
+
+### Scala Highlights
+
+We are about to release the first edition of Scala Highlights, a new quarterly newsletter showcasing technical achievements, online resources, and community news.
+
+The newsletter is a joint effort by the Scala Center, LAMP, Akka, and VirtusLab, the four core organizations involved in the Scala language development.
+It also covers our collaborations with other parties, such as the Scala Center's advisory board.
+
+This inaugural issue is special as it offers a recap of 2024, celebrating the year's most significant advancements and their impact on the Scala ecosystem.
+Future issues will cover quarterly highlights.
+
+It might be released by the time you read these lines.
+If not, you can [read it in the pull request](https://github.com/scala/scala-lang/pull/1744).
+
+### Google Summer of Code
+
+Google Summer of Code (GSoC) has been a long-standing vehicle for the Scala Center to attract newcomers to the Scala OSS world.
+
+The Scala Center acts as an organization shepherding the projects related to Scala.
+As such, we perform administrative tasks and mentor several projects.
+
+We concluded the 2024 edition with 10 successfull projects, which is a record high for our organization.
+You can learn more about those projects [on the dedicated GSoC page for the Scala Center](https://summerofcode.withgoogle.com/programs/2024/organizations/scala-center).
+
+For the upcoming year, [we are again applying to be an organization in 2025](https://www.scala-lang.org/blog/2025/01/28/gsoc-projects.html).
+
+#### Scala Advent of Code
+
+As in the past two years, we stewarded the participation to [Advent of Code](https://adventofcode.com/) for Scala developers, together with LAMP and Akka.
+
+One of our core priorities is to communicate excitement about Scala.
+We participate in the Advent of Code so that we can share to the wider programming community how great Scala is for solving these programming puzzles.
+
+We had 281 solutions submitted to the website this year, increased from 237 last year and 164 the year before, with many first time contributors.
+Many external volunteers wrote solution articles, leading to 24 out of the 25 days to be covered.
+
+See the [announcement blog](https://scala-lang.org/blog/2024/12/02/advent-of-code-announce.html) and [recap blog post](https://scala-lang.org/blog/2025/01/16/advent-of-code-recap.html) for more details.
+
+### Compiler Sprees
+
+We maintained our involvement in the [Scala 3 Compiler Academy Issue Spree](https://www.scala-lang.org/blog/2022/11/02/compiler-academy.html).
+
+Since its inception, the compiler spree has helped close [more then a hundred issues](https://github.com/lampepfl/dotty/issues?q=is%3Aissue+sort%3Aupdated-desc+label%3ASpree+is%3Aclosed) with the help of over 80 contributors.
+
+## Scala Center Administration
+
+### Sovereign Tech Fund
+
+We applied for a large grant from the [Sovereign Tech Fund](https://www.sovereigntechfund.de/) (STF), a governmental German fund that "supports the development, improvement, and maintenance of open digital infrastructure."
+The STF has significantly contributed to the maintenance of several other open-source programming languages in the past, such as Ruby, Python and Node.js.
+We are hopeful that they will choose to support Scala as well.
+
+So far, we passed the first stage of the evaluation process.
+Next steps involve scoping more precisely the work that would be covered by the grant.
diff --git a/records/2024-Q4-roadmap.md b/records/2024-Q4-roadmap.md
new file mode 100644
index 00000000..17f907e0
--- /dev/null
+++ b/records/2024-Q4-roadmap.md
@@ -0,0 +1,110 @@
+---
+layout: contact
+title: Scala Center Roadmap for 2024 Q4
+---
+
+This page lists the projects that the Scala Center plans to work on during 2024 Q4.
+We also post regular updates about our projects on the [Scala Contributors forum](https://contributors.scala-lang.org/c/scala-center/25).
+
+To have more information about our _completed_ projects, please see the [quarterly activity reports]({% link records.md %}).
+
+## Roadmap for 2024 Q4
+{: .no_toc}
+
+The following sections present our plan for the current quarter.
+Every project description is followed by the concrete results we will deliver and their expected outcome on the Scala community.
+
+* Table of Contents
+{:toc}
+
+### Language, Compiler, Standard Library
+
+Our mission is to reduce the number of bugs in the compiler implementation, to help the community to contribute to these tools, and to make sure they evolve in a way that takes into account the needs of the community.
+
+#### WebAssembly backend for Scala.js
+
+Scala.js 1.17.0 will soon ship with an initial release of the WebAssembly backend.
+This initial implementation produces correct code (the entire test suite of Scala.js passes) and already contains low-hanging fruit optimizations.
+
+Further work is necessary to unlock better performance.
+In particular, we will integrate with [`wasm-opt`](https://github.com/WebAssembly/binaryen), a Wasm-to-Wasm optimizer.
+We already contributed support for the new Exception Handling spec, which our WebAssembly backend relies on.
+
+#### Scala Improvement Process
+
+The [Scala Improvement Process](https://docs.scala-lang.org/sips/index.html) is a process for submitting changes to the Scala language.
+It aims to evolve Scala openly and collaboratively.
+
+We hold regular committee meetings, which we both coordinate and participate in.
+
+### Documentation and Education
+
+Our mission is to improve the structure and content of the website, to create and maintain high-quality online educational content (including online courses), and to help the community to contribute to the website.
+
+#### Getting Started experience with scala-cli
+
+Now that Scala 3.5.0 has been released with Scala CLI as the default Scala command ([SIP-46](https://docs.scala-lang.org/sips/scala-cli.html)), we are updating the getting started experience to be based on it.
+We are creating a new learning path for beginners, recommending the new Scala command.
+There will be emphasis on important Scala tooling, and how it helps the developer experience.
+
+#### Standard library API documentation
+
+Compared to other popular languages, the API documentation of our standard library is terse.
+While that terseness is somewhat compensated by good collections guides, the Scaladoc remains an important source of documentation, as it is available right in our IDEs.
+
+We will start working on a library-wide review of the API documentation, and will make sure it contains comprehensive, standalone information.
+
+#### Tutorials
+
+We identified tutorials as a form of documentation that is underrepresented in the Scala ecosystem.
+As part of the Scala Toolkit effort, we have been writing more tutorials to get things done in Scala.
+We will continue doing so.
+
+### Developer Experience
+
+Our mission is to make sure the tools Scala developers use to edit, analyze, navigate through, transform, compile, run, and debug Scala programs are as easy to use as possible, that they work reliably for everyone, and deliver a great developer experience.
+
+#### sbt 2.x
+
+As mentioned in our past quarterly reports, work on sbt 2.x is well under way.
+
+Many tests now pass after the migration to Scala 3, but much remains to be done.
+We are working on stabilization, as well as on build caching.
+
+In addition, we intend to work on the loading process.
+We will investigate how we can make it lighter and faster.
+
+### Community and Contributor Experience
+
+Our mission is to create the best environment for the emergence of a strong Scala ecosystem made of high-quality, reliable, libraries that bring simple solutions to complex problems.
+
+#### Communication
+
+We will conduct actions aiming at communicating a positive image of Scala, and making people excited about it.
+
+- We will regularly share our achievements and engage the community on our projects _via_ our [LinkedIn](https://www.linkedin.com/company/scala-center/) page.
+- We will speak at tech conferences and local meetups to encourage people to contribute to the Scala ecosystem, and to let non-Scala programmers know about Scala.
+
+### Maintenance Work
+
+We will also spend a small part of our time reviewing pull requests, triaging issues, and fix issues for the following projects, to make sure important points are addressed:
+
+- Scala 3 compiler
+- Scala 2 TASTy reader
+- Scala.js
+- Scaladex
+- Scalafix
+- Scastie
+- Coursier
+- Bloop
+- Metals
+- sbt
+- sbt-dependency-submission
+- scala-debug-adapter
+- tasty-query
+- tasty-mima
+
+## Advisory Board Proposals
+{: .no_toc}
+
+For reference, you can see [here](https://github.com/scalacenter/advisoryboard/tree/master/proposals) the list of Advisory Board proposals and their respective status.
diff --git a/records/2025-Q1-roadmap.md b/records/2025-Q1-roadmap.md
new file mode 100644
index 00000000..cd34248c
--- /dev/null
+++ b/records/2025-Q1-roadmap.md
@@ -0,0 +1,106 @@
+---
+layout: contact
+title: Scala Center Roadmap for 2025 Q1
+---
+
+This page lists the projects that the Scala Center plans to work on during 2025 Q1.
+We also post regular updates about our projects on the [Scala Contributors forum](https://contributors.scala-lang.org/c/scala-center/25).
+
+To have more information about our _completed_ projects, please see the [quarterly activity reports]({% link records.md %}).
+
+## Roadmap for 2025 Q1
+{: .no_toc}
+
+The following sections present our plan for the current quarter.
+Every project description is followed by the concrete results we will deliver and their expected outcome on the Scala community.
+
+Our engineering team will soon be reduced to a single half-time employee.
+The scope of this roadmap reflects that situation.
+
+* Table of Contents
+{:toc}
+
+### Language, Compiler, Standard Library
+
+Our mission is to reduce the number of bugs in the compiler implementation, to help the community to contribute to these tools, and to make sure they evolve in a way that takes into account the needs of the community.
+
+#### Scala Improvement Process
+
+The [Scala Improvement Process](https://docs.scala-lang.org/sips/index.html) is a process for submitting changes to the Scala language.
+It aims to evolve Scala openly and collaboratively.
+
+We hold regular committee meetings, which we both coordinate and participate in.
+
+### Documentation and Education
+
+Our mission is to improve the structure and content of the website, to create and maintain high-quality online educational content (including online courses), and to help the community to contribute to the website.
+
+#### Merge the Scala 2 and 3 books
+
+During the previous year, we brought the Scala 3 book up to date with the content available in the Scala 2 book.
+It is now time to merge them to simplify the documentation structure.
+Moreover, we will replace the Tour of Scala by a single section at the beginning of the common book.
+
+Note that the Scala 3 book covers Scala 2 as well.
+Systematic version tabs allow the readers to consult the same documentation in either version.
+
+#### Scala 3 language specification
+
+In 2024, we updated the Scala 3 specification with all the core changes brought by Scala 3.
+We will finish the effort of integrating the remaining aspects from the Scala 3 reference.
+
+### Developer Experience
+
+Our mission is to make sure the tools Scala developers use to edit, analyze, navigate through, transform, compile, run, and debug Scala programs are as easy to use as possible, that they work reliably for everyone, and deliver a great developer experience.
+
+#### The Scala 3 expression compiler
+
+For Scala 3 only.
+
+The expression compiler is the underlying technology powering "evaluate expression" features in Metals.
+Now that the expression compiler has been stabilized, we will move its Scala 3 support to the Scala 3 compiler repository.
+
+First, this will reduce maintenance efforts.
+The expression compiler will be released automatically as part of the Scala 3 release process.
+Users of Scala 3 will directly benefit from the full debugging features upon release.
+
+Second, this will add a significant amount of tests for debugging features to the CI process of Scala 3.
+It will ensure that changes to the compiler do not break the debugging experience of users.
+Besides the expression compiler per se, tests cover debugging info such as line numbers, which IntelliJ relies on as much as Metals.
+
+Similar work for Scala 2 would not have as much impact, as the Scala 2 compilation pipeline changes less often.
+
+### Community and Contributor Experience
+
+Our mission is to create the best environment for the emergence of a strong Scala ecosystem made of high-quality, reliable, libraries that bring simple solutions to complex problems.
+
+#### Communication
+
+We will conduct actions aiming at communicating a positive image of Scala, and making people excited about it.
+
+- We will regularly share our achievements and engage the community on our projects _via_ our [LinkedIn](https://www.linkedin.com/company/scala-center/) page.
+- We will speak at tech conferences and local meetups to encourage people to contribute to the Scala ecosystem, and to let non-Scala programmers know about Scala.
+
+### Maintenance Work
+
+We will also spend a small part of our time reviewing pull requests, triaging issues, and fix issues for the following projects, to make sure important points are addressed:
+
+- Scala 3 compiler
+- Scala 2 TASTy reader
+- Scala.js
+- Scaladex
+- Scalafix
+- Scastie
+- Coursier
+- Bloop
+- Metals
+- sbt
+- sbt-dependency-submission
+- scala-debug-adapter
+- tasty-query
+- tasty-mima
+
+## Advisory Board Proposals
+{: .no_toc}
+
+For reference, you can see [here](https://github.com/scalacenter/advisoryboard/tree/master/proposals) the list of Advisory Board proposals and their respective status.
diff --git a/resources/img/aissaoui.jpg b/resources/img/aissaoui.jpg
new file mode 100644
index 00000000..0b175b2d
Binary files /dev/null and b/resources/img/aissaoui.jpg differ
diff --git a/resources/img/aissaoui@2x.jpeg b/resources/img/aissaoui@2x.jpeg
new file mode 100644
index 00000000..1da56fe6
Binary files /dev/null and b/resources/img/aissaoui@2x.jpeg differ
diff --git a/resources/img/akka.png b/resources/img/akka.png
new file mode 100644
index 00000000..e2fb4376
Binary files /dev/null and b/resources/img/akka.png differ
diff --git a/resources/img/akka@2x.png b/resources/img/akka@2x.png
new file mode 100644
index 00000000..638f1d6d
Binary files /dev/null and b/resources/img/akka@2x.png differ
diff --git a/resources/img/gradle.png b/resources/img/gradle.png
new file mode 100644
index 00000000..56b54d6f
Binary files /dev/null and b/resources/img/gradle.png differ
diff --git a/resources/img/gradle@2x.png b/resources/img/gradle@2x.png
new file mode 100644
index 00000000..dc8cbae1
Binary files /dev/null and b/resources/img/gradle@2x.png differ
diff --git a/resources/img/jetbrains-original.png b/resources/img/jetbrains-original.png
new file mode 100644
index 00000000..51828374
Binary files /dev/null and b/resources/img/jetbrains-original.png differ
diff --git a/resources/img/jetbrains.png b/resources/img/jetbrains.png
new file mode 100644
index 00000000..1865568c
Binary files /dev/null and b/resources/img/jetbrains.png differ
diff --git a/resources/img/jetbrains@2x.png b/resources/img/jetbrains@2x.png
new file mode 100644
index 00000000..1d5adf60
Binary files /dev/null and b/resources/img/jetbrains@2x.png differ
diff --git a/resources/img/lightbend.png b/resources/img/lightbend.png
deleted file mode 100644
index a937c0bd..00000000
Binary files a/resources/img/lightbend.png and /dev/null differ
diff --git a/resources/img/lightbend@2x.png b/resources/img/lightbend@2x.png
deleted file mode 100644
index 88270b93..00000000
Binary files a/resources/img/lightbend@2x.png and /dev/null differ