Skip to content

Commit 59a1905

Browse files
committed
April 2023 minutes
1 parent 91629e9 commit 59a1905

File tree

2 files changed

+217
-0
lines changed

2 files changed

+217
-0
lines changed
200 KB
Binary file not shown.
Lines changed: 217 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,217 @@
1+
---
2+
layout: contact
3+
---
4+
5+
# Minutes of the 28th meeting of the Scala Center, Q1 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/028-2023-q1.md).
14+
15+
Center activities for the past quarter focused on Scala 3 maintenance
16+
and evolution, the Scala Improvement Process, Scala.js maintenance and
17+
tooling and tutorials, the Scala Toolkit, the Scala websites, the
18+
Scala Tooling Summit, TASTy-MiMa and TASTy-Query, Metals and BSP,
19+
Scaladex, the Scala 3 Compiler Academy and Compiler Sprees, Google
20+
Summer of Code, Scala Lunches at EPFL, Scala Days, and the
21+
Center's five-year impact report.
22+
23+
Details are below and in the Center's activity report:
24+
25+
* [report](https://scala.epfl.ch/records/2023-Q1-activity-report.html)
26+
27+
Two new proposals were received this quarter:
28+
29+
* [SCP-029](https://github.com/scalacenter/advisoryboard/blob/main/proposals/029-sbt-community-repository.md): Sbt community repository
30+
* [SCP-030](https://github.com/scalacenter/advisoryboard/blob/main/proposals/030-governance-page.md): Governance page
31+
32+
Both proposals were voted on and accepted by the board.
33+
34+
Other business discussed included SCP-027 (Refactoring), the Tooling
35+
Summit, and company overviews for Morgan Stanley and Spotify.
36+
37+
## Date, Time and Location
38+
39+
The meeting took place virtually on Thursday, April 27, 2023 at
40+
15:00pm (UTC).
41+
42+
Minutes were taken by Seth Tisue (secretary).
43+
44+
## Attendees
45+
46+
Officers:
47+
48+
* Chris Kipp (chairperson)
49+
* also board member, representing Lunatech
50+
* Darja Jovanovic (executive director), EPFL
51+
* Julien Richard-Foy (technical director), EPFL
52+
* Seth Tisue (secretary), Lightbend
53+
54+
Apologies:
55+
56+
* Martin Odersky (technical advisor), EPFL
57+
58+
Board members:
59+
60+
* Diego Alonso, 47 Degrees
61+
* Maureen Elsberry, Xebia Functional
62+
* Claire McGinty & Kellen Dye, Spotify
63+
* Krzysztof Romanowski, VirtusLab
64+
* Lukas Rytz, Lightbend
65+
* Daniela Sfregola, Morgan Stanley
66+
* Eugene Yokota, community representative
67+
68+
## Technical report
69+
70+
Julien summarized Scala Center activities since the last meeting.
71+
He presented from these slides, which concisely show what the
72+
Center is working on:
73+
74+
* [slides](./2023-04-27-julien.pdf)
75+
76+
His slides and remarks were based on the Center's more detailed Q1
77+
quarterly activity report:
78+
79+
* [report](https://scala.epfl.ch/records/2023-Q1-activity-report.html)
80+
81+
And the Center's Q2 roadmap:
82+
83+
* [roadmap](https://scala.epfl.ch/records/2023-Q2-roadmap.html)
84+
85+
The following notes do not repeat the content of the report and
86+
roadmap, but only supplement them.
87+
88+
### SCP-027: Refactoring
89+
90+
Julien asked the board about [SCP-027: Refactoring](https://github.com/scalacenter/advisoryboard/blob/main/proposals/027-refactoring.md), which he suggested be marked "dormant", based on what seems to be limited interest from either the board or the community. The proposal was originally submitted by Eugene when he was representing Twitter. In response, Eugene observed that there were multiple talks at Scala Matsuri about refactoring in large monorepos and reaffirmed the proposal's importance, in his opinion (though he acknowledged that resources are always finite). Darja and Julien said let's wait to see if there was any more external feedback, before changing the proposal's status.
91+
92+
## Management report
93+
94+
Darja presented this section. She especially highlighted the following items.
95+
96+
Since the last meeting, the Scala Center published the following
97+
annual roadmap for 2023:
98+
99+
* [roadmap blog post](https://scala-lang.org/blog/2023/01/31/scala-center-2023-roadmap.html)
100+
101+
Scala.js celebrated its 10th anniversary:
102+
103+
* [Scala.js anniversary blog post](https://www.scala-lang.org/blog-detail/2023/02/05/ten-years-of-scala-js.html)
104+
105+
The Scala Center hosted a Tooling Summit at EPFL, with about 40 participants:
106+
107+
* [Tooling Summit blog post](https://www.scala-lang.org/blog/2023/04/11/march-2023-scala-tooling-summit.html)
108+
109+
The Center published its Five Year Impact Report:
110+
111+
* [Five Year Impact Report](https://scala.epfl.ch/records/first-five-years/)
112+
113+
Staffing levels remained constant this quarter, except for interns.
114+
Quentin Bernet's internship with the Center is now complete. Johanna
115+
Reichen and Lucas Nouguier have joined the Center for a limited time.
116+
117+
Darja shared some thoughts and plans around fundraising for the
118+
Center. Some discussion followed.
119+
120+
## Scala 2 report
121+
122+
This was presented by Lukas.
123+
124+
The Scala 2.13.11 and 2.12.18 releases are nearly complete but will
125+
wait for 3.3.0 to happen first. Since the last meeting, we opened the
126+
following Discourse threads for discussion and updates on release
127+
timing:
128+
129+
* [Scala 2.13.11](https://contributors.scala-lang.org/t/scala-2-13-11-release-planning/6088)
130+
* [Scala 2.12.18](https://contributors.scala-lang.org/t/scala-2-12-18-release-planning/6089)
131+
132+
Since the meeting, these threads were updated to include draft release
133+
notes. Themes in these releases including alignment with Scala 3,
134+
linting, JDK 20 and 21 support, `Vector` concatenation, reimplemented
135+
`LinkedHashMap` and `LinkedHashSet`, supported for Java 17's `sealed`,
136+
and more.
137+
138+
## Community report
139+
140+
Eugene said that recurring concerns in the community currently include
141+
Scala 3 adoption, the Akka relicensing, competing library ecosystems,
142+
and the question of what Scala's main use cases or selling points are
143+
perceived to be, going forward.
144+
145+
## Proposals
146+
147+
### SCP-029: Sbt community repository
148+
149+
The text of Eugene's proposal is here:
150+
151+
* [SCP-029](https://github.com/scalacenter/advisoryboard/blob/main/proposals/029-sbt-community-repository.md): Sbt community repository
152+
153+
The proposal was prompted by the recent (April 7) repo.scala-sbt.org
154+
[outage](https://github.com/sbt/sbt/issues/7202). It proposes making
155+
the Scala Center responsible for ensuring the continuance of sbt's
156+
artifact hosting. The repository in question contains both old sbt
157+
plugins and current (and old) Linux installers.
158+
159+
As one board member observed, sbt isn't formally a Scala Center
160+
project, and this proposal, which is limited in scope to binary
161+
hosting, wouldn't change that. But the community doesn't always make
162+
these distinctions around ownership; an sbt outage is damaging to
163+
Scala's image regardless.
164+
165+
Julien said the Center is already investigating options. (Perhaps the
166+
existing hosting is adequate as long as we are better prepared to
167+
respond to outages?)
168+
169+
A suggestion was made to host the Linux installers on GitHub instead.
170+
171+
**Voting**: The proposal was accepted, by unanimous vote of members
172+
present.
173+
174+
### SCP-030: Governance page for Scala
175+
176+
* [SCP-030](https://github.com/scalacenter/advisoryboard/blob/main/proposals/030-governance-page.md): Governance page
177+
178+
Krzysztof presented his proposal. He emphasized that the proposal
179+
isn't to create any new structures or responsibilities, but just to
180+
document what exists. He also said that incremental progress on
181+
documenting governance would be valuable; it doesn't need to happen
182+
all at once.
183+
184+
Seth noted on the pull request that there is already a "Who's behind
185+
Scala?" section on the Community page
186+
[here](https://scala-lang.org/community/#whos-behind-scala), as a
187+
modest starting point.
188+
189+
Darja noted that any such page would need regular updating, and it
190+
would be important for the page not to promise more than the Center
191+
is actually able to provide.
192+
193+
**Voting**: The proposal was accepted, by unanimous vote of members
194+
present.
195+
196+
## Other topics
197+
198+
### Tooling Summit
199+
200+
Since time was running short, Chris kept his remarks about the recent
201+
Tooling Summit very brief. He said that conversation is ongoing about
202+
setting up some ongoing structure for work and communication around
203+
Scala tooling.
204+
205+
Maureen said that the interviews recorded at the summit are still
206+
being edited.
207+
208+
## Company overviews
209+
210+
Daniela gave an overview of Scala usage at Morgan Stanley.
211+
212+
Claire gave an overview of Scala usage at Spotify.
213+
214+
## Conclusion
215+
216+
As was usual through 2019, we hope to hold an in-person board meeting
217+
later this year in conjunction with Scala Days.

0 commit comments

Comments
 (0)