full minutes

Author: SethTisue

minutes/_posts/2024-09-05-september-5-2024.md

@@ -9,18 +9,16 @@ Scala Center website.
 
 ## Summary
 
-The following agenda was distributed to attendees:
-[agenda](TODO).
-
 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.
 
-(TODO any board changes?)
-
-(TODO staffing changes?)
-
-Center activities for the past two quarters focused on TODO
+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:
 
@@ -34,7 +32,7 @@ Two new proposals were received:
 Both proposals were accepted by the board (and both were later
 completed, in October).
 
-Other topics covered included TODO
+Other topics covered included the long-term future of the Center.
 
 ## Date, Time and Location
 
@@ -65,6 +63,7 @@ Board members:
 Guests:
 
 * James Belsey, Morgan Stanley
+* Damian Mazurkiewicz, SiriusXM
 * Valérie Meillaud, Scala Center
 
 Apologies:
@@ -73,7 +72,7 @@ Apologies:
 
 ## Introduction
 
-TODO
+This special in-person meeting lasted two full days.
 
 ## Technical report
 
@@ -90,54 +89,118 @@ And the Center's Q4 roadmap:
 The following notes do not repeat the contents of the report and
 roadmap, but only supplement them.
 
-TODO
+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.
 
-## Management and financial report
+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.
 
-TODO
+### Scala 2 report
 
-## Scala 2 report
+This was presented by Lukas.
 
-This was presented by TODO
+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.
 
-TODO
+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 Eugene and Zainab.
+This section was led by Zainab. (Eugene was unable to attend.)
 
-TODO
+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
 
-The proposal was discussed by the board. We neglected to hold a formal
-vote, but we confirmed with the board afterwards that the proposal
-should be considered accepted by acclaim.
+Discussion was brief, since the board sees the need, but there wasn't
+yet a draft text available to give feedback on.
 
-(Later, in October 2024, the proposal was considered completed.)
+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. We neglected to hold a formal
-vote, but we confirmed with the board afterwards that the proposal
-should be considered accepted by acclaim.
+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.)
 
-## Other business
+## 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.
 
-TODO
+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).
-