Encourage use of open badges

[loleg]

Badges are now widespread, with their use promoted by tutorials and tools, on GitHub and other coding platforms. In addition to #7, assist hackathon participants in employing badges as signals of code quality or other "selling points" of their project. In particular, we would want people to label their projects as clearly adhering to code standards or ensuring their platforms or data are fully open.

Badges could forge the way to encouraging platform-building - continuous integration, data scraping and quality, etc. - could be goal posts for the teams if they can get a selection of badges applicable to the current hackathon. See this blog post overview and #115 - integration with community platforms.

Selecting badges could be another feature of the data entry experience #123

Inspiration: Mozilla, Hackerrank, Codemonk

[loleg]

https://forthebadge.com/ via @ggcaponetto

[loleg]

What about also providing a "Hacked on Dribdat" badge along the lines of FlatHub Badges for teams that want to link to their hackathon page on GitHub etc.?

[loleg]

See also Open Badges via https://blog.weareopen.coop/finding-the-others-1f43b48ceff1