Skip to content
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

Closed
jcscottiii opened this issue Oct 18, 2016 · 5 comments
Closed

Decide on source of truth for tenant system owners #402

jcscottiii opened this issue Oct 18, 2016 · 5 comments
Labels
business Business development, bizops, agreements, and other business unit issues

Comments

@jcscottiii
Copy link

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:

@jcscottiii jcscottiii added the business Business development, bizops, agreements, and other business unit issues label Oct 18, 2016
@afeld
Copy link
Contributor

afeld commented Oct 25, 2016

...particularly for systems operated by GSA, per @jezhumble.

@afeld
Copy link
Contributor

afeld commented Nov 1, 2016

Other places this information is being tracked:

@afeld afeld changed the title Gather information for system owners for applications Decide on source of truth for tenant system owners Nov 14, 2016
@afeld
Copy link
Contributor

afeld commented Nov 14, 2016

@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.

@mogul
Copy link
Contributor

mogul commented Dec 3, 2016

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.

@suprenant
Copy link

This is now redundant per https://github.com/18F/cg-migration/issues/42 and some other issues that came out of PI planning

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
business Business development, bizops, agreements, and other business unit issues
Projects
None yet
Development

No branches or pull requests

4 participants