Skip to content

Commit 32107dd

Browse files
SethTisueSethTisue
committed
Merge remote-tracking branch 'origin/main' into minutes-032
2 parents eed37c1 + 03a1b45 commit 32107dd

File tree

5 files changed

+423
-1
lines changed

5 files changed

+423
-1
lines changed

‎minutes/_posts/2024-02-07-february-7-2024.md

+167
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,167 @@
1+
---
2+
layout: contact
3+
---
4+
5+
# Minutes of the 31st meeting of the Scala Center, Q4 2023
6+
7+
Minutes are [archived](https://scala.epfl.ch/records.html) on the
8+
Scala Center website.
9+
10+
## Summary
11+
12+
The following agenda was distributed to attendees:
13+
[agenda](https://github.com/scalacenter/advisoryboard/blob/main/agendas/031-2023-q4.md).
14+
15+
Center activities for the past quarter focused on Scala 3 features and
16+
compiler performance, Scala.js, the Scala Improvement Process, sbt 2,
17+
Scastie, Scala CLI, TASTy Query, Advent of Code, compiler sprees,
18+
Google Summer of Code, fundraising, and more.
19+
20+
Details are below and in the Center's activity report:
21+
22+
* [report](https://scala.epfl.ch/records/2023-Q4-activity-report.html)
23+
24+
No new proposals were received this quarter.
25+
26+
## Date, Time and Location
27+
28+
The meeting took place virtually on Tuesday, February 7, 2024 at
29+
15:00 (UTC).
30+
31+
Minutes were taken by Seth Tisue (secretary).
32+
33+
## Attendees
34+
35+
Officers:
36+
37+
* Chris Kipp (chairperson)
38+
* Darja Jovanovic (executive director), EPFL
39+
* Sébastien Doeraene (interim technical director), EPFL
40+
* Martin Odersky (technical advisor), EPFL
41+
* Seth Tisue (secretary), Lightbend
42+
43+
Board members:
44+
45+
* Noel Markham, Xebia Functional
46+
* Paweł Marks, VirtusLab (subbing for Krzysztof Romanowski)
47+
* Claire McGinty, Spotify
48+
* Lukas Rytz, Lightbend
49+
* Daniela Sfregola, Morgan Stanley
50+
* Eugene Yokota, community representative
51+
52+
## Technical report
53+
54+
Seb, as interim technical director, summarized Scala Center activities
55+
since the last meeting. His remarks mainly consisted of brief
56+
highlights taken from the Center's more detailed Q4 quarterly activity
57+
report:
58+
59+
* [report](https://scala.epfl.ch/records/2023-Q4-activity-report.html)
60+
61+
And the Center's Q4 roadmap:
62+
63+
* [roadmap](https://scala.epfl.ch/records/2023-Q4-roadmap.html)
64+
65+
The following notes do not repeat the contents of the report and
66+
roadmap, but only supplement them.
67+
68+
Martin offered congratulations to Eugene and the Center on getting sbt
69+
2.x initially compiling on Scala 3. Eugene mentioned that a number of
70+
"hacks" in the sbt codebase were no longer necessary on Scala 3, and
71+
that the new macro implementations were "safer" thanks to Scala 3.
72+
73+
The Center declined to issue a ruling on whether Scala CLI is
74+
pronounced "Scala C.L.I." or "Scala Clee" :-)
75+
76+
Chris asked about broader Scalafix improvements, as previously
77+
discussed in 2021 when
78+
[SCP-027](https://github.com/scalacenter/advisoryboard/blob/main/proposals/027-refactoring.md)
79+
was submitted. Seb said that hasn't been revisited recently but
80+
they'll take a second look if there is sufficient engineering time
81+
available this year.
82+
83+
Seth observed that Scalafix seems underused in the community, and
84+
although it's not clear why. It could be because it's not well
85+
integrated enough with tooling, and/or insufficient documentation and
86+
publicity? And do people know where to find rules?
87+
88+
Branching off the Scalafix discussion, Eugene observed that we don't
89+
have good centralized documentation and recommendations on what
90+
compiler flags are available and which ones should be enabled (in
91+
general, and also in specific scenarios such as cross-building).
92+
93+
Chris praised the successful recent work on "quickfixes" in Scala 2.
94+
"I'm amazed how easy it is to trigger a quickfix and it makes me so
95+
happy every time it works." This connects to the Scalafix discussion
96+
because quickfixes and Scalafix overlap in purpose, and the compiler
97+
has information about user code that Scalafix may not.
98+
99+
## Scala 2 report
100+
101+
This was presented by Seth.
102+
103+
At the time of the meeting, 2.12.19 was at the release-candidate
104+
stage, 2.13.13 was almost there, and the following forum threads were
105+
open for discussing the contents and timing of the two impending
106+
releases:
107+
108+
* [Scala 2.13.13](https://contributors.scala-lang.org/t/scala-2-13-13-release-planning/6315)
109+
* [Scala 2.12.19](https://contributors.scala-lang.org/t/scala-2-12-19-release-planning/6216)
110+
111+
After the meeting, the following threads were opened to discuss the
112+
next releases:
113+
114+
* [Scala 2.12.20](https://contributors.scala-lang.org/t/scala-2-12-20-release-planning/6580)
115+
* [Scala 2.13.14](https://contributors.scala-lang.org/t/scala-2-13-14-release-planning/6581)
116+
117+
The technical highlight of 2.13.13 is the introduction of
118+
`-Xsource:3-cross` as an alternative to `-Xsource:3`; the former is
119+
for crossbuilding, the latter for migration.
120+
121+
## Community report
122+
123+
Eugene led some brief discussion about the health of various segments
124+
of the community (Spark users, Typelevel, ZIO, Akka, and so forth).
125+
126+
He also noted that his experience with co-organizing Scala Matsuri is
127+
that times are currently tough for conference organizers, especially
128+
in seeking sponsorship, likely because the job market in IT generally
129+
is weak, and sponsorship money is often motivated by recruiting.
130+
131+
Darja said that she's very encouraged by all the signs she's seeing
132+
that conference and meetup activity are reviving, post-pandemic.
133+
134+
Eugene also updated us on the health of the sbt plugin ecosystem.
135+
Many plugins have changed owners, dormant plugins are being revived,
136+
and many are now publishing to Maven Central. The Play and Pekko
137+
projects are among the drivers of this work.
138+
139+
Chris asked the Center if a second community representative has
140+
been found yet. Darja says that a strong candidate has emerged
141+
and will hopefully join next quarter.
142+
143+
## Management and financial report
144+
145+
This was presented by Darja. Her report centered on fundraising. The
146+
Center is in need of new money, as a number of board members bowed out
147+
in 2023. The Center is pursuing various potential funding
148+
prospects. It seems that times are tough all over for open source
149+
funding. As part of bringing new members on board, some adjustments to
150+
the charter may be proposed, for example, to flexibly accommodate
151+
different sizes of company. Details remain to be seen.
152+
153+
For practical reasons, and to the Center's regret, there is little
154+
likelihood of Scala Days happening in 2024. The Center is highly
155+
optimistic that it can be revived in 2025; doing that is a high
156+
priority. (There was a long discussion about various ways this
157+
might hypothetically play out.)
158+
159+
There was also some discussion of what online services the Center
160+
should be using for publicity. One theme that came up is that some
161+
venues are better suited for interaction with the community, others
162+
best used only to broadcast announcements.
163+
164+
## Conclusion
165+
166+
We talked about what upcoming conferences we might see each other at,
167+
otherwise, see you online!

‎projects.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,3 @@
11
---
2-
redirect_to: /records/2024-Q4-roadmap.html
2+
redirect_to: /records/2025-Q1-roadmap.html
33
---

‎records.md

+2
Original file line numberDiff line numberDiff line change
@@ -14,6 +14,7 @@ Every quarter, the Scala Center publishes an activity report detailing the
1414
work that has been achieved. You can find the roadmap for the current quarter
1515
in the [Projects page]({% link projects.md %}).
1616

17+
- [2024, Q4]({% link records/2024-Q4-activity-report.md %})
1718
- [2024, Q2-Q3]({% link records/2024-Q2-Q3-activity-report.md %})
1819
- [2024, Q1]({% link records/2024-Q1-activity-report.md %})
1920
- [2023, Q4]({% link records/2023-Q4-activity-report.md %})
@@ -39,6 +40,7 @@ in the [Projects page]({% link projects.md %}).
3940

4041
### Board meeting minutes
4142

43+
- [February 7, 2024 - Thirty-First SC Advisory Board Meeting](/minutes/2024/02/07/february-7-2024.html)
4244
- [October 17, 2023 - Thirtieth SC Advisory Board Meeting](/minutes/2023/10/17/october-17-2023.html)
4345
- [July 26, 2023 - Twenty-Ninth SC Advisory Board Meeting](/minutes/2023/07/26/july-26-2023.html)
4446
- [April 27, 2023 - Twenty-Eighth SC Advisory Board Meeting](/minutes/2023/04/27/april-27-2023.html)

‎records/2024-Q4-activity-report.md

+147
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,147 @@
1+
---
2+
layout: contact
3+
title: Scala Center Activity Report for 2024 Q4
4+
---
5+
6+
Scala Center team:
7+
Darja Jovanovic, 100%;
8+
Adrien Piquerez, 80%;
9+
Sébastien Doeraene, 50%;
10+
Guillaume Martres, 20%;
11+
Valérie Meillaud: 30%.
12+
VirtusLab team: Gabriel Kepka, 100%.
13+
14+
## At a Glance
15+
{: .no_toc}
16+
17+
* Table of Contents
18+
{:toc}
19+
20+
21+
## Language, Compiler, Standard Library
22+
23+
### Maintainance of the Scala 3 Compiler
24+
25+
For Scala 3.
26+
27+
Every month, about 100 new issues are opened on [the Scala 3 repository](https://github.com/scala/scala3).
28+
The project welcomes any help it can get in triaging, bug-fixing, PR reviewing, etc.
29+
30+
Our goal is to solve long-standing issues while keeping up with new ones.
31+
We also aim to get more people involved in working on the compiler to ensure the sustainability of the project.
32+
33+
We contributed PRs for bug fixes in various areas, notably match types.
34+
We also invested more in reviewing PRs from external and internal contributors alike.
35+
36+
### Scala.js maintenance
37+
38+
For Scala 2 and 3.
39+
40+
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/).
41+
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.
42+
43+
This quarter, we only performed behind-the-scenes maintenance of Scala.js: internal cleanups that will ease future developments.
44+
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/).
45+
46+
### Scala Improvement Process
47+
48+
For Scala 3.
49+
50+
The [Scala Improvement Process](https://docs.scala-lang.org/sips/) coordinates the evolution of the language.
51+
It ensures that the decisions are made by taking into account the needs of all the stakeholders of the language.
52+
53+
## Developer Experience
54+
55+
### Scala Toolkit
56+
57+
For Scala 2 and Scala 3.
58+
59+
We released a new version of the Toolkit:
60+
61+
- [0.6.0](https://github.com/scala/toolkit/releases/tag/0.6.0): updated library versions
62+
63+
### Documentation
64+
65+
For Scala 2 and Scala 3.
66+
67+
After the release of Scala 3.5.0, we updated the documentation website to use `scala-cli` as the entry point to the language.
68+
69+
We continued our work to simplify the documentation structure.
70+
In particular, the Scala 3 book now contains at least as much information as the Scala 2 book.
71+
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.
72+
73+
We also worked on documenting features not yet included in the documentation, such as `boundary`/`break`.
74+
75+
### sbt
76+
77+
For Scala 2 and Scala 3.
78+
79+
We continued our efforts to stabilize sbt 2.x.
80+
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.
81+
82+
### Scala 3 specification
83+
84+
For Scala 3.
85+
86+
We finished the following areas of the Scala 3 specification:
87+
88+
* for comprehensions
89+
* match types
90+
91+
## Community and Contributor Experience
92+
93+
For Scala 2 and Scala 3 throughout.
94+
95+
### Scala Highlights
96+
97+
We are about to release the first edition of Scala Highlights, a new quarterly newsletter showcasing technical achievements, online resources, and community news.
98+
99+
The newsletter is a joint effort by the Scala Center, LAMP, Akka, and VirtusLab, the four core organizations involved in the Scala language development.
100+
It also covers our collaborations with other parties, such as the Scala Center's advisory board.
101+
102+
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.
103+
Future issues will cover quarterly highlights.
104+
105+
It might be released by the time you read these lines.
106+
If not, you can [read it in the pull request](https://github.com/scala/scala-lang/pull/1744).
107+
108+
### Google Summer of Code
109+
110+
Google Summer of Code (GSoC) has been a long-standing vehicle for the Scala Center to attract newcomers to the Scala OSS world.
111+
112+
The Scala Center acts as an organization shepherding the projects related to Scala.
113+
As such, we perform administrative tasks and mentor several projects.
114+
115+
We concluded the 2024 edition with 10 successfull projects, which is a record high for our organization.
116+
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).
117+
118+
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).
119+
120+
#### Scala Advent of Code
121+
122+
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.
123+
124+
One of our core priorities is to communicate excitement about Scala.
125+
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.
126+
127+
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.
128+
Many external volunteers wrote solution articles, leading to 24 out of the 25 days to be covered.
129+
130+
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.
131+
132+
### Compiler Sprees
133+
134+
We maintained our involvement in the [Scala 3 Compiler Academy Issue Spree](https://www.scala-lang.org/blog/2022/11/02/compiler-academy.html).
135+
136+
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.
137+
138+
## Scala Center Administration
139+
140+
### Sovereign Tech Fund
141+
142+
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."
143+
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.
144+
We are hopeful that they will choose to support Scala as well.
145+
146+
So far, we passed the first stage of the evaluation process.
147+
Next steps involve scoping more precisely the work that would be covered by the grant.

0 commit comments

Comments
 (0)