-
Notifications
You must be signed in to change notification settings - Fork 15
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
Decide on source of truth for tenant system owners #402
Comments
...particularly for systems operated by GSA, per @jezhumble. |
Other places this information is being tracked:
|
@jezhumble @nikzei @mogul @berndverst Would love your input on how we can reduce the number of canonical sources here. Happy to set up a meeting, if that's the best way to do it. |
My intention was that the sheet tracking results from the org request form start acting as the single list. All of the others are hand-managed and have no standards around how the information is gathered, refactored, and updated. At least with the survey sheet we know that other groups aren't using it for other purposes. My hope is that we eventually hold this information in a microservice, but so long as we're using the form and avoiding hand-editing of the sheet, I think it's a good place in the meantime. |
This is now redundant per https://github.com/18F/cg-migration/issues/42 and some other issues that came out of PI planning |
As a system operator, I would like to maintain knowledge of the owner for a particular application to prevent stale apps from taking up resources.
Ideas of implementation:
The text was updated successfully, but these errors were encountered: