Skip to content

berserktech/2019-april-codeathon

 
 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

54 Commits
 
 
 
 
 
 
 
 

Repository files navigation

Code for Venezuela - April 2019 Codeathon

This repo contains all the information needed for both in-person and remote participation in the event.

Before the Event

TODO

During the Event

  1. Teams:
    1. Make sure to have a team.
    2. We want to bring together: developers, PMs, Data scientists, designers etc.
    3. A team could be made up of engineers only or a mix of cross-discipline teammates.
    4. We encourage freedom to innovate and be creative.
    5. Recommended team size: 3 to 5 people.
  2. Logistics: 6. Slack will be the main communication channel for the event. Please use #hackathon-ga to post questions and requests. 7. When there are talks or workshops, we will make sure we have a video stream available for remote participants.

Challenges

The focus of the event would be in the following areas:

  • Using data to analyze, understand and communicate the Venezuelan crisis.
  • Digital products and platforms to connect the diaspora with the country.
  1. In the challenges folder you will find a list of challenges proposed by our partner organizations. Please take time to review them before the event. The more prepared, the more chances your team will have of making good progress during the weekend!
  2. Each challenge will have a dedicated Slack channel where you could ask questions and get clarifications. The slack channel for a channel follows the following convention: chal-challenge_code. (e.g #chal-mpv-inf, #chal-mit-rea)

If you want to work on a challenge that is not by our partner organization, you are welcome to do so! Share you challenge in #hackathon-ga.

Demos and Presentations

  1. Each team will present a 3 minute demo on their work.

  2. You can record a video and we will present it on site as a part of the final presentations.

  3. Deadline: Sunday 14, 4:30pm Pacific Time)

  4. Software:

    1. We suggest using Loom to record the video of the demo: https://www.useloom.com
  5. Post your video to Slack

  6. We are inviting folks to watch live the feedback from our panelist. This will happen around 4:30PM PST, Sunday 14.

    If you can't join live, we will let you know via Slack on Monday 04/15 any feedback from our panelists.

  7. Continuity: 2. If your project has scope that goes beyond the weekend of the Hackathon, let us know if you would like to keep contributing.

Pro Tips

  1. We recommend you use Trello to organize your day.
  2. We suggest participants choose just one challenge to focus on and get it 100% done (hopefully!)
  3. Ask questions using the designated Slack channel for your challenge.
  4. Keep an eye out for our Zoom links that we will use to live-stream the event for participants.
  5. We will send you virtual food (🍌 🍉 🍇 🍓) but you will need something real. Make sure to have enough arepas or pizza! And have enough water too ☺

Remote participation

Join our event remotely! Do you have a team? A location? Let's do this!

We will set up a Slack channel to allow remote folks to participate in this event. If your location has a webcam we can discuss using Zoom to live-stream the event.

Mingle with other hackers in your city

The following cities are hosting remote locations for the Hackathon. Please check out their RSVP website and make sure you respond if you want to attend to the event there:

Remote Mentor

Guidelines During the Hackathon, there will be one of our team members (Juan Campa), monitoring all the slack channels for the remote locations. He will be answering questions and making sure your requests are funneled back to the team in SF.

Contact info

If you have any questions email us at contact at codeforvenezuela.org

Code of Conduct

All participants must adhere to the following Code of Conduct.

About

Code For Venezuela - April Codeathon

Resources

Code of conduct

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published