| Expand |
|---|
|
A couple bullet points on the team’s general goals/focus points this week, and if there’s anything that is blocking your team. | Panel |
|---|
| panelIconId | 1fab4 |
|---|
| panelIcon | :potted_plant: |
|---|
| panelIconText | 🪴 |
|---|
| bgColor | #DEEBFF |
|---|
| Directors Re-examining comp timelines. Setting up our next set of comp operators. Re-aligning team direction
|
| Panel |
|---|
| panelIconId | 1f4f7 |
|---|
| panelIcon | :camera: |
|---|
| panelIconText | 📷 |
|---|
| bgColor | #EAE6FF |
|---|
| Autonomy |
| Panel |
|---|
| panelIconId | 1f39b |
|---|
| panelIcon | :control_knobs: |
|---|
| panelIconText | 🎛️ |
|---|
| bgColor | #FFEBE6 |
|---|
| EFS have meeting about zp telemetry manager → make tasks and assign follow-up with old drivers rangefinder altimeter sd card
buy imu breakout boards Fix tracking antenna issue and re-test
|
| Panel |
|---|
| panelIconId | 1f50c |
|---|
| panelIcon | :electric_plug: |
|---|
| panelIconText | 🔌 |
|---|
| bgColor | #FFFAE6 |
|---|
| EE order pre-crimped JST gh wires order wire strippers order solder paste order heat shrinks with glue bring-up more Lighting PCBs capacitor analysis
|
| Panel |
|---|
| panelIconId | 1f6e0 |
|---|
| panelIcon | :tools: |
|---|
| panelIconText | 🛠️ |
|---|
| bgColor | #E3FCEF |
|---|
| Mechanical |
| Panel |
|---|
| panelIconId | 1fa99 |
|---|
| panelIcon | :coin: |
|---|
| panelIconText | 🪙 |
|---|
| bgColor | #DEEBFF |
|---|
| Operations |
|
| Expand |
|---|
| title | Director nominations |
|---|
|
reach out to directors if confused director role! Megan Spee to go over this document and make it more clear https://uwarg-docs.atlassian.net/wiki/spaces/AD/pages/2307719388/Organization+Roles#Director Tech director noms - https://forms.office.com/r/ZBY30TeCw3 Exec director noms - https://forms.office.com/r/FY51bnHZsj |
| Expand |
|---|
| title | SDC Team Leads meeting |
|---|
|
| 2023-02-01 SDC Team Leads Meeting Megan Spee sending out email about EE crimps soon/tomorrow (shared in RPC) |
| Expand |
|---|
| title | Reading week / midterm week downtime? |
|---|
|
different dates for different programs subteam leads please check with your team members when your midterm week/ midterm dates are. currently week before and week after reading week are pretty light. will follow up with leads in #leads Megan Spee prefer not to run aeac/leads meetings generally optional around this time, and at leads discretion (including during reading week) |
|
| Expand |
|---|
| title | Flight Test Schedule re-examination |
|---|
| How is this working out for everyone? |
Are sub-team members actively coming to flight tests? Haven’t seen many members except for core / old members….. briefings pushed to 10 to lower barrier of entry for flight tests - this worked well encourage members to show up, you get to fly drones ideally help the subteam members prepare for flight test tasks, and get in touch with people to run FTs to better prepare them! → gets them more involved and they are less lost on the flight line |
| Expand |
|---|
| title | Competition pilot/gso + advanced operator |
|---|
|
Thinking we should lock-in people who can commit for critical roles. Have had volunteer from numerous people in varying ways - seems fair to open ground schooling to all members & then only sponsor a few tests?
criteria for comp pilots and GSO interested attending flight tests avail for comp
|
| Expand |
|---|
| title | Subteam socials & workshops |
|---|
| EE tried to do work session, not a lot of EE attendance onsite.
branch this out to other subteams+ general announcements! get more people (not just EEs) on board.
Prospective board building sesh upcoming
get core team avail by fri/sat, we announce it sunday, and other subteams can pull up if they’re interested
EFS socials- most leads are offsite
shoutout to mech for good work sessions!
not a lot of enthusiasm for attending socials on mech side. people are probably busy gggg
Amy onsite for autonomy
could do a software crossover social efs/auto pog
| Expand |
|---|
| title | Resume Review Session |
|---|
|
This Saturday at 5 PM in the bay Encourage your subteam members to attend! Leads are also invited to attend as reviewers
|
...
| Expand |
|---|
| title | WARG open source licencing and which parts of WARG is under this licence |
|---|
|
R D DRAFT Open Source Licencing How much of WARG’s information is open source? Background: Goal of open source licences in general: Preemptively give permission to the public to use, redistribute, and modify the publically accessible technical information. May come with restrictions: Acknowledgement, non commercial only, any incorporation of information must also be under the same licence, etc.
If the technical information is publically accessible but not under open source, it retains copyright by default (which means a 3rd party needs to request and receive written permission before copying/modifying the work). For example: WARG: Software: Open source under BSD-4 (decided in 2021) BSD-4 conditions: Acknowledgement in source, binary, documentation, advertizing, and marketing May not use the copyright holder’s name and contributors as endorsement or promotion, unless permission is given in writing
Hardware: Documentation: No licence Logs: No licence Discussion (e.g. Discord): No licence Marketing (e.g. social media, posters): No licence Other (am I missing anything)?
general slander/defamation potentially to use peoples' names. |
Daniel Puratich 's message about team improvement and making things better for everyone!\
2/8/2024: Reflections & Rambling
Daniels ramblings
Minimum requirement for an SDC team: compete at least once per year, have a safety captain, and follow all the SDC policies
Anthony Luo - anyone needing to do director syncs before comp swing?if you think your subteam/you need to talk about scope, integration, etc, let’s set up a call!