{"action":"closed","issue":{"url":"https://api.github.com/repos/techx/quill/issues/64","repository_url":"https://api.github.com/repos/techx/quill","labels_url":"https://api.github.com/repos/techx/quill/issues/64/labels{/name}","comments_url":"https://api.github.com/repos/techx/quill/issues/64/comments","events_url":"https://api.github.com/repos/techx/quill/issues/64/events","html_url":"https://github.com/techx/quill/issues/64","id":294498121,"number":64,"title":"Using QR Codes to track hacker activity","user":{"login":"SaltyQuetzals","id":15918436,"avatar_url":"https://avatars0.githubusercontent.com/u/15918436?v=4","gravatar_id":"","url":"https://api.github.com/users/SaltyQuetzals","html_url":"https://github.com/SaltyQuetzals","followers_url":"https://api.github.com/users/SaltyQuetzals/followers","following_url":"https://api.github.com/users/SaltyQuetzals/following{/other_user}","gists_url":"https://api.github.com/users/SaltyQuetzals/gists{/gist_id}","starred_url":"https://api.github.com/users/SaltyQuetzals/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/SaltyQuetzals/subscriptions","organizations_url":"https://api.github.com/users/SaltyQuetzals/orgs","repos_url":"https://api.github.com/users/SaltyQuetzals/repos","events_url":"https://api.github.com/users/SaltyQuetzals/events{/privacy}","received_events_url":"https://api.github.com/users/SaltyQuetzals/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":2,"created_at":"2018-02-05T18:37:58Z","updated_at":"2018-02-07T17:37:29Z","closed_at":"2018-02-07T17:37:29Z","author_association":"NONE","body":"There's a lot of untapped data in hackathons that can be utilized if, in addition to (or instead of) using paper IDs distributed at the beginning of the event, users had QR codes that could be scanned. This could help determine which events are popular among hackers, which sponsors are the most popular (and should return the next year), who has had their meals and who hasn't, and, depending on how in-depth you want to be, you can get data on all kinds of activities, determining which snacks are the most popular, etc.\r\n\r\n## Event Popularity Tracking\r\nAt a mini event (say, a typing competition) supervising organizers/staff members open a link on Quill that requests access to their camera. Once granted, they are able to scan hackers who want to participate. This tracks the popularity of the typing competition, and indicates whether it should make an appearance next year.\r\n\r\n## Sponsor Popularity Tracking\r\nSimilarly to the example above, a sponsor representative could open a link that requests access to their camera, and once granted, they're able to scan QR codes of hacker who are interested in networking or just making conversation. This is a mutually-beneficial situation as well, as sponsors could maybe view the hacker's resume after scanning the code, and the event organizers can track which sponsors are popular and should make a reappearance.\r\n\r\n## Meal Tracking\r\nMeal tracking is an interesting application of this system. Rather than checking boxes on a paper ID (which costs money to produce), users could have their codes scanned when getting a meal, which \"checks\" their meal off. Another application of the code scanning would be optimizing dietary restriction ordering. If 20 people indicate that they want a vegetarian option, and 30 people over the course of the event scan in at the vegetarian line, maybe next year, more vegetarian meals could be ordered.\r\n\r\nSome people might have qualms with their data being tracked, so it could be an opt-in system."}}
{"actor":{"display_login":"SaltyQuetzals"}}