Sept 20th: /swiftlang migration for swift-foundation

Related Projects Foundation
1

Foundation community,

September 21st update: we're live -

Tomorrow, September 20th, between the hours of 3-4pm PT / 10-11pm UTC, we will be migrating GitHub - swiftlang/swift-foundation: The Foundation project to GitHub - swiftlang/swift-foundation: The Foundation project.

What to expect:

  • Most repos to date have taken <20 minutes to transfer.
  • At the time of transferring, there will be no forking, pushing, pulling, etc. The repo is down.
  • Once the transfer has happened, the repo will still be down for CI until it's been fixed.
  • Total time per repo until all activities can be resumed can be 30 minutes to 1.5 hours based on our past experience.

On Monday, September 23rd, the Foundation Workgroup will also update swift.org with a charter to represent the group.

We'll send an update to this thread once we've crossed various milestones.

Thanks
Paris

7 Likes
2

Perhaps a silly question, but could we name it swiftlang/foundation? The "Swift" part is implied by the org now

4 Likes
3

Good idea, but that would require updating several build scripts, both official ones and downstream like mine, so maybe that can be done later?

4

Wouldn't they need to be updated anyway?

5

No, this change only requires changing the org name in the update-checkout script, whereas changing the repo name requires more extensive changes.

I agree with you that both should be done, I just don't think they should be tied together.

1 Like
6

Ah, ok.

I tend to take a fast-rip approach to bandaids, but I'm not the one impacted, so it'd be unreasonable for me to demand one way or another.

Ideally, I'd love if we could get to just having github.com/swift/foundation :D

1 Like
7

Pretty much all repositories under the swiftlang org (39 when you exclude llvm-project and swift proper) have a swift- prefix. Renaming only swift-foundation but not the rest would introduce inconsistency and confusion.

8 Likes
8

Renaming only swift-foundation but not the rest would introduce inconsistency and confusion.

Can you guess what question I'm about to ask next? ;)

(I hope that comes off as fun and light-hearted, and not quippy and annoying lol)

7 Likes
9

Careful, or we'll get swift-swiftlang/swift-foundation

6 Likes
10

Quick! I'll register swift-github.com so we can have swift-github.com/swift-swiftlang/swift-foundation.

5 Likes
11

Re: swift- prefix.

The Core Team has been talking about this as well and agrees that there are things in the org that can have the swift- prefix removed. We'll update folks when we have come up with a decision and a matrix on what gets a prefix v what doesn't. As @Finagolfin mentions, we need to uncouple this from the migration though. We'll update folks in a broader sense about the prefix and repos that will be changed in the wider -dev category here.

Re: migration schedule today:
We are also moving 2 additional repos today in the Foundation window. Check out the full line up in the mega GitHub Org thread.

14 Likes
12

Great, thanks for the update Paris

1 Like
13

By the way, is it okay that update-checkout-config.json says still their org is apple?

14

It works fine because links to the old org redirect to the new one, but Mishal is updating that file to use the new org.

2 Likes
15

The prefix is still useful when repositories are forked (from swiftlang, apple, and others).

  • username/swift-evolution
  • username/pkl-evolution
  • username/haxe-evolution

However, it's also possible to customize the name when creating a new fork.