Meeting Duration: 11:50am - 12:20pm Participants: Everyone, Joe. Meeting brought up from talking with Edgar & Andy, this meeting is about the possibility of coproduction. ## Production Alignment, Expecations >[!question] Are you okay with coproducing? >>[!info] Edgar (Response Paraphrased) >>We talked about it at the beginning of the semester and I did not want to do it. I am okay with trying it now but I want it to be clear what the tasks are concretely. > >>[!info] Andy >>I did not define any of the concrete tasks at the beginning but I am willing to do so for coproduction. These next few weeks can serve as a test to see whether or not we should bring this into spring or not. >[!question]- Who else thinks they have a nack for being a producer? >*The only one raising their hand was Emi*. They recommended 'backups' to spread out the work being this is a 20 people team, in the real world we would never put 20 people on a prototype. >[!info] Brendan hates Andy, thinks they are soft on people. Joe wants us to revisit our team pledges, we did not do a cohesive team pledge. This pledge should be clear expecations from everyone so we all know where anyone else stands on things. (Joe) Bare Minimum: Should be here at lab when it starts, be when it ends, breaks are ok "breaks are awesome." Not just to interface with instructors or TA's but for interfacing with the team. The pledge should establish expectations about deadlines, what to do when block, who to go to when block, etc. They are not saying spend an hour on this, this should be short. >[!info] Andres (Paraphrased for my Carpal Tunnel): >For weekly builds, one thing I see is a lot of time is put in is not reflective in what is shown off, which I know is not intentional but I want everyone's work to be apparent. It is a prototype, it doesn't need to be polished, being there is better than nothing. (Joe) It is much preferrable to a janky collection of features than something that isn't there. "You guys don't know what you don't know, so we want you guys to test stuff so you can feel, if you find significant friction in a pipeline, lets talk" Andres makes weekly builds, these are meant to be played and tested by people. This is a note for everyone, you should verify what you did is in the build. Recommended scheduling looking at the build with someone, encourging people to bring in content. Maya Shoutout, but "too much detail for a prototype." You should have something in the engine with primitatives or whatnot that showcases what that area should feel like. Doing high fidelity work for a prototype is not sustainable. Every artist should have a seperate eyes both for the quality but also making sure you aren't putting in too much. What we need for the prototype is *proxies* / shapes. You don't need textures for the prototype, you just need a couple for the corner. >[!warn] We are firing Brendan >[!question] Feedback for designers? >(Joe) "We have been talking about definitivly seeing music and seeing mechanics for that. As long as it shows up in the M3 submission that would be good." Closing Notes: "ok joe"