Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consolidation of orgs #26

Open
tas50 opened this issue Dec 12, 2018 · 8 comments
Open

Consolidation of orgs #26

tas50 opened this issue Dec 12, 2018 · 8 comments
Labels
Triage: Confirmed Indicates and issue has been confirmed as described.

Comments

@tas50
Copy link
Contributor

tas50 commented Dec 12, 2018

We have a large number of orgs at Chef. Do we want to consider consolidation of some of our orgs? It's hard to find projects sometimes since they're spread all over based on the teams that created them.

  • chef
  • chef-boneyard
  • chef-cft
  • chef-customers
  • chef-marketing
  • chef-partners
  • chef-training
  • chef-cookbooks
  • learn-chef
  • habitat-sh
  • inspec
  • opscode-cookbooks
@eeyun
Copy link

eeyun commented Dec 18, 2018

I'm not sure that this will fly with the hab-team or not tbph. However, the larger concern that probably needs thorough discussion is how this might affect membership. We're going to have to start using GH teams very heavily if membership includes being added as a member to the org your project is a part of. Does having one org make that experience cleaner or dirtier? We could use GH teams like habitat-members, builder-members, habitat-reviewers and the like - does it make more sense for these orgs to instead exist separately with their own "members, reviewers, approvers" GH teams?

@tas50
Copy link
Contributor Author

tas50 commented Dec 22, 2018

I'm not really suggesting habitat/inspec. More suggesting we take a serious look at our Chef orgs. We split out due to permissions issues. If we automate the permissions there we can consolidate our work into a single repo which is easier to navigate, easier to manage, and probably a bit cheaper.

@jtimberman
Copy link

I am 100% in favor of consolidating "Chef" organizations and it's something we've talked about on the ops team multiple - many times over the years.

@bennyvasquez bennyvasquez self-assigned this Apr 30, 2021
@tas50
Copy link
Contributor Author

tas50 commented Apr 30, 2021

I would still really like us to consolidate the chef and inspec orgs. Having components like train in their own org makes cross team collaboration very difficult and really serves no purpose in 2021.

@bennyvasquez
Copy link
Contributor

Resolving this will likely involve #50, too.

@bennyvasquez bennyvasquez added the Triage: Confirmed Indicates and issue has been confirmed as described. label Apr 30, 2021
@damacus
Copy link
Contributor

damacus commented May 5, 2021

Do we still need https://github.com/opscode-cookbooks?

@jtimberman
Copy link

@damacus For historical context, that organization was created in order to preserve the namespace so that some other person didn't "squat" it, or use it for nefarious purposes.

@damacus
Copy link
Contributor

damacus commented Jun 2, 2021

Thanks! I knew someone would know.

@bennyvasquez bennyvasquez removed their assignment May 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Triage: Confirmed Indicates and issue has been confirmed as described.
Projects
None yet
Development

No branches or pull requests

5 participants