Merge pull request #283 from scala/2023-Q1-reports

Add activity report for Q1 2023 and roadmap for Q2.

Author: julienrf

.github/workflows/ci.yml

@@ -34,4 +34,5 @@ jobs:
              --ignore-empty-alt=true\
              --allow-hash-href=true\
              --enforce-https=false\
-             --ignore-missing-alt=true
+             --ignore-missing-alt=true\
+             --swap-urls "https\:\/\/scala\.epfl\.ch:"

Gemfile

@@ -4,3 +4,4 @@ gem 'webrick'
 #
 gem 'html-proofer'
 # gem 'html-proofer' # link-checking:  bundle exec htmlproofer ./_site/ --only-4xx --ignore-empty-alt=true --allow-hash-href=true
+gem 'jekyll-redirect-from'

Gemfile.lock

@@ -268,6 +268,7 @@ PLATFORMS
 DEPENDENCIES
   github-pages
   html-proofer
+  jekyll-redirect-from
   webrick
 
 BUNDLED WITH

_config.yml

@@ -5,7 +5,7 @@ description: > # this means to ignore newlines until "baseurl:"
   The Scala Center at EPFL. Not-for-profit, "for the good of all"
   steward of Scala.
 baseurl: "" # the subpath of your site, e.g. /blog
-url: "http://scala.epfl.ch" # the base hostname & protocol for your site
+url: "https://scala.epfl.ch" # the base hostname & protocol for your site
 twitter_username: scala_lang
 github_username:  scala
 
@@ -24,3 +24,6 @@ markdown: kramdown
 exclude: ["node_modules", "gulpfile.js", "package.json", "vendor"]
 sass:
   sass_dir: resources/css/sass
+
+plugins:
+  - jekyll-redirect-from

projects.md

@@ -1,175 +1,3 @@
 ---
-layout: contact
+redirect_to: /records/2023-Q2-roadmap.html
 ---
-
-This page lists the projects that the Scala Center will work on during
-the current quarter. 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](./records.html).
-
-## Roadmap for 2023 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.
-
-* Table of Contents
-{:toc}
-
-### Make Scala tooling seamless for newcomers, and provide robust foundations for the Scala ecosystem
-
-#### Polish sbt and Coursier
-
-Most of the Scala projects are built with sbt, which uses Coursier under the hood.
-The Coursier CLI is also the recommended way to get started in Scala. We want to make sure these tools
-work well for everyone. In collaboration with the current maintainers Eugene Yokota and Alexandre Archambault, we will
-address the most important issues that are currently opened. Read our roadmap for Coursier [here](https://contributors.scala-lang.org/t/bugfixes-and-seamless-installation-process-for-coursier/6052).
-
-#### TASTy-MiMa
-
-[TASTy-query](https://github.com/scalacenter/tasty-query) is a work-in-progress
-library to read TASTy files, explore them, and ask semantic questions about
-them. It is independent from the compiler, and can be used as a building 
-block to implement tools performing static analyses of Scala programs. An
-example is TASTY-MiMa, an upcoming tool “like
-[MiMa](https://github.com/lightbend/mima), but for TASTy”.
-
-We plan to implement support for semantic queries such as “are two types 
-equivalent?”, “is a type a subtype of another one?”, etc., and to publish a 
-prototype of TASTy-MiMa.
-
-You can read the full roadmap
-[here](https://contributors.scala-lang.org/t/the-scala-centers-roadmap-for-tasty-query/5564).
-
-#### Create a Stable API for the Scala 3 Presentation Compiler
-
-Currently, Metals works only for a limited subset of Scala 3 versions. Furthermore, we need to publish
-a new release of Metals after every new release of the compiler to support it.
-
-We would like to create a stable API for the Scala 3 presentation compiler to untie Metals to the compiler
-release cycle and support a wider range of Scala 3 versions (including experimental versions of Scala 3).
-
-#### Reduce the Number of Ways to Import Scala Projects in IDEs
-
-Currently, when starting new projects in Metals the build server that is used by default is Bloop. Part of this is for historical reasons, but part of it is also due to the speed of Bloop and the integrations that exist for it. Bloop has been incredibly important in the Build Server arena. However, there is also BSP implementation in sbt and in Mill and even when a `.bsp/<build-tool>.json` entry exists, Metals will still force Bloop on the user unless they manually switch. This can cause confusion and also may add extra steps into choosing a build server that shouldn't be needed.
-
-This problem also exists in a different way in IntelliJ when you open for example an sbt project that has an existing `.bsp/sbt.json` file you'll be prompted to import the project either as a BSP project or an sbt project. Arguably, newcomers have no idea what BSP is, and they shouldn't have to.
-
-We'd like to minimize the number of ways to import projects and revisit the default choices
-that Metals makes of using Bloop no matter the build tool. The aim is to make
-the experience a newcomer has smoother, abstracting away things like Bloop and
-BSP, while still allowing for a powerful user experience for advanced users. Read the full roadmap and progress
-reports [here](https://contributors.scala-lang.org/t/revisiting-the-default-build-server-for-metals-roadmap/6054).
-
-### Education and Documentation
-
-#### Scala Website
-
-We plan to modernize the Scala website, and to integrate better the Scala 2
-and Scala 3 documentation.
-
-Following up on [the work]({% link records/2022-Q4-activity-report.md %})
-we did in the previous quarter, we plan to polish further the content of the
-website.
-
-The next main tasks are:
-
-- make the content more use-case-oriented rather than features-oriented,
-- reorganize the structure to make it more intuitive according to the reader’s background,
-- create new tutorials to document better how to contribute to the Scala open-source
-  ecosystem.
-
-#### Scala.js
-
-We will finish the work started in early 2022 to [consolidate the Scala.js
-ecosystem](https://contributors.scala-lang.org/t/the-scala-centers-roadmap-for-a-unified-scala-js-ecosystem/5568).
-
-With the help of the community, we plan to document the best practices to 
-have a productive development environment in Scala.js.
-
-#### Language Specification
-
-Currently, there is no proper language specification for Scala 3. A specification would be useful for
-developers, when they want to quickly check something about a feature they are using. It would also
-be useful to the [Scala Improvement Process](https://docs.scala-lang.org/sips), to provide a basis
-for discussions and proposals.
-
-Some pieces of specification
-are available in the [Scala 3 Reference](https://docs.scala-lang.org/scala3/reference), but these
-pieces are mostly about the differences compared to Scala 2. We will complete them, and publish a
-proper language specification for Scala 3.
-
-### Communication
-
-We will conduct many actions aiming at communicating a positive image of Scala,
-and making people excited about it.
-
-- We will publish a five-year report detailing the activities and impact of 
-  the Scala Center during the past five years!
-- 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 create an online shop where individual will be able to give 
-  donations to the Scala Center in exchange for goodies,
-- 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,
-- We will publish two new videos in the series [Let’s talk about Scala
-  3](https://www.youtube.com/playlist?list=PLTx-VKTe8yLxYQfX_eGHCxaTuWvvG28Ml)
-  to highlight the strengths of Scala 3.
-
-### Community, Sustainability, and Governance
-
-#### Scala 3 Compiler Academy
-
-We believe that the pool of knowledgeable people about the Scala 3 compiler 
-implementation is too small. We will create a self-sustaining knowledge hub 
-for the compiler where others can come and be effectively mentored to be 
-compiler contributors.
-
-We are continuously adding content to the
-[Scala 3 Compiler Academy](https://www.youtube.com/channel/UCIH0OgqE54-KEvYDg4LRhKQ)
-YouTube channel, and we run regular events to onboard external contributors on
-the compiler codebase. In case you are interested in contributing to the Scala 3
-compiler, please register by [filling this form](https://forms.gle/DfoSuHFm3T6MA3L59).
-
-#### 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 have restarted the process in 2022, and
-we now have regular committee meetings.
-
-#### Promote Simple Scala Solutions
-
-We feel that, currently, the Scala ecosystem has a focus on advanced
-expert-level tools and libraries, favouring power and flexibility over
-familiarity and ease of onboarding. We believe that newcomers don’t need to
-learn advanced concepts such as pure functional programming or reactive
-programming to be productive in Scala.
-
-In partnership with VirtusLab, we will contribute to the creation of tutorials
-demonstrating how to solve typical programming tasks in a more approachable
-programming style.
-
-### Maintenance Work
-
-We will also spend a small part of our time reviewing pull requests, 
-triaging issues, and sometimes implementing pull requests for the following 
-projects, to make sure important points are addressed:
-
-- Scala 3 compiler
-- Scala 2 TASTy reader
-- Scaladex
-- Scastie
-- Coursier
-- sbt
-
-## 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.

records.md

@@ -13,6 +13,7 @@ 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 %}).
 
+- [2023, Q1]({% link records/2023-Q1-activity-report.md %})
 - [2022, Q4]({% link records/2022-Q4-activity-report.md %})
 - [2022, Q3]({% link records/2022-Q3-activity-report.md %})
 - [2022, Q2]({% link records/2022-Q2-activity-report.md %})