Hackathon timetable
The full schedule is available here.
Before starting
- Things to do before the hackathon
-
Check the [preparation & installation document](preparation%26installation.md) note for things to do before the hackathon.
- Sign up on related services
-
Qiskit hackathons make heavy use of two external services, and it's expected you have a user available in both of them:
- [Qiskit Slack](https://qiskit.slack.com): Our main way of communication is on Slack. You can join the workspace
[by clicking here](https://join.slack.com/t/qiskit/shared_invite/enQtODQ2NTIyOTgwMTQ3LTI0NzM2NzkzZjJhNDgzZjY5MTQzNDY3MGNiZGQzNTNkZTE4Nzg1MjMwMmFjY2UwZTgyNDlmYWQwYmZjMjE1ZTM). After that, join the `#qiskit-camp-africa` channel where you will find all your co-participants, coaches, and organizers.
- [GitHub](https://github.com/): Ideas collection and team formation and tracking happens on GitHub. It's important you have a registered user in the platform before starting the hackathon. You can sign up in this [link](https://github.com/join). It is important for the organization that you enter **your full name in the field `Name` of [your profile](https://github.com/settings/profile)**.
- I have an idea for the hackathon
-
Open an issue in this repo (using the [`new project`](https://github.com/qiskit-community/qiskit-camp-africa-19/issues/new?assignees=&labels=members+wanted&template=new-project-template.md&title=Project+name) template) and explain your idea in some paragraphs.
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 and hackathons for inspiration.
## Time for pitching the idea
Before the hackathon starts, the first thing to be done on the first day is to pitch all the ideas registered [here](https://github.com/qiskit-community/qiskit-camp-africa-19/issues). The pitch is a 60-second-long exposition by the original submitter of the idea. Make sure that you mention, at least, these three elements: team number, the problem to solve, the kind of people you need in your team. The goal is to recruit participant behind your idea. If your idea does not get critical mass, it will be discarded for this hackathon.
## Team formation
- 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](#time-for-pitching-the-idea), 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 you want to join the team, add a comment in the issue mentioning `@qcamp` (our [helpful bot](https://github.com/qcamp)). 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 `@qcamp` in 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 none of the proposed ideas is suitable for you, consider submitting your own idea. If you feel that the full thing is over your head, maybe consider joining the [Good First Issues team](https://github.com/qiskit-community/qiskit-camp-africa-19/issues/1). You'll want to participate in the competition, this is a great oportunity to 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](https://github.com/qiskit-community/qiskit-camp-africa-19/labels/candidate%20to%20be%20closed) 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.
## The hacking part of the hackathon
- 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` (qiskit.slack.com) to add the label `group 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.
## It's presentation time!
After the hackathon finishes, the team will have extra time (around 1 hour) to prepare for a 3-minute-long presentation. [This article](https://link.medium.com/K1Tw374Wk2) has good advice that coaches and judges have been collecting during the past camp editions. Make sure you are following those guidelines!
## It's awards time!
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:
1. Originality and Uniqueness
2. Live Pitch Presentation
3. Usefulness
4. Technical complexity.
The 1st place winners will receive a paid trip to the annual flagship [Qiskit Camp event](https://medium.com/qiskit/qiskit-camp-2020-coming-next-march-7b8c39e5d42c) 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.