2024-02-12 Leads meeting

A couple bullet points on the team’s general goals/focus points this week, and if there’s anything that is blocking your team.

@Georgia Westerlund

• Please fill out ASAP: Winter 2024 EngSoc Sponsorship Proposal Wishlist Items Mech + EE

reach out to directors if confused

director role! @Megan Spee to go over this document and make it more clear Organization Roles | Director

Tech director noms - Microsoft Forms

• nominate anyone, Willing to do on-boarding in the fall term.

• Closes feb 19th

Exec director noms - Microsoft Forms

• @Megan Spee looking to bring someone else up as an exec dir over summer/fall.

  • plan to bring-up in person / online over fall / summer.

  • nominate anyone! yourself! your friends! pikachu! etc.

  •  

• Not running sync meetings for aeac

• Leads probably cancelled as well. will ping if something is to be discussed

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

• 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?

  • people who go to flight test

    • open ground school to everyone? - @Anthony Luo

    • from there can choose to sponsor 2 tests for people who can go to comp. @Yuchen Lin ! :D

    • lock in around reading week?

      • ideally get a lot of time operating the drone

      • @Megan Spee @Anthony Luo to work on handoff of RC setup and integ specifically for piloting

criteria for comp pilots and GSO

1. interested

2. attending flight tests

3. avail for comp

• PLEASE TT

• plan maybe after midterms ~

@R D (Deactivated) Redistribution Policy

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:

• Datasheet for part

• User manual for product

• Documentation for API usage

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:

  • Schematics(?) are on GitHub:

    • EE leads: @Nolan Haines @Nolan Haines @Jerry Tian @Mena Azab (Deactivated) @Neel Patel @Neel Patel

    • Directors: @Megan Spee

  • CAD is not publically available: No licence by default

• 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.