finalize project plan drafts

[CECSpecialistI]

https://drive.google.com/drive/folders/1fw41QPOh0m1L3j5Pmk2CuHrXqfhE7pLr?usp=drive_link

[sarahruska]

Hi @CECSpecialistI - I'm looking at Milestones to get a sense of the volume of issues working towards the end of the year. I think I need some more info on them - perhaps help defining which each is?

We have 172 issues without a milestone, and some milestones that are unused, like Mapping Review. In June 2022, meeting notes say BSR milestone = MVP. In July 2022, Decisions Index says "Current milestone: MVP for Transform. Priority order for subsequent milestones: BSR, CSR, Mapping Review, Publication [milestone for transform will be created once we have MVP done]."

Does this mean we should deprecate either the BSR or MVP milestone and combine into one? Or is the way to think of it that an issue is first part of the BSR milestone, then moved to the Mapping Review milestone, and finally to the MVP milestone?

[CECSpecialistI]

The MVP for Transform milestone should be collapsed into the BSR milestone. The Mapping Review milestone can probably be abandoned since we are doing review as we go as part of the BSR/CSR milestones

[sarahruska]

I've deleted the Mapping Review milestone and moved all issues (open & closed) that were under MVP for Transform into PCC RDA BSR. For the moment I've left the MVP for Transform milestone available, with a note to not use, and see this thread

[sarahruska]

Hi @CECSpecialistI - here's a proposal for Timelines & Milestones, and a few questions/comments - let me know

Timeline:

• Phase I: March 3, 2021 - December 20, 2024
• Post-Phase I Close-out: January 2, 2025 - February 28, 2025
• Phase II: March 1, 2025 - June 30, 2026

Milestones:

• Phase I:
  • PCC RDA BSR: December 20, 2024
  • Wikibase Cloud: December 20, 2024
  • Phase I Publication: December 20, 2024
• Post-Phase I Close-out:
  • Post-Phase I Publication: February 28, 2025
• Phase II:
  • Transformation Output Review: March 31, 2025
  • PCC RDA BSR v2: December 23, 2025
  • PCC RDA CSR: June 30, 2026
  • Phase II Publication: June 30, 2026

Comments/Questions:

• I initially was considering Wikibase Cloud to be a milestone next year. My current thinking is that the current work setting it up is both a milestone and deliverable that is part of this year's Phase 1. Then next steps with it are part of a Transformation Output milestone next year.
  • I understand from discussing with Cypress that a full end-to-end transformation output will not be complete by EOY. Given that, I'm thinking of this as a separate milestone from what we'll complete this year towards transformation
• Currently we have a milestone called Publication. Since publications are ongoing, I suggest we update this to account for Phase 1. Then, we open another for later phases of publications. I think this would be items that are a combination of our community engagement and documentation labels (i.e., all community engagement, but likely a subset of all documentation).
• I'm considering the white paper to justify phase 2 as part of a separate Post-Phase 1 Close-out milestone, rather than part of Phase 1 or 2 itself. Do you think about this differently?
  • I would include grant applications as part of this as well
• Do the proposed dates seem like a good starting point?
  • I'm presuming we'll tighten up Phase 2 dates following the white paper. With BSR taking 3+ years, I cut CSR to 1.5 years, since I'm optimistic we'll be able to leverage work and learnings to be quicker.

[CECSpecialistI]

I like the Post-Phase-1 close-out milestone. The proposed dates seem like a great starting point, but until we have an actual plan or approval for phase II I don't think we should assign any dates to it without qualifying them in some way. Maybe including a "tentative" qualifier or something like that. I think the Publications Milestone was an artifact of a very early stage in the project planning process and deserves to be thrown aside. We should talk about what end-to-end transformation means and what transformation review means, because Phase II and work into March of next year, while it would be great, requires commitments that haven't yet been made.

[CECSpecialistI]

Thank you Sara for all of this work!! I think it's ready to be used as a starting point for sure.

[sarahruska]

Thanks, Crystal! I've incorporated high-level problem statement, goals, impact into the wiki About section. I've updated the Projected Phases and Timelines in the wiki. The Project Overview document has this information in one place. I also created a high-level Project Overview Brief slide that has Phase I executive summary style overview. Last on this task is finalizing the longer form project plan document.

[sarahruska]

We should talk about what end-to-end transformation means and what transformation review means, because Phase II and work into March of next year, while it would be great, requires commitments that haven't yet been made.

I discussed this more with Cypress yesterday. End of year all coding will be done for the transform. Being able to run it against LC will most likely not be done, i.e., we will not have all the output (and therefore, won't have that to review). We need more memory to run against otherwise the transform process will time out. We also expect there will be errors that will need debugging, as part of the regular course of the coding lifecycle, once we run the transform against LC. If Wikibase Cloud is also not ready, then will have only files.