# DVMeshNoise remote module fork and redirection

**URL:** https://discourse.itk.org/t/dvmeshnoise-remote-module-fork-and-redirection/604
**Category:** Engineering
**Tags:** remotemodule
**Created:** [January 19, 2018, 7:11am UTC](https://discourse.itk.org/t/dvmeshnoise-remote-module-fork-and-redirection/604 "2018-01-19T07:11:50Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![jhlegarreta](https://discourse.itk.org/user_avatar/discourse.itk.org/jhlegarreta/32/476_2.png) [@jhlegarreta](https://discourse.itk.org/u/jhlegarreta)
#### Post date: [January 19, 2018, 7:11am UTC](https://discourse.itk.org/t/dvmeshnoise-remote-module-fork-and-redirection/604/1 "2018-01-19T07:11:50Z")

</div>

Folks,  
I’ve realized that the [DVMeshNoise](https://github.com/DVigneault/DVMeshNoise) remote module that @DVigneault contributed with has the following GitHub address in ITK’s remote modules:

> <https://github.com/InsightSoftwareConsortium/ITK/blob/550cf512dfe3670f91439f4228d2b9fb64689d7a/Modules/Remote/DVMeshNoise.remote.cmake#L8>

However, that seems to be redirecting to:

> **[GitHub - InsightSoftwareConsortium/ITKMeshNoise: Classes to perturb ITK mesh...](https://github.com/InsightSoftwareConsortium/ITKMeshNoise)**
>
> Classes to perturb ITK mesh objects with Gaussian noise - GitHub - InsightSoftwareConsortium/ITKMeshNoise: Classes to perturb ITK mesh objects with Gaussian noise

@DVigneault’s [IJ submission](https://github.com/DVigneault/DVMeshNoiseSubmission) `README.md` reads:

> An up-to-date version of `DVMeshNoise` will be maintained at [GitHub - InsightSoftwareConsortium/ITKMeshNoise: Classes to perturb ITK mesh objects with Gaussian noise](https://github.com/DVigneault/DVMeshNoise/).

There seems to be a redirection there. Hence, I’m wondering whether we should rather change the URL to be the one at the `InsightSoftwareConsortium` GitHub repo’s, or else this was done on purpose, and everything is fine.

Thanks,  
JON HAITZ

---

<div class="post-metadata">

### Author: ![DVigneault](https://discourse.itk.org/user_avatar/discourse.itk.org/dvigneault/32/189_2.png) [@DVigneault](https://discourse.itk.org/u/DVigneault)
#### Post date: [January 19, 2018, 3:56pm UTC](https://discourse.itk.org/t/dvmeshnoise-remote-module-fork-and-redirection/604/2 "2018-01-19T15:56:57Z")

</div>

Jon–

We recently (in the last few weeks) transferred the module from my github account to the InsightSoftwareConsortium–I think both URLs you’ve pointed out are just holdovers from that. I’ve updated the `README` on the IJ submission–I think that the remote module URL should be updated as well, as I’m not sure how long github redirects transferred repositories.

Best,

–Davis

---

<div class="post-metadata">

### Author: ![dzenanz](https://discourse.itk.org/user_avatar/discourse.itk.org/dzenanz/32/1093_2.png) [@dzenanz](https://discourse.itk.org/u/dzenanz)
#### Post date: [January 19, 2018, 8:05pm UTC](https://discourse.itk.org/t/dvmeshnoise-remote-module-fork-and-redirection/604/3 "2018-01-19T20:05:02Z")

</div>

I think that GitHub redirects moved repositories until a new repository is created in the moved repository’s place (same name within same organization). But we should update the remote module to the new direct address.

---

<div class="post-metadata">

### Author: ![dzenanz](https://discourse.itk.org/user_avatar/discourse.itk.org/dzenanz/32/1093_2.png) [@dzenanz](https://discourse.itk.org/u/dzenanz)
#### Post date: [January 19, 2018, 8:24pm UTC](https://discourse.itk.org/t/dvmeshnoise-remote-module-fork-and-redirection/604/4 "2018-01-19T20:24:57Z")

</div>

I made a [patch](http://review.source.kitware.com/#/c/23033/) to avoid the redirect.

---

<div class="post-metadata">

### Author: ![jhlegarreta](https://discourse.itk.org/user_avatar/discourse.itk.org/jhlegarreta/32/476_2.png) [@jhlegarreta](https://discourse.itk.org/u/jhlegarreta)
#### Post date: [January 20, 2018, 9:19am UTC](https://discourse.itk.org/t/dvmeshnoise-remote-module-fork-and-redirection/604/5 "2018-01-20T09:19:20Z")

</div>

@dzenanz @DVigneault Thanks for the clarification and for addressing this.