diff --git a/.DS_Store b/.DS_Store new file mode 100644 index 0000000..66bea6c Binary files /dev/null and b/.DS_Store differ diff --git a/.gitignore b/.gitignore new file mode 100644 index 0000000..f40fbd8 --- /dev/null +++ b/.gitignore @@ -0,0 +1,5 @@ +_site +.sass-cache +.jekyll-cache +.jekyll-metadata +vendor diff --git a/404.html b/404.html new file mode 100644 index 0000000..5e1bb16 --- /dev/null +++ b/404.html @@ -0,0 +1,25 @@ +--- +permalink: /404.html +layout: default +--- + + + +
+

404

+ +

Page not found :(

+

The requested page could not be found.

+
diff --git a/Gemfile b/Gemfile new file mode 100644 index 0000000..8e0e38d --- /dev/null +++ b/Gemfile @@ -0,0 +1,30 @@ +source "https://rubygems.org" +# Hello! This is where you manage which Jekyll version is used to run. +# When you want to use a different version, change it below, save the +# file and run `bundle install`. Run Jekyll with `bundle exec`, like so: +# +# bundle exec jekyll serve +# +# This will help ensure the proper Jekyll version is running. +# Happy Jekylling! +# gem "jekyll", "~> 4.2.1" +# This is the default theme for new Jekyll sites. You may change this to anything you like. +gem "minima", "~> 2.5" +# If you want to use GitHub Pages, remove the "gem "jekyll"" above and +# uncomment the line below. To upgrade, run `bundle update github-pages`. +gem "github-pages", "~> 219", group: :jekyll_plugins +# If you have any plugins, put them here! +group :jekyll_plugins do + gem "jekyll-feed", "~> 0.12" +end + +# Windows and JRuby does not include zoneinfo files, so bundle the tzinfo-data gem +# and associated library. +platforms :mingw, :x64_mingw, :mswin, :jruby do + gem "tzinfo", "~> 1.2" + gem "tzinfo-data" +end + +# Performance-booster for watching directories on Windows +gem "wdm", "~> 0.1.1", :platforms => [:mingw, :x64_mingw, :mswin] + diff --git a/Gemfile.lock b/Gemfile.lock new file mode 100644 index 0000000..1b2517e --- /dev/null +++ b/Gemfile.lock @@ -0,0 +1,282 @@ +GEM + remote: https://rubygems.org/ + specs: + activesupport (6.0.4.1) + concurrent-ruby (~> 1.0, >= 1.0.2) + i18n (>= 0.7, < 2) + minitest (~> 5.1) + tzinfo (~> 1.1) + zeitwerk (~> 2.2, >= 2.2.2) + addressable (2.8.0) + public_suffix (>= 2.0.2, < 5.0) + coffee-script (2.4.1) + coffee-script-source + execjs + coffee-script-source (1.11.1) + colorator (1.1.0) + commonmarker (0.17.13) + ruby-enum (~> 0.5) + concurrent-ruby (1.1.9) + dnsruby (1.61.7) + simpleidn (~> 0.1) + em-websocket (0.5.2) + eventmachine (>= 0.12.9) + http_parser.rb (~> 0.6.0) + ethon (0.15.0) + ffi (>= 1.15.0) + eventmachine (1.2.7) + execjs (2.8.1) + faraday (1.8.0) + faraday-em_http (~> 1.0) + faraday-em_synchrony (~> 1.0) + faraday-excon (~> 1.1) + faraday-httpclient (~> 1.0.1) + faraday-net_http (~> 1.0) + faraday-net_http_persistent (~> 1.1) + faraday-patron (~> 1.0) + faraday-rack (~> 1.0) + multipart-post (>= 1.2, < 3) + ruby2_keywords (>= 0.0.4) + faraday-em_http (1.0.0) + faraday-em_synchrony (1.0.0) + faraday-excon (1.1.0) + faraday-httpclient (1.0.1) + faraday-net_http (1.0.1) + faraday-net_http_persistent (1.2.0) + faraday-patron (1.0.0) + faraday-rack (1.0.0) + ffi (1.15.4) + forwardable-extended (2.6.0) + gemoji (3.0.1) + github-pages (219) + github-pages-health-check (= 1.17.7) + jekyll (= 3.9.0) + jekyll-avatar (= 0.7.0) + jekyll-coffeescript (= 1.1.1) + jekyll-commonmark-ghpages (= 0.1.6) + jekyll-default-layout (= 0.1.4) + jekyll-feed (= 0.15.1) + jekyll-gist (= 1.5.0) + jekyll-github-metadata (= 2.13.0) + jekyll-mentions (= 1.6.0) + jekyll-optional-front-matter (= 0.3.2) + jekyll-paginate (= 1.1.0) + jekyll-readme-index (= 0.3.0) + jekyll-redirect-from (= 0.16.0) + jekyll-relative-links (= 0.6.1) + jekyll-remote-theme (= 0.4.3) + jekyll-sass-converter (= 1.5.2) + jekyll-seo-tag (= 2.7.1) + jekyll-sitemap (= 1.4.0) + jekyll-swiss (= 1.0.0) + jekyll-theme-architect (= 0.2.0) + jekyll-theme-cayman (= 0.2.0) + jekyll-theme-dinky (= 0.2.0) + jekyll-theme-hacker (= 0.2.0) + jekyll-theme-leap-day (= 0.2.0) + jekyll-theme-merlot (= 0.2.0) + jekyll-theme-midnight (= 0.2.0) + jekyll-theme-minimal (= 0.2.0) + jekyll-theme-modernist (= 0.2.0) + jekyll-theme-primer (= 0.6.0) + jekyll-theme-slate (= 0.2.0) + jekyll-theme-tactile (= 0.2.0) + jekyll-theme-time-machine (= 0.2.0) + jekyll-titles-from-headings (= 0.5.3) + jemoji (= 0.12.0) + kramdown (= 2.3.1) + kramdown-parser-gfm (= 1.1.0) + liquid (= 4.0.3) + mercenary (~> 0.3) + minima (= 2.5.1) + nokogiri (>= 1.10.4, < 2.0) + rouge (= 3.26.0) + terminal-table (~> 1.4) + github-pages-health-check (1.17.7) + addressable (~> 2.3) + dnsruby (~> 1.60) + octokit (~> 4.0) + public_suffix (>= 3.0, < 5.0) + typhoeus (~> 1.3) + html-pipeline (2.14.0) + activesupport (>= 2) + nokogiri (>= 1.4) + http_parser.rb (0.6.0) + i18n (0.9.5) + concurrent-ruby (~> 1.0) + jekyll (3.9.0) + addressable (~> 2.4) + colorator (~> 1.0) + em-websocket (~> 0.5) + i18n (~> 0.7) + jekyll-sass-converter (~> 1.0) + jekyll-watch (~> 2.0) + kramdown (>= 1.17, < 3) + liquid (~> 4.0) + mercenary (~> 0.3.3) + pathutil (~> 0.9) + rouge (>= 1.7, < 4) + safe_yaml (~> 1.0) + jekyll-avatar (0.7.0) + jekyll (>= 3.0, < 5.0) + jekyll-coffeescript (1.1.1) + coffee-script (~> 2.2) + coffee-script-source (~> 1.11.1) + jekyll-commonmark (1.3.1) + commonmarker (~> 0.14) + jekyll (>= 3.7, < 5.0) + jekyll-commonmark-ghpages (0.1.6) + commonmarker (~> 0.17.6) + jekyll-commonmark (~> 1.2) + rouge (>= 2.0, < 4.0) + jekyll-default-layout (0.1.4) + jekyll (~> 3.0) + jekyll-feed (0.15.1) + jekyll (>= 3.7, < 5.0) + jekyll-gist (1.5.0) + octokit (~> 4.2) + jekyll-github-metadata (2.13.0) + jekyll (>= 3.4, < 5.0) + octokit (~> 4.0, != 4.4.0) + jekyll-mentions (1.6.0) + html-pipeline (~> 2.3) + jekyll (>= 3.7, < 5.0) + jekyll-optional-front-matter (0.3.2) + jekyll (>= 3.0, < 5.0) + jekyll-paginate (1.1.0) + jekyll-readme-index (0.3.0) + jekyll (>= 3.0, < 5.0) + jekyll-redirect-from (0.16.0) + jekyll (>= 3.3, < 5.0) + jekyll-relative-links (0.6.1) + jekyll (>= 3.3, < 5.0) + jekyll-remote-theme (0.4.3) + addressable (~> 2.0) + jekyll (>= 3.5, < 5.0) + jekyll-sass-converter (>= 1.0, <= 3.0.0, != 2.0.0) + rubyzip (>= 1.3.0, < 3.0) + jekyll-sass-converter (1.5.2) + sass (~> 3.4) + jekyll-seo-tag (2.7.1) + jekyll (>= 3.8, < 5.0) + jekyll-sitemap (1.4.0) + jekyll (>= 3.7, < 5.0) + jekyll-swiss (1.0.0) + jekyll-theme-architect (0.2.0) + jekyll (> 3.5, < 5.0) + jekyll-seo-tag (~> 2.0) + jekyll-theme-cayman (0.2.0) + jekyll (> 3.5, < 5.0) + jekyll-seo-tag (~> 2.0) + jekyll-theme-dinky (0.2.0) + jekyll (> 3.5, < 5.0) + jekyll-seo-tag (~> 2.0) + jekyll-theme-hacker (0.2.0) + jekyll (> 3.5, < 5.0) + jekyll-seo-tag (~> 2.0) + jekyll-theme-leap-day (0.2.0) + jekyll (> 3.5, < 5.0) + jekyll-seo-tag (~> 2.0) + jekyll-theme-merlot (0.2.0) + jekyll (> 3.5, < 5.0) + jekyll-seo-tag (~> 2.0) + jekyll-theme-midnight (0.2.0) + jekyll (> 3.5, < 5.0) + jekyll-seo-tag (~> 2.0) + jekyll-theme-minimal (0.2.0) + jekyll (> 3.5, < 5.0) + jekyll-seo-tag (~> 2.0) + jekyll-theme-modernist (0.2.0) + jekyll (> 3.5, < 5.0) + jekyll-seo-tag (~> 2.0) + jekyll-theme-primer (0.6.0) + jekyll (> 3.5, < 5.0) + jekyll-github-metadata (~> 2.9) + jekyll-seo-tag (~> 2.0) + jekyll-theme-slate (0.2.0) + jekyll (> 3.5, < 5.0) + jekyll-seo-tag (~> 2.0) + jekyll-theme-tactile (0.2.0) + jekyll (> 3.5, < 5.0) + jekyll-seo-tag (~> 2.0) + jekyll-theme-time-machine (0.2.0) + jekyll (> 3.5, < 5.0) + jekyll-seo-tag (~> 2.0) + jekyll-titles-from-headings (0.5.3) + jekyll (>= 3.3, < 5.0) + jekyll-watch (2.2.1) + listen (~> 3.0) + jemoji (0.12.0) + gemoji (~> 3.0) + html-pipeline (~> 2.2) + jekyll (>= 3.0, < 5.0) + kramdown (2.3.1) + rexml + kramdown-parser-gfm (1.1.0) + kramdown (~> 2.0) + liquid (4.0.3) + listen (3.7.0) + rb-fsevent (~> 0.10, >= 0.10.3) + rb-inotify (~> 0.9, >= 0.9.10) + mercenary (0.3.6) + minima (2.5.1) + jekyll (>= 3.5, < 5.0) + jekyll-feed (~> 0.9) + jekyll-seo-tag (~> 2.1) + minitest (5.14.4) + multipart-post (2.1.1) + nokogiri (1.12.5-x86_64-darwin) + racc (~> 1.4) + octokit (4.21.0) + faraday (>= 0.9) + sawyer (~> 0.8.0, >= 0.5.3) + pathutil (0.16.2) + forwardable-extended (~> 2.6) + public_suffix (4.0.6) + racc (1.6.0) + rb-fsevent (0.11.0) + rb-inotify (0.10.1) + ffi (~> 1.0) + rexml (3.2.5) + rouge (3.26.0) + ruby-enum (0.9.0) + i18n + ruby2_keywords (0.0.5) + rubyzip (2.3.2) + safe_yaml (1.0.5) + sass (3.7.4) + sass-listen (~> 4.0.0) + sass-listen (4.0.0) + rb-fsevent (~> 0.9, >= 0.9.4) + rb-inotify (~> 0.9, >= 0.9.7) + sawyer (0.8.2) + addressable (>= 2.3.5) + faraday (> 0.8, < 2.0) + simpleidn (0.2.1) + unf (~> 0.1.4) + terminal-table (1.8.0) + unicode-display_width (~> 1.1, >= 1.1.1) + thread_safe (0.3.6) + typhoeus (1.4.0) + ethon (>= 0.9.0) + tzinfo (1.2.9) + thread_safe (~> 0.1) + unf (0.1.4) + unf_ext + unf_ext (0.0.8) + unicode-display_width (1.8.0) + zeitwerk (2.5.1) + +PLATFORMS + x86_64-darwin-20 + +DEPENDENCIES + github-pages (~> 219) + jekyll-feed (~> 0.12) + minima (~> 2.5) + tzinfo (~> 1.2) + tzinfo-data + wdm (~> 0.1.1) + +BUNDLED WITH + 2.2.30 diff --git a/_config.yml b/_config.yml new file mode 100644 index 0000000..e342837 --- /dev/null +++ b/_config.yml @@ -0,0 +1,55 @@ +# Welcome to Jekyll! +# +# This config file is meant for settings that affect your whole blog, values +# which you are expected to set up once and rarely edit after that. If you find +# yourself editing this file very often, consider using Jekyll's data files +# feature for the data you need to update frequently. +# +# For technical reasons, this file is *NOT* reloaded automatically when you use +# 'bundle exec jekyll serve'. If you change this file, please restart the server process. +# +# If you need help with YAML syntax, here are some quick references for you: +# https://learn-the-web.algonquindesign.ca/topics/markdown-yaml-cheat-sheet/#yaml +# https://learnxinyminutes.com/docs/yaml/ +# +# Site settings +# These are used to personalize your new site. If you look in the HTML files, +# you will see them accessed via {{ site.title }}, {{ site.email }}, and so on. +# You can create any custom variable you would like, and they will be accessible +# in the templates via {{ site.myvariable }}. + +title: Hackathon Openbook +email: momo@dorahacks.com +description: (Almost) everything you want to know and discuss about hackathons +twitter_username: hackathonDAO +github_username: dorahacksglobal + +# Build settings +markdown: kramdown +theme: minima +plugins: + - jekyll-seo-tag + - jekyll-avatar + - jekyll-github-metadata + - jekyll-feed + - jekyll-remote-theme + +# Exclude from processing. +# The following items will not be processed, by default. +# Any item listed under the `exclude:` key here will be automatically added to +# the internal "default list". +# +# Excluded items can be processed by explicitly listing the directories or +# their entries' file path in the `include:` list. +# +# exclude: +# - .sass-cache/ +# - .jekyll-cache/ +# - gemfiles/ +# - Gemfile +# - Gemfile.lock +# - node_modules/ +# - vendor/bundle/ +# - vendor/cache/ +# - vendor/gems/ +# - vendor/ruby/ diff --git a/_posts/2021-10-29-event-planning.md b/_posts/2021-10-29-event-planning.md new file mode 100644 index 0000000..ff78745 --- /dev/null +++ b/_posts/2021-10-29-event-planning.md @@ -0,0 +1,107 @@ +--- +layout: post +title: "Event Planning and Organizing" +date: 2021-10-29 11:22:44 +0800 +categories: jekyll update +--- +> Owner: @Penny.Wang @Momo.Hou + +## Before the Hack + +### 1. Key Steps in Preparation for a Hackathon +Preparation can be really simple depending on your specific event scale and goals. The end goal of the whole planning process is to better engage hackers while equipping them with proper support. + +- Step 1 - finalize and decide your topic, location(online or offline), and target participants. +- Step 2 - calculate your budget and contact potential partners or sponsors accordingly. Keep step 1 in mind. +- Step 3 - Make final confirmation with all third-parties and validate all communication materials (both online and offline). +- Step 4 - Promote your events and prepare offline logistics. +- Step 5 - The moment of truth and follow up. + +### 2. Topic +Topic is one of the most important things for a successful hackathon and it can impact all the downstream preparation effort. With a clear and specific theme, it will be easy for you to decide who to approach as your target participants and potential partners; it also allows you to customize all the details such as location, event dates, the prize, promotion channel, etc. + +### 3. Location - offline or virtual + +For an **offline** hack, the minimum requirement of the venue would be fast and stable internet connections, other setups such as decoration and furniture simply depends on your budget. + +For a **virtual** hack, all you need is a solid online platform for project submission and voting, and probably also an online meeting room for ceremonies and project demos. + +| | Pros | Cons | +|---------|-------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------| +| offline | - Irreplaceable experience of communicating and developing； | - Complex logistics; - Limitation imposed by place and time; | +| virtual | - Not restricted by physical location; - Can last for a comparably longer period of time; - No complicated logistics, lower cost; | - It might be difficult for participants to find partners online, so it would be hard for lone wolves; | + + + +### 4. Communication and Publicity +Before preparing any materials, you have to determine **who is your target participants** based on your topic and location. After that we suggest you use “participants = channel x conversion rate” to estimate your final participants. + +Although you may think promotion materials like posters and content scripts are critical for participant recruiting, it's the promotion channel that matters the most to attract the right participants. Here are several tips to help you to get more proper participants for your event: + +- The main message you want to deliver includes location, time, topic, requirements for the participants, prize, partners, mentors and judges. +- Make sure your register entry is obvious and simple. +- Connect with locale developer communities and let them help +- Use hackers that already registered to refer others +- Holding related warm-up workshops or preparing other learning resources can be a good way to attract high quality participants. +- Good posters and slogans help. +- Influential mentors or judges help. +- More to come... + +Plus, a good register questionnaire can help you better understand, engage and manage your participants. You can also do some preliminary screening before the real hack based on your preference. A simple format can be reached here. + +### 5.Partners +Partners are totally optional for most of the hacks. However, holding a hackathon with the right partners may result in more valuable and more interesting results. For example, **local developer community** can help you to promote your event, experienced experts can join as **mentors or judges**, **entity** could be the funder for the rewards, and a **cloud service platform** could help provide 'stable and secure' computing services. + +HackathonDAO is a focused and professional sponsor, where they don't only provide monetary support but also help the organizers to maintain an active community composed of hackathon organizers and volunteers. + +--- + +## On the Hack + +### 1. Team up +As mentioned above, it’s better to let the participants know each other so they could exchange ideas before the real hack day. Useful tools include Discord, Slack, Telegram and more. Different communication methods work best in different scenario, so we don't have the most efficient way listed here but you are welcome to share your thoughts regarding this problem. + +Most likely there will be some hackers without a team on the hack day, you can **1)** hold an open-mic and encourage those who have ideas to recruit teammates and **2)** hold a coroner for individuals with no teams to connect to each other while making it easier for teams who want to recruit to find them. These can be used for both online and offline events. + +## 2. Projects Submission & Demo +The final demo show is usually the most interesting and exciting part of the whole event, yet it's also one of the hardest parts of organizing a hackathon since it could be chaotic and embarrassing. Here are some tips for you： +- Set a clear time limit (3-5mins per project) with an obvious timer visible for the presenters, the judges and all the participants. +- Always let the participants clarify what’s the incremental change made during the hackathon as some would use their previous projects. +- Encourage them to show a live demo of their product rather than a deck. +- Hold a small demo fair after the demos if you have 20+ projects. +- For online hacks, we have seen a lot of demos employing YouTube + Zoom (or other alternatives) for the final demo and we believe this is a convenient way for everyone and makes project follow-ups easy. +- Platforms such as hackerlink are very convenient tools for project submission. +- More to come... + +### 3. Voting and Awards +This is the most critical part of a successful hackathon, and we have listed three of the most prevalent voting methods employed by hackathon organizers below. Please note that you can always combine the voting methods according to your specific event. + +- **Judges vote** - A limited number of judges will decide the prizes. This is the most traditional and direct way, yet the final decision could be controversial. +- **Hackers vote** - every participant will get an opportunity to vote for their favorite projects and the allocation of the final prize would depend on the vote count. + - Pros - This final decision would be decentralized and diversified, and the more teams would be able to share the final prize. + - Cons - Susceptible to fraud and collusion. +- **Community vote** - let almost everyone vote. In this case, we suggest a quadratic voting mechanism to prevent fraud. + - Pros - Other than all the advantages of hackers voting, this can provide greater publicity for projects while further expanding your event's influence in the community.. + - Cons - You need a platform like gitcoin and hackerlink to hold this vote. + + +### 4. Further Improving Your Hacking Experience + +All hackathon organizers would have tons of advice and tips for you to further improve your hackathon and hacking experiences. Some of them are listed below and you are more than welcome to contribute more!! + +- From @Penny (Dorahacks) - If you have 120+ participants, you should consider holding the hack in several separate venues. +- From @Penny (Dorahacks) - A countdown timer would increase the sense of competitiveness. +- From @Momo (Individual) - Water is necessary. And try to take care of people with different eating habits such as vegan or paleo when food is provided. +- Party/Beer +- Workshop +- More to come... + +--- + +## After the Hack +Participants and projects are both valuable rewards of a hackathon. However, we find most of the events neglecting this step, which caused them to miss a great opportunity to expand their community influence or to further develop a project from prototype. + +Thus, we invite all of you to share your event results here. Each folder may or may not include their own contact, participants info, final projects and preparation kits. This can help all the subsequent organizers and would attract more opportunities for all participants as well. + + + diff --git a/_posts/2021-10-29-toolkits.md b/_posts/2021-10-29-toolkits.md new file mode 100644 index 0000000..f72a1f5 --- /dev/null +++ b/_posts/2021-10-29-toolkits.md @@ -0,0 +1,8 @@ +--- +layout: post +title: "Toolkits" +date: 2021-10-29 11:22:44 +0800 +categories: playground +--- + +> Owner: @Peter diff --git a/_posts/2021-10-29-topics.md b/_posts/2021-10-29-topics.md new file mode 100644 index 0000000..84a39a5 --- /dev/null +++ b/_posts/2021-10-29-topics.md @@ -0,0 +1,16 @@ +--- +layout: post +title: "Hacking Topics" +date: 2021-10-29 11:22:44 +0800 +categories: playground +--- + +> Owner: @Momo.Hou + +Just as Eric Raymond said in his article "How To Become A Hacker"(2003): _The world is full of fascinating problems waiting to be solved._ We are invitig all hackers to propose and discuss the most valuable and urgent problems to solve in your focus areas. + +Communication channels and details will be released soon. +Stay tunned!!! + +[Discord]: https://hackerlink.io/ +[HackathonDAO]: https://hackerlink.io/ \ No newline at end of file diff --git a/_posts/2021-10-29-upcoming-hacks.md b/_posts/2021-10-29-upcoming-hacks.md new file mode 100644 index 0000000..77c0289 --- /dev/null +++ b/_posts/2021-10-29-upcoming-hacks.md @@ -0,0 +1,18 @@ +--- +layout: post +title: "Upcoming Hacks" +date: 2021-10-29 11:22:44 +0800 +categories: playground +--- + +> Owner: @Peter + +Here, we are excited to list all the upcoming hackathons (both online and offline) to provide the visibility to all our subsribers and potential readers. This list will at least be updated at a weekly cadence by the playground owner and **if you have a hackathon on schedule, please do add here by submitting a PR to [this repo][repo]**!!! + +| Event | Start Date | End Date | Topic | Link | Contacts | Comment | +|-------|------------|----------|-------|------|----------|---------| +| | | | | | | | +| | | | | | | | +| | | | | | | | + +[repo]: https://github.com/dorahacksglobal/Hackathon-Playbook \ No newline at end of file diff --git a/_posts/2021-10-29-voting.md b/_posts/2021-10-29-voting.md new file mode 100644 index 0000000..262a11b --- /dev/null +++ b/_posts/2021-10-29-voting.md @@ -0,0 +1,37 @@ +--- +layout: post +title: "Voting" +date: 2021-10-29 11:22:44 +0800 +categories: playground +--- + +> Owner: @Momo.Hou + +## Quadratic Voting + +Quoting from "Quadratic Voting: How Mechanism Design Can Radicalize Democracy"(2017): _Quadratic voting is a collective decision-making procedure which involves individuals allocating votes to express the degree of their preferences, rather than just the direction of their preferences._ It is often considered an innovative improvement of the traditional 1-person-1-vote scheme and, as doing so, it can address issues like majority rule. + +The simplified formula is: +``` +cost of the voter = 1 + 2 + 3 + ... + number of votes MATIC +``` + +Quadratic voting hugely promotes the development of hackathon topic selection and prize allocation. With it, community contributors can vote for their favourite topics and/or projects and emphasize their preference with multiple votes. Along with increased cost, of course:-) + +Currently, platforms like [gitcoin][gitcoin] and [hackerlink][hackerlink] can hold quadratic votings. However, [gitcoin][gitcoin] only takes to their own events and [hackerlink][hackerlink] is open to everyone with reasonable application. + + + +## Award Voting in a Hackathon + +This is the a critical part of a hackathon with prizes. We list three frequently used ways as following and you are welcomed to add your own ideas: + +| | Description | Pros | Cons | +|--------------|--------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------| +| Judges vote | Limited number of judges will decide the prizes. | Straightforward and easy to compute. | The final decision could be controversial. | +| Hackers vote | Every participant will get a ticket to vote for their favorite projects and the allocation of the final prize would depend on the tickets count. | This final decision would be decentralized and diversified, and the more teams would be able to share the final prize. | Fraud and collude could happen. | +| Open vote | Let almost everyone to vote. We strongly suggest you to use quadratic voting in this case. | Except for all the advantages of hackers vote, this can provide greater chance to expose the projects and can further expand the impact of your event. | You need a platform to hold this vote. | + + +[gitcoin]: https://gitcoin.co/ +[hackerlink]: https://hackerlink.io/ diff --git a/_posts/2021-10-31-city-guide.md b/_posts/2021-10-31-city-guide.md new file mode 100644 index 0000000..dfdc7c4 --- /dev/null +++ b/_posts/2021-10-31-city-guide.md @@ -0,0 +1,26 @@ +--- +layout: post +title: "Hackers City Guide" +date: 2021-10-29 11:22:44 +0800 +categories: playground +--- + +> Owner: @Momo.Hou + +Here, we want to provide a city guide **customized for hackers** and we are inviting everyone to contribute your own ideas for your own city! The content is unlimited and anything would be informative, benefitial and interesting for hackers would be welcomed! + +## Beijing + +TBD + +---- + +## Shenzhen + +TBD + +---- + +## Denver + +TBD \ No newline at end of file diff --git a/img/.DS_Store b/img/.DS_Store new file mode 100644 index 0000000..a44796e Binary files /dev/null and b/img/.DS_Store differ diff --git a/img/hori_a_color_bg.png b/img/hori_a_color_bg.png new file mode 100644 index 0000000..f9e5a59 Binary files /dev/null and b/img/hori_a_color_bg.png differ diff --git a/index.md b/index.md new file mode 100644 index 0000000..0b81ed0 --- /dev/null +++ b/index.md @@ -0,0 +1,15 @@ +--- +# Feel free to add content and custom Front Matter to this file. +# To modify the layout, see https://jekyllrb.com/docs/themes/#overriding-theme-defaults + +layout: home +title: "Welcome!" +--- + +This is an open-source manual actively maintained by global **hackers** and **hackathon organizers**, trying to capture almost everything you need to know or want to discuss about hackathons. You can participate in all the active discussions on our "[playground][playground]". Enjoy:-) + +And you are more than welcome to contribute by commenting or submitting a PR to [this repo][repo] if you have any suggestions or anything to add. + + +[playground]: https://momohou21.github.io/hackathon-openbook/playground/ +[repo]: https://github.com/dorahacksglobal/Hackathon-Playbook \ No newline at end of file diff --git a/playground.md b/playground.md new file mode 100644 index 0000000..74d6f9e --- /dev/null +++ b/playground.md @@ -0,0 +1,25 @@ +--- +layout: page +title: Playground +permalink: /playground/ +--- + +Here are all the areas that are activly maintained in this openbook. + +- [Hacking Topics][Hacking Topics] +- [Event Planning Guide][Event Planning] +- [Voting and Prize Allocation][Voting and Prize Allocation] +- [Upcoming Hacks][Upcoming Hacks] +- [Toolkit][Toolkit] +- [Hackers City Guide][Hackers City Guide] + +> You are more than welcome to contribute by commenting or submitting a PR to [this repo][repo] if you have any suggestions or anything to add. + +[repo]: https://github.com/dorahacksglobal/Hackathon-Playbook +[Hacking Topics]: https://dorahacksglobal.github.io/Hackathon-Playbook/playground/2021/10/29/topics.html +[Voting and Prize Allocation]: https://dorahacksglobal.github.io/Hackathon-Playbook/playground/2021/10/29/voting.html +[Upcoming Hacks]: https://dorahacksglobal.github.io/Hackathon-Playbook/playground/2021/10/29/upcoming-hacks.html +[Toolkit]: https://dorahacksglobal.github.io/Hackathon-Playbook/playground/2021/10/29/toolkits.html +[Event Planning]: https://dorahacksglobal.github.io/Hackathon-Playbook/playground/2021/10/29/event-planning.html +[Hackers City Guide]: https://dorahacksglobal.github.io/Hackathon-Playbook/playground/2021/10/31/city-guide.html + diff --git a/thedao.md b/thedao.md new file mode 100644 index 0000000..6f7a42f --- /dev/null +++ b/thedao.md @@ -0,0 +1,222 @@ +--- +layout: page +title: Hackathon DAO +permalink: /dao/ +--- + +![hori_a_color_bg.png](/Hackathon-Playbook/img/hori_a_color_bg.png) + +## Vision + +A decentralized community to support global hackathons on meaningful technical problems and innovations. + +## Mission + +To financially and operationally support and free global hackers and hackathon organizers (especially open-source repo maintainers) and let them focus on the real valuable technical issues and improvements. + +## Why Hackathon? Why DAO? + +Ever since the first wave of hackathons in 2010, hackathon has undoubtedly proven its capability of boosting innovation and cooperation. + +- **⚙️To Build** - We see a lot of brilliant ideas and prototypes being developed yet later grow into valuable products, companies and/or technologies in areas like cyber security contests, Internet industry, Web 3.0 applications and so on. +- **📢To communicate** - For those innovative and passionate participants with solid technical skills, hackathons provide them great opportunities to demonstrate their capabilities and projects, exchange ideas, make friends and find partners. + +However, big companies dominated hackathons and the hacker movement in recent years and the voices of grass-root hackers are becoming a comparablely small minority now. Through a decentralized organization of hackers with great technical skills and vision, we want to democratize the hacker movement again, where + +- hackers themselves can propose and decide what is actually the problems to solve. +- hackers can connect with and inspire each other. +- hackers‘ valuable contribution can get proper supports both financially and operationally. + +## Products + +- Hackathon Open Book - a Github Repo +- Gov Forum + snapshot voting - HackerLink BUIDL +- Community Discussion - Discord +- Hackathon List - HackerLink Hackathon + +
+ +---- +
+ +## **Governance Overview** + +Address: 0xFD9F97126EF903872fe96eDE82915f2F2B183da6 + +Hackathon DAO's governance mechanism will revolve around 1) **hackathon grant rules** and 2)**community operation**(on discord). And, with the goal to boost more valuable technical innovations, the mechanism design of Hackathon DAO will try to make sure: + +- the DAO is open for any proposals, yet the community members will vote on whether to approve or reject these proposals. +- the DAO decision represents the will of the community and is controlled by the community. +- the core decision makers in the community are with great tech visions and solid skills. +- the fund and resources mainly go to hackers that make true contribution. + +### **1. Hackathon Grant Rules** + +Our grant will be happening on a quarterly basis and each grant program will last for 3 months. You can see an example timeline for the upcoming 2022Q1 grant. + +| Step | Start Date | End Date | What will be happening | +|-------------|-------------|-------------|------------------------------------------------------------------| +| Application | Jan 01 | Jan 31 | Hackathon proposal submission / Applicants and community meetups | +| Voting | Feb 01 | Feb 07 | Community discussion and voting | +| Hacking | Feb 07 | Mar 21 | Hackathon preparation and online | +| Grant | Mar 21 | Mar 31 | Grant issue and reimbursement | +| Review | Mar 21 | Mar 27 | Hackathon review and project faire | + +Currently, Hackathon DAO will be focusing on three main areas: Web3, Cryptography(ZK) and Quantum Computing(open-source tool and crypto crossover), and we will gradually get more topics involved if we have more credential members from more technical fields in our community. + +### 1.1 Hackathon Application + +A Hackathon proposal needs to be submitted as a BUIDL on HackerLink with all information properly filled. Any hackathon meets the following standards are more than welcomed to apply: + +- The organizer or the organizing team is a maintainer of an active Github repo. +- The organizer or one of the organizing team members has passed Hackathon DAO KYC. +- None of the organizing team is not on the blacklist of Hackathon DAO. +- Hackathon must have a clear and specific problem to solve instead of aimlessly exploring. +- Hackathon must have a budget plan if the grant will be used for anything other than bonus. +- Hackathon needs to be organized ONLY through HackerLink platform using its bounty or hackathon feature. +- Hackathon must happen during the season hacking time window according to the posted agenda. + +### 1.2. Hackathon Vote + +For each season, we will hold a grant for each focus area with an independent funding pool each. The token holders can vote for their preferred hackathon using quadratic voting. All the hackathon proposal will be ranked descending according to the vote and hackathon proposals will be supported according to the rank until no enough funding is available. + +>In short term, the voting will be happening offline within all voting token holders. + +### 1.3. Hackathon Grant Issue + +All the grant will be issued after the hackathon and before the end of the grant season according to calendar date. For different applicants and different uses of funds, we will have different process: + +- **Organizer on Hackathon DAO whitelist** - all fund issue directly +- **Organizer on Hackathon DAO blacklist** - no fund will be issued +- **Organizer neither on whitelist or blacklist** - fund that used for hackathon bonus will be issued after the organizer updating their BUIDL page with the latest updates and getting at least one DAO staff's review. Other logistic cost will be released using reimbursement mode. + +### 1.4. Hackathon DAO Seasonal Faire - Public Vote + +We will hold an public vote using quadratic voting with XXX USDT grant from Hackathon DAO for all the projects submitted from this season’s hackathons, where everyone (in or outside the Hackathon DAO) can vote and show their supports. + +- The bonus received will directly go to the hackers themselves. +- The votes obtained of one hacker/team will be converted into Hackathon DAO credits (HCs) one-to-one. + +### 1.5. Hackathon Review + +By the end of each season, we will have all the supported hackathons evaluated according to their hacking experience, outcome quality and owner's organizing skills. + +All the hackathon organizers will be asked to update their origin application BUIDL page with the latest progress, so that the DAO workers and all the participated hackers of the season can vote according to their preference with more context. + +- **workers votes** (DAO admin and staffs) - each DAO worker will get N votes where N equals to the amount of this seasons' supported hackathons. +- **Hackers votes** (all hackathon participants) - each hacker will get vote(s) according to the number of hackathon he/she participated in the season. One hackathon, one vote. + +The final results will be the sum of **workers‘ votes**, **hackers votes** and **public votes** and will have the following impacts: + +- The votes obtained of one organizer will be converted into Hackathon DAO credits (HCs) one-to-one. +- The organizer that gets both the highest workers' votes, hackers' votes or public votes will be added into the Hackathon DAO whitelist for the next season and removed from blacklist if exists. If there's a tie for first place, all the winning organizers will be added to the whitelist. +- The organizer that violates the community rules and gets reported by more than two DAO worker or hackers will be added into Hackathon DAO blacklist for the next season and removed from whitelist if exists. + +> public votes = the total votes gained of all the submitted projects in the seasonal DAO public vote + +### **2. Community Governance** + +### 2.1. Roles, Responsibilities and Rights + +The Hackathon DAO community will be **a community of active hackathon sponsors and organizers**. What we want to point out in particular is the hackathon organizers we are looking for are great hackers who have great technical vision, solid skills and enthusiasm to boost communicatin and push technological advances. + +- **DAO Funder (token holder)** + - Source: Donors / DoraHacks assigned / Hackathon DAO token holders + - Responsibilities & Rights: + - All Discord channels are open for them. + - Discuss and vote for hackathon proposals. +- **Hackathon Organizer** + - Source: Hackathon DAO grant applications + - Responsibilities & Rights: + - All Discord channels are open for them except for the funders' channel. + - Submit Hackathon proposals. + - Actively update the proposals with the latest progress. + - Share their experience and knowledge about hackathon through Hackathon Openbook. +- **DAO Staff** + - Source: Volunteers after interview / DoraHacks assigned + - Responsibilities & Rights: + - All Discord channels are open for them. + - Actively update the announcement Discord channels with the latest Hackathon DAO progress and agenda. + - Actively maintain the Discord channel of his/her own focus area. + - Organize community activities like Hackathon roadshow, project demo show and tech meetups, talks, workshops, etc. + - Assist hackathon events through hackathon proposal reviewing, hackathon result reviewing, Hackathon DAO product Q&A, reimbursement, etc. +- **Developer** + - Source: Applicants after KYC + - Responsibilities & Rights: + - Only announcement, topic and show room channels are available for them. + - Participate in community activities like Hackathon roadshow, project demo show and tech meetups, workshops, etc. + +### 2.2 Reputation System - Hackathon DAO Credit + +In Hackathon DAO community we want to use "Hacking Credits"(HCs) to reflect a memeber's credibility, community contribution and technical ablity. + +**Who Can Gain the Credits** +- Anyone in the Hackathon DAO community. +- The default credits for all members will be zero. + +**How to Gain the Credits** +- Submit hackathon proposal to Hackathon DAO, get granted and get votes in the seasonal final review. The votes obtained of one organizer will be converted into Hackathon DAO HC one-to-one. +- Submit projects in Hakcathon DAO supported hackathon(s) and get votes in the seasonal project faire. The votes obtained of one hacker/team will be converted into Hackathon DAO HC one-to-one. +- Hold technical events like meetups, talks and workshops can get 1-5 HC(s) depending on the quality and performance of the event. The amount issued will be decided by the DAO staffs depending on the audiences' feedback. + +**How to Use the Credits** +- The community can use the organizer' HCs as a reference when evaluate hackathon proposals in future seasons. +- The HCs can be exchanged into DAO voting tokens under a one-to-X ratio for the whitelisted members, so that those trustworthy and active members with solid technical skills can join the core decision making progress of grants. + +### 2.3. Community Rules + +**Gating rules** +- All members must pass KYC before joining. +- One can join as an organizer after submitting Hackathon DAO grant application or get validated by at least one DAO admin or staff with previous hackathon organizing experiences. +- One can join as an DAO funder by providing prove of holding Hackathon DAO token and this channel will be actively maintained by staffs according to the latest token holders. +- If a member gets reported by more than 3 other members in the community, this member will be added into Hackathon DAO blacklist and removed from our Discord server. + +**Generic rules** +- Respect each other - hate speech, racism, homophobia, bullying or toxic behavior are not tolerated. +- No controversial topics - this includes, but is not limited to politics, religion, or other heavy subjects. +- No spam - this includes, but is not limited to posting unapproved advertising, excessive pings, emote or image spam, abusing spoiler tags, malicious links, etc. +- No fraud - this includes, but is not limited malicious cash out, collision, plagiarism or account stealing. +- Keep discussions relevant to the channel topic. Each channel's description tells you the topic. +- Interfering with staff’s duties by arguing, misinforming them or giving false evidence is forbidden. + +### 2.4. Discord + +**Channel Structure** +- **Information** + - Welcome! + - Rules + - Help + - Introduce yourself +- **Announcement Channel** + - Upcoming hackathons + - Upcoming events + - Hackathon DAO grant updates and agenda reminder + - Hackathon Openbook updates +- **Topics** + - Web3 + - Cryptography + - Quantum Computing + - ... +- **Show Room** (for events like hackathon road shows, hackathon projects demo show, organizers' meetup live, talks, workshops, etc.) +- [private for funders] **DAO token holders** +- [private for organizers] **Hackathon Open Book** + +
+ +--- +
+ +## **Additional Notes** + +### **1. Notes** + +1. Hackathon DAO funds will be used ONLY to support hackathons and will not be used for product developing, community operation or staff salary. +2. All the cost other than hackathons grants will be supported by DoraHacks. +3. The governance of DAO does not involve the election of any DAO members. staff is directly delegated and managed by DoraHacks, but it needs to be managed in accordance with DAO's governance rules. +4. The funding of Hackathon DAO is completed by Hackathon DAO in the multi-signature wallet of Gnosis SAFE, and the multi-signature wallet is fully controlled by the results of community governance. +5. The current governance rules do not require the use of Snapshot and non-HackerLink voting tools. +6. Other possible governance rules in the future: For a single Hackathon Grant funding, use Futarchy for community voting. These governance rules are currently not considered. + +### **2. References** + +1. Decentralize The Hacker Movement by @ericzhagn90