# Chef github organization rename

**URL:** <https://discourse.chef.io/t/chef-github-organization-rename/6169>\
**Category:** Chef Infra (archive)\
**Created:** [January 15, 2015, 9:12pm UTC](https://discourse.chef.io/t/chef-github-organization-rename/6169 "2015-01-15T21:12:02Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Mark\_Harrison](https://avatars.discourse-cdn.com/v4/letter/m/ebca7d/32.png) [@Mark\_Harrison](https://discourse.chef.io/u/Mark_Harrison)\
**Post date:** [January 15, 2015, 9:12pm UTC](https://discourse.chef.io/t/chef-github-organization-rename/6169/1 "2015-01-15T21:12:02Z")

</div>

Ohai Chefs!

It’s been a long time coming, but we are finally renaming the opscode  
github organizations to ‘chef’. This will be happening on Thursday  
January 22 2015 at approximately 11:00 PST/19:00 UTC.

All repositories will continue to be accessible using their old names,  
so those of you with existing checkouts have no need to worry.  
However, after that date you will start to see references to  
repositories being available from their new names.

To summarize:

[https://github.com/opscode/repositoryname](https://github.com/opscode/repositoryname) will become  
[https://github.com/chef/repositoryname](https://github.com/chef/repositoryname)

and similar changes will be made for accessing repositories via ssh  
and the git protocol.

The migration into chef-cookbooks will work a little differently.  
Instead of renaming the org and being done with it, we will be moving  
cookbooks one by one, as they go through heavy duty QA and testing  
procedures. The opscode-cookbooks organization will remain until all  
cookbooks have been migrated or adopted.

Thanks,

Mark Harrison  
Systems Administrator, Chef

---

<div class="post-metadata">

**Author:** ![Mark\_Harrison](https://avatars.discourse-cdn.com/v4/letter/m/ebca7d/32.png) [@Mark\_Harrison](https://discourse.chef.io/u/Mark_Harrison)\
**Post date:** [January 22, 2015, 6:28pm UTC](https://discourse.chef.io/t/chef-github-organization-rename/6169/2 "2015-01-22T18:28:12Z")

</div>

Hi all,

This email is just a reminder that the opscode github organization  
rename will be happening today in approximately 1 hour (about 30  
minutes later than originally planned). I'll be sending out another  
post to the mailing list once the rename is complete.

Thanks,

Mark

On Thu, Jan 15, 2015 at 4:12 PM, Mark Harrison [mharrison@chef.io](mailto:mharrison@chef.io) wrote:

> Ohai Chefs!
> 
> It’s been a long time coming, but we are finally renaming the opscode  
> github organizations to ‘chef’. This will be happening on Thursday  
> January 22 2015 at approximately 11:00 PST/19:00 UTC.
> 
> All repositories will continue to be accessible using their old names,  
> so those of you with existing checkouts have no need to worry.  
> However, after that date you will start to see references to  
> repositories being available from their new names.
> 
> To summarize:
> 
> [https://github.com/opscode/repositoryname](https://github.com/opscode/repositoryname) will become  
> [https://github.com/chef/repositoryname](https://github.com/chef/repositoryname)
> 
> and similar changes will be made for accessing repositories via ssh  
> and the git protocol.
> 
> The migration into chef-cookbooks will work a little differently.  
> Instead of renaming the org and being done with it, we will be moving  
> cookbooks one by one, as they go through heavy duty QA and testing  
> procedures. The opscode-cookbooks organization will remain until all  
> cookbooks have been migrated or adopted.
> 
> Thanks,
> 
> Mark Harrison  
> Systems Administrator, Chef

---

<div class="post-metadata">

**Author:** ![Mark\_Harrison](https://avatars.discourse-cdn.com/v4/letter/m/ebca7d/32.png) [@Mark\_Harrison](https://discourse.chef.io/u/Mark_Harrison)\
**Post date:** [January 22, 2015, 7:49pm UTC](https://discourse.chef.io/t/chef-github-organization-rename/6169/3 "2015-01-22T19:49:37Z")

</div>

Hi everyone,

The organization rename is now complete. You can now access chef's  
public code by going to [GitHub - chef/chef: Chef Infra, a powerful automation platform that transforms infrastructure into code automating how infrastructure is configured, deployed and managed across any environment, at any scale](https://github.com/chef/chef) (and similar for  
other repository names) in addition to the old names.

Regards,

Mark

On Thu, Jan 22, 2015 at 1:28 PM, Mark Harrison [mharrison@chef.io](mailto:mharrison@chef.io) wrote:

> Hi all,
> 
> This email is just a reminder that the opscode github organization  
> rename will be happening today in approximately 1 hour (about 30  
> minutes later than originally planned). I'll be sending out another  
> post to the mailing list once the rename is complete.
> 
> Thanks,
> 
> Mark
> 
> On Thu, Jan 15, 2015 at 4:12 PM, Mark Harrison [mharrison@chef.io](mailto:mharrison@chef.io) wrote:
> 
> > Ohai Chefs!
> > 
> > It’s been a long time coming, but we are finally renaming the opscode  
> > github organizations to ‘chef’. This will be happening on Thursday  
> > January 22 2015 at approximately 11:00 PST/19:00 UTC.
> > 
> > All repositories will continue to be accessible using their old names,  
> > so those of you with existing checkouts have no need to worry.  
> > However, after that date you will start to see references to  
> > repositories being available from their new names.
> > 
> > To summarize:
> > 
> > [https://github.com/opscode/repositoryname](https://github.com/opscode/repositoryname) will become  
> > [https://github.com/chef/repositoryname](https://github.com/chef/repositoryname)
> > 
> > and similar changes will be made for accessing repositories via ssh  
> > and the git protocol.
> > 
> > The migration into chef-cookbooks will work a little differently.  
> > Instead of renaming the org and being done with it, we will be moving  
> > cookbooks one by one, as they go through heavy duty QA and testing  
> > procedures. The opscode-cookbooks organization will remain until all  
> > cookbooks have been migrated or adopted.
> > 
> > Thanks,
> > 
> > Mark Harrison  
> > Systems Administrator, Chef

---

<div class="post-metadata">

**Author:** ![tknerr](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.chef.io/tknerr/32/21_2.png) [@tknerr](https://discourse.chef.io/u/tknerr)\
**Post date:** [January 30, 2015, 9:49am UTC](https://discourse.chef.io/t/chef-github-organization-rename/6169/4 "2015-01-30T09:49:07Z")

</div>

Hi Mark,

I noticed there is also:

[https://github.com/opscode-cookbooks](https://github.com/opscode-cookbooks)  
vs.

> **[Chef Community Cookbooks](https://github.com/chef-cookbooks)**
>
> This repository is for public community cookbooks that are shared on the supermarket site. - Chef Community Cookbooks

Is this the distinction between offical Chef cookbooks and community  
contributed Chef cookbooks, or just migration in progress?

Cheers,  
Torben

On Thu, Jan 22, 2015 at 8:49 PM, Mark Harrison [mharrison@chef.io](mailto:mharrison@chef.io) wrote:

> Hi everyone,
> 
> The organization rename is now complete. You can now access chef's  
> public code by going to [GitHub - chef/chef: Chef Infra, a powerful automation platform that transforms infrastructure into code automating how infrastructure is configured, deployed and managed across any environment, at any scale](https://github.com/chef/chef) (and similar for  
> other repository names) in addition to the old names.
> 
> Regards,
> 
> Mark
> 
> On Thu, Jan 22, 2015 at 1:28 PM, Mark Harrison [mharrison@chef.io](mailto:mharrison@chef.io) wrote:
> 
> > Hi all,
> > 
> > This email is just a reminder that the opscode github organization  
> > rename will be happening today in approximately 1 hour (about 30  
> > minutes later than originally planned). I'll be sending out another  
> > post to the mailing list once the rename is complete.
> > 
> > Thanks,
> > 
> > Mark
> > 
> > On Thu, Jan 15, 2015 at 4:12 PM, Mark Harrison [mharrison@chef.io](mailto:mharrison@chef.io) wrote:
> > 
> > > Ohai Chefs!
> > > 
> > > It’s been a long time coming, but we are finally renaming the opscode  
> > > github organizations to ‘chef’. This will be happening on Thursday  
> > > January 22 2015 at approximately 11:00 PST/19:00 UTC.
> > > 
> > > All repositories will continue to be accessible using their old names,  
> > > so those of you with existing checkouts have no need to worry.  
> > > However, after that date you will start to see references to  
> > > repositories being available from their new names.
> > > 
> > > To summarize:
> > > 
> > > [https://github.com/opscode/repositoryname](https://github.com/opscode/repositoryname) will become  
> > > [https://github.com/chef/repositoryname](https://github.com/chef/repositoryname)
> > > 
> > > and similar changes will be made for accessing repositories via ssh  
> > > and the git protocol.
> > > 
> > > The migration into chef-cookbooks will work a little differently.  
> > > Instead of renaming the org and being done with it, we will be moving  
> > > cookbooks one by one, as they go through heavy duty QA and testing  
> > > procedures. The opscode-cookbooks organization will remain until all  
> > > cookbooks have been migrated or adopted.
> > > 
> > > Thanks,
> > > 
> > > Mark Harrison  
> > > Systems Administrator, Chef

---

<div class="post-metadata">

**Author:** ![Mark\_Harrison](https://avatars.discourse-cdn.com/v4/letter/m/ebca7d/32.png) [@Mark\_Harrison](https://discourse.chef.io/u/Mark_Harrison)\
**Post date:** [January 30, 2015, 3:21pm UTC](https://discourse.chef.io/t/chef-github-organization-rename/6169/5 "2015-01-30T15:21:24Z")

</div>

Hi Torben,

The migration into chef-cookbooks is going to work a little differently.  
Instead of renaming the organization, we are going to be be moving  
cookbooks one by one, as they go through heavy duty QA and testing  
procedures. For now, the opscode-cookbooks organization will remain  
until all cookbooks have been migrated or adopted.

Thanks,

Mark

On Fri, Jan 30, 2015 at 4:49 AM, Torben Knerr [mail@tknerr.de](mailto:mail@tknerr.de) wrote:

> Hi Mark,
> 
> I noticed there is also:
> 
> [https://github.com/opscode-cookbooks](https://github.com/opscode-cookbooks)  
> vs.  
> [Chef Community Cookbooks · GitHub](https://github.com/chef-cookbooks)
> 
> Is this the distinction between offical Chef cookbooks and community  
> contributed Chef cookbooks, or just migration in progress?
> 
> Cheers,  
> Torben
> 
> On Thu, Jan 22, 2015 at 8:49 PM, Mark Harrison [mharrison@chef.io](mailto:mharrison@chef.io) wrote:
> 
> > Hi everyone,
> > 
> > The organization rename is now complete. You can now access chef's  
> > public code by going to [GitHub - chef/chef: Chef Infra, a powerful automation platform that transforms infrastructure into code automating how infrastructure is configured, deployed and managed across any environment, at any scale](https://github.com/chef/chef) (and similar for  
> > other repository names) in addition to the old names.
> > 
> > Regards,
> > 
> > Mark
> > 
> > On Thu, Jan 22, 2015 at 1:28 PM, Mark Harrison [mharrison@chef.io](mailto:mharrison@chef.io) wrote:
> > 
> > > Hi all,
> > > 
> > > This email is just a reminder that the opscode github organization  
> > > rename will be happening today in approximately 1 hour (about 30  
> > > minutes later than originally planned). I'll be sending out another  
> > > post to the mailing list once the rename is complete.
> > > 
> > > Thanks,
> > > 
> > > Mark
> > > 
> > > On Thu, Jan 15, 2015 at 4:12 PM, Mark Harrison [mharrison@chef.io](mailto:mharrison@chef.io) wrote:
> > > 
> > > > Ohai Chefs!
> > > > 
> > > > It’s been a long time coming, but we are finally renaming the opscode  
> > > > github organizations to ‘chef’. This will be happening on Thursday  
> > > > January 22 2015 at approximately 11:00 PST/19:00 UTC.
> > > > 
> > > > All repositories will continue to be accessible using their old names,  
> > > > so those of you with existing checkouts have no need to worry.  
> > > > However, after that date you will start to see references to  
> > > > repositories being available from their new names.
> > > > 
> > > > To summarize:
> > > > 
> > > > [https://github.com/opscode/repositoryname](https://github.com/opscode/repositoryname) will become  
> > > > [https://github.com/chef/repositoryname](https://github.com/chef/repositoryname)
> > > > 
> > > > and similar changes will be made for accessing repositories via ssh  
> > > > and the git protocol.
> > > > 
> > > > The migration into chef-cookbooks will work a little differently.  
> > > > Instead of renaming the org and being done with it, we will be moving  
> > > > cookbooks one by one, as they go through heavy duty QA and testing  
> > > > procedures. The opscode-cookbooks organization will remain until all  
> > > > cookbooks have been migrated or adopted.
> > > > 
> > > > Thanks,
> > > > 
> > > > Mark Harrison  
> > > > Systems Administrator, Chef

---

<div class="post-metadata">

**Author:** ![tknerr](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.chef.io/tknerr/32/21_2.png) [@tknerr](https://discourse.chef.io/u/tknerr)\
**Post date:** [February 1, 2015, 10:55pm UTC](https://discourse.chef.io/t/chef-github-organization-rename/6169/6 "2015-02-01T22:55:01Z")

</div>

Thanks Mark!

On Fri, Jan 30, 2015 at 4:21 PM, Mark Harrison [mharrison@chef.io](mailto:mharrison@chef.io) wrote:

> Hi Torben,
> 
> The migration into chef-cookbooks is going to work a little differently.  
> Instead of renaming the organization, we are going to be be moving  
> cookbooks one by one, as they go through heavy duty QA and testing  
> procedures. For now, the opscode-cookbooks organization will remain  
> until all cookbooks have been migrated or adopted.
> 
> Thanks,
> 
> Mark
> 
> On Fri, Jan 30, 2015 at 4:49 AM, Torben Knerr [mail@tknerr.de](mailto:mail@tknerr.de) wrote:
> 
> > Hi Mark,
> > 
> > I noticed there is also:
> > 
> > [https://github.com/opscode-cookbooks](https://github.com/opscode-cookbooks)  
> > vs.  
> > [Chef Community Cookbooks · GitHub](https://github.com/chef-cookbooks)
> > 
> > Is this the distinction between offical Chef cookbooks and community  
> > contributed Chef cookbooks, or just migration in progress?
> > 
> > Cheers,  
> > Torben
> > 
> > On Thu, Jan 22, 2015 at 8:49 PM, Mark Harrison [mharrison@chef.io](mailto:mharrison@chef.io) wrote:
> > 
> > > Hi everyone,
> > > 
> > > The organization rename is now complete. You can now access chef's  
> > > public code by going to [GitHub - chef/chef: Chef Infra, a powerful automation platform that transforms infrastructure into code automating how infrastructure is configured, deployed and managed across any environment, at any scale](https://github.com/chef/chef) (and similar for  
> > > other repository names) in addition to the old names.
> > > 
> > > Regards,
> > > 
> > > Mark
> > > 
> > > On Thu, Jan 22, 2015 at 1:28 PM, Mark Harrison [mharrison@chef.io](mailto:mharrison@chef.io) wrote:
> > > 
> > > > Hi all,
> > > > 
> > > > This email is just a reminder that the opscode github organization  
> > > > rename will be happening today in approximately 1 hour (about 30  
> > > > minutes later than originally planned). I'll be sending out another  
> > > > post to the mailing list once the rename is complete.
> > > > 
> > > > Thanks,
> > > > 
> > > > Mark
> > > > 
> > > > On Thu, Jan 15, 2015 at 4:12 PM, Mark Harrison [mharrison@chef.io](mailto:mharrison@chef.io) wrote:
> > > > 
> > > > > Ohai Chefs!
> > > > > 
> > > > > It’s been a long time coming, but we are finally renaming the opscode  
> > > > > github organizations to ‘chef’. This will be happening on Thursday  
> > > > > January 22 2015 at approximately 11:00 PST/19:00 UTC.
> > > > > 
> > > > > All repositories will continue to be accessible using their old names,  
> > > > > so those of you with existing checkouts have no need to worry.  
> > > > > However, after that date you will start to see references to  
> > > > > repositories being available from their new names.
> > > > > 
> > > > > To summarize:
> > > > > 
> > > > > [https://github.com/opscode/repositoryname](https://github.com/opscode/repositoryname) will become  
> > > > > [https://github.com/chef/repositoryname](https://github.com/chef/repositoryname)
> > > > > 
> > > > > and similar changes will be made for accessing repositories via ssh  
> > > > > and the git protocol.
> > > > > 
> > > > > The migration into chef-cookbooks will work a little differently.  
> > > > > Instead of renaming the org and being done with it, we will be moving  
> > > > > cookbooks one by one, as they go through heavy duty QA and testing  
> > > > > procedures. The opscode-cookbooks organization will remain until all  
> > > > > cookbooks have been migrated or adopted.
> > > > > 
> > > > > Thanks,
> > > > > 
> > > > > Mark Harrison  
> > > > > Systems Administrator, Chef