cloud-gov / product

Program-level artifacts, workflow and issues for cloud.gov
Creative Commons Zero v1.0 Universal
31 stars 15 forks source link

List our tenants who will need to be migrated #229

Closed brittag closed 8 years ago

brittag commented 8 years ago

In order for our team to plan this migration, we need a sense of who we're working with and what they need.

We need an authoritative list of:

Acceptance criteria:

brittag commented 8 years ago

Noting that we need to have both a name and an email address for the key contact.

brittag commented 8 years ago

We will likely also use this spreadsheet to track their progress:

datn commented 8 years ago

Should this list exclude all "sandbox" orgs?

brittag commented 8 years ago

I'd recommend including a list of sandbox orgs, since that serves our purpose of having a sense of who we're working with and what they need. People using sandbox orgs don't need migration of services for those orgs (for example), but they still need communications, etc.

datn commented 8 years ago

Document shared with Britta, Diego and John B. Please let me know if you need it modified -- script to be checked in shortly.

brittag commented 8 years ago

Yay thanks! I moved it over to our cloud.gov team folder so that other team members can see it as well (since we'll likely be collaborating with others); it's over here.

datn commented 8 years ago

Great! Wasn't sure who to share it with, so thanks for sharing it appropriately :)

brittag commented 8 years ago

I estimate that in order for this to be usable for our next steps, we'll need to keep this open until we list who is the key contact + list whether they have technical labor funding+staffing, so I'll reopen it for now. We may need to reassign it for that info (it's also ok with me if we consider that a new story).

brittag commented 8 years ago

(Also I made a new tab of the spreadsheet for turning this into more human-usable info, without messing with the nice tidy info straight from CF.)

datn commented 8 years ago

Didn't mean to close it -- sorry about that!

datn commented 8 years ago

This info can be regenerated at a moment's notice using this script.

datn commented 8 years ago

@mogul points out that the services call in this script shows available services, not used services. While we probably want a deeper analysis of app usage (cf. #247), we should at least develop this initial list based on actual app usage. I'm reworking the script to show only services with a service binding.

jbarnicle commented 8 years ago

@brittag I think this issue overlaps and is adequately covered by the spreadsheet produced in https://github.com/18F/cg-product/issues/247. Can we close?

brittag commented 8 years ago

@jbarnicle What's the current link to the spreadsheet produced by #247? (I checked those comments but wasn't quite sure.) That would be nice to have in these comments for the record (in case somebody finds this issue while looking for it). Then I think we can close it!

jbarnicle commented 8 years ago

@brittag Here is the last one that I ran - https://docs.google.com/spreadsheets/d/1Ur3ciaTrrlriJ5HNsGLyBgaWDLjcFZutxqWuB4fVSJg/edit#gid=580587808

brittag commented 8 years ago

@jbarnicle OK! I moved that to the cloud.gov team folder so that it's easier for other people to find. I see there are a couple earlier iterations of this document in that folder as well - up to you how you want to manage them. Thank you!