All participants of GDG Addis events must abide by the following policy:

  1. Be excellent to each other

We want the event to be an excellent experience for everyone regardless of gender identity and expression, sexual orientation, disabilities, neurodiversity, physical appearance, body size, ethnicity, nationality, race, age, religion, or other protected category. Treat everyone with respect. Participate while acknowledging that everyone deserves to be here -- and each of us has the right to enjoy our experience without fear of harassment, discrimination, or condescension, whether blatant or via micro-aggressions. Jokes shouldn’t demean others. Consider what you are saying and how it would feel if it were said to or about you.

 2. Speak up if you see or hear something.

Harassment is not tolerated, and you are empowered to politely engage when you or others are disrespected. The person making you feel uncomfortable may not be aware of what they are doing, and politely bringing their behavior to their attention is encouraged. If a participant engages in harassing or uncomfortable behavior, the event organizers may take any action they deem appropriate, including warning or expelling the offender from the event with no refund. If you are being harassed or feel uncomfortable, notice that someone else is being harassed, or have any other concerns, please contact a member of the event staff immediately.

 3. Practice saying "Yes and" to each other.

It’s a theatre to improve techniques to build on each other’s ideas. We all benefit when we create together.

Community guidelines

Be nice. We're all part of the same community, so be friendly, welcoming, and generally a nice person. Be someone that other people want to be around.

Be respectful and constructive. Remember to be respectful and constructive with your communication with fellow members. Don't get into flame wars, make personal attacks, vent, or rant unconstructively. Everyone should take responsibility for the community and take the initiative to diffuse tension and stop a negative thread as early as possible.

Be collaborative. Work together! We can learn a lot from each other. Share knowledge, and help each other out.

Participate. Join in on discussions, show up for in-person meetings regularly, offer feedback, and help implement that feedback.

Step down considerately. If you have some form of responsibility in your community, be aware of your own constraints. If you know that a new job or personal situation will limit your time, find someone who can take over for you and transfer the relevant information (contacts, passwords, etc.) for a smooth transition.

Basic etiquette for online discussions. Don’t send messages to a big list that only need to go to one person. Keep off-topic conversations to a minimum. Don’t be spammy by advertising or promoting personal projects which are off-topic.




  • Anyone living in Ethiopia.
  • Anyone who is interested in computer programming and loves to learn and build cool stuff can attend.
  • Your age must be between 18 to 25.
  • You need to be willing to attend the hackathon for 48 hours.
  • The basics of programming is enough for anyone to be considered.
  • Make sure that this is a team's event.
    • The whole point of forming teams and working on a project gives you the opportunity to work in a real-life setting. I mean seriously, that’s how it works in the industry. You have to learn to work with people from different backgrounds, different skill sets, etc. What better way than a hackathon to get used to it? Teams include a maximum of 5 people. Our hackathons have “Meet-and-Greet” events before the actual event where you get to talk to attendees and look for teammates.


Submission project requirements 


Your solution is regardless of platforms (Website, Mobile Application, etc) as the focus is on the solution itself. However, follow the criteria in the "Judging Criteria" section: 

Don't forget to:

  • Name your group
  • The demo is working properly 
  • Stick to your time (- minutes)
  • Ask questions if you have any concerns or questions left to one of the organizers


Judging criteria 
  • Feasibility
    How the proposed system is feasible in terms of cost and operation.
  • Functional Requirement
    How much the system addressed the required problem.
  • Technical Methodology
    How the proposed system is built and the methodology they followed
  • Team Work
    How much the team collaborated throughout the stay, by defining roles to the team members.
  • Applied Technology
    The technology they have applied and range of technology usage
  • UI/UX
    The User Interface and The User Experience they have applied in the system
  • Localization and Usability
    How the system is built in consideration of local user and people with disability
  • Version Control
    How far the team applied version control mechanism (using either GitHub, GitLab and so on).
  • *Note on Version Control
    This criteria of Version Control has a small scoring point but helps the teams to exercise the version control methodology which is currently essential in every software development process especially for team collaboration.