Dates
- Hackathon: Saturday, March 7 ā Sunday, March 8, 2026
- Submission Deadline: Sunday, March 8, 2026 at 3:30 PM ET
Eligibility
- Above the legal age of majority in your country of residence
- Able to attend in person in New York City for both days (March 7-8, 2026)
- Agreed to the Code of Conduct below
Project and Submission Requirements
- New work only. All code and designs must be created during the hackathon. Publicly available libraries, frameworks, and APIs are permitted.
- Guild submissions. Projects must be submitted as guild-level submissions combining Team Alpha and Team Beta. Individual team submissions will not be accepted.
- Open source. All code produced during the hackathon will be contributed to the Open Connect project under the OpenConnect Software License. You retain attribution rights as a contributor.
- Required artifacts. Working prototype, GitHub repository, README documentation, and a 3-5 minute demo video. See the submission requirements on the main page for full details.
Code of Conduct
Code for Connection is dedicated to a harassment-free experience for everyone, regardless of gender, gender identity, age, sexual orientation, disability, physical appearance, body size, race, ethnicity, nationality, religion, prior incarceration status, or technical experience.
We do not tolerate harassment in any form, including offensive comments related to any protected characteristic, intimidation, stalking, harassing photography or recording, sustained disruption of events, inappropriate physical contact, or unwelcome sexual attention.
Expectations: Be respectful. Honor the expertise and lived experience all participants bring. Collaborate openly. Ask consent before photographing or recording others. Alert organizers if you notice someone in distress.
Consequences: Participants asked to stop harassing behavior must comply immediately. Organizers may warn, expel, or ban offenders at their discretion.
Reporting: If you experience or witness harassment, report it immediately to an event organizer or email rajaini@worthrises.org.
Additional Rules
- Attendance. Participants must be present for the opening session on Saturday and remain engaged throughout. Extended absences may result in removal from your team.
- Team changes. Once guilds and teams are assigned, no switching without organizer approval.
- External help. No substantial help from non-participants. Mentors and organizers are available for guidance.
- Disputes. Resolved by hackathon organizers, whose decisions are final.