Update repository URLs

.github/pull_request_template.md

@@ -2,7 +2,7 @@ Thanks for sending a pull request! A few things before we get started:
 
 1. If this is your first time, please read the [contributing guide](https://metallb.universe.tf/community/#contributing)
 2. For non-trivial pull requests, please [file an
-   issue](https://github.com/google/metallb/issues/new) first, and get
+   issue](https://github.com/metallb/metallb/issues/new) first, and get
    agreement that the change is a good idea, and a general guideline
    for how it should be implemented, before sending code. Large PRs
    that weren't first discussed and agreed upon in an issue won't be

speaker/main.go

@@ -160,7 +160,7 @@ type controllerConfig struct {
 	SList  SpeakerList
 
 	// For testing only, and will be removed in a future release.
-	// See: https://github.com/google/metallb/issues/152.
+	// See: https://github.com/metallb/metallb/issues/152.
 	DisableLayer2 bool
 }
 

tasks.py

@@ -396,9 +396,9 @@ def _replace(pattern):
         newpat = pattern.format("v{}").format(version)
         run("perl -pi -e 's#{}#{}#g' website/content/*.md website/content/*/*.md".format(oldpat, newpat),
             echo=True)
-    _replace("/google/metallb/{}")
-    _replace("/google/metallb/tree/{}")
-    _replace("/google/metallb/blob/{}")
+    _replace("/metallb/metallb/{}")
+    _replace("/metallb/metallb/tree/{}")
+    _replace("/metallb/metallb/blob/{}")
 
     # Update the version listed on the website sidebar
     run("perl -pi -e 's/MetalLB .*/MetalLB v{}/g' website/content/_header.md".format(version), echo=True)

website/config.toml

@@ -7,7 +7,7 @@ theme = "docdock"
 
 [params]
 	# General information
-    editURL = "https://github.com/google/metallb/edit/main/website/content/"
+    editURL = "https://github.com/metallb/metallb/edit/main/website/content/"
 	description = "MetalLB, bare metal load-balancer for Kubernetes"
     disableNavChevron = true
 
@@ -17,7 +17,7 @@ home = ["HTML", "RSS", "JSON"]
 [[menu.shortcuts]]
 pre = "<hr>"
 name = "<i class='fa fa-github'></i> Github repo"
-url = "https://github.com/google/metallb"
+url = "https://github.com/metallb/metallb"
 weight = 10
 
 [[menu.shortcuts]]
@@ -32,5 +32,5 @@ weight = 30
 
 [[menu.shortcuts]]
 name = "<i class='fa fa-copyright'></i> License"
-url = "https://github.com/google/metallb/blob/main/LICENSE"
+url = "https://github.com/metallb/metallb/blob/main/LICENSE"
 weight = 40

website/content/_index.md

@@ -67,5 +67,5 @@ information.
 
 One lightweight way you can contribute is
 to
-[tell us that you're using MetalLB](https://github.com/google/metallb/issues/5),
+[tell us that you're using MetalLB](https://github.com/metallb/metallb/issues/5),
 which will give us warm fuzzy feelings :).

website/content/community/_index.md

@@ -33,7 +33,7 @@ if you don't already have an IRC client.
 ## Issue Tracker
 
 Use the [GitHub issue
-tracker](https://github.com/google/metallb/issues) to file bugs and
+tracker](https://github.com/metallb/metallb/issues) to file bugs and
 features request. If you need support, please send your questions to
 the metallb-users mailing list rather than filing a GitHub issue.
 
@@ -127,7 +127,7 @@ To develop MetalLB, you'll need a couple of pieces of software:
 ## Building and running the code
 
 Start by fetching the MetalLB repository, with `git clone
-https://github.com/danderson/metallb`.
+https://github.com/metallb/metallb`.
 
 From there, you can use Invoke to build Docker images, push them to
 registries, and so forth. `inv -l` lists the available tasks.
@@ -149,7 +149,7 @@ For example:
  metallb$ go run ./speaker/main.go ./speaker/*controller.go -config-ns metallb-system -kubeconfig $KUBECONFIG -node-name node0
 
 For development, fork
-the [github repository](https://github.com/google/metallb), and add
+the [github repository](https://github.com/metallb/metallb), and add
 your fork as a remote in `$GOPATH/src/go.universe.tf/metallb`, with
 `git remote add fork git@github.com:<your-github-user>/metallb.git`.
 

website/content/concepts/layer2.md

@@ -63,7 +63,7 @@ During an unplanned failover, the service IPs will be unreachable until the
 buggy clients refresh their cache entries.
 
 If you encounter a situation where layer 2 mode failover is slow (more than
-about 10s), please [file a bug](https://github.com/google/metallb/issues/new)!
+about 10s), please [file a bug](https://github.com/metallb/metallb/issues/new)!
 We can help you investigate and determine if the issue is with the client, or a
 bug in MetalLB.
 

website/content/configuration/_index.md

@@ -8,7 +8,7 @@ creating and deploying a configmap into the same namespace
 (metallb-system) as the deployment.
 
 There is an example configmap in
-[`manifests/example-config.yaml`](https://raw.githubusercontent.com/google/metallb/main/manifests/example-config.yaml),
+[`manifests/example-config.yaml`](https://raw.githubusercontent.com/metallb/metallb/main/manifests/example-config.yaml),
 annotated with explanatory comments.
 
 If you've named the configmap `config.yaml`, you can deploy the manifest with `kubectl apply -f config.yaml`.

website/content/configuration/calico.md

@@ -206,7 +206,7 @@ graph BT
 While this should theoretically work, it hasn't been demonstrated, and
 setting it up varies wildly based on which routing software/hardware
 you are interfacing with. If you get this working,
-please [let us know](https://github.com/google/metallb/issues/new),
+please [let us know](https://github.com/metallb/metallb/issues/new),
 especially if you have tips on how to make this work best!
 
 ## Ideas wanted!
@@ -217,4 +217,4 @@ acrobatics to integrate the two.
 
 If you have an idea for another workaround that would enable Calico
 and MetalLB to coexist nicely,
-please [tell us](https://github.com/google/metallb/issues/new) !
+please [tell us](https://github.com/metallb/metallb/issues/new) !

website/content/faq/_index.md

@@ -26,4 +26,4 @@ Yes but by default, OpenStack has anti-spoofing protection enabled which prevent
 
 ## Can I update one pool at a time?
 
-Not yet.  The whole configuration for MetalLB is stored in a ConfigMap called `config` in the metallb-system namespace. We anticipate converting to Custom Resources at some point as described in [Issue 196](https://github.com/google/metallb/issues/196).  Contributions Welcome! 
+Not yet.  The whole configuration for MetalLB is stored in a ConfigMap called `config` in the metallb-system namespace. We anticipate converting to Custom Resources at some point as described in [Issue 196](https://github.com/metallb/metallb/issues/196).  Contributions Welcome! 

website/content/installation/clouds.md

@@ -153,5 +153,5 @@ willing to pay for the resources (servers, IPs, ...) required to test
 the integration, then we could *potentially* add support to MetalLB.
 
 If you think you can help with getting resources for testing, [file a
-bug](https://github.com/danderson/metallb/issues/new) and we can talk
+bug](https://github.com/metallb/metallb/issues/new) and we can talk
 about it!

website/content/installation/network-addons.md

@@ -32,4 +32,4 @@ efficient "IPVS mode", in addition to the default "iptables mode."
 MetalLB **might** work with IPVS mode in kube-proxy, in Kubernetes
 1.13 or later. However, it is not explicitly tested yet, so it's at
 your own risk. See our [tracking
-bug](https://github.com/google/metallb/issues/153) for details.
+bug](https://github.com/metallb/metallb/issues/153) for details.