You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We've been giving Meltano core engineers repo access on a one off basis by adding them to the repo specific Github teams. It also looks like theres inconsistent levels of access for the repo teams (some write and some maintainers).
Should we give the meltano engineering team maintainer access to all repos to avoid this one off permission setting? Then it might make sense to have all repo teams be consistently write level access and not maintainer.
@WillDaSilva raised a point to consider - that we might not want to do this to avoid fall out if an account is compromised. It's probably a tradeoff we want to weigh. Either simpler maintenance for engineering team for on/offboarding or higher security in case of compromise but harder to manage on/offboarding.
@pnadolny13 - In the context of MeltanoLabs, yes, I agree we can give the Meltano Team "Write" on all repos.
pnadolny13
changed the title
Should we give meltano engineering team access to all repos?
Give meltano engineering team write access to all repos
Sep 29, 2022
We've been giving Meltano core engineers repo access on a one off basis by adding them to the repo specific Github teams. It also looks like theres inconsistent levels of access for the repo teams (some write and some maintainers).
Should we give the meltano engineering team maintainer access to all repos to avoid this one off permission setting? Then it might make sense to have all repo teams be consistently write level access and not maintainer.
@WillDaSilva raised a point to consider - that we might not want to do this to avoid fall out if an account is compromised. It's probably a tradeoff we want to weigh. Either simpler maintenance for engineering team for on/offboarding or higher security in case of compromise but harder to manage on/offboarding.
@aaronsteers @WillDaSilva @kgpayne what do you think?
Proposed
The text was updated successfully, but these errors were encountered: