Update links to use scala/scala3 instead of lampepfl/dotty

README.md

@@ -4,7 +4,7 @@ This repository contains the source for the [scala-lang.org](https://scala-lang.
 
 It does not contain the source for the [docs.scala-lang.org](https://docs.scala-lang.org) subdomain. You can visit the [docs.scala-lang repository](https://github.com/scala/docs.scala-lang) if you are interested in contributing to the Scala documentation site.
 
-The repository for Scala 3 itself is https://github.com/lampepfl/dotty .
+The repository for Scala 3 itself is https://github.com/scala/scala3 .
 
 Scala 2 is at https://github.com/scala/scala. Scala 2 bug reports are at https://github.com/scala/bug.
 

_data/governance.yml

@@ -72,9 +72,9 @@ cards:
     anchorTarget: "gov-scala-3"
     links:
       - name: Core Maintainers
-        url: https://github.com/lampepfl/dotty/blob/main/MAINTENANCE.md#compiler
+        url: https://github.com/scala/scala3/blob/main/MAINTENANCE.md#compiler
       - name: Maintenance Procedures
-        url: https://github.com/lampepfl/dotty/blob/main/MAINTENANCE.md
+        url: https://github.com/scala/scala3/blob/main/MAINTENANCE.md
   - title: "Moderation"
     description: "Learn how the Scala community is moderated."
     expandText: "Process & People"

_includes/downloads-scala3.html

@@ -1,10 +1,10 @@
 <p>Are you looking for <a href="{{ site.baseurl }}/download/all.html">another release</a> of Scala?</p>
 <br/>
-<p>Scala binaries for <strong>{{page.release_version}}</strong> are available at <a href="https://github.com/lampepfl/dotty/releases/tag/{{page.release_version}}">github</a>.</p>
+<p>Scala binaries for <strong>{{page.release_version}}</strong> are available at <a href="https://github.com/scala/scala3/releases/tag/{{page.release_version}}">github</a>.</p>
 
 <h3>Release Notes</h3>
 For a summary of important changes, see the <a
-  href="https://github.com/lampepfl/dotty/releases/tag/{{page.release_version}}">GitHub release notes</a>.
+  href="https://github.com/scala/scala3/releases/tag/{{page.release_version}}">GitHub release notes</a>.
 <br /><small>(Or consult our archive of <a href="{{ site.baseurl }}/blog/announcements/">older release
     notes</a>.)</small>
 
@@ -20,7 +20,7 @@ <h2>Ways to Install This Release</h2>
       </li>
       <li>
         Download the Scala binaries for <strong>{{page.release_version}}</strong> at <a
-          href="https://github.com/lampepfl/dotty/releases/tag/{{page.release_version}}">github</a>.
+          href="https://github.com/scala/scala3/releases/tag/{{page.release_version}}">github</a>.
         <br /><span class="install"><a href="{{ site.baseurl }}/download/install.html">Need help running the
             binaries?</a></span>
       </li>

_layouts/downloadpage.html

@@ -34,9 +34,9 @@ <h1>{{page.title}}</h1>
         </div>
         <ul>
           {% if scala_edition == "3" %}
-            <li><a href="https://github.com/lampepfl/dotty/releases/tag/{{page.release_version}}">Release Notes</a></li>
+            <li><a href="https://github.com/scala/scala3/releases/tag/{{page.release_version}}">Release Notes</a></li>
             <li class="dot">•</li>
-            <li><a href="https://github.com/lampepfl/dotty/releases/tag/{{page.release_version}}">Changelog</a></li>
+            <li><a href="https://github.com/scala/scala3/releases/tag/{{page.release_version}}">Changelog</a></li>
           {% else %}
             <li><a href="https://github.com/scala/scala/releases">Release Notes</a></li>
             <li class="dot">•</li>

_posts/2015-10-23-dotty-compiler-bootstraps.md

@@ -7,7 +7,7 @@ title: We got liftoff! The Dotty compiler for Scala bootstraps.
 
 ## We got liftoff!
 
-The [Dotty project](https://github.com/lampepfl/dotty)
+The [Dotty project](https://github.com/scala/scala3)
 is a platform to develop new technology for Scala
 tooling and to try out concepts of future Scala language versions.
 Its compiler is a new design intended to reflect the
@@ -67,4 +67,4 @@ Samuel Gruetter ([@samuelgruetter](https://github.com/samuelgruetter)),
 Vera Salvis ([@vsalvis](https://github.com/vsalvis)),
 and Jason Zaugg ([@retronym](https://github.com/retronym)).
 
-To get started: <https://github.com/lampepfl/dotty>.
+To get started: <https://github.com/scala/scala3>.

_posts/2015-11-16-minutes-from-nov-2015.md

@@ -155,7 +155,7 @@ Notes:
 
 ### SIP: Auto-uncurry n-ary functions
 
-There is no SIP tracking issue as yet, but information can be found here: [https://github.com/lampepfl/dotty/issues/897](https://github.com/lampepfl/dotty/issues/897)
+There is no SIP tracking issue as yet, but information can be found here: [https://github.com/scala/scala3/issues/897](https://github.com/scala/scala3/issues/897)
 
 No issue created as yet, but [@odersky](https://github.com/odersky) will create one if needed
 

_posts/2016-01-11-minutes-from-jan-2016.md

@@ -26,11 +26,11 @@ Notes:
 - The SIP is a design proposal about the syntax and what the semantics of these features might be, but at this point has no code.
 - This idea has come up a few times over the years and is based on those previous discussions.
 
-This proposal and [dotty](https://github.com/lampepfl/dotty):
+This proposal and [dotty](https://github.com/scala/scala3):
 
 [@odersky](https://github.com/odersky):
 
-- have considering something like this in [dotty](https://github.com/lampepfl/dotty). Doing this involves considering quite a few rules (and their corner cases), which this SIP doesn't cover.
+- have considering something like this in [dotty](https://github.com/scala/scala3). Doing this involves considering quite a few rules (and their corner cases), which this SIP doesn't cover.
 - generally sympathetic, but not sure this has the format for a SIP.
 
 [@odersky](https://github.com/odersky) thinks there should be a wider discussion about this, involving:
@@ -41,7 +41,7 @@ This proposal and [dotty](https://github.com/lampepfl/dotty):
 
 Conclusion:
 
-[@odersky](https://github.com/odersky) thinks this is promising, but needs to be fleshed out for a SIP. He also notes that [dotty](https://github.com/lampepfl/dotty) wants to do this, so we might want to wait and synchronize rather than have [@ahmadsalim](https://github.com/ahmadsalim) spend a lot of time working on this, only to find a different approach has been made in dotty.
+[@odersky](https://github.com/odersky) thinks this is promising, but needs to be fleshed out for a SIP. He also notes that [dotty](https://github.com/scala/scala3) wants to do this, so we might want to wait and synchronize rather than have [@ahmadsalim](https://github.com/ahmadsalim) spend a lot of time working on this, only to find a different approach has been made in dotty.
 
 [@non](https://github.com/non), it's good to be clear that there are two things people want here:
 
@@ -55,4 +55,4 @@ Conclusion:
 
 Actions:
 
-Ask [@ahmadsalim](https://github.com/ahmadsalim) to talk to the [dotty](https://github.com/lampepfl/dotty) team about this.
+Ask [@ahmadsalim](https://github.com/ahmadsalim) to talk to the [dotty](https://github.com/scala/scala3) team about this.

_posts/2016-02-17-scaling-dot-soundness.md

@@ -69,9 +69,9 @@ categories:
     is not associated with a runtime value.
 
 We can in fact construct soundness issues in all of these cases. Look
-at the discussion for issues [#50](https://github.com/lampepfl/dotty/issues/50)
-and [#1050](https://github.com/lampepfl/dotty/issues/1050) in the
-[dotty](https://github.com/lampepfl/dotty/issues/1050) repository
+at the discussion for issues [#50](https://github.com/scala/scala3/issues/50)
+and [#1050](https://github.com/scala/scala3/issues/1050) in the
+[dotty](https://github.com/scala/scala3/issues/1050) repository
 on GitHub. All issues work fundamentally in the same way: Construct a type `S`
 which has a type member `T` with bad bounds, say
 
@@ -94,7 +94,7 @@ course. The promise is usually broken at run-time by failing with a
 ## Plugging the Loopholes
 
 To get back to soundness we need to plug the loopholes. Some of the
-necessary measures are taken in pull request [#1051](https://github.com/lampepfl/dotty/issues/1051).
+necessary measures are taken in pull request [#1051](https://github.com/scala/scala3/issues/1051).
 That pull request
 
  - tightens the rules for overrides of lazy values: lazy values

_posts/2016-05-06-multiversal-equality.md

@@ -8,7 +8,7 @@ discourse: true
 
 I have been working recently on making equality tests using `==` and
 `!=` safer in Scala. This has led to a [Language Enhancement
-Proposal](https://github.com/lampepfl/dotty/issues/1247) which I summarize in this blog.
+Proposal](https://github.com/scala/scala3/issues/1247) which I summarize in this blog.
 
 ## Why Change Equality?
 
@@ -118,7 +118,7 @@ backwards compatibility, we allow comparisons of such types as well,
 by means of a fall-back `eqAny` instance. But we do not allow comparisons
 between types that have an `Eq` instance and types that have none.
 Details are explained in the
-[proposal](https://github.com/lampepfl/dotty/issues/1247).
+[proposal](https://github.com/scala/scala3/issues/1247).
 
 ## Properties
 

_posts/2016-10-14-dotty-errors.md

@@ -97,7 +97,7 @@ information for the error or warning.
 
 So - this is what you do:
 
-1. Go to the [Error messages issue](https://github.com/lampepfl/dotty/issues/1589)
+1. Go to the [Error messages issue](https://github.com/scala/scala3/issues/1589)
 2. Read the howto on error messages
 3. Choose an error message you want to help with and post a comment saying
    which one(s)

_posts/2016-12-07-implicit-function-types.md

@@ -5,7 +5,7 @@ by: Martin Odersky
 isHighlight: true
 ---
 
-I just made the [first pull request](https://github.com/lampepfl/dotty/pull/1775) to add _implicit function types_ to
+I just made the [first pull request](https://github.com/scala/scala3/pull/1775) to add _implicit function types_ to
 Scala. I am pretty excited about it, because - citing the explanation
 of the pull request - "_This is the first step to bring contextual
 abstraction to Scala_". What do I mean by this?
@@ -180,7 +180,7 @@ type of `f1` is:
 
 Just like the normal function type syntax `A => B`, desugars to `scala.Function1[A, B]`
 the implicit function type syntax `implicit A => B` desugars to `scala.ImplicitFunction1[A, B]`.
-The same holds at other function arities. With dotty's [pull request #1758](https://github.com/lampepfl/dotty/pull/1758)
+The same holds at other function arities. With dotty's [pull request #1758](https://github.com/scala/scala3/pull/1758)
 merged there is no longer an upper limit of 22 for such functions.
 
 The type `ImplicitFunction1` can be thought of being defined as follows:

_posts/2017-02-28-collections-rework.md

@@ -4,7 +4,7 @@ by: Stefan Zeiger
 title: Scala 2.13 Collections Rework
 ---
 
-In October of 2015 Martin Odersky [asked for strawman proposals](https://github.com/lampepfl/dotty/issues/818) for a new collections library design for Scala 2.13, which eventually led to the project that we are currently working on, based on his latest proposal. This was not the first redesign for the Scala collections. The [current design](https://docs.scala-lang.org/overviews/core/architecture-of-scala-collections.html) was first implemented in Scala 2.8 along with the required improvements to type inference in the Scala compiler. It can generally be considered a success, providing powerful and flexible abstractions that bring together immutable and mutable collections, both sequential and parallel, with a high amount of shared interfaces and implementations. However, it does exhibit some symptoms of [second-system syndrome](https://en.wikipedia.org/wiki/Second-system_effect) that have been problematic in practice.
+In October of 2015 Martin Odersky [asked for strawman proposals](https://github.com/scala/scala3/issues/818) for a new collections library design for Scala 2.13, which eventually led to the project that we are currently working on, based on his latest proposal. This was not the first redesign for the Scala collections. The [current design](https://docs.scala-lang.org/overviews/core/architecture-of-scala-collections.html) was first implemented in Scala 2.8 along with the required improvements to type inference in the Scala compiler. It can generally be considered a success, providing powerful and flexible abstractions that bring together immutable and mutable collections, both sequential and parallel, with a high amount of shared interfaces and implementations. However, it does exhibit some symptoms of [second-system syndrome](https://en.wikipedia.org/wiki/Second-system_effect) that have been problematic in practice.
 
 ## Goals
 

_posts/2017-12-01-fifth-dotty-milestone-release.md

@@ -24,7 +24,7 @@ support for Scala 2.12 and came with a brand new REPL.
 
 ## What’s new in the 0.5.0-RC1 technology preview?
 
-### Reworked implicit search [#3421](https://github.com/lampepfl/dotty/pull/3421)
+### Reworked implicit search [#3421](https://github.com/scala/scala3/pull/3421)
 The treatment of ambiguity errors has changed. If an ambiguity is encountered
 in some recursive step of an implicit search, the ambiguity is propagated to the caller.
 Example: Say you have the following definitions:
@@ -55,7 +55,7 @@ techniques no longer work. But there is now a new special type `scala.implicits.
 implements negation directly. For any query type `Q`: `Not[Q]` succeeds if and only if the
 implicit search for `Q` fails.
 
-### Dependent function types [#3464](https://github.com/lampepfl/dotty/pull/3464)
+### Dependent function types [#3464](https://github.com/scala/scala3/pull/3464)
 A dependent function type describes functions where the result type may depend
 on the function's parameter values. Example:
 
@@ -107,7 +107,7 @@ are currently two backends using the TASTY frontend:
    This is the first step toward linking and whole world optimisations, recompiling code to a
    different backends...
 
-### Generic java signatures [#3234](https://github.com/lampepfl/dotty/pull/3234)
+### Generic java signatures [#3234](https://github.com/scala/scala3/pull/3234)
 Dotty now emits generic signatures for classes and methods. Theses signatures are used by compilers,
 debuggers and to support runtime reflection. For example:
 
@@ -141,7 +141,7 @@ the IDE sections of the <a href="https://docs.scala-lang.org/scala3/getting-star
 ### Standalone installation
 Releases are available for download on the _Releases_
 section of the Dotty repository:
-[https://github.com/lampepfl/dotty/releases](https://github.com/lampepfl/dotty/releases)
+[https://github.com/scala/scala3/releases](https://github.com/scala/scala3/releases)
 
 We also provide a [homebrew](https://brew.sh/) package that can be installed by running:
 
@@ -158,7 +158,7 @@ brew upgrade dotty
 ## Let us know what you think!
 If you have questions or any sort of feedback, feel free to send us a message on our
 [Gitter channel](https://gitter.im/lampepfl/dotty). If you encounter a bug, please
-[open an issue on GitHub](https://github.com/lampepfl/dotty/issues/new).
+[open an issue on GitHub](https://github.com/scala/scala3/issues/new).
 
 ## Contributing
 Thank you to all the contributors who made this release possible!
@@ -195,7 +195,7 @@ According to `git shortlog -sn --no-merges 0.4.0-RC1..0.5.0-RC1` these are:
 If you want to get your hands dirty and contribute to Dotty, now is a good time to get involved!
 You can have a look at our [Getting Started page for new contributors](https://dotty.epfl.ch/docs/contributing/getting-started.html),
 the [Awesome Error Messages](https://scala-lang.org/blog/2016/10/14/dotty-errors.html) project or some of
-the simple [Dotty issues](https://github.com/lampepfl/dotty/issues?q=is%3Aissue+is%3Aopen+label%3Aexp%3Anovice).
+the simple [Dotty issues](https://github.com/scala/scala3/issues?q=is%3Aissue+is%3Aopen+label%3Aexp%3Anovice).
 They make perfect entry-points into hacking on the compiler.
 
 We are looking forward to having you join the team of contributors.

_posts/2019-12-18-road-to-scala-3.md

@@ -167,7 +167,7 @@ If you don't have time to do a cross-build yourself, consider asking your users
 
 #### Working on Scala itself
 
-The Dotty team welcomes contributors, including first-time Scala contributors.  Scala 3 has already benefited considerably from years of active external participation [on GitHub](https://github.com/lampepfl/dotty). For guidance and getting-started help, there is an active [chat room on Gitter](https://gitter.im/lampepfl/dotty).  There are many ways to be helpful that don't require large time outlays or a background in compiler hacking.
+The Dotty team welcomes contributors, including first-time Scala contributors.  Scala 3 has already benefited considerably from years of active external participation [on GitHub](https://github.com/scala/scala3). For guidance and getting-started help, there is an active [chat room on Gitter](https://gitter.im/lampepfl/dotty).  There are many ways to be helpful that don't require large time outlays or a background in compiler hacking.
 
 If you are already a Scala 2 contributor, you are welcome to move to the new repo, but you might also choose to stay focused on Scala 2 for now if you prefer. Scala 2 will be maintained for several more years, and many kinds of improvements remain possible and desirable in the 2.13 series, subject to the usual compatibility constraints.  Standard library fixes are directly applicable to both versions; back end improvements benefit both compilers; improved linting could help Scala 2 users get their codebases ready for 3.
 

_posts/2020-02-20-community-build.md

@@ -134,8 +134,8 @@ And what about Scala 3?  Dotty has its own community build,
 and it continues to grow. It now contains 25 repos, compared to 5
 a year ago.
 
-Here is the [list of included repos](https://github.com/lampepfl/dotty/tree/master/community-build/community-projects).  If you want to add something,
-there are [instructions](https://github.com/lampepfl/dotty/tree/master/community-build/test/scala/dotty/communitybuild).
+Here is the [list of included repos](https://github.com/scala/scala3/tree/main/community-build/community-projects).  If you want to add something,
+there are [instructions](https://github.com/scala/scala3/tree/main/community-build/test/scala/dotty/communitybuild).
 
 ## Credits
 

_posts/2021-02-26-tuples-bring-generic-programming-to-scala-3.md

@@ -332,5 +332,5 @@ instead of `concat((1, 2), (3, 4))`, similarly to how we implemented `*:`.
 
 We can use the same approach for other functions on tuples, I invite you to
 have a look at the [source code of the standard
-library](https://github.com/lampepfl/dotty/blob/87102a0b182849c71f61a6febe631f767bcc72c3/library/src-bootstrapped/scala/Tuple.scala)
+library](https://github.com/scala/scala3/blob/87102a0b182849c71f61a6febe631f767bcc72c3/library/src-bootstrapped/scala/Tuple.scala)
 to see how the other operators are implemented.

_posts/2023-02-01-release-notes-3.2.2.md

@@ -3,7 +3,7 @@ category: announcement
 permalink: /news/3.2.2
 title: "Scala 3.2.2 is now available!"
 ---
-[Scala 3.2.2](https://github.com/lampepfl/dotty/releases/tag/3.2.2) is now available!
+[Scala 3.2.2](https://github.com/scala/scala3/releases/tag/3.2.2) is now available!
 
 This version not only fixes bugs but also brings two new flags:
 

_posts/2023-07-17-signature-polymorphic-methods.md

@@ -194,7 +194,7 @@ overloaded, with each individual overload only being brought into
 existence as needed.
 
 For details, see [the pull
-request](https://github.com/lampepfl/dotty/pull/16225).
+request](https://github.com/scala/scala3/pull/16225).
 
 ### The path not taken
 

_posts/2023-09-07-release-notes-3.3.1.md

@@ -3,7 +3,7 @@ category: announcement
 permalink: /news/3.3.1
 title: "Scala 3.3.1 LTS is now available!"
 ---
-[Scala 3.3.1 LTS](https://github.com/lampepfl/dotty/releases/tag/3.3.1) is now available!
+[Scala 3.3.1 LTS](https://github.com/scala/scala3/releases/tag/3.3.1) is now available!
 
 This version adds support for records in Java dependencies of Scala projects. It also brings improvements to the bytecode generation and a new linting rule: `-Wnonunit-statement`.