Skip to content

Plugin Development Hackathon

Neeraj edited this page Oct 9, 2024 · 6 revisions

Duration: October 9th - October 31st, 2024
Goal: Develop plugins for Hyperswitch


Key Dates

  • Start Date: Wednesday, October 9th, 2024

  • Registration Deadline: Monday, October 14th, 2024

  • Approach Submission: Monday, October 14th, 2024 (EOD IST)

  • End Date: Thursday, October 31st, 2024

  • Demo Day: First week of November 2024 (exact date TBA in our community)


Prizes for Winners

How to Participate

  1. Sign Up: Fill out the registration form to be eligible. You can participate individually or in teams of up to 4 members.

  2. Submit Your Approach: Work on a solution approach and submit it by October 14th, 2024. Form

  3. Shortlisting: The Hyperswitch team will review your submission and notify shortlisted candidates via email within 2-3 business days.

  4. Develop the Solution: If shortlisted, you will have two weeks to complete your solution.

  5. Final Submission: Once your solution is ready, submit it before October 31st, 2024 via the provided submission form.

  6. Demo Day: We will reach out with Demo Day details. Be prepared to showcase your plugin’s functionality and ensure all edge cases are addressed.

  7. Hacktoberfest Tagging: The 3 winners—one for each plugin—will raise a Pull Request (PR), which will be tagged hacktoberfest-accepted to qualify for Hacktoberfest.


What Happens on Demo Day?

On Demo Day, participants will present their plugins, demonstrating functionality and handling of edge cases. After the demos, winners will be announced within 5 business days.

All shortlisted candidates will receive Hyperswitch goodies. You can view the goodies here: Hyperswitch Goodies


FAQs

  1. Should I host this in my own repository?

Yes, host the project in your repository and ensure you have provided an Apache 2.0 License for your repo.

  1. Will my issue count towards Hacktoberfest?

Yes, but only the PRs raised by the winners will be considered for Hacktoberfest.

  1. Is there a sample project I can refer to?

Yes, you can check out these sample projects:

  1. Will I receive goodies if I’m rejected at the Approach stage?

No, only shortlisted candidates will be eligible for goodies.

  1. Where can I get the Hyperswitch API key?

You can sign up for our Sandbox environment and generate your API key.

  1. Where can I ask questions if I face any issues?

We recommend reaching out to us via our community channels on Slack or Discord.

  1. What happens if the same GitHub user participates in multiple teams?

Any individual found participating in multiple teams will be disqualified.

  1. How will I know if I’ve been shortlisted after the Approach stage?

We will announce the list of shortlisted candidates in our community.

  1. How will the Price money be distributed for a team?

Individual or team, we will initiate the price money distribution for the POCs email that is shared in the Registration form

  1. Can the same team/individual can build multiple Plugins?

No, we would recommend each team/Individual to participate on a single Plugin only.

  1. What should the Approach doc consist?

Approach doc should outline a high-level plan detailing the plugin’s core features, how it integrates with Hyperswitch’s API, and how it will address the identified problem. Include key functionalities, technical stack, and how you’ll handle edge cases to ensure seamless performance.


Note:

Participation guidelines may change if the number of participants increases.

We recommend staying active in our community to stay informed about any timeline changes.


Please make sure to read this through the below Guidelines before attempting the problem statements

Contribution Guidelines Bounty Program Guidelines Terms of Contest