Vercel
Operating under a single Vercel team
- Currently on the "Pro" plan for free thanks to our Vercel sponsorship
- Teams on this tier are limited to 5 team member seats
- Serious limitation in an org with 1000s people and potentially infinite projects
- Current members with seats
with-heart
kempsterrrr
thomasmetta
narbs
dhaiwat
- Why is this a bottleneck?
- Since we're maxed out, adding a new member means we have to remove someone else
- Git Fork Protection requires a team member to approve each preview deploy from a fork branched on any project with environment variables stored in Vercel (which is a healthy practice)
- 5 seated team members = 5 members that have to approve every single preview deploy from a fork = major bottleneck, even with the few projects we currently have
- Problem will only get worse as we add more projects
- We could get around this bottleneck by disabling Git Fork Protection, but I think that exposes us to potential risk and isn't a viable solution
- Potential short-term solution
- Define the process and requirements for receiving sponsorship from Vercel
- Create a new team for each project and apply for sponsorship
- Allow each project team to determine which of its own members are given access to the project
- Why is this a short-term solution?
- Even if we implement this solution, we still have a limited number of seats available to each project
- We'd still be bottlenecked by the fact that each project needs to establish its own sponsorship