Done: transfer of the repository to scala/scala3

[hamzaremmal]

This PR is part of the upcoming transfer of the lampepfl/dotty repository to the scala organisation (scala/scala3).

[hamzaremmal]

Protocol for transfering lampepfl/dotty to scala/scala3

By @hamzaremmal and @sjrd

---

• Remove all the runners from lampepfl/dotty repository.
  We need to make sure that the runners don't execute any job when they are transferred.
  To check this: https://github.com/organizations/lampepfl/settings/actions/runners

• Transfer the repository to the scala organization.
  The renaming of the repository should be done at that moment, not later.
  (We believe that this is important for redirections; dry-run was completed this way).

• Copy and link all the GitHub Projects related to lampepfl/dotty. The projects are the following:

• Scala 3.3 LTS Backporting
• Scala 3.Next
• Scala 3.x planning

• Only allow the scala/scala3 repository to use the custom runners in the scala organization settings.

• Once we confirm that the runners are up in the scala organization (and that GitHub Actions is still enabled),
  we merge the following PR (Done: transfer of the repository to scala/scala3 #19839) to switch the
  configuration from lampepfl/dotty to scala/scala3.

• (Probably Nothing) @Kordyjan: Check if the backport to LTS project workflow is still working.
  We weren't able to test this during the dry-run. (Not a blocker).

• A few links to remove:

  • Remove the link to lampepfl/dotty in .github/profile/ See PR (Drop link to lampepfl/dotty repository .github#2)
  • Remove the link to lampepfl/dotty in the scala/scala repository (About section)

• Add warning in the .github-private of lampepfl (More info) to never create
  a repository with the name dotty.
  This is important for the redirections.

• Grant the correct access to the repository for (Same system as for the Scala 2 repository):

  • scala3-commiters: Should be granted Write role
  • scala3-admins: Should be granted Admin role

• Delete the scala3-transfer-test repository from the scala organization.

• Pin the repository in the scala organisation.

• Add link to the repository in the lampepfl organisation.

  • Add note about scala/scala3 lampepfl/.github#1
  • https://github.com/lampepfl/.github-private/pull/1

• Merge the following PRs:

  • Update links in the repository to scala/scala3 #19864
  • Update links to use scala/scala3 instead of lampepfl/dotty docs.scala-lang#2987
  • Update links to use scala/scala3 instead of lampepfl/dotty scala-lang#1600

Benchmarking infrastructure:

@mbovel will do the necessary after the transfer.

[hamzaremmal]

Second commit in this PR is not important to have a successful transfer.
Note to myself: Should I move it to a different PR ?

[SethTisue]

This is really minor, but once it's transferred, it should also become of the "pinned" repos at https://github.com/scala . (I just unpinned something else to make room for it.)

[hamzaremmal]

This is really minor, but once it's transferred, it should also become of the "pinned" repos at https://github.com/scala . (I just unpinned something else to make room for it.)

I had it in mind but I forgot to add it in the protocol. Just did.

[SethTisue]

s/commiters/committers/

[SethTisue]

about teams and permissions, if people feel that the right thing is to have Scala 3 specific GitHub teams, for permissions purposes, then great, I certainly don't object. but if it's being kept separate out of fear that you'll, like, step on Lightbend's toes, or disrupt tradition, or anything like that, you really needn't worry, it's fine, let's do whatever makes sense and isn't overly elaborate. cc @lrytz

[sjrd]

Second commit in this PR is not important to have a successful transfer. Note to myself: Should I move it to a different PR ?

I suggest we keep it for a separate PR that we'll do once we have confirmed that we have a working CI after the migration. This way, we will actually get a proper CI run of these additional changes.

[hamzaremmal]

Second commit in this PR is not important to have a successful transfer. Note to myself: Should I move it to a different PR ?

I suggest we keep it for a separate PR that we'll do once we have confirmed that we have a working CI after the migration. This way, we will actually get a proper CI run of these additional changes.

Agreed 👍

[sjrd]

about teams and permissions, if people feel that the right thing is to have Scala 3 specific GitHub teams, for permissions purposes, then great, I certainly don't object. but if it's being kept separate out of fear that you'll, like, step on Lightbend's toes, or disrupt tradition, or anything like that, you really needn't worry, it's fine, let's do whatever makes sense and isn't overly elaborate. cc @lrytz

IMO we could do that in a second phase. I'd like to minimize the amount of changes that we have to do at the time of the migration itself.

[hamzaremmal]

Second commit was moved to the following PR:

• Update links in the repository to scala/scala3 #19864

[hamzaremmal]

@Kordyjan This PR needs to be backported ASAP to the LTS branch (to have the new configuration setup).

It should also be backported to any active release branch too (mainly release-3.4.1)

[Kordyjan]

@Kordyjan This PR needs to be backported ASAP to the LTS branch (to have the new configuration setup).

Backported to all relevant branches.

[Kordyjan]

Check if the backport to LTS project workflow is still working.

Looks like it follows the redirects correctly, so nothing urgent to do here.

[hamzaremmal]

Check if the backport to LTS project workflow is still working.

Looks like it follows the redirects correctly, so nothing urgent to do here.

@Kordyjan There is a new project in the scala organization (https://github.com/orgs/scala/projects/2). The other one still has all the old PRs and we will be retiring it slowly. New PRs should go to this new project.