# CMake update

**URL:** https://discourse.itk.org/t/cmake-update/870
**Category:** Engineering
**Created:** [April 25, 2018, 9:04pm UTC](https://discourse.itk.org/t/cmake-update/870 "2018-04-25T21:04:18Z")
**Posts on this page:** 1
**Showing post:** 19

<div class="post-metadata">

### Author: ![matt.mccormick](https://discourse.itk.org/user_avatar/discourse.itk.org/matt.mccormick/32/7_2.png) [@matt.mccormick](https://discourse.itk.org/u/matt.mccormick)
#### Post date: [May 7, 2018, 7:59pm UTC](https://discourse.itk.org/t/cmake-update/870/19 "2018-05-07T19:59:28Z")

</div>

> [@phcerdan](#):
>
> Another option for ITKIsotropicWavelets is to transfer the repository to the InsightSoftwareConsortium.
> 
> I will be happy about this if I keep admin privileges on this one!

Great! Certainly, you will keep admin privileges. Since you are member of the _InsightSoftwareConsortium_ GitHub Org, I think you should be able to transfer the repository, according [to this documentation](https://help.github.com/articles/repository-permission-levels-for-an-organization/#creating-repositories). Please let us know if you have any issues.

> [@phcerdan](#):
>
> This is a good idea. How about 1 month?
> 
> 1 month without commits seems too short to me if the repo is stable. I mean, the maintainer can be active, but not actively working on the external module because there are no open issues, etc.

Agreed – fork if no activity in over 1 year?

---

_[View the full topic](https://discourse.itk.org/t/cmake-update/870)._