Upgrading to GitHub Teams #137
Replies: 1 comment 4 replies
-
What this means in terms of membership. For now, we've greatly reduced the number of maintainers in Sous-Chefs (down to 18 from 50+). This reduces our yearly bill significantly. Members that contribute to OpenCollective haven't been removed as the cost of their seat is almost certainly covered in the contribution they give (even the lowest tier covers that cost). In the future @xorima and I have been mulling over different options for how we get maintainers more engaged and not destroy their inboxes with standardfiles PRs. We can't add any new members via an outside collaborator, as this still uses a seat. Any ideas that don't involve us rewriting the world would be appreciated! |
Beta Was this translation helpful? Give feedback.
-
Thanks to the spring clean we now have access to a bunch of new features:
Private repositories: We're moving a few repositories to private. Notably, the terraform job and the Kubernetes cluster. The Kubernetes cluster isn't currently in the Sous-chefs org given it would be public.
This won't be a breaking change for anyone.
Codespaces: This is now an option but given it's billed pay-as-you we're going to not enable it right now.
GitHub Insights: We can now tell who's using our cookbooks and how they're getting there
Beta Was this translation helpful? Give feedback.
All reactions