Conversation
I'm going to move web views away from git.kernel.org, to be fronted by a CDN. It's already up and running as a trial on kernel.linuxsources.org. I like using a different domain for this (for cookie reasons), but it can be confusing to others. Should I put it under kernel.org subdomain, or keep it on kernel.linuxsources.org?
9% kernel.linuxsources.org
90% see.git.kernel.org
0
3
3

@monsieuricon Does it have to be a fourth-level domain, why not gitweb.kernel.org or smth similar? Cookie reasons as well?

1
0
0
@forst it must, because it's a pun on "cgit".
0
0
3

@monsieuricon Should always remain under kernel.org to look reputable blobcatcoffee

1
0
0

@monsieuricon What's going to happen to existing URLs all over the place?

1
0
0

@monsieuricon Absolutely - it's not some random linuxsources.org afterall blobcatbaguettehero

1
0
0
@jani they will get a 301 to the new location.
0
0
1
@gytisrepecka is that a blobcat holding a baguette?
1
0
1

@monsieuricon That cat votes for kernel.org with a baguette. Can also add croissant blobcatfingerguns

0
0
0

@monsieuricon thank you for working on this! Why not taking this opportunity to get shorter URLs g.kernel.org that would take less place in patches or ML discussions?

I like the pun with cgit, but that's a long one 😊
If we want long ones, what about bitkeeper.kernel.org? 🤔

0
0
0
@monsieuricon <something>.kernel.org, but I don't think a play on cgit is better than something KISS.
1
0
0
@conor I think we may actually just serve the web view out of kernel.org/pub/scm/*. It currently redirects to git.kernel.org from that location, but it doesn't have to, and it would be easy to map that.
0
0
2

@monsieuricon I always liked the concept of SRV records, to reuse a URL and then get content depending on the app type. No need to remember multiple URLs. But I guess that wouldn't work here as people use HTTP for both Git and cgit?

0
0
0