Edited content version 43
Hack Code of Conduct
A generic and configurable Code of Conduct for hackathons
Challenge for Hack:Org:X
Help us to review and freshen up the Hack Code of Conduct, initiated and for years maintained by Cristiano Betta. We are grateful to this project for providing a key baseline for many of our events. There are a number of areas today where the content and technical set up for this important document could be improved.
See also: dribdat/Guidelines & Discussion (GitHub)
🌟 Inspirations:
- Contributor Covenant
- GitHub Community Guidelines
- "Be excellent to each other" (My Geek Wisdom)
- Updating the Open Definition (OKFN)
- Participating in Hackathons (Google Open Source)
- The Paradox of Open (openfuture.eu)
- House Rules
The Accessible Events Checklist (PDF) and Access Guides from the University of Glasgow, were kindly suggested by Christian Hansen. In addition to supporting diversity, such a checklist for organizers - perhaps as part of a handbook - would be quite useful.
Please contribute further ideas on GitHub at https://github.com/dribdat/code-of-conduct
See also:
Market days of the ancient Roman calendar, forming a kind of weekend including, for a certain period, rest from work for the ruling class.
Event finished
Accessible Events Checklist (PDF, via Christian Hansen)
Event started
Ask
Joined the team
Ask
Repository updated
Challenge posted