Mechanism for hackathon discoverability about dribdat HOT 13 CLOSED

This schema might also be related/interesting https://schema.org/Dataset

from dribdat.

Another interesting example is the civic.json file used by @codeforamerica - which they suggest adding to repos as follows:

Merge this to add a civic.json file to your project. This little bit of metadata will make your project easier to search for at https://www.codeforamerica.org/brigade/projects and elsewhere. You can read more about the status attribute at https://www.codeforamerica.org/brigade/projects/stages.

from dribdat.

Note: this is related to some work on an API-first redesign of the platform earlier this year.

from dribdat.

I guess the projects (teams) should be listed under performer category? To be continued..

from dribdat.

@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
Is there a way we could share the implementation?

from dribdat.

@gonzalocasas that's great! Probably using the separate repo to specify and develop the Event Schema would make sense. See also the schema for Hackathon-Hackers events aggregation, as well as the HackClub directory for examples of what people look for.

from dribdat.

Interesting example of someone going the other route - writing a scraper to aggregate hackathon results: https://github.com/andrew-m-h/HackanationGovhack

from dribdat.

Additional inspiration, from earlier discussions: https://spaceapi.io/
Also, we at one point did some work on an OpenAPI spec (Swagger)

from dribdat.

The basic mechanism has been in place for a while, but to close this issue, we need to have a clear and accepted validation. In my mind, this is the "community calendar" mentioned in the top posted, generated from a federated list of dribdat instances.

I would also appreciate seeing at least one "static" hackathon.json involved in such this, not coming out of an app, at some point. Any updates from your side @gonzalocasas are welcome.

from dribdat.

Recent discussions and experiments around #325 make me think: wouldn't it be cool if dribdat instances federated each other automatically, rather than the manual import and export of Data Packages that I have to do now?

from dribdat.

It would be amazing!

from dribdat.

I've been thinking recently that instead of a full-blown installation of Dribdat, a hackathon organizer should be able to quickly generate a hackathon.json or META-tags for the Schema.org spec using a simple tool, like a one-page app with a form to fill out, a CSV to upload or paste in - and then they can do what they want with the generated file. In this project, we could also then use the backboard app to offer quick visualization or static-site deployment of the hackathon for archiving purposes.

from dribdat.

I'm going to say that we have solved the original proposal - all the data is being served by our API + hackathon.json + OpenGraph meta-tags. We are still far from the Ultimate Mechanism (which, today, probably means getting your event to stand out in GPT results), and there are some great further ideas in this ticket - but we have at least ensured that hackathons powered by Dribdat have decent SEO, and that is something.

See also #379

from dribdat.