Content: Data Flows : TV Show #1189
Conversation
this was missing btw
✅ Deploy Preview for cyf-curriculum canceled.
|
✅ Deploy Preview for cyf-tracks ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
✅ Deploy Preview for cyf-programming ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
✅ Deploy Preview for cyf-sdc ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
✅ Deploy Preview for cyf-common canceled.
|
✅ Deploy Preview for cyf-itd canceled.
|
✅ Deploy Preview for cyf-piscine ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
✅ Deploy Preview for cyf-launch ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
|
I'm not sure about this... This feels like something we could maybe do by applying tags to existing backlog items (to extract the pieces), rather than duplicating? Currently this PR duplicates what you're meant to do each sprint between the module tickets (e.g. CodeYourFuture/Module-Data-Flows#46) and the project tickets (e.g. CodeYourFuture/Project-TV-Show#9) I feel like either we should reference the project tickets in the sprint backlog, or we should reference the module tickets, but not both. Concretely, if we move Level 200 back to sprint 1, I only want to be modifying that in one place not two. |
It references the tickets using sprint filters, so if you update the label, it moves by itself. It's not duplicating - it mirrors the project. Can you say a bit more, because to me it sounds like your solution is this already? Edited! OK now I see what you're saying. You're not talking about the content in this PR, you're talking about the tickets between the module and the project repo. These tickets are the original tickets - they already existed - so I didn't pick up what you meant. It sounds like you're wondering whether we need the module tickets sending them to the project tickets. We have it that way because trainees felt it wasn't clear what to do when and asked for both sets. They liked the TV show project being a separate understandable thing - this came up in feedback a few times - but mentors worried they would miss the coursework if it wasn't spelled out on the main repo too. I actually have a preference for fewer tickets myself, but I'd keep the project tickets and dump the module ones. This would be vastly easier for maintenance and for lower context volunteers. What do you think? |
|
I think we agreed to block this on #1204 but let me know if that's not how you felt we concluded! |
Yep, we have blocked |
…nto content/TV-Show
this can't work until #1204 is merged
What does this change?
Just closing down my tabs - here's the TV show project re-added to the website and renamed according to the project naming convention.
Org Content?
Data Flows | 1-3 | Project
Checklist
Who needs to know about this?