BisonHacks Code of Conduct

Be respectful.


Harassment and abuse are never tolerated. If you are in a situation that makes you uncomfortable at BisonHacks 2024, if the event itself is creating an unsafe or inappropriate environment, or if interacting with a BisonHacks committee member or event organizer makes you uncomfortable, please report it using the procedures included in this document.

Howard University stands for inclusivity. We believe that every person has the right to hack in a safe and welcoming environment.

Harassment includes, but is not limited to, offensive verbal or written comments related to gender, age, sexual orientation, disability, physical appearance, body size, race, religion, social class, economic status, veteran status, sexual images, deliberate intimidation, stalking, following, harassing photography or recording, sustained disruption of talks or other events, inappropriate physical contact, and unwelcome sexual attention. If what you are doing makes someone feel uncomfortable, that counts as harassment and is sufficient reason to stop doing it.

Participants asked to stop any harassing behavior are expected to comply immediately.

Sponsors, judges, mentors, volunteers, organizers, BisonHacks committee members, and anyone else at the event are also subject to this anti-harassment policy. In particular, attendees should not use sexualized images, activities, or other materials in their hacks or during the event. Booth staff (including volunteers) should not wear sexualized clothing, uniforms, or costumes, or otherwise create a sexualized environment.

If a participant engages in harassing behavior, BisonHacks committee members and organizers may take any action they deem appropriate, including warning the offender or expelling them from the event with no eligibility for reimbursement or refund of any type.

If you are being harassed, notice that someone else is being harassed, or have any other concerns, please contact BisonHacks committee members or Mrs. Salas-Burnett using the reporting procedures defined below.

BisonHacks committee members will be happy to help participants contact campus security or local law enforcement, provide escorts, or otherwise assist those experiencing harassment in feeling safe for the duration of the event. We value your attendance.

We expect participants to follow these rules at all hackathon venues, in online interactions related to the event, during hackathon-related social events, and on hackathon-supplied transportation.

Reporting Procedures
If you feel uncomfortable or think there may be a potential violation of the code of conduct, please report it immediately using one of the following methods. All reporters have the right to remain anonymous. By sending information to the general reporting line, your report will go to any or all of the BisonHacks committee members and event organizers listed below:

BisonHacks committee members reserve the right to revise, make exceptions to, or otherwise amend these policies in whole or in part. If you have any questions regarding these policies, please contact BisonHacks committee members via email at [email protected].

 

Team Rules

  • Minimum team of 3, maximum team of 5.
  • Teams are encouraged to have a mix of business, engineering, and design-oriented students. Diversity is encouraged.
  • 3 min presentation is required during judging, explaining and demonstrating the team’s application. In addition, 1 minute will be allowed for questionsOne members of the team will be allowed to present.
  • Teams can be determined before or during the hack.
  • All team members must be present at opening and closing ceremonies. Virtual or remote team members are not permitted. 
  • Teams are required to choose a name.
  • Have fun and learn something new!

Project Rules

  1. Team projects can be brainstormed beforehand, but code MUST be written at the event only. Code cannot be brought in from outside the event. Cheating of any kind will not be tolerated. The project must contain a README within the repository that describes the project.
  2. 3 min presentation is required during judging, explaining and demonstrating the team’s application. In addition, 1 minute will be allowed for questions.
  3. All projects must be submitted to our Bison Hacks DevPost (include website) by February 23, 2025 at 1:00 PM.

  Projects must not contain any advertisement or solicitation. Projects must not contain anything that is or may be construed as:

  • Threatening, harassing, degrading or hateful.
  • Defamatory
  • Fraudulent or tortious
  • Obscene, indecent or otherwise objectionable; or (v) protected by copyright, trademark or another proprietary right without the express prior consent of the owner of such right;

Projects must not contain any material that would give rise to criminal or civil liability or that encourages conduct that constitutes a criminal offense, and Projects must otherwise comply in all respects with these Rules and the Policies.  

The "Judging Criteria" for this challenge is as follows:

  • Impact: How well does this solution address this challenge or problem?
  • Innovation & Creativity: Does it bring new ideas and approaches to solving the problem?
  • Completeness of Solution: Does it work? If not, is there a roadmap for future enhancements?
  • Sustainability: Is the solution sustainable within the context of the community it's aiming to impact?
  • Design: Is the solution well thought out and designed?