Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add a link to the Tooling Spree page #1787

Merged
merged 1 commit into from
Apr 4, 2025
Merged

Add a link to the Tooling Spree page #1787

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion blog/_posts/2025-03-24-evolving-scala.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -301,7 +301,7 @@ This means you can directly dig into the code and make the fixes or improvements

* You can fix bugs in [Scala3](https://github.com/scala/scala3), [IntelliJ](https://github.com/JetBrains/intellij-scala), and [Metals](https://github.com/scalameta/metals) yourself.
Although the codebases are large, it’s not unheard of that someone can dive in and make the fixes necessary for their own use case
* A [Compiler Spree](https://docs.scala-lang.org/contribute/#so-you-want-to-improve-the-scala-3-compiler) and a Tooling Spree are run every three weeks.
* A [Compiler Spree](https://docs.scala-lang.org/contribute/#so-you-want-to-improve-the-scala-3-compiler) and a [Tooling Spree](https://scalameta.org/scala-tooling-spree/) are run every three weeks.
These are remote coding sessions where you can collaborate with core Scala language and tooling contributors on bite-sized bugs and acquire the skills and knowledge to tackle more ambitious issues.

Contributing fixes and improvements to tooling and infrastructure is not easy, but neither is it impossible.
Expand Down