Melrose iRaiders 2713Code of ConductOverview This is the iRaiders team 2713 Code of Conduct. It outlines acceptable social behaviors, general rules for the team, and the FIRST standards. They are guided by both tenant of FIRST Gracious Professionalism as well as the Melrose High School School Handbook.
General BehaviorWe attend meetings nearly everyday during the build season and disagreements are bound to arise, it’s important that we do not allow things to get out of hand. On this team you must treat your fellow teammates as friends. Team members should be on their very best behavior at all times, especially at competitions. Your actions will affect how others see you and the iRaiders as a whole.EmailsEmails from a student to an adult should always include at least one other adult mentor or the Mentors Mailing list in “cc:”.
Code of Behavior and ConsequencesThe iRaiders code of behaviors is a more detailed definition of expected behaviors that can be found in the Melrose High School Student Handbook. As such all students are expected to have read and adhere to all rules in the Melrose High School Student Handbook. Any team expulsion must be determined by a mentor meeting.
Consequences BehaviorMinimumMaximum Verbal (Repeated name calling, Making fun of others, Mocking)Mentor WarningParental Notification,Written Apology, Three Meeting suspension
Severe Verbal (Spreading rumors, Excluding others, Written harassment, Threats)Written apology and note home Team suspension and or police/school involvement Physical (Pushing, Pinching, Poking, Stealing)Documented WarningParental Notification,Written Apology,Possible Team Expulsion (following mentor meeting) Severe Physical (Violent Punching, Kicking, Hitting)Two Meeting SuspensionExpulsion from team, School / Police involvement. Responsibility of observersAttempt to calm down both parties and find a team captain or adult if necessary. Allowing or encouraging the situation to escalate without even trying to stop it will not be tolerated. If you can’t or don’t want to inform a mentor yourself, ask someone else.AttendanceYou must make a genuine effort to attend as many meetings and competitions as you can. If you know you will be absent you should inform a captain at your earliest opportunity, and prepare accordingly. You must attend 80% of the build season during the two weeks before a competition in order to attend with the team (you may still attend by arranging your own ride, food, etc.). Absences may be excused due to prior obligations, illness, etc. and will be contemplated on a case by case basis. Members on the Robot Drive team need to have a 90% attendance during the build season in order to still be on the drive team.Device EtiquetteWe don’t want to take your devices or put firm rules about usage in place. However, use common sense. Don’t use them when you should be doing something else, don’t be rude while using them, and don’t use anybody else's device without permission. Devices should only be used for iRaiders tasks, so no goofing off when there is work to be done. Would your grandmother approve? If not, don’t do it. The Focus of team meetings is the robot/program, not your phone/other device or gameplay/other projects.Mentors/Leaders/ChaperonesCompetitions and meetings will always be attended by at least 2 mentors, and at least one mentor per occupied room. If there isn’t sufficient availability, the event may be canceled. All mentors and adult chaperones will be cleared through the school’s CORI/Volunteer registration program.Management of Behavioral IssuesMentors will collect all facts relative to the behavior and discuss amongst the mentors on duty. Mentors will then gather all parties involved in the behavior to openly discuss the situation. The situation will be reviewed objectively and fairly against the consequences issued.MAIN POINTSRespect the team, respect the robot, respect each other.