-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
Document Azure Pipelines owner/admins #39084
base: master
Are you sure you want to change the base?
Conversation
@@ -58,6 +58,14 @@ explicitly-managed secret. | |||
- [GitHub](https://github.com/): w3c | |||
- [@plehegar](https://github.com/plehegar) | |||
- [@sideshowbarker](https://github.com/sideshowbarker) | |||
- [Azure Pipelines](https://dev.azure.com/web-platform-tests/wpt) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
so we have both users with org access and users in the project…
there's a variety of different groups within the project with different levels of permissions, which makes it hard to tell that all these "project admins" listed below have the same level of access
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yep, there's a mess of different default teams and access levels, and leftovers from trying different things.
Would you like me to change something to get this PR merged?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd like some sort of explanation as to what's going on. Who has access to what—do we care that some users are stakeholders and some are basic in the org? Should we simplify the groups we have within the project, so it's more obvious who has access to what?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't want to make any changes as part of documenting this, because to be confident in any change requires understanding the mess. I can document that it's a bit messy and that nobody understands it, however.
No description provided.