Community Guidelines

All events/workshops/hackathons/meet-ups organized by OrangeHacks follows the Code of Conduct of GitHub and MLH.

TL;DR - Be respectful, harassment and abuse are never tolerated. If you are in a situation that makes you uncomfortable in OrangeHacks space, if the space is itself creating an unsafe or inappropriate environment, or if interacting with any of OrangeHacks representative or organizers make you uncomfortable, please report it using the procedures included in the document.

OrangeHacks (Oh!) is a diversified and inclusive community where we believe every single person has the right to participate in a safe and welcoming environment.

Harassment includes but is not limited to offensive verbal or written comments related to gender, age, sexual orientation, physical appearance, body size, race, religion, social class, economic status, and veteran status. Additional cases of harassment include but are not limited to sharing sexual images, deliberate intimidation, stalking, following, brigading, doxing, harassing photography or recording, sustained disruption of talks or other events, inappropriate physical contact, and unwelcoming sexual attention. If you’re making someone feel uncomfortable, that comes as harassment and is enough reason to stop doing it.

Community members, OrangeHacks representatives, and organizers asked to stop any harassing behavior are expected to comply immediately.

Sponsors, speakers, mentors, judges, volunteers, representatives, organizers, and anyone else participating in the event are also subject to the anti-harassment policy. In particular, attendees should not use sexualized images, activities, or other material both in their projects and during the event. Volunteers, representatives, and organizers should not use sexualized clothing/uniforms/costumes or otherwise create a sexualized environment.

If a participant engages in harassing behavior, OrangeHacks may take action it deems appropriate, including warning the offender or expulsion 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 OrangeHacks using the appropriate procedures defined underneath.

OrangeHacks representatives can help attendees contact campus security or local law enforcement, provide escort, or otherwise assist those experiencing harassment to feel safe for the duration of the event. We value your attendance.

We expect attendees to follow these rules at all event venues, online interaction in relation to the event, social events, hackathons, meet-ups, and on OrangeHacks-supplied transportation.

Reporting Procedures:

If you feel uncomfortable or think there may be a potential violation of the code of conduct, please report 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 of the OrangeHacks representatives listed below.

General Reporting Line:

Special Incidents:

If you are uncomfortable reporting your situation to one or more of these people or need to contact any of them directly in case of emergency, direct contact details are listed below.

Laksh Samdariya:

OrangeHacks reserves 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 OrangeHacks by email at

Blogs Guidelines

In this document, OrangeHacks is referred to as “OrangeHacks”. OrangeHacks believes in expanding the community and providing a chance to everyone to share something new that others didn’t know.

Here are the instructions and guidelines to be followed by the participants/ applicants willing to post blogs through GDSC GHRCE publication on Medium.

General Rules

The blogs are distinguished into two categories.

  • Technical Blogs
    • Theoretical Information
    • Practical Tutorials
    • Comparison of Technologies
    • Review of new technologies
    • Personal work with a particular technology
    • Any other format of blog writing in the realms of technology
  • Non-Technical Blogs
    • Soft Skills
    • Professional Experience (Interviews/ Startup/ Industry Experience)
    • Guidance and Motivation

Submission Instructions

  • The blog needs to be grammatical error free. Use Grammarly to ensure there aren’t any prominent errors.
  • Use markdown language to insert links, photos and to make any formatting - Markdown Language Cheat Sheet
  • Make sure your blog’s cover photo (header) contains the title of your blog, your name, and an illustration (design on your own)
  • This is a community initiative. No personal branding or promotion of any product is acceptable


  • OrangeHacks shall deal strictly with plagiarism.
  • Note: OrangeHacks accepts blogs with less than 15% plagiarism.
  • In case plagiarism is detected, applicants shall be asked to rephrase the blog.
  • In case of quoting/taking references from some resources, mention proper credits and provide the reference links.


  • OrangeHacks reserves the right to Accept or Reject the blog submitted by the applicant.
  • Reasons for rejection may be stated to the applicant upon the applicant’s request to state the same.
  • The applicant would receive an email from OrangeHacks on publishing a blog.
  • Feel free to reachout to us at


  • OrangeHacks has the right to amend “OrangeHacks blog Guidelines”.
  • A rule can be added/ removed/ amended without prior notice if more than fifty percent of the core team members vote in favor of the motion.
  • Each applicant wanting to publish their blog at OrangeHacks shall follow these guidelines ​formulated by OrangeHacks at all times.