The full schedule is available
|
| ||||||||||||||||||||||||||||
- Things to do before the hackathon
-
Check the preparation & installation document note for things to do before the hackathon.
- I would like to participate in an existing idea
-
Participants and coaches can comment and add information as comments in the ideas (as issue comments). After the pitches, there is time for team formation. Find the person behind the idea (feel free to slack them) and ask for more. Once you are convinced, add a comment in the issue mentioning
@qcamp(our helpful bot). After some seconds, you will be assigned to the issue. Being assigned to the issue means being part of the team. - I am already in a team, but I want to change
-
If a participant is assigned to team and she changes her mind, she has to unassigned herself from the current team and post a comment mentioning
@qcampin the new team. A participant cannot be assigned to more than one open team at any time. - None of the existing ideas is suitable for me :(
-
If any of the proposed ideas is suitable for you, considering submitting your own idea. Maybe, you feel that the full thing is over your head, considering joining the Good First Issues team
⚠️ (link). You want be participating of the competition, but you will contribute and learn a lot! - My team is not reaching the minimum amount of members
-
If during the team formation stage your team is not gaining traction (has two or less members) it will be considered a candidate to be closed. It will be labeled as such and that will serve as some sort of "last call" to encourage its members to find more participants interested in the idea. After some undefined amount of time, it will be closed and its members are free to find new teams.
- My team is complete
-
Once a team reaches 5 members, the issue is labeled as
group is full. Since 5 is a hard limit, the team cannot have more members. If you see that there is more people interested, consider opening a new team as a spin off and forward the participants to this new issue. - My team is ready. Let's hack!
-
After the project is defined and the team is complete, you can ask an IBMer in the channel
#qiskit-camp-africa⚠️ (slack channel) (qiskit.slack.com) to add the labelgroup ready. This should happen before the group formation stage is finished. From this point on, you can use the issue to communicate progress as additional comments. - The team needs a coach
-
A Qiskit coach guides and advises the team in its project. A Qiskit coach will also be your contact point after the hackathon, in case the project continues. Your team will get a coach assigned during the first hours of the hackathon on the first day. A team might have more than one coach, but at least one coach.
- Originality and Uniqueness
- Live Pitch Presentation
- Usefulness
- Technical complexity.
<dt name="collect">I have an idea for the hackathon</dt>
<dd>
Open an issue in this repo (using the new project
All the proposed projects should make use of some part of Qiskit (including the backends). They can also extend Qiskit or analyze it in some way. Take a look to projects from previous camps/hackathons for inspiration.
Before the hackathon starts, the first thing to be done on the first day is to pitch all the ideas registered here
After the hackathon finishes, the team will have extra time (around 1 hour) to prepare for a 3-minute-long presentation. This article has good advice that coaches and judges have been collecting during the past camp editions. Make sure you are following those guidelines!
After the presentations, the 3 judges will have an hour for deliberating the hackathon winners. There is a 1st and a 2nd prize winners, which will be evaluated on:
The 1st place winners will receive a paid trip to the annual flagship Qiskit Camp event near Yorktown Heights, NY
Also during this time all the participant will vote for the community choice award. Instructions on how to vote will be provided after the presentations.