This document summarises the current status and makes some vision statements about possible future developments. For more background and references, see the User handbook, Whitepaper and issue #100.
An open source project board designed for splendid collaboration, dribdat is used to collect and showcase all projects from an event in one place. Originally designed for use at hackathons - more than just a trendy way to get recruited into an IT job, these are a venue for open collaboration, civic engagement, and technical experimentation in a social setting. We've packed in a lot of experience running and optimizing the participant experience into this platform.
Screenshots of the Stages screen and Backboard
The name dribdat is an amalgam of "Driven By Data" - with a tip of the hat to Dribbble, a famous online community for graphic design which was one of the inspirations at the start of the project. We have organised a lot of hackathons over the years, and started this platform to streamline our own efforts. It is designed with the goal of helping teams - and their facilitators - sustain efforts over time, streamline information channels, and let everyone focus on driving their ideas forward.
On the front page you can see the upcoming event, as well as any previous events. A short description is followed by a link to the event home page, as well as a countdown of time remaining until the start or finish (if already started) of the event. All the Projects and Challenges are shown on the event home page. Here you can learn about topics, schedules, get directions and any other vital information that the organizers of the event have provided. Once the event has started, and you have formed a team, you can login and "Share project".
Once a team has formed around a Challenge, any of the team members can Post an update, and promote it to Project status. At that point you can see a log of the progress the team is making (encourage them to Post regularly to help track activities), and the latest version of their pitch and documentation. As we will discuss in more detail below, this documentation can come from almost any open Internet source and be embedded on the project page.
Users can use Markdown formatting to document their project and customise its display. Projects which are published in a compatible source repository - such as GitHub or supported wikis - can be auto-synced in dribdat, so that the documentation work can take place in the README's favored by the open source community. You can also update your progress level, in addition to an automatic metric for profile completeness and activity levels, to give each project a progress score. Your team members can subscribe to the project once you have started it, link their public profile in the team roster, and make changes to the data.
Out of the box, your projects advance through a series of stages inspired by the School of Data Pipeline, which you can also configure to follow a different methodology. At the end of the event, the teams, audience and organizers should have an excellent overview of the work that was done during the event, see the progress of the documentation at a glance, and export data for analysis using the administrative console. The Whitepaper has additional background.
For more user-facing guidance, see the User's Guide and installation instructions in the README.
One starts an Event, to which Challenges (= Ideas) are added. These can take the form of Projects (at progress level 0), or Categories. A team is made of up of any number of Users who have certain organizer-defined Roles and have joined a Project.
The main models are represented here:
What are the differences between a Project and a Challenge?
We have built this project to "scratch our own itch". In it's first two years of service, it has supported dozens of events around Switzerland, and become the official hackathon platform of Opendata.ch - Swiss chapter of Open Knowledge, the Open Network Infrastructure Association, and others. We have interesting ideas about how to develop the project further, and a supportive community giving us the feedback and means to realize them.
Easiest of all is to sign up for an upcoming hackathon, and try dribdat out as a participant. You can also visit the project's home page for instructions on how to quickly deploy it on your own server and set up your own events.
dribdat is a responsive Web application written using the Flask framework for Python and Bootstrap. Using dribdat's API, it is also possible to create a live dashboard, for example for use as Digital Signage at the event, or to connect apps like backboard. It runs on all major operating systems and databases. Take it for a spin!
Photo credit: MakeZurich 2018 by Christina Rieder CC BY-SA 4.0
The following questions were compiled as part of the projects DINAcon nomination, and last updated on May 5, 2021.
> How mature is the project?
Live and production ready.
> When was the project started?
> Under which license is your project licensed?
OSI/FSD-approved free software license (MIT)
> Does one need to sign a contributor agreement?
> How many different contributors did contribute to the project within the last 12 months?
> How many commits did your project receive within the last 12 months? Projects not having a version control system (e.g. Open Data projects or similar) can also specify changesets or similar.
> Was this project forked (split into different communities) in the past or is this project a fork of an other project? Please describe the situation (was it a friendly/unfriendly fork, what was the reason, what is the current state of the projects that are/were involved).
> If your project is based on a (public) GitLab instance, on Github, on Bitbucket, etc. that offers a metric like "followers" or "likes", what is the metric of your project?
38 stars, 17 forks
> Does the community meet in "real life" on a regular base (e.g. yearly, monthly, ...)? How many people do meet at such meetings?
Yes. We meet at least twice a year at events where we use, and further develop, this platform. There is a small group of people that has directly influenced, and continues to take an interest in, the course of this project. We have several online locations to share updates (notably on Mattermost, Discord and Slack).
> Do you have other metrics that you would like to share with us, which help us to understand how successful your project is?
Used at 50+ hackathons. The single largest installation has 750+ users.
> Does your project have a non-coder community e.g. UX designer, translator, marketing, etc.? What kind of non-coder people are involved in your project?
Yes. Hackathon participations are not just coders, and non-technical users who would like to discover open source activities are an important prerogative for this project. The process of running creative events like hackathons, combining our experience in code, is something we have aimed to build into all parts of the tool to make the event format accessible to an even wider public.
> Does your project offer something like "easy hacks" to make it easy to get a foot into the project?
Yes, there is a getting started page which can also be customized by the organisers. We have a community instance, where people can start their own events. To run your own instance of dribdat, there are clear installation instructions to follow.
> Please provide the page where we can find more information about the easy hacks.
For deployment see the deployment guide.
For usage notes, see the user handbook.
For general information, visit our website.
> Do you have people mentoring new contributors and actively helping them to get on board of the project?
Oleg and other people with experience in using the platform are available via various community channels to new users of dribdat. We regularly mentor new users in getting started. There is also a hosted version of the platform which we can set up to get hackathons going quickly. And a reasonably active forum.
> Does your project undertake specific efforts to make sure, that people regardless of ethnicity, gender, etc. can contribute and participate in the project? Does your project for example have a Code of Conduct or is it in general open and friendly to all human beings? Please explain the current situation.
The Hack Code of Conduct, which we have applied to events for the past 3 years, is now in dribdat by default to help facilitate inclusive events.
> Please describe the business case of your project.
There are hackathons happening all over the world every weekend. Countless more collaborative online "hacking" events happen every day in companies, institutions and the civil society. Each of them generates interest, activity, networking and new initiatives. While several hackathon platforms contend to "lead the market", we are one of a handful of open source alternatives, most notably HackDash and Sparkboard - which operate in a SaaS model.
Please visit our OpenCollective, where we are currently focusing our fundraising and transparent budgeting.
> How relevant is your project in regard to a commercial use?
Currently we accept sponsoring and distribute it within the project, but do not charge a licensing fee of any kind. There is a strong, recurrent interest from companies in using dashboards similar to this one for tracking internal activities above and beyond hackathon-type events. Several commercial models come to mind: the original motivation for the project came out of a hackathon sponsored by Swisscom, a company that champions innovation culture. We are inspired us to pursue an organic and grassroots business model that benefits a wide variety of "start-up" initiatives.
> This project is important to the world because....
Hackathons have become a useful instrument to see critically beyond the veil of pragmatic utility in Information Technologies, and have been embraced by the most disruptive companies and organisations around the world as a vehicle for positive change. By imbuing a software project with the ethics and values of hackathons, we can scale these experiments from our local community to many other corners of the world and many domains of creative collaboration.
> If this project stops its development and ceases to exist, this would be the impact...
We wouldn't have our own platform to hack the meta-side of hackathons, and that would be a shame. We could go back to using wikis and repo organisations, with all the constraints and loss of user friendliness that entails.
> Do you have any usage metrics you can provide which show how succesful your project is? (downloads, visits on website, registered users, etc.)
In addition to the low thousands of user accounts and hundreds of projects across the different installations (these are visible to administrators in the dashboard), many dribdat instances have "open analytics": scroll down to the bottom of the page (for example, on hack.opendata.ch) and click Analytics.