Skip to content

Latest commit

 

History

History
234 lines (200 loc) · 15.9 KB

Bylaws.md

File metadata and controls

234 lines (200 loc) · 15.9 KB

Bylaws

Bylaw #1

Each lead must maintain a task list. This should be readily available. The purpose is to instruct whosoever is at any given meeting while the leads are not there in how to proceed with the jobs they need to do, and to document exactly what has been done for future reference.

This document will be posted where any may see it so that it can be used at any time.

Bylaw #2

There will be a folder, accessible to all, in which important documents will be placed pertaining to this club.

  • This file will contain all important documents to each division of the club, including the constitution, design plans, any scripts, and other such documents.
  • This will be kept accessible to all.
  • It will be the responsibility of the leads of each division to make sure a copy of all the important documents pertaining to that division is accessible within the file.
  • It will be the responsibility of the leads to make sure a copy of all the important documents pertaining to the government of the club is accessible within the file.
  • The leads of each division will determine which documents are important.
  • A mentor may overrule a lead by placing or removing any document they deem necessary.
  • This will be a hardcopy paper file or an electronic file.

Bylaw #3

This Bylaw establishes the chain of club command. In the event that a captain is needed, this is the order.

  • Team Captain
  • Communications Lead
  • Project Manager
  • Business Lead
  • Strategy Lead
  • Build Lead
  • Software Lead
  • CAD Lead

Bylaw #4

The following leads are responsible for maintaining the following roles.

  • Team Captain
    • Lead Meetings
    • Lead Team and People Management
    • Managing the constitution
    • Ensure that the club is ASR compliant
    • Maintain team roster (personal info, status on things, anonymous demographics)
    • Paperwork, forms etc...
    • Post agendas for meeting/announce about meetings
    • Contacting people on an individual level
    • Communication with other teams → 17-18 leads can decide this
    • Recruit new members
    • Ensure diversity and inclusion
    • Mentor Recruitment
    • RHS event coordination
    • Help PM make a timeline for the year and finalize that timeline
    • Encourage team spirit (make sure we have things like t-shirts, hats, a flag, cheers, a mascot, and other swag and that people are being spirited)
    • Encourage gracious professionalism and coopertition
    • Encourage STEM
    • Appoint executive assistants to aid them and the communications lead (ex: food/transport, outreach, paperwork, social media)
    • Jointly appoints a separate outreach coordinator with the Communications Lead
    • Required to create meeting agendas 24 hours in advance of meeting
    • In charge of psychological safety (by working with the other team leaders, mentors, and members)
  • Project Manager
    • PMs main responsibility is managing the construction of the robot during build season by keeping track of the tasks and timelines and preparing for it ahead of time. They communicate directly with the engineering leads (aka the people managers) not with the individual members of their departments. Off season, the PM becomes a “consultant” who is only responsible for managing a project if requested by another lead/people manager.
    • PM is held responsible for using some type of PM system that is accessible to the entire team digitally all the time and displayed if needed during work meetings. Project manager would be responsible for helping the department leads set up ad hoc groups (not assigning people to them or helping them, but keeping track of the progress of those working groups and helping department leads know what pieces of a project should be broken into ad hoc groups) → PM holds accountable the working groups/ad hoc groups for delivering their projects (ie interdepartmental groups working on pieces of a project). Additionally they would be responsible for advising working groups (working on projects nobody has asked the PM to manage themselves) on how to PM their project.
    • Manages daily list of tasks for projects assigned to them (displays and allows sign-ups)
    • Must hold status updates at a minimum 1 per week during a project managed by them
  • Communications Lead
    • Stand in for/help out Team Captain when needed
    • Communication with our team
    • Send/Post announcements (big announcements and updates)
    • Outreach (coordinating with other teams and with our team)
    • Mentor Communication
    • Roosevelt community communications
    • Alumni relations
    • Parental contact
    • Booster club contact
    • Food/Transportation
    • Regular all-team updates (ex: Iron Update)
    • Communications
    • Help lead team
    • Help lead meetings
    • Documentation
    • Update website
    • Leads Meetings Minutes
    • Other Meeting Minutes When Necessary
    • Chairman's Award
    • Jointly appoints a separate outreach coordinator with the Team Captain
    • In charge of social media
  • Business Manager
    • Grant writing
    • Treasurer
    • Fundraising
    • Getting and maintaining sponsorships
    • Maintaining fiscal workflows (Purchase approvals and reimbursements)
    • Training members on workflows
    • Keep track of cost for part sourcing
    • Marketing/Advertising (posters, social media presence etc.)
    • Branding (team swag, graphic design etc.)
    • Taking photos and video
    • In charge of keeping track of which sponsors are on the aesthetics board and making sure that it gets done by hardware and design
  • Strategy Lead
    • Must research and/or be knowledgeable in the areas of Strategic Design, Scouting, Match Strategies, and Robot Control & Operation, or similar
    • Lead the Strategy Department by teaching the curriculum, working to recruit and retain members, and attending leads meetings,
    • Organise and lead the team in through the Game Analysis phase of Strategic Design on Kickoff
    • Must lead the team through the Cost-Benefit Analysis phase of Strategic Design
    • Must compile the ultimate goal for the season, general game strategy and robot priorities into a draft of the Design Platform with help from the Strategy Department and Design Leads.
    • Responsible for editing and presenting the Design Platform to the Design Leads for review, which will be frozen upon the signature of both leads.
    • The Strategy Lead or a delegate form the Strategy Department will advise the Design Leads and Department during the Functional Design Process and transition to Mechanical Design
    • Strategy Lead must become an expert on the rules and ensure that the team is on the same page with the rules starting on kickoff and throughout the season.
    • Must determine the order of priority for the construction of the Field Elements and ensure Field/ Field Element construction is built to Feild Drawing specifications
    • Strategy Lead must manage Q&A in regards to the rules
    • Must give Weekly updates on the rules
    • Strategy Lead must facilitate the creation and training of Drive Team working to recruit and retain members, and hold practices, and select the final Competition Drive Team.
    • Must appoint or act as and train a Drive Coach, Head Strategist, and Match Strategist (or equivalent positions determined by the Veteran Strategy Department Members). However, the Strategy Lead may not act as either of the latter two in addition to the former most.
    • Strategy Lead and/or Department will meet with the Software Lead and members of the Software department to determine Auto Strategy for the season.
    • Responsible for ensuring pre-scouting reports are created and shared as per the scouting guidelines determined by the Veteran Strategy Department Members
    • Must appoint a Head Pit Scout and Head Match Scout
    • Strategy Lead is responsible for the Strategy sub leads executing appropriate strategic procedures at competitions, including but limited to, scouting, match strategizing, briefing drive team, coordinating with alliance members, post-match analysis, etc.
    • Strategy Lead manages and/or advises the creation of the Reveal Video or any other public reveal and decides what information to and not to reveal interest of long term strategies.
  • Build Lead
    • Manage robot construction based off of the robot design
    • Make/Teach hardware curriculum
    • RP lab inventory
    • Pit inventory
    • Part Sourcing
    • Keep RP lab clean
    • Appoint pit boss
    • Make field elements
    • Pit building
    • Electronics/Wiring
    • Pneumatics
    • Motors
    • Mechanical fabrication
    • Manag robot transport
    • Make bumpers
    • Makes Aesthetics board
    • Combined hardware and design to form Engineering
    • Rename hardware lead to Build Lead
    • Have co-managers (design and hardware leads) lead the engineering department
    • Jointly responsible with design specialist for creating a fall curriculum
    • Have a Quartermaster responsible for managing supplies in RP lab (this would be an appointed position by the build specialist)
    • Appoint safety lead
  • Software lead
    • Manage development and testing of software components of robot control systems
    • Work with Software Members, Strategy Lead, and Strategy members to develop an auto Strategy for the season.
    • Lead the software department by teaching curriculum, working to recruit and retain members, attending leads meetings, Organize
    • Help Drivers understand and use robot control software.
    • As an owner of the Iron Riders github, take responsibility for the upkeep of repositories and teams.
    • Ensure software on the development computers and robot components it up to date.
    • Troubleshoot connection issues with the robot
    • Keep inventory of software resources such as laptops, joysticks, and sensors
    • Maintain and contribute to the documentation and history, stored on the website and github.
    • Coordinate development and use of software solutions for competition scouting, such as apps and/or other types of computerized data analysis
    • Work with communications lead to maintain functionality of the website, as opposed to content management.
    • Work with Strategy to win the Innovation In Control Systems Award
  • CAD Lead
    • Develop CAD/Design curriculum
    • Teach curriculum
    • Work with Strategy Department to draft the Design Platform
    • Review Design Platform presented by Strategy Lead, propose changes in needed, and freeze by signing.
    • Provide hardware with list of specific parts used in the design
    • Design robot (with bumpers included) working hand-in-hand with strategy
    • Ensure the other departments have access to the design of the robot
    • CAD robot
    • Ensure robot is built to game manual specifications
    • Designs Aesthetics Board
    • Combined hardware and design to form Engineering
    • Rename Design Lead to Design Specialist
    • Have co-managers (design and hardware specialists) lead the engineering department
    • Jointly responsible with hardware specialist for creating a fall curriculum

Bylaw #5

Section 1

With the passage of this bylaw FIRST WA Team FRC 4180, The Iron Riders, formally:

  • Recognise and acknowledge that we meet and operate on the traditional land of the first people of Seattle, the Duwamish People past and present, and honor with gratitude the land itself and the Duwamish Tribe.

  • Recognise and acknowledge Systemic Racism/Sexism/Discrimination is real and exists.

    • In the context of this bylaw, Discrimination (capital D) will be used as an umbrella term that includes but is not limited to discrimination based on gender indentity, disability, department, speech/accent, etc.
  • Recognise and acknowledge Systemic Racism/Sexism/Discrimination on basis of identity/Discrimination on Basis of Disability extends to and effects Roosevelt High School as an institution, it’s community, the neighborhoods it’s students and staff come from, Seattle, and the USA as a whole.

  • Recognise and acknowledges that as a consequence of the above Systemic Racism/Sexism/Bias extends to Education (including but not limited to Science Technology Engineering and Mathematics (STEM) Education), STEM Programs including but limited to FIRST, and to this team FIRST WA Team Iron Riders, FRC 4180.

  • Recognise and acknowledge that Systemic Racism/Sexism/Discrimination can take place through both macro and micro aggressions, through both visible and invisible inequities and are very damaging.

  • Recognise and acknowledges that multiple alumni and members experienced Racism,Sexism, and/or Discrimination while on Iron Riders.

  • Recognise, even publicly, that the Iron Riders need to do everything within their power to address and eliminate Racism, Sexism, and Discriminition within the team and community and replace it with Equity, Diversity, and Inclusion.

Section 2

This bylaw will require the team and it’s leadership to comply with the following:

  • Require Student Leaders and the Team’s Mentors/Coaches to through and discuss Equity Diversity and Inclusion Training modules. This must be completed before build season starts at the latest. (It should be noted and recommended that doing this before starting the school year will have the most beneficial effect.)

    • Specifically Require the following modules or equivalent training determined by Mentors/Coaches
      • Strategies for Inspiring Success Modules 1-3
        • Module 1: Invisible Equities
        • Module 2: Hidden Messages
        • Module 3: Inspiring Success Link to modules
    • Specifically recommend, but do not require, the following modules
      • Inspiring Youth Voices Modules 1 - 3
    • Generally encourages leads and mentors/coaches to explore the following resources from FIRST or take the following actions
    • Exploring FIRST Resources on Gender Equity, Disability Inclusion, and more here
      • Maintaining Gold Tier Partnership with LGBTQ+ of FIRST
      • Becoming a #FIRSTLikeAGirl Ambassador
      • Consider a recruitment strategy that targets underrepresented groups in STEM, for example a recruitment strategy that targets girls by reaching out to them at the middle school level, similar to FRC 1710’s You Go Girl Initiative
  • Members cannot be prevented from participation on this team solely because of a failure to meet a fundraising goal.

  • Requires Leadership Team to discuss and implement specific recruitment and retainment strategies to ensure that the team recruits and retains underrepresented groups in STEM, including BIPoCs and Non-Male students.

  • Requires Student Leadership to record demographic information on team members when the sign up.

  • Requires department leads to keep attendance data, collecting attendance at least every month.

  • Requires Student Leadership to track students who drop out during the school year, and once a month have an agenda item to discuss reasons for drop out and/or reasons why members have been retained.

  • Requires Iron Riders Leadership to maintain a Black Lives Matter (BLM) statement on the Iron Riders website.

  • Requires that feminine hygiene products be made accessible in the pit during meetings and at competitions.

  • Requires the Iron Riders to be able to accommodate all students equitably to the best of their abilities.

Section 3

This Bylaw shall be voted on by the rules stated in Article 10 Amendment 1 of the Iron Riders Constitution and will be passed by a simple majority open ballot. It will be ratified by approval of a Coach. Quorum for second was set at 7, 7 votes were cast, bylaw passed 7 yes, 0 no, 0 abstain.

Bylaw #6

A member can nominate another member for an appointed position and the lead/leads that appoint that position will take that nomination into consideration.

Bylaw #7

Absentee voting is allowed. However some extra rules apply, namely:

  1. One must contact a coach with the intent to absent-vote at least 48 hours before the vote commences.
  2. One must vote prior to the physical election