| | | |
---|
5 Mins | Introduction | @Pratyush Patra | WOOOO new cycle Overall super excited cause we get to build this thing from the ground up. With that comes the need to make sure we are very diligent and thoughtful about all decisions we make Pickle Update |
5 Mins | Main takeaways from 1 on 1s | @Pratyush Patra | Clickup needs to be properly maintained this time. Timelines and things like that can also go on clickup Push to do cross system reviewing. Sid brought this up but our best engineers shouldn’t only be reviewing their own systems. Need to think about how we can do this without just overloading people with reviews on top of dev work
|
15 Mins | System Architecture | Everyone | Priority is having this laid out before recruiting problems hit (End of Aug to Early September) Diagram of intersystem connections and ideally basic system level connections if that can be done in this time frame Does not need to be locked but want it generally laid out and maintained somewhere so that it can be referenced by Emech and other systems What is a reasonable date to have draft of system interfaces(what connections your system needs to have to other systems) done by? What about internal system diagram?
|
15 Mins | Embedded Sharepoint + SOM | Everyone | Schedule meetings and make sure all relevant parties are included. Announce these meetings in electrical so interested people can join Want to determine timeline for initial tasks/MVP Set milestones and define general expectations at those milestones Sharepoint can be laid out longer but ideally SOM timeline for development is accelerated Can be done offline from the meeting but need to identify starter projects for both Don’t expect a ton of actual work to be getting done these last couple weeks of summer Ishan (Not Platform Lead) and Lakshay (Not Platform Lead but still relevant) will help organize
|
15 Mins | Onboarding | Everyone | How do we want to approach onboarding? Emphasis on supported self-learning. Try and avoid full on lectures for a lot of things and rather provide them with resources they can look at to learn more on their own power. Philip discussed having a day where they sit in front of the car and just ask questions about what everything does and more of a team building and basic tool introductions first workday. I think we do one small guided tutorial for them to get accustomed to the tools like Kicad and then dive them into a very basic but still on car starter project. Need to make sure members are still getting help where they need here. They should try and figure out stuff on their own but some stuff they will inevitably need guidance on so need to support that with either a buddy or directly from leads. What lectures do we want to do if any? How should we organize the resource center? When do we plan to have our starter projects identified?
|
5 Mins | Conclusion | @Pratyush Patra | Start thinking about system requirements, recruiting, and onboarding for next week Please have a general number for how many people you plan to recruit/how many people you plan to have on your team and be able to justify those decisions based on workload Do a census of some starter projects available within your system for new members. Some will end being shared with SOM and sharepoint tasks. Need to discuss status of how we want to work on Daybreak at some point. I am of the opinion that we take a census of critical fixes that need to happen and rework those boards/software. All next-gen design should be completely with the intent of putting it in the next car imo. Schedule next E-Leads
|
Welcome to the University Wiki Service! Please use your IID (yourEID@eid.utexas.edu) when prompted for your email address during login or click here to enter your EID. If you are experiencing any issues loading content on pages, please try these steps to clear your browser cache.