| .github | ||
| data | ||
| docs | ||
| dribdat | ||
| image | ||
| migrations | ||
| profile | ||
| requirements | ||
| tests | ||
| .dockerignore | ||
| .gitignore | ||
| .python-version | ||
| .pyup.yml | ||
| app.json | ||
| autoapp.py | ||
| cli.py | ||
| code_of_conduct.md | ||
| deploy-stackscript.sh | ||
| docker-compose.example.yml | ||
| docker-compose.local.yml | ||
| docker-compose.sqlite.yml | ||
| Dockerfile | ||
| force-migrate.sh | ||
| gunicorn.conf.py | ||
| LICENSE | ||
| manage.py | ||
| manifest.yml | ||
| package.json | ||
| PACKAGE.txt | ||
| patched.py | ||
| poetry.lock | ||
| Procfile | ||
| publish-docker-dev.sh | ||
| publish-docker-tag.sh | ||
| pyproject.toml | ||
| pytest.ini | ||
| README.md | ||
| release.sh | ||
| requirements.txt | ||
| SECURITY.md | ||
| tox.ini | ||
Dribdat
An open source hackathon management application that playfully assists your team in crowdsourcing technical designs.
🚲 See Tour de Hack for examples, and User handbook for screenshots. 🏔️ There are mirrors on Codeberg and GitHub. 🩵 Support us on OpenCollective
We aim to include people of all backgrounds in using + developing this tool - no matter your age, gender, race, ability, or sexual identity 🏳️🌈 Please read our Code of Conduct if you have questions.
Purpose
Created in light of the Hacker ethic, the Zen of Dribdat is (in a nutshell):
- Commit sustainably: aggregate results in open, web-friendly data formats for search and archiving.
- Go live and let live: efficiently deploy designs, dev envs, docs accessible to your entire team.
- Co-create in safe spaces: with content and tools promoting safer conduct and increased privacy.
Designed to bootstrap your awesome hackathon, Dribdat's toolset can be used as a versatile toolbox for civic tech sprints. To get started, install the software.
Visit the Hackfinder to find events connected to current research, and join our Hack:Org:X meetings to say 'hi' to the maintainers and fellow hackathon organizers.
For more background and references, see the 📖 User Handbook. If you need help or advice in setting up your site, or would like to contribute to the project: please get in touch via 🗣️ Discussions.
Quickstart
The Dribdat project can be deployed to any server capable of serving Python applications, and is set up for fast deployment using Ansible or Docker 🏀 The first user that registers becomes an admin, so don't delay when you make your play on D}}BD{T
If you would like to run this application on any other cloud or local machine, there are instructions in the Deployment guide. Information on contributing and extending the code can be found in the Contributors guide, which includes API documentation, and other details.
See also backboard: a responsive, modern alternative frontend, and our dridbot chat client. Both demonstrate reuse of the dribdat API. If you need support with your deployment, please reach out through Discussions. Pull Requests and Issues welcome!
Development Status: 🍌 Perpetual beta
Credits
This application was based on cookiecutter-flask by Steven Loria, a more modern version of which is cookiecutter-flask-restful. Cookiecutter could also be a good bootstrap for your own hackathon projects!
♡ The Open Data, Open Networking and Open Source communities in 🇨🇭 Switzerland gave this project initial form and direction through a hundred events. ♥-felt thanks to our Contributors, and additionally: F. Wieser and M.-C. Gasser at Swisscom for support at an early stage of this project, to Alexandre Cotting, Anthony Ritz, Chris Mutel, Fabien Schwob, Gonzalo Casas, Iliya Tikhonenko, Janik von Rotz, Jonathan Schnyder, Jonathan Sobel, Philip Shemella, Thomas Amberg, Yusuf Khasbulatov .. and all participants and organizers sending in bugs and requests! You are all awesome hackers ♡
License
This project is open source under the MIT License.
The Contributor Covenant Code of Conduct applies to interactions with the maintainers and support community of the project.
Due to the use of the boto3 library for optional S3 upload support, there is a dependency on OpenSSL via awscrt. If you use these features, please note that the product includes cryptographic software written by Eric Young (eay@cryptsoft.com) and Tim Hudson (tjh@cryptsoft.com).