From Skype conversation with Lloyd, as he sends his regrets:
- Jean is done testing, I think. I think we're a little tight to transition before the WGM, so my leaning now is to transition as soon as possible after the WGM.
- Don't need to be done reconciliation, but probably best to be done gForge load.
- When we move, it'll be all at once
- gForge needs to be locked down when Jira goes live (note, just for the FHIR change tracker)
- Conversion can only happen once.
- So it should definitely happen before ballots open again
- We will transition while reconciliation is ongoing
Lorraine: Just saying we will have to prepare explanations and answers to the inevitable questions everyone will ask
- Lloyd, 11:41 AM
Sure Documentation is already pretty robust, but we can enhance if areas are found lacking. And we'll have to do training webinars.
So that needs to be prepped before we switch, and likely some communication in atlanta
- Lloyd, 11:42 AM
It'd be nice to identify a transition date for announcement in Atlanta.
- Transition will involve a bunch of time in cleaning up gForge (again) and making sure it loads cleanly. Then locking gForge from submissions, doing a final export, running the conversion and import and getting Joshua to change the permalink to redirect to Jira instead of gForge.
- We'll also update gForge intro with a big bold link telling people to go look at Jira.
- Lorraine: do you have a level of effort estimate for that?
- Lloyd: 3-4 solid days for cleanup (it's invariable a pia). Have to do a bunch of cross-checking of user emails, manage duplicate accounts and other noise too.
- Actual conversion and load takes about 5 hours
- Actually, make that 6, because need to give the gForge extract process time to run too.
- Lorraine: any way to give you assistance?
- Lloyd: Some parts of the cleanup can definitely be done by others
- We need the QA report to be clean as a start
- And I can spit out the reports from the load process that identify user issues, etc.
- Lorraine: Which means people need to pause making changes for a few days after qa clean, or will never be stable
- Lloyd: Not really. The bulk of the cleanup work will be with existing records. If we do the cleanup in the week before load, the cleanup needed when actually doing the load will typically be pretty small.
- But yes, will need to allocate a few more hours for that too.
- Basically, should assume that the tracker will be unavailable for 1 day.
- Lorraine: My bias is to put some contingency around that
- Lloyd: Sure. If we say it's unavailable for a few days and make it available after 8 hours, no-one will complain :)
Need to draft a transition plan - talk to Jean about the steps and when. Draft for Atlanta
Lloyd said some training material available. Review the material and decide next steps