Transition <dev> tasks from Notion Roadmap to GitHub Project

[coreymjames]

Read through Notion SMS Roadmap and Notion SPARK Roadmap to LabWeek and ensure that dev issues / sub-tasks are 1) captured in GitHub Issues and 2) connected to their associated milestones

Note: This has been done for PM issues, but CJ is adding this here to ensure dev issues don't slip through the cracks during this transition.

[bajtos]

Created the following roadmap items:

• SPARK tasking based on MERidian rounds space-meridian/roadmap#41
• SPARK CAR checksums spark#30
• SPARK CID sampling alpha space-meridian/roadmap#43
• SPARK: post-LabWeek roadmap #54

Over to you, @juliangruber

[juliangruber]

@bajtos I believe these issues are still missing the assignments to their respective milestones

[juliangruber]

@coreymjames where do you think milestones should be created? Or are you thinking about milestone-type issues in the roadmap repo?

[juliangruber]

I created issues for my work

[coreymjames]

@juliangruber we made milestones within GH that align with the roadmap (see this proj board view). They all exist within the proj-mgmt repo, but i also created identically named milestones within the spark repo's milestones for M3 & M4.

This duplicated milestones solution is not ideal. It's a byproduct of limited functionality within GitHub, in that issues in two separate repos cannot be added within one shared milestone. In other words, milestones are particular to repo's and not to GitHub organizations.

Does this make sense?

If this solution works well enough, I can create milestones within Meridian and other necessary repo's so that we have accurate labelling of issues and their associated milestones.

[coreymjames]

Going to close this issue, but we can continue the Milestones discussion in the slack thread i created.

[juliangruber]

Reopening as my issues aren't assigned to milestones yet 👋

[juliangruber]

@coreymjames ok, would be great if you could duplicate these milestones also into the meridian-ie repo 🙏

[coreymjames]

done