@@ -12,15 +12,26 @@ Scala Center website.
12
12
The following agenda was distributed to attendees:
13
13
[ agenda] ( https://github.com/scalacenter/advisoryboard/blob/main/agendas/032-2024-q1.md ) .
14
14
15
- Center activities for the past quarter focused on TODO
15
+ We were joined by two new board members, Dmitrii Naumenko (JetBrains)
16
+ and Zainab Ali (community representative).
17
+
18
+ Center activities for the past quarter focused on pipelined
19
+ compilation (Scala 3), TASTy Reader (Scala 2), Scala.js minifier (2
20
+ and 3), WebAssembly backend for Scala.js (2 and 3), Metals debugger (2
21
+ and 3), presentation compiler (3), sbt 2.x (2 and 3), the Scala
22
+ Ambassadors initiative, Google Summer of Code, conferences (Scala.IO
23
+ and Scalar), compiler sprees, combating Scala website scammers,
24
+ and fundraising.
16
25
17
26
Details are below and in the Center's activity report:
18
27
19
28
* [ report] ( https://scala.epfl.ch/records/2024-Q1-activity-report.html )
20
29
21
30
No new proposals were received this quarter.
22
31
23
- Other business discussed included TODO
32
+ Other topics covered included Scala Days community discussions around
33
+ "lean Scala" and "direct style" and related concepts, Scala LTS
34
+ vs. Scala Next, the Scala Native 0.5 upgrade, and more.
24
35
25
36
## Date, Time and Location
26
37
@@ -48,7 +59,22 @@ Board members:
48
59
* Daniela Sfregola, Morgan Stanley
49
60
* Eugene Yokota, community representative
50
61
51
- TODO board changes?
62
+ Apologies:
63
+
64
+ * Michel Davit, Spotify
65
+
66
+ ## Introduction
67
+
68
+ Our two new board members introduced themselves.
69
+
70
+ Dmitrii Naumenko will represent JetBrains, who have just finished
71
+ joining the board. Dmitrii is the leader of the IntelliJ Scala plugin
72
+ team there.
73
+
74
+ Zainab Ali is a new community representative, serving alongside Eugene
75
+ Yokota. She has been organizing the London Scala Users Group for the
76
+ last five years or so. She describes herself as a functional Scala
77
+ developer who does training in the functional space.
52
78
53
79
## Technical report
54
80
@@ -62,25 +88,120 @@ And the Center's Q2 roadmap:
62
88
63
89
* [ roadmap] ( https://scala.epfl.ch/records/2024-Q2-roadmap.html )
64
90
65
- The following notes do not repeat the content of the report and
91
+ The following notes do not repeat the contents of the report and
66
92
roadmap, but only supplement them.
67
93
68
- TODO
94
+ (No questions were asked about Seb's updates, so there are no further
95
+ notes here.)
69
96
70
97
## Management and financial report
71
98
72
99
Darja presented this section.
73
100
101
+ In February, the Center published their [ 2024
102
+ roadmap] ( https://www.scala-lang.org/blog/2024/02/06/scala-center-2024-roadmap.html ) .
103
+
104
+ The Center published two blog posts about scammers targeting Scala users:
105
+
106
+ * https://scala-lang.org/blog/2024/03/01/fake-scala-courses.html
107
+ * https://www.scala-lang.org/blog/2024/03/18/scam-response.html
108
+
109
+ Combating these scams consumed considerable time and effort, but the
110
+ good news is that the scamming activity did stop.
111
+
112
+ At the Scalar conference in Warsaw, the Center organized a meeting of
113
+ conference and meetup organizers and also launched the new [ Scala
114
+ Ambassadors program] ( https://scala-lang.org/blog/2024/03/28/ambassadors-initiative.html ) .
115
+
116
+ The Center's participation in Google Summer of Code for 2024 is moving
117
+ ahead.
118
+
119
+ The Center's moderation team met in person in Lausanne to share knowledge
120
+ and experiences and to discuss and strategize.
121
+
122
+ The Center's governance project made progress which Darja summarized.
123
+ That work was eventually completed later in the year, as described
124
+ in this October 2024 blog post:
125
+
126
+ * https://www.scala-lang.org/news/new-governance.html
127
+
128
+ Several engineers completed their time at the Center and moved on:
129
+ Anatolii Kmetiuk, Jamie Thompson, and Jedrzej Rochala. Seb will be
130
+ teaching part-time at EPFL, so his effort level at the Center will be
131
+ reduced to 50%. Hiring new engineers would require new funding.
132
+
133
+ The Center's 2024 roadmap reflects the smaller size of the engineering
134
+ team. Center staff will travel less unless the travel is sponsored.
135
+ The Center will continue to "support, empower, and amplify" active
136
+ Scala communities and community members to accomplish things that the
137
+ Center itself cannot.
138
+
139
+ The Center continues to collect income from its MOOCs, but the amount
140
+ continues to gradually decline.
141
+
142
+ Fundraising efforts are ongoing. Multiple leads are being pursued.
143
+
144
+ The effort to revive Scala Days for 2025 is ongoing. In the meantime,
145
+ the Scala website's [ events page] ( https://www.scala-lang.org/events/ )
146
+ is kept up to date with upcoming events.
147
+
74
148
## Scala 2 report
75
149
76
150
This was presented by Lukas.
77
151
78
- TODO
152
+ Since the last meeting, Scala 2.12.19 and 2.13.13 were released,
153
+ and 2.13.14 is almost ready. The 2.13.14 cycle was short because
154
+ of a few regressions. 2.13.14 introduces ` -Xsource-features ` .
155
+
156
+ Lukas contributed an sbt PR, now merged, which aligns sbt with
157
+ [ SIP-51] ( https://docs.scala-lang.org/sips/drop-stdlib-forwards-bin-compat.html ) ,
158
+ which will allow the Scala 2.13 standard library (which is also used
159
+ by Scala 3) to make additions again. A process for that will need
160
+ to be set up.
79
161
80
162
## Community report
81
163
82
- TODO
164
+ This section was led by Eugene and Zainab.
165
+
166
+ They said that in the community there is a great deal of discussion,
167
+ some confusion and uncertainty, and even some tension around the
168
+ following complex of issues and developments: effect systems, the
169
+ advent of Project Loom, the concept of "direct style", and Martin's
170
+ [ blog post] ( https://odersky.github.io/blog/2024-04-11-post.html ) about
171
+ "lean Scala". Discussion involving nearly the entire board ensued.
172
+
173
+ Eugene said there was also some confusion in the community about Scala
174
+ LTS vs Scala Next. As will be described in the next minutes, Zainab
175
+ later submitted a proposal asking the Center to provide clearer public
176
+ guidance on this, and that proposal was completed by the publication
177
+ of [ this new page] ( https://scala-lang.org/development/ ) .
178
+
179
+ Zainab praised the organizers gathering at Scalar in Warsaw in March,
180
+ which was "useful" in strengthening networking between conference and
181
+ meetup organizers. In London they are hoping to do even more events
182
+ besides just talks, such as workshops, open-source sprees, and katas.
183
+ She also expressed hope that the Center's new [ Scala
184
+ Ambassadors] ( https://scala-lang.org/blog/2024/03/28/ambassadors-initiative.html )
185
+ initiative will help onboard people who want to get more involved with
186
+ community.
187
+
188
+ Zainab mentioned that pushing the Scala Native 0.4 to 0.5 upgrade
189
+ through the open source ecosystem has been difficult. In response, Seb
190
+ recalled when Scala.js went from 0.6 to 1.0, a transition he described
191
+ as "difficult and long", yet necessary. Scala Native 0.4 was 3 to 4
192
+ years ago, so the big jump to 0.5 is now "unfortunately necessary",
193
+ but the Native team "very much hopes" that this is "the last one
194
+ before 1.0", which is probably "a few years down the line". Eugene
195
+ added that setting up a Scala.js or Scala Native community build, like
196
+ the existing JVM-centric Scala 2 and Scala 3 community builds, could
197
+ really help (if resources could be found for such an effort). Seth
198
+ added that library maintainers shouldn't be shy about requesting help
199
+ from Scala Native enthusiasts, rather than feeling obligated to sort
200
+ out problems themselves.
83
201
84
202
## Conclusion
85
203
86
- TODO
204
+ Darja intends to organize an in-person advisory board meeting to be
205
+ held at EPFL in the fall. Everyone on the board indicated they would
206
+ make an effort to attend. (The in-person meeting did in fact occur, in
207
+ September, and it will be covered in the next minutes.)
0 commit comments