cer-hunter
commented
1 week ago Hey all,
-
So firstly when it says "Have a clear plan on which team members will show which parts of the POC demo" it just means y'all aren't talking over each other in the demo, as in you've rehearsed what you're going to say and do.
-
"Issues aren't too big" this is subjective basically all this means is that what it says afterward, that they are feasible to be completed by one person and clear (ie. Hunter is completing section 6, 7, 8 of the SRS)... also that's not in the rubric that's just advice remember when I mention the rubric I mean the one on avenue not the checklists, the checklists are good but sometimes I think they go a bit to far
-
It's probably fine that you haven't met with your supervisor yet since the project was your idea although Dr. Smith might just ask you about it in the demo so prepare to talk about it
-
starting up GitHub actions would be a good plan as soon as you have any code at all, however the plans you have in the docs should be fine
If you have any other questions @ me so I can see it, otherwise feel free to close the issue!
AhmedAl-Hayali
Inquiries follow from the PoC Checklist. Sections are bullet-points, checklist items have checkboxes next to them, and questions are enclosed in square brackets below checklist items.
Project Status/scope
[Is this necessary to have this early? Can't we make the PoC then decide who presents what? Also, 5-min demo w/ interruptions would be super chaotic to have 5 ppl presenting it, no?].
Issue Tracker
[We don't have sub-issues in GitHub projects, so this isn't too reasonable of an ask - we can make commits atomic, but issues being atomic would be gargantuan overhead].
[Supervisor meetings haven't been carried out yet because of wobbly scope, but multiple are planned for soon, is that fine?]
CI/CD
[What constitutes planning? We've got a pretty complete, almost-concrete idea in section 3.5 of the VnV plan, does that suffice, or should we start attaching GitHub Actions from now?]