Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Mechanism for hackathon discoverability #112
In the context of the
Discoverability implies machine-readable formats and standardized access patterns. Dribdat already tracks projects and a significant part of the event details, so this information needs to be exposed, but in a standard way to allow others to implement it without the need to run dribdat. The two parts (Event details and Hackathon projects) have potentially different implementations, and conceptual differences, so I will describe them separately.
Conceptually, this would be a mechanism similar to
Schema.org has a format for generic events, and some sub-classing for specific event types, but none of them fits exactly a hackathon: http://schema.org/Event.
On the other hand, the simplicity of a root-level file descriptor (i.e.
So the proposal would be to define a root-level
The sibling event link list creates a crawlable graph that connects events to each other, fostering discoverability in general, and also establishing a relations between events.
This root-level file descriptor should be placed at the event's main website's root.
A second level of detail in the meta-description of an event is its actual content, i.e. the projects presented during the event. For this, Dribdat already hosts all the information required, and the only additional need to be to expose it over a well-defined JSON end-point and format/spec.
As mentioned in the previous section, this end-point would be linked from the root-level file descriptor through the
In combination these two metadata end-points would allow an event/hackathon to self-describe itself in a fully decentralized manner while allowing the creation of a graph of events to keep things tied together (for a multitude or reasons: forked events, friend events, topical events, etc).
On top of it, additional tools and services (also decentralized) could be created by crawling and visualizing the event graph in various ways. For instance, this community event calendar could be generated out of this data.
@loleg I implemented also parts of the Event Schema thing on the website side of things: https://github.com/open-network-infrastructure/hugo-hackatheme/blob/master/layouts/partials/meta/schema.html