diff --git a/_includes/masthead-governance.html b/_includes/masthead-governance.html
new file mode 100644
index 000000000..9338bc039
--- /dev/null
+++ b/_includes/masthead-governance.html
@@ -0,0 +1,52 @@
+
diff --git a/_layouts/inner-page-governance.html b/_layouts/inner-page-governance.html
new file mode 100644
index 000000000..cfdf25ac6
--- /dev/null
+++ b/_layouts/inner-page-governance.html
@@ -0,0 +1,9 @@
+---
+layout: inner-page-parent
+---
+
+
+{% include masthead-governance.html %}
+
+
+{% include inner-page-main-content.html %}
diff --git a/_posts/2024-10-16-announcing-governance.md b/_posts/2024-10-16-announcing-governance.md
new file mode 100644
index 000000000..dc294159c
--- /dev/null
+++ b/_posts/2024-10-16-announcing-governance.md
@@ -0,0 +1,97 @@
+---
+category: announcement
+permalink: /news/new-governance
+title: "Scala: a mature open-source project"
+by: Scala Core Team
+---
+
+In over twenty years of developing Scala, we’ve learned that good project governance is the key to the maturity, resilience, and health of any open-source project, even more so for a project of the size and complexity of Scala. We learned that governance is iterative and ever-evolving, to follow the project’s development needs and adjust to them. We also learned that transparency is very important to build trust and stability. These are the guiding principles for the Scala teams at LAMP, Lightbend, Scala Center, and VirtusLab, [the organisations that drive Scala development](/governance/#whos-behind-scala).
+
+## The journey so far
+
+We started working on the Scala governance redesign in the wake of the [Scala 3 release](https://scala-lang.org/blog/2021/05/14/scala3-is-here.html) in May 2021\.
+
+The vast landscape of Scala governance was mapped out and presented in a [keynote at ScalaCon 2022](https://www.youtube.com/watch?v=svWnwU5PXxE) by Darja Jovanovic and Adam Goodman. It includes areas like development and release coordination, community management, knowledge transfer, SIP, IT security, Scala Tooling and more. We are proud of the great progress achieved on these fronts in the last three years, and we will continue to grow and evolve these efforts further.
+
+In 2022 we also announced the first major milestone, the updated [Scala Improvement Process](https://www.scala-lang.org/blog/2022/07/13/scala-improvement-process-reloaded.html) to openly and collaboratively evolve the Scala language by accepting and evaluating formal proposals.
+
+In 2023 we held two Tooling Summits to consolidate the tooling ecosystem and ensure a better user experience across the board, as described in the [Lausanne gathering](https://www.scala-lang.org/blog/2023/04/11/march-2023-scala-tooling-summit.html) from March ’23.
+
+And today we are proud and delighted to announce the following additions:
+
+* [Updated governance structure and processes](/governance)
+ outlines the organisation and decision-making bodies, as well as individuals and organisations working on Scala language releases and development, and
+
+* [Scala development guiding policies and guarantees](/development)
+ gives a detailed overview about the key policies, best practices, and guarantees that guide Scala development, ensuring consistency, reliability, and maintainability.
+
+If you are interested in going deeper in these topics, we invite you to read the pages mentioned above.
+
+If you are wondering how these matters impact your daily life as a Scala programmer or a company who uses Scala, keep reading this blog post.
+
+## 5 key improvements every Scala user will benefit from
+
+### Product-driven decision making process
+
+One of the most significant updates was the paradigm shift from treating Scala 3 as an open-source project to approaching it as an open-source product. Scala 3 is developed with predictable release cycles, issue reports are consistently prioritised and added to a milestone, and the roadmap for new features and improvements is well-defined. This focus on product success is fully reflected in the governance model and structure, led by the Product Manager, Piotr Chabelski from the Scala team at VirtusLab. This approach was inspired by the Scala 2 era and its ongoing success.
+
+### Well defined Scala distributions
+
+Scala 3.x releases are always backward compatible, but not the opposite to allow evolving and improving the language. This creates a complex challenge of aligning the library ecosystem on a baseline version, which was resolved with introducing two parallel distributions, as designed by Paweł Marks from the Scala team at VirtusLab:
+
+* Scala Next is the default line that is actively developed by the compiler team, and is the preferred target version for all non-library projects.
+* Scala LTS (long term support) is the preferred target version for libraries.
+
+This is explained further in [Scala development guarantees](/development).
+
+As before, Scala 2 has stable 2.13 and 2.12 distributions.
+
+### Predictable and frequent releases
+
+The new governance model and structure improved the coordination between different teams working on Scala development and releases. We have been testing the model since February 2024 and we are confident that technical decisions around Scala releases and distributions are now synchronised and running smoothly. As a result, Scala 3 users experience [predictable, well-managed releases](/development/#schedule-iterations-and-roadmap), typically at six to twelve week intervals.
+
+### Standardised backlog management on the Scala repo
+
+One big hurdle in the Scala 3 journey was the backlog of issues on the Scala repo. Users and contributors were reporting bugs, but there were more open issues than the team could manage. Now, a clear and efficient process is in place to triage, validate, and label issues within a week of their submission.
+
+### Easier access to Scala maintainers
+
+You can now find a list of Scala maintainers and their roles on the updated Governance page, under [“Teams Behind Scala”](/governance/#gov-scala). We invite Scala users and contributors to tag maintainers on Scala related issues, according to their expertise and role, to further help responsiveness. Also, we encourage everyone to follow and engage with maintainers on official [GitHub discussions](https://github.com/scala/scala3/discussions), [Users](https://users.scala-lang.org/) and [Contributors](https://contributors.scala-lang.org/) forums, [Discord chat rooms](https://discord.com/invite/scala).
+
+### Conclusion
+
+Following the major Scala 3 release in May 2021, the Scala teams faced many challenges. To name a few: Would Scala 3 succeed? How would the ecosystem migrate, and how long would it take? Who would provide and coordinate the resources necessary to operate and advance this big project? At the time of the release, the pool of Scala 3 experts was quite small and existing governance was not adapted to absorb the big change. With significant engineering and time commitment, financial investment and expertise from companies backing Scala, incredible support from the community contributors, and various community driven Scala organisations, we have overcome these challenges and delivered a stable and reliable Scala project.
+
+## Acknowledgements
+
+We have the pleasure to recognise those organisations and individuals who have significantly contributed to bringing the Scala project to this stage.
+
+To each and every person who worked at the **Programming Methods Laboratory at Ecole Polytechnique Fédérale de Lausanne** (or: LAMP at EPFL) for their extraordinary contributions to the world of programming through Scala, and especially to:
+
+* **Martin Odersky**, Scala language designer, from creating the language to continuously inventing and pushing the boundaries of what’s possible, Martin’s vision and dedication have shaped not just Scala, but modern programming itself. His commitment to driving innovation has had an immeasurable impact on both the community and the future of software development.
+* **Fabien Salvi**, System Admin, for patiently and diligently taking care of both the Scala infrastructure and for his technical assistance to each person that has ever worked in Martin’s lab and Scala Center over the last twenty years.
+* **Nicolas Stucki**, Compiler Engineer, for his outstanding work on metaprogramming in Scala 3, his contributions in the Scala governance project, and mentoring on the Scala 3 compiler.
+* **Matt Bovel**, PhD student, for stepping in as the LAMP representative in the Core team for crucial six months, contributing to community building by consistently hosting Scala Issue Sprees over the last year and a half, and for providing valuable feedback throughout.
+* **Hamza Remmal**, Compiler Engineer and Infrastructure Manager, for his critical role in centralising documentation, maintaining the infrastructures, and implementing new security policies.
+
+**Lightbend** for their diligent efforts in overseeing and maintaining Scala 2 for more than a decade. Their stewardship has been a crucial reason Scala is a trusted brand. In addition to maintaining Scala 2 and the standard library, the team is a core participant in Scala 3 governance and development. The team is led by **Lukas Rytz**. The other current, longtime members are **Jason Zaugg**, **Seth Tisue**, and **Dale Wijnand**. We thank them, past members, and the team’s founder, **Adriaan Moors**.
+
+To all the **Scala Center** team members since its founding in 2016 for their work on coordinating projects with the stakeholders and community, keeping educational materials and documentation up to date, developing essential migration tools, and enhancing the compiler and tooling ecosystem. A special thanks goes to:
+
+* **Heather Miller**, first Executive Director, for her founding vision, putting Scala Center on the map and bringing the key stakeholders to collaboratively push the Scala project forward.
+* **Darja Jovanovic**, Executive Director, for her outstanding leadership and for creating a neutral and safe space while coordinating delicate processes across multiple organisations and stakeholder groups over several years, ultimately enabling the Scala teams in delivering a strong, updated governance model. She coordinated the Scala 3 release process, spearheaded the governance project, and played a crucial role in designing and implementing the key governance bodies.
+* **Sébastien Doeraene**, Principal Engineer, for his long history of taking part in the Scala Improvement Process and its transformations, and for consistently controlling backward output compatibility guarantees, the technological means that allows Scala Next to use libraries built with Scala LTS and earlier, and
+* **Guillaume Martres**, Compiler Engineer, for his decade of regular contributions (top 3 contributor) and mentoring on the Scala 3 compiler, for making the type system more robust both theoretically and practically, and for his work as SIP member over the years.
+* **Julien Richard-Foy**, former Technical Director, for co-authoring the new Scala Improvement Process and being the first chair and setting its protocols and standards. For his work on Scala MOOCs, both managing and creating new ones.
+* **Anatolii Kmetiuk**, Developer Relationship, co-managing the Scala 3 release, setting and optimising internal processes, and his contributions as a chair of the SIP committee.
+
+**VirtusLab** for their continued support of Scala 3 and the tooling ecosystem for the last 5 years. They have been fundamental pillars of the open source community with their work especially on the compiler, Metals language server and Scala CLI. Special thanks goes to:
+
+* **Krzysztof Romanowski** who is the author of the vision of VirtusLab being a company behind Scala 3, for starting and managing the engagement between EPFL and VirtusLab throughout the years.
+* **Paweł Marks**, former lead of the Scala team at VirtusLab, for his stellar work on leading Scala releases from 3.0.2 to 3.5.0 and authoring the Scala distribution lines. He was instrumental in formalising the specific governance bodies around the Scala release process, defining roles and responsibilities, as well as onboarding the Product Manager.
+* **Piotr Chabelski**, Senior Scala Engineer, for taking on the big role of the Scala Product Manager as of Scala 3.4.2 release, earlier this year. We thank him for his exceptional effort on preparing detailed release plans, coordinating between teams, being the first responder on issue reports, and keeping a hand on the pulse of users' feedback.
+* **Wojciech Mazur**, Senior Scala Engineer, for developing and managing the Scala Open Community Build, leading Scala Native development and taking on the Release Officer role for Scala Next. Without his constant work, maintaining compatibility guarantees and releasing LTS would be impossible.
+
+Additionally, a big thanks to **Adam Goodman**, Director of the Center for Leadership, Northwestern University, who was instrumental in guiding the governance project setup and mentorship of the project leaders.
+
+To all the individuals who have contributed to Scala, engaged in language design discussions, fostered a welcoming Scala community, and championed Scala’s adoption in the industry—thank you for your trust and efforts, we’re excited to continue building Scala’s future together\!
diff --git a/_sass/layout/moderation.scss b/_sass/layout/moderation.scss
new file mode 100755
index 000000000..9c02664ba
--- /dev/null
+++ b/_sass/layout/moderation.scss
@@ -0,0 +1,33 @@
+.moderation {
+ @include clearfix;
+ padding-bottom: $padding-small;
+ .heading-box {
+ margin-bottom: $padding-medium;
+ text-align: center;
+ h3 {
+ color: $gray-dark;
+ font-size: 1.25rem;
+ font-weight: $font-regular;
+ padding-bottom: 8px;
+ }
+ }
+
+ .description {
+ margin-bottom: $padding-medium;
+ text-align: center;
+ }
+
+ .links-list {
+ @include clearfix;
+
+ .links-item {
+ text-align: center;
+ // @include span-columns(4);
+ // @include omega(3n);
+ @include bp(large) {
+ @include span-columns(12);
+ }
+ }
+ }
+
+}
diff --git a/blog/index.md b/blog/index.md
index 01fc17eb3..f17f293f1 100644
--- a/blog/index.md
+++ b/blog/index.md
@@ -11,3 +11,4 @@ paginate:
reversed: false
per_page: 10
---
+
diff --git a/community/index.md b/community/index.md
index c281ead96..bbf55906b 100644
--- a/community/index.md
+++ b/community/index.md
@@ -5,148 +5,181 @@ permalink: /community/
includeTOC: true
---
-Popular ways to connect with the Scala community include forums, chat rooms, local user groups, and conferences.
+Popular ways to connect with the Scala community include forums, chat rooms,
+local user groups, and conferences.
-The community is also the source of many libraries, tools, and other resources around Scala.
+The community is also the source of many libraries, tools, and other resources
+around Scala.
-## Who's behind Scala?
-
-Scala was created by
-[Prof. Martin Odersky](https://lampwww.epfl.ch/~odersky/) at [EPFL](https://epfl.ch).
+## Ambassadors
-The Scala language and associated websites are cooperative projects of
-the [Scala Center](https://scala.epfl.ch) at [EPFL](https://epfl.ch),
-the Scala 3 team in Martin's research group (also at EPFL),
-the Scala teams at [Lightbend](https://www.lightbend.com) and
-[VirtusLab](https://virtuslab.com), and the Scala community more
-broadly, with participation from many companies, organizations, and
-individuals.
+Ambassadors are key figures in the Scala community: speakers, organizers,
+teachers, content creators, open source maintainers, and so on. They are often
+present at community events, or open to answering questions.
-Scala 2 maintenance is primarily handled by the Lightbend team.
-They also participate in Scala 3 development.
+To learn more and discover who is an ambassador near you: see the dedicated
+[Scala Ambassadors](../ambassadors/) page.
-VirtusLab focuses on infrastructure and tooling for Scala 3.
+## Scala Tooling Summit
-The Scala Center focuses on education (especially online courses),
-documentation, open source community outreach, and tooling. Community
-participation in all of these efforts is strongly encouraged.
+Scala tooling summit is an event with a purpose of bringing together maintainers
+of build tools, linters, IDEs, and other tools. These summits are usually held
+alongside major Scala conferences. During the event they discuss ongoing
+problems within the tooling ecosystem and work towards solving them.
-## Ambassadors
+Previously held tooling summits:
-Ambassadors are key figures in the Scala community: speakers, organizers, teachers, content creators, open source maintainers, and so on. They are often present at community events, or open to answering questions.
+- Scala Tooling Summit of September 2023
+- [Scala Tooling Summit of March 2023](https://www.scala-lang.org/blog/2023/04/11/march-2023-scala-tooling-summit.html)
-To learn more and discover who is an ambassador near you: see the dedicated [Scala Ambassadors](../ambassadors/) page.
+The announcement of each new tooling summit will be public.
## Forums
The Scala Center operates the following Discourse forums:
- * **[users.scala-lang.org](https://users.scala-lang.org)**: The main forum for questions, discussions, and announcements about programming in Scala. Beginner questions are very welcome. Any question can and should receive a courteous and insightful answer. (Replaces the old scala-user and scala-announce groups.)
-
- * **[contributors.scala-lang.org](https://contributors.scala-lang.org)**: For anything related to moving Scala forward; from Scala Platform library discussions, to Scala Improvement Process discussions, to development work on the Scala compiler, standard library, and modules. Core maintainers and open-source contributors are both welcome, as well as those who want to see what’s coming down the pipe and would like to be involved. (Replaces the old scala-internals, scala-language, scala-debate, scala-sips, and scala-tools groups.)
-
- * **[teachers.scala-lang](https://teachers.scala-lang.org)**: Discussions related to the usage of Scala to teach programming: material, tooling, guidelines.
-
-Discourse is an open-source forum and mailing list platform. You can participate via the web, or you can use "mailing list mode", where you receive posts in your inbox and can reply to them via email. The web interface provides statistics, upvoting, polls, and other features. Posts can be written in Markdown, including syntax highlighting.
+- **[users.scala-lang.org](https://users.scala-lang.org)**: The main forum for
+ questions, discussions, and announcements about programming in Scala. Beginner
+ questions are very welcome. Any question can and should receive a courteous
+ and insightful answer. (Replaces the old scala-user and scala-announce
+ groups.)
+
+- **[contributors.scala-lang.org](https://contributors.scala-lang.org)**: For
+ anything related to moving Scala forward; from Scala Platform library
+ discussions, to Scala Improvement Process discussions, to development work on
+ the Scala compiler, standard library, and modules. Core maintainers and
+ open-source contributors are both welcome, as well as those who want to see
+ what’s coming down the pipe and would like to be involved. (Replaces the old
+ scala-internals, scala-language, scala-debate, scala-sips, and scala-tools
+ groups.)
+
+- **[teachers.scala-lang](https://teachers.scala-lang.org)**: Discussions
+ related to the usage of Scala to teach programming: material, tooling,
+ guidelines.
+
+Discourse is an open-source forum and mailing list platform. You can participate
+via the web, or you can use "mailing list mode", where you receive posts in your
+inbox and can reply to them via email. The web interface provides statistics,
+upvoting, polls, and other features. Posts can be written in Markdown, including
+syntax highlighting.
These forums are covered by the [Scala Code of Conduct](../conduct.html).
Lightbend operates a Discourse forum as well:
- * **[discuss.lightbend.com](https://discuss.lightbend.com)**: For discussion of reactive architectures, Akka, Play, and related tooling including sbt.
+- **[discuss.lightbend.com](https://discuss.lightbend.com)**: For discussion of
+ reactive architectures, Akka, Play, and related tooling including sbt.
## Scala Jobs
-Employers and job seekers can find each other in the #jobs channel of the [Scala Discord](https://discord.gg/scala).
+Employers and job seekers can find each other in the #jobs channel of the
+[Scala Discord](https://discord.gg/scala).
Job postings are not allowed in our other forums and chat rooms.
-The [Scala Reddit](https://www.reddit.com/r/scala/) has a monthly "who is hiring?" thread.
+The [Scala Reddit](https://www.reddit.com/r/scala/) has a monthly "who is
+hiring?" thread.
## Scala LinkedIn Group
-The [Scala Enthusiasts Group](https://www.linkedin.com/groups/746917/) is a place for Scala professionals to share information and come into contact with people and companies using Scala.
+The [Scala Enthusiasts Group](https://www.linkedin.com/groups/746917/) is a
+place for Scala professionals to share information and come into contact with
+people and companies using Scala.
## Chat Rooms
Our main chat platform is Discord, and the main Scala server is:
-* **[Scala](https://discord.com/invite/scala)**
- * the #scala-users channel is especially beginner-friendly
- * the #scala-contributors channel is about moving Scala forward
- * the #jobs channel is the only place we allow job postings
- * ask on #admin if you have questions or suggestions about the server itself
- * there are many other channels, including #spark, #scala-js, and #scala-native
+- **[Scala](https://discord.com/invite/scala)**
+ - the #scala-users channel is especially beginner-friendly
+ - the #scala-contributors channel is about moving Scala forward
+ - the #jobs channel is the only place we allow job postings
+ - ask on #admin if you have questions or suggestions about the server itself
+ - there are many other channels, including #spark, #scala-js, and
+ #scala-native
The server is covered by the [Scala Code of Conduct](../conduct.html).
-Alternate clients such as [Element](https://element.io) are supported
-via a [Matrix](https://matrix.org) bridge. Connect to
-`#scala-lang:matrix.org` to access the main Discord channel, or explore `#scala-space:matrix.org` to see channels from all over the Scala community (many are bridged in from other places like Discord, Gitter, or IRC).
+Alternate clients such as [Element](https://element.io) are supported via a
+[Matrix](https://matrix.org) bridge. Connect to `#scala-lang:matrix.org` to
+access the main Discord channel, or explore `#scala-space:matrix.org` to see
+channels from all over the Scala community (many are bridged in from other
+places like Discord, Gitter, or IRC).
Scala-oriented Discord servers operated by the community include:
-* **[IntelliJ](https://discord.gg/aUKpZzeHCK)**: the IntelliJ IDEA development environment
-* **[Scalameta](https://discord.gg/RFpSVth)**: Scalameta-based tooling: Metals, Scalameta, Scalafix, Scalafmt, and Mdoc
-* **[Play Framework](https://discord.gg/g5s2vtZ4Fa)**: the Play web framework for Scala and Java
-* **[Typelevel](https://discord.gg/XF3CXcMzqD)**: the Typelevel ecosystem for pure-functional programming in Scala
-* **[ZIO](https://discord.gg/2ccFBr4)**: the ZIO ecosystem for Type-safe, composable asynchronous and concurrent programming in Scala
-* **[Laminar](https://discord.gg/JTrUxhq7sj)**: the Laminar, Native Scala.js library for building user interfaces
-* **[Smithy4s](https://discord.gg/wvVga94s8r)**: the smithy4s for generating Scala code from Smithy files.
-* **[indigo](https://discord.gg/b5CD47g)**: the Indigo, Scala 2D game engine based on functional programming
-* **[Scala Space](https://discord.gg/vcHsmEQx)**: Discord server for VirtusLab's and Software Mill's open source projects
-* **[Business4s](https://bit.ly/business4s-discord)**: Scala community focused on product development and business
-* **[Creative Scala](https://discord.gg/rRhcFbJxVG)**: Making Scala fun through non-traditional means
-
+- **[IntelliJ](https://discord.gg/aUKpZzeHCK)**: the IntelliJ IDEA development
+ environment
+- **[Scalameta](https://discord.gg/RFpSVth)**: Scalameta-based tooling: Metals,
+ Scalameta, Scalafix, Scalafmt, and Mdoc
+- **[Play Framework](https://discord.gg/g5s2vtZ4Fa)**: the Play web framework
+ for Scala and Java
+- **[Typelevel](https://discord.gg/XF3CXcMzqD)**: the Typelevel ecosystem for
+ pure-functional programming in Scala
+- **[ZIO](https://discord.gg/2ccFBr4)**: the ZIO ecosystem for Type-safe,
+ composable asynchronous and concurrent programming in Scala
+- **[Laminar](https://discord.gg/JTrUxhq7sj)**: the Laminar, Native Scala.js
+ library for building user interfaces
+- **[Smithy4s](https://discord.gg/wvVga94s8r)**: the smithy4s for generating
+ Scala code from Smithy files.
+- **[indigo](https://discord.gg/b5CD47g)**: the Indigo, Scala 2D game engine
+ based on functional programming
+- **[Scala Space](https://discord.gg/vcHsmEQx)**: Discord server for VirtusLab's
+ and Software Mill's open source projects
+- **[Business4s](https://bit.ly/business4s-discord)**: Scala community focused
+ on product development and business
+- **[Creative Scala](https://discord.gg/rRhcFbJxVG)**: Making Scala fun through
+ non-traditional means
English-language Scala rooms on other chat platforms besides Discord include:
-* **[scala_en](https://t.me/scala_en)** (Telegram)
-* **[scala/scala](https://gitter.im/scala/scala)** (Gitter)
-* **[#scala](https://libera.chat)** (IRC)
+- **[scala_en](https://t.me/scala_en)** (Telegram)
+- **[scala/scala](https://gitter.im/scala/scala)** (Gitter)
+- **[#scala](https://libera.chat)** (IRC)
International chat rooms are available as well:
-* **[scala/cn](https://gitter.im/scala/cn)** (Gitter)
-* **[Scala Fr](https://discord.gg/w6VUKrrZK3)** (Discord)
-* **[scala/it](https://discord.gg/8wadTgcZVt)** (Discord)
-* **[Scala Jp](https://discord.gg/SaXM8s4Cyr)** (Discord)
-* **[Scala Poland](https://join.slack.com/t/scala-poland/shared_invite/zt-1jeq834yd-iOTH4U1Gto3YWu_lEVY5oA)** (Slack)
-* **[scala_ru](https://t.me/scala_ru)** (Telegram)
-* **[Scala Ukraine](https://t.me/scala_ukraine)** (Telegram)
+- **[scala/cn](https://gitter.im/scala/cn)** (Gitter)
+- **[Scala Fr](https://discord.gg/w6VUKrrZK3)** (Discord)
+- **[scala/it](https://discord.gg/8wadTgcZVt)** (Discord)
+- **[Scala Jp](https://discord.gg/SaXM8s4Cyr)** (Discord)
+- **[Scala Poland](https://join.slack.com/t/scala-poland/shared_invite/zt-1jeq834yd-iOTH4U1Gto3YWu_lEVY5oA)**
+ (Slack)
+- **[scala_ru](https://t.me/scala_ru)** (Telegram)
+- **[Scala Ukraine](https://t.me/scala_ukraine)** (Telegram)
-Note also that Stack Overflow offers languages other than English, for
-example [the scala tag on es.stackoverflow.com](https://es.stackoverflow.com/questions/tagged/scala).
+Note also that Stack Overflow offers languages other than English, for example
+[the scala tag on es.stackoverflow.com](https://es.stackoverflow.com/questions/tagged/scala).
## Reporting issues
-If you're having a problem with Scala, your first line of defense is
-our forums and chat rooms. The unexpected behavior you're seeing might
-not be a bug. Especially if you're new to the language, it's best to
-discuss the matter with more experienced users before filing a bug
-report.
+If you're having a problem with Scala, your first line of defense is our forums
+and chat rooms. The unexpected behavior you're seeing might not be a bug.
+Especially if you're new to the language, it's best to discuss the matter with
+more experienced users before filing a bug report.
-That said, bugs do occur and bug reports are valuable. You can report
-bugs here:
+That said, bugs do occur and bug reports are valuable. You can report bugs here:
Scala 2 compiler, standard library, and language spec:
-* [scala/bug](https://github.com/scala/bug/issues)
+- [scala/bug](https://github.com/scala/bug/issues)
Scala 3 compiler and standard library additions:
-* [scala/scala3](https://github.com/scala/scala3/issues)
+- [scala/scala3](https://github.com/scala/scala3/issues)
-Don't forget to search past issues first to see if the issue has
-already been reported.
+Don't forget to search past issues first to see if the issue has already been
+reported.
## Security
-To receive security announcements or contact us about security issues, see our [security policy](/security/).
+To receive security announcements or contact us about security issues, see our
+[security policy](/security/).
## User Groups
-Most local Scala user groups are listed on [Meetup](https://www.meetup.com/topics/scala/).
+Most local Scala user groups are listed on
+[Meetup](https://www.meetup.com/topics/scala/).
## Conferences
@@ -154,101 +187,125 @@ See our [events page](/events/).
## ScalaBridge
-Volunteers organizing free introductory Scala programming workshops
-for underrepresented groups, to improve diversity in the Scala community.
+Volunteers organizing free introductory Scala programming workshops for
+underrepresented groups, to improve diversity in the Scala community.
-* [ScalaBridge site](https://scalabridge.org)
-* [How to organize](https://scalabridge.org/organizers): advice and help
- on how to bring ScalaBridge to your city
+- [ScalaBridge site](https://scalabridge.org)
+- [How to organize](https://scalabridge.org/organizers): advice and help on how
+ to bring ScalaBridge to your city
## Stack Overflow
-Scala is an active [topic on Stack Overflow](https://stackoverflow.com/questions/tagged/scala), a very popular programmer Q&A site.
+Scala is an active
+[topic on Stack Overflow](https://stackoverflow.com/questions/tagged/scala), a
+very popular programmer Q&A site.
## Reddit
-There is a large and active Scala community on the [/r/Scala](https://reddit.com/r/scala) subreddit.
+There is a large and active Scala community on the
+[/r/Scala](https://reddit.com/r/scala) subreddit.
## Sources of Scala News
Official:
-* [Blog/News Page](https://www.scala-lang.org/blog/) on this site
-* [@scala_lang](https://fosstodon.org/@scala_lang) on Mastodon
-* [@scala_lang](https://twitter.com/scala_lang) on Twitter
+- [Blog/News Page](https://www.scala-lang.org/blog/) on this site
+- [@scala_lang](https://fosstodon.org/@scala_lang) on Mastodon
+- [@scala_lang](https://twitter.com/scala_lang) on Twitter
Community:
-* [Scala Times](https://scalatimes.com) weekly Scala newspaper
-* [This Week in Scala](https://petr-zapletal.medium.com) weekly Scala newspaper
-* [Scala News](https://www.scalanews.net) source for Scala news and blog feeds
- * [blog directory](https://www.scalanews.net/Resources/Blog_Directory.html)
-* [Tooling Talks](https://www.tooling-talks.com) A series of talks about Scala and tooling.
-* [The Scala Logs](https://twitter.com/thescalalogs) Podcast with interviews with developers, open source contributors, subject matter experts, and the like
+- [Scala Times](https://scalatimes.com) weekly Scala newspaper
+- [This Week in Scala](https://petr-zapletal.medium.com) weekly Scala newspaper
+- [Scala News](https://www.scalanews.net) source for Scala news and blog feeds
+ - [blog directory](https://www.scalanews.net/Resources/Blog_Directory.html)
+- [Tooling Talks](https://www.tooling-talks.com) A series of talks about Scala
+ and tooling.
+- [The Scala Logs](https://twitter.com/thescalalogs) Podcast with interviews
+ with developers, open source contributors, subject matter experts, and the
+ like
-Many Scala users are active on Twitter for sharing Scala-related news
-items and opinions. Ask your Scala friends who they follow on Twitter
-(besides [@scala_lang](https://twitter.com/scala_lang)!).
+Many Scala users are active on Twitter for sharing Scala-related news items and
+opinions. Ask your Scala friends who they follow on Twitter (besides
+[@scala_lang](https://twitter.com/scala_lang)!).
## Community-Powered Learning Resources
-* [Scala Exercises](http://scala-exercises.org/)
-* [Scala School](https://twitter.github.io/scala_school/)
-* [Scala Puzzlers](https://scalapuzzlers.com/)
-* [Scala Cookbook](http://www.scalacookbook.com/)
-* [Interactive Tour](https://scalatutorials.com/tour)
-* [Functional programming course/exercises](https://github.com/dehun/learn-fp)
-* [Best Scala Tutorials On YouTube](https://www.nbshare.io/blog/best-scala-tutorials-on-youtube/)
+- [Scala Exercises](http://scala-exercises.org/)
+- [Scala School](https://twitter.github.io/scala_school/)
+- [Scala Puzzlers](https://scalapuzzlers.com/)
+- [Scala Cookbook](http://www.scalacookbook.com/)
+- [Interactive Tour](https://scalatutorials.com/tour)
+- [Functional programming course/exercises](https://github.com/dehun/learn-fp)
+- [Best Scala Tutorials On YouTube](https://www.nbshare.io/blog/best-scala-tutorials-on-youtube/)
## Community Libraries and Tools
Finding libraries:
-* [Scaladex](https://index.scala-lang.org), maintained by the Scala Center, is "an index of the known Scala ecosystem"
-* [Awesome Scala](https://index.scala-lang.org/awesome) is "a community driven list of useful Scala libraries, frameworks and software"
-* [Typelevel.org](https://typelevel.org) provides an assortment of popular libraries and extensions to Scala.
-* [Trending Scala repositories](https://github.com/trending?l=scala&since=monthly) on GitHub
+- [Scaladex](https://index.scala-lang.org), maintained by the Scala Center, is
+ "an index of the known Scala ecosystem"
+- [Awesome Scala](https://index.scala-lang.org/awesome) is "a community driven
+ list of useful Scala libraries, frameworks and software"
+- [Typelevel.org](https://typelevel.org) provides an assortment of popular
+ libraries and extensions to Scala.
+- [Trending Scala repositories](https://github.com/trending?l=scala&since=monthly)
+ on GitHub
Staying current:
-* [Scala Times](https://scalatimes.com) includes library releases
-* [#ThisWeekInScala](https://medium.com/disney-streaming/tagged/thisweekinscala) includes library releases
+- [Scala Times](https://scalatimes.com) includes library releases
+- [#ThisWeekInScala](https://medium.com/disney-streaming/tagged/thisweekinscala)
+ includes library releases
## Non-JVM platforms
-* [Scala.js](https://www.scala-js.org) compiles Scala code to JavaScript
-* [Scala Native](https://www.scala-native.org) compiles Scala code to LLVM for native execution
-* [Scala on Android](https://scala-android.org) community site
+- [Scala.js](https://www.scala-js.org) compiles Scala code to JavaScript
+- [Scala Native](https://www.scala-native.org) compiles Scala code to LLVM for
+ native execution
+- [Scala on Android](https://scala-android.org) community site
## The Scala Center
-* [The Scala Center](https://scala.epfl.ch/) is an open source foundation that brings together a coalition of individuals and organizations working together to contribute to Scala.
- * [Scala Center FAQ](https://scala.epfl.ch/faqs.html)
+- [The Scala Center](https://scala.epfl.ch/) is an open source foundation that
+ brings together a coalition of individuals and organizations working together
+ to contribute to Scala.
+ - [Scala Center FAQ](https://scala.epfl.ch/faqs.html)
## Scala open source
-Want to start making open-source contributions to projects in the
-Scala ecosystem?
+Want to start making open-source contributions to projects in the Scala
+ecosystem?
-Scaladex lists [projects welcoming contributions](https://index.scala-lang.org/search?q=&contributingSearch=true).
+Scaladex lists
+[projects welcoming contributions](https://index.scala-lang.org/search?q=&contributingSearch=true).
-Also, on GitHub, a common convention is to use the label "good first issue"
-on issues that are especially easy on-ramps to getting started in
-a particular repo:
+Also, on GitHub, a common convention is to use the label "good first issue" on
+issues that are especially easy on-ramps to getting started in a particular
+repo:
-* "good first issue" tickets: [GitHub link](https://github.com/search?q=type%3Aissue+label%3A%22good+first+issue%22+language%3AScala+state%3Aopen&type=Issues)
+- "good first issue" tickets:
+ [GitHub link](https://github.com/search?q=type%3Aissue+label%3A%22good+first+issue%22+language%3AScala+state%3Aopen&type=Issues)
-And, some repos also use a "help wanted" label if the maintainers
-especially desire contributor attention:
+And, some repos also use a "help wanted" label if the maintainers especially
+desire contributor attention:
-* "help wanted" tickets: [GitHub link](https://github.com/search?q=type%3Aissue+label%3A%22help+wanted%22+language%3AScala+state%3Aopen&type=Issues)
+- "help wanted" tickets:
+ [GitHub link](https://github.com/search?q=type%3Aissue+label%3A%22help+wanted%22+language%3AScala+state%3Aopen&type=Issues)
## Phil Bagwell Memorial Scala Community Award
-The [Phil Bagwell Memorial Scala Community Award](./phil-bagwell-award.html) is given to individuals who have made significant efforts to grow the Scala Community.
+The [Phil Bagwell Memorial Scala Community Award](./phil-bagwell-award.html) is
+given to individuals who have made significant efforts to grow the Scala
+Community.
## Archives
Read-only archives of these retired groups remain available.
- * [scala-user](https://groups.google.com/g/scala-user), [scala-announce](https://groups.google.com/g/scala-announce), [scala-language](https://groups.google.com/g/scala-language), [scala-debate](https://groups.google.com/g/scala-debate), [scala-internals](https://groups.google.com/g/scala-internals), [scala-sips](https://groups.google.com/g/scala-sips)
+- [scala-user](https://groups.google.com/g/scala-user),
+ [scala-announce](https://groups.google.com/g/scala-announce),
+ [scala-language](https://groups.google.com/g/scala-language),
+ [scala-debate](https://groups.google.com/g/scala-debate),
+ [scala-internals](https://groups.google.com/g/scala-internals),
+ [scala-sips](https://groups.google.com/g/scala-sips)
diff --git a/development/index.md b/development/index.md
new file mode 100644
index 000000000..213f3fbba
--- /dev/null
+++ b/development/index.md
@@ -0,0 +1,254 @@
+---
+layout: inner-page-no-masthead
+title: Scala development guarantees
+permalink: /development/
+includeTOC: true
+---
+
+## The TL;DR
+
+1. There are 2 distribution lines of Scala 3: **Scala Next** and **Scala LTS**.
+2. The **Scala Next** line is the **default** to be used by most users,
+ containing the latest features, bug fixes and improvements.
+3. The **Scala LTS** line is advised to be used for publishing **libraries**.
+ (Some especially conservative users might also choose it over Scala Next.)
+4. Bug fixes and usability improvements from the Scala Next line are regularly
+ backported to the currently supported LTS lines.
+5. Scala minor releases (3.x) are backwards compatible, meaning libraries built
+ with older versions can be consumed by newer versions. Patch releases (3.5.x)
+ are backwards and forwards compatible.
+6. Thus, existing source code continues to compile when upgrading to a new
+ version, except for rare situations when a bugfix requires breaking source
+ compatibility.
+
+## Contribute to Scala
+
+Scala is and always has been an open source effort. It is a collaboration
+between multiple entities (business, nonprofits, individuals) and relies on
+community contributions as much as the work of its maintainers.
+
+If you are interested in contributing to Scala, be sure to start by visiting
+[the GitHub repository of the compiler](https://github.com/scala/scala3) (or the
+[standard library](https://github.com/scala/scala/tree/2.13.x/src/library)).
+
+If you’d like for your organization to work with us more closely, please contact
+scala.center (at) epfl.ch which will be able to arrange the possible
+collaboration.
+
+## Semantic versioning of the language
+
+Scala 3 follows [Semantic Versioning](https://semver.org/). Each version number
+has a well-defined meaning, following the `major.minor.patch` scheme, with each
+component representing a subset of our compatibility guarantees.
+
+### Patch versions
+
+`Patch` versions increase the patch component of the version scheme. Examples
+are 3.3.3 \-\> 3.3.4 or 3.5.0 \-\> 3.5.1.
+
+These are generally focused on bug fixes. They may also include usability
+improvements (such as better error messages), performance enhancements or
+internal changes (refactorings, optimizations). Patch releases can also add
+experimental features intended for trial and evaluation by interested users;
+such features are never enabled by default, only via explicit opt-in.
+
+**Patch versions are guaranteed to be both forward and backward compatible.**
+This means a library compiled with, for example, Scala 3.3.3 can be consumed by
+a project built with any other past for future Scala 3.3.x version, and vice
+versa.
+
+### Minor versions
+
+Minor versions increase the `minor` component of the version scheme. Examples
+are 3.3.4 \-\> 3.4.0 or 3.4.3 \-\> 3.5.0.
+
+They are generally focused on features, with the limitation that any new feature
+has to be backward compatible. Those features could be bigger usability
+improvements (like adding linting in 3.3.0), loosening implementation
+restrictions (like allowing exports in extension clauses in 3.2.0), adding new
+tools (like adding Scala CLI as the new `scala` runner in 3.5.0) and others. We
+take utmost care to not change the existing semantics of any working code
+whenever it is avoidable. Some changes might be possible, but if detected they
+will be announced properly beforehand.
+
+Language changes requiring the SIP Committee approval usually have to be
+delivered in a minor version.
+
+**Minor versions are guaranteed to be backwards TASTy and binary compatible.**
+This means that code compiled with Scala 3.2.x can still be used in Scala 3.3.x,
+3.4.x, 3.5.x or any other future version, indefinitely. However, the opposite is
+not true. Code compiled with Scala 3.5.x cannot be used in a Scala 3.4.x
+project. Allowing this would not be considered safe. For instance, the Scala 3.5
+code might want to access a library method which did not exist in 3.4.
+
+### Major versions
+
+**Only major versions could, theoretically, introduce both backwards and
+forwards incompatible changes.** However, **we do not plan to increase a new
+major version of Scala in the currently foreseeable future**. There is currently
+no Scala 4 on the horizon. The major version of the language remains final and
+immutable until announced otherwise.
+
+### Output compatibility
+
+The guarantees described above are called output compatibility. They encompass
+binary compatibility (compatibility on the level of generated bytecode) and
+TASTy compatibility (the possibility for the newer versions to read well-defined
+and structured metadata describing the original source code necessary for
+correct linking).
+
+Thanks to the output compatibility guarantees, a published library can be used
+with any future version of Scala, without the need for cross-publishing or any
+other intervention from the maintainers.
+
+This is especially useful when a critical security problem is found in an older
+version of the library that was compiled with an older version of the language.
+If the maintainers follow the standard practice of only bumping the minor
+compiler version in minor library releases, they can fix the bug without needing
+to bump the compiler version and then release the fix in a patch release. All
+projects that depend on a problematic version of the library can switch to the
+newly-released patch, no matter what version of the language they are using.
+
+### Source compatibility
+
+Source compatibility means that a developer can change the version of the
+compiler they are using without making any changes in the source code and still
+receive a program that will function in the same way. As with output
+compatibility, we (slightly counterintuitively) can say that two versions of the
+compiler are backward source compatible if the code created for an older version
+works with a newer version. The reverse, when the developer is downgrading the
+compiler, is called forward compatibility.
+
+In the compiler team, we are paying attention to source compatibility and
+ensuring that code compiling today should compile with future versions of the
+compiler. We cannot always guarantee that. Like any other compiler and any other
+piece of software, the Scala compiler can have bugs. In very rare cases, the
+fact that some code is considered correct may be the result of a bug in the
+compiler. Fixing this bug may result in code that was previously compiling to
+stop doing so in a newer version. Moreover, sometimes improving type inference
+for some code snippets may degrade it for another snippet, causing problems like
+failures related to implicit search.
+
+There is a multi-layer safety net to catch source incompatibilities early so
+they do not make it into the stable versions of the compiler.
+
+The first layer is obviously an extensive
+[set of compiler tests](https://github.com/scala/scala3/tree/main/tests) run on
+each PR.
+
+The second layer is an integration test that builds over 70 popular Scala
+libraries. Failures of compilation or tests in any of those libraries also block
+merging of the PR.
+
+The last layer is the **Open Community Build**, introduced around the release of
+Scala 3.2. It runs weekly, building the entire Scala 3 open-source ecosystem.
+Every failure here is investigated and treated as a high-priority bug. For more
+information on how to add your project to the community build consult
+[the README](https://github.com/VirtusLab/community-build3)
+
+We also run the Open Community Build for every RC version, as well as some Pull
+Requests deemed to require closer scrutiny. We analyze all regressions detected
+by the Open Community Build to ascertain their impact on the ecosystem. If
+necessary, we may prolong the RC period and delay a release to give ourselves
+time to fix a particularly troublesome regression.
+
+## Scala distributions
+
+Scala 3 is currently developed in 2 parallel **distributions** (or **lines**),
+code-named **Scala LTS** (for **Long Term Support**) and **Scala Next**.
+
+More information about why we decided on this specific release cadence can be
+found in an
+[earlier blogpost](/blog/2022/08/17/long-term-compatibility-plans.html), but the
+relevant information can be found below.
+
+### Scala LTS
+
+**Scala LTS** is a designated **minor** version that is the **preferred target
+version for libraries**. Currently, it is the Scala 3.3.x series.
+
+It is possible to use a library if it was published with the same minor version
+(x in 3.x.y) or lower than the one you use. There are 2 main reasons for
+preferring LTS for building libraries: extended support and source compatibility
+guarantees. Any other minor Scala version receives patches with bug fixes and
+small usability improvements only until the release of the next minor version.
+For example, Scala 3.1 will forever remain on the 3.1.3 patch, and all later
+fixes were available only in Scala 3.2.0 and later versions. The LTS line
+receives patches with bug fixes and usability improvements ported from the newer
+versions. **Those patches are guaranteed until at least a year after the release
+of the next LTS line**. Moreover, **we ensure that there will be no new LTS line
+for at least two years after the first release of the current LTS line**. This
+means guaranteed patch releases for a period longer than three years after the
+initial release.
+
+### Scala Next
+
+**Scala Next** is the default line that the compiler team actively develops. It
+is the **preferred target version for all non-library projects**. If the API of
+your project is not meant to be consumed by other Scala projects, we advise to
+use Scala Next rather than LTS.
+
+Do not be confused; **there is nothing experimental or unstable about Scala
+Next**. The difference to LTS is that Scala Next is the target for language
+changes (after approval by the SIP Committee), larger new features and
+occasional bugfixes that may affect source compatibility. All of our testing and
+maintenance practices apply in the same way to Scala Next and LTS.
+
+## Schedule, iterations and roadmap
+
+Scala 3 is developed in iterations, according to a roadmap as designed by its
+Product Manager and governed by the [Scala Core Team](/scala-core). Each
+iteration is tied to a given Scala Next release.
+
+The Scala Compiler Team aims for a set schedule. However, we work on a
+best-effort basis, delays and extensions may happen. The Scala Core Team
+reserves the right to readjust the schedule as deemed necessary, with the
+language users’ best interest in mind.
+
+### Scala Next iterations
+
+The length of an iteration is normally between 6 and 12 weeks. We default to 6
+weeks for cycles devoted to a patch version and 8 weeks for a minor version. The
+length of a given iteration and its type (minor or patch) is decided by the
+Scala Core Team at the end of the previous one. It takes into account the
+current team capacity, recent developments and the contents of the roadmap.
+Under normal circumstances, there should be at least 2 patch versions between
+consecutive minor versions in the Scala Next line. For example, after the
+release of Scala 3.5.0, we are unlikely to work on Scala 3.6.0 before 3.5.1 and
+3.5.2 are out. The aim is to hold to a schedule which allows for delivering
+stable and timely releases, with a fresh batch of enhancements and fixes for the
+Scala Next and LTS lines, while holding technical debt at a healthy minimum.
+
+### Scala Next releases
+
+At the end of each Scala Next iteration, an RC (Release Candidate) version is
+published for the community to test and the next development iteration starts.
+If no regressions are detected in a given RC for **at least a week**, it is
+deemed suitable to be re-released as the new stable version.
+
+Otherwise, a new RC is released until either no more regressions are known, or
+the iteration for the next version ends. At this point, the most stable RC is
+released and remaining problems are listed in the release notes. Of course we
+will not release a final version if it has critical known issues.
+
+As a result, we expect to release **a new Scala Next stable version every 6 to
+12 weeks**.
+
+### Scala LTS iterations
+
+There are no dedicated iterations for working on Scala LTS. Scala LTS is tied to
+Scala Next iterations instead. Any relevant bug fixes introduced in Scala Next
+are successively backported to the LTS. Each PR merged that is included in the
+current Next version will be analyzed for compatibility and merged if possible
+to the current LTS branch.
+
+### Scala LTS releases
+
+We expect to publish a release candidate of a new Scala LTS patch version around
+the time Scala Next `3.
.2` is out. Then (with possible
+intermediary release candidates) that should turn into a stable LTS release
+around the time Scala Next `3..0` is out. For example, we would
+release Scala LTS 3.3.6-RC1 together with Scala Next 3.6.2, and then we should
+have a stable Scala LTS 3.3.6 by the time Scala Next 3.7.0 is out.
+
+As a result, we expect to release **a new Scala LTS patch every 3 to 6 months**.
diff --git a/governance/index.md b/governance/index.md
new file mode 100644
index 000000000..1e8b9cba4
--- /dev/null
+++ b/governance/index.md
@@ -0,0 +1,35 @@
+---
+layout: inner-page-governance
+title: Governance
+permalink: /governance/
+includeTOC: true
+---
+
+## Who's behind Scala?
+
+Scala was created by [Prof. Martin Odersky](https://lampwww.epfl.ch/~odersky/)
+at [EPFL](https://epfl.ch).
+
+The Scala language and associated websites are cooperative projects of the
+[Scala Center](https://scala.epfl.ch) at [EPFL](https://epfl.ch), the Scala 3
+team in Martin's research group, [LAMP](https://lamp.epfl.ch) (also at EPFL),
+the Scala teams at [Lightbend](https://www.lightbend.com) and
+[VirtusLab](https://virtuslab.com), and the Scala community more broadly, with
+participation from many companies, organizations, and individuals.
+
+Scala 2 maintenance is primarily handled by the Lightbend team. They also
+participate in Scala 3 development.
+
+VirtusLab focuses on infrastructure and tooling for Scala 3.
+
+The Scala Center focuses on coordinating governance, education (especially
+online courses), documentation, open source community outreach, and tooling.
+Community participation in all of these efforts is strongly encouraged.
+
+The main decision body is the [Scala Core team](/scala-core/) which meets weekly
+to discuss issues within the language and its' ecosystem.
+
+Scala 3 development is done by the compiler team currently listed at
+[Scala Compiler Team](/maintainers/) page and Scala 2 maintainers list is
+located in [the github README](https://github.com/scala/scala#get-in-touch) of
+the scala/scala repository.
diff --git a/governance/phil-bagwell-award.md b/governance/phil-bagwell-award.md
new file mode 100644
index 000000000..22e349994
--- /dev/null
+++ b/governance/phil-bagwell-award.md
@@ -0,0 +1,48 @@
+---
+title: Phil Bagwell Memorial Scala Community Award
+layout: inner-page-no-masthead
+---
+
+The Phil Bagwell Memorial Scala Community Award is given to individuals who have made significant efforts to grow the Scala Community.
+It recognizes someone who is well respected in the community and composes themselves as one of respect.
+Specifically this person should be: Encouraging, Welcoming, Humble, Optimistic and Kind.
+
+Additionally, the candidate should have significant contributions in one or more of the following areas:
+
+* **Technical Benefaction**
+
+ A candidate should show a clear and measurable technical influence on or within the Scala Community.
+ This influence can take the form of open source contributions, documentation, or bug reports.
+ The candidate should show that not only are they a recognized expert in Scala, but they are willing to share their own work with others.
+
+* **Evangelism**
+
+ A candidate should show a willingness to promote Scala around them.
+ This promotion should be thoughtful, considerate and inclusive.
+ Evangelism can take the form of blog posts, book authoring, forum answers (stack overflow or others) or public speaking.
+ The candidate should show that they are willing to share their knowledge of Scala with others, to the betterment of all.
+
+* **Activism**
+
+ A candidate should show a propensity for building the community around them.
+ This can be done via organizing local meetup groups, organizing conferences, promoting a sense of community and camaraderie in online communities or helping run events.
+ The candidate should show that they are able to bring people together.
+
+Phil Bagwell is remembered for his contributions to building the Scala community.
+In [a 2012 blog post](https://www.lightbend.com/blog/rip-phil-bagwell), Prof. Martin Odersky remembers Phil and his special place in the Scala community.
+This award seeks to build that which he helped start.
+
+## Past winners
+
+* 2019: [Kelley Robinson](https://www.scala-lang.org/news/2019/09/13/bagwell-award-2019.html)
+* 2018: [Kenji Yoshida](https://www.scala-lang.org/news/2019/09/13/bagwell-award-2018.html)
+* 2017: [Josh Suereth](https://www.scala-lang.org/news/2017/09/25/bagwell-award-2017.html)
+* 2016: [Erik Osheim](https://www.scala-lang.org/news/2016/10/26/bagwell-award-2016.html)
+* 2015: [Bill Venners](https://scala-lang.org/news/2015/06/25/bagwell-award-2015.html)
+* 2014: [Lalit Pant](https://kojoenv.wordpress.com/2014/09/27/phil-bagwell-award/)
+* 2013: [Dick Wall](https://twitter.com/dickwall)
+
+## Selection process
+
+Each year, a committee decides who to award, possibly based on nominations from the community.
+The committee consists of Martin Odersky along with all past winners (who still have time to take part).
diff --git a/maintainers/index.html b/maintainers/index.html
new file mode 100644
index 000000000..7d00c642c
--- /dev/null
+++ b/maintainers/index.html
@@ -0,0 +1,75 @@
+---
+layout: inner-page-no-masthead
+title: Scala 3 Compiler Team
+permalink: /maintainers/
+includeTOC: false
+---
+
+
+
+
+
Scala Teams
+
+
+
Scala consists of multiple teams including the core compiler team and Scala Native team.
+
+ {% for member in site.data.scala-compiler-team %}
+
+
+
{{member.name}}
+
{{member.org}}
+
+ {% if member.email %}
+
+
+
+ {% endif %}
+ {% if member.twitter %}
+
+
+
+ {% endif %}
+ {% if member.mastodon %}
+
+
+
+ {% endif %}
+ {% if member.github %}
+
+
+
+ {% endif %}
+ {% if member.linkedin %}
+
+
+
+ {% endif %}
+ {% if member.meetup %}
+
+
+
+ {% endif %}
+
+
{{member.description}}
+
+ {% endfor %}
+
+
+
Scala Core Team
+
+
+
Scala Core is the main team responsible for decisions deciding the direction of the Scala language.
+
+ {% for coreMember in site.data.scala-core %}
+
+
+
{{coreMember.name}}
+
{{coreMember.org}}
+
+ {{coreMember.city}}
+ {% if coreMember.discord %}
+
{{coreMember.discord}}
+ {% endif %}
+
+
+ {% if coreMember.email %}
+
+
+
+ {% endif %}
+ {% if coreMember.twitter %}
+
+
+
+ {% endif %}
+ {% if coreMember.mastodon %}
+
+
+
+ {% endif %}
+ {% if coreMember.github %}
+
+
+
+ {% endif %}
+ {% if coreMember.linkedin %}
+
+
+
+ {% endif %}
+ {% if coreMember.meetup %}
+
+
+
+ {% endif %}
+
+
{{coreMember.description}}
+
+ {% endfor %}
+
+