├── README.md ├── apis.md ├── checklist.md ├── getting-started.md ├── judging-protocol.md ├── judging.md ├── opentable ├── documentation-explorer.png ├── graphiql-intellisense.png ├── graphql-quickstart.md ├── restaurant-with-cuisines-query.png └── simple-restaurant-query.png ├── schedule.md └── teams.md /README.md: -------------------------------------------------------------------------------- 1 | ![Reactathon Logo Header](http://i.imgur.com/4SWixbw.png) 2 | 3 | # Hackathon Rules & Guidelines 4 | Please read this in its entirety, including the other files. It includes specific instructions to get set up. 5 | ## Code of Conduct 6 | By attending the hackathon, you affirm that you have read and agree to our Code of Conduct, and you will abide by its guidelines laid out here: http://jsconf.com/codeofconduct.html 7 | 8 | ## Purpose 9 | The Hackathon is designed to be a fun, casual, and educational environment. There will also be competition for prizes, but our main goal is education, building community, and learning to use some cool APIs and technologies. We will have tutors and volunteers to assist with your questions if you need help. 10 | Thanks to OpenTable for their sponsorship, we will provide you with lunch on Saturday, and lunch + dinner on Sunday. GitHub will be providing us with beer and wine on Sunday evening. 11 | 12 | ## Location 13 | GitHub HQ 14 | 88 Colin P Kelly Jr St, 15 | San Francisco, CA 94107 16 | 17 | ## Team Size 18 | * Max team size: 7 19 | * Recommended team size: 2-5 20 | 21 | ## Review the APIs 22 | Review the APIs in the `apis.md` file in this repo. 23 | Here you'll find lists of APIs with links to docs, tutorials, and a video overview 24 | 25 | ## Join the Reactathon Slack Group 26 | Sign up here http://bit.ly/reactathon2017-slack 27 | ##### More info: 28 | * You can ask API sponsors questions directly in their respective channel, i.e. `api_opentable` 29 | * View API introductions (30 secs) and demos (<5 mins) in their respective channels 30 | * Pay special attention to `announcements` channel. Do not post here. 31 | * Ask questions about certain technologies in the `q-and-a-` channel 32 | * Have general communication in the `general` channel 33 | * Find a teammate or a team in the `team-formation` team 34 | 35 | ## Team Formation 36 | #### If you have a team 37 | 1. List your team in the `teams.md` file in this repo 38 | 2. Fork the repo and make a PR to list your team 39 | 3. Follow the style guide for listing your team 40 | 4. Tag `BerkeleyTrue` in your PR. 41 | 42 | #### If you don't have a team 43 | 1. Browse teams in the `teams.md` file of this repo 44 | 2. Contact team members via Slack or in-person on Saturday morning 45 | -------------------------------------------------------------------------------- /apis.md: -------------------------------------------------------------------------------- 1 | # APIs 2 | Listed here are the APIs for your use. 3 | * Browse the APIs here. Visit docs etc. 4 | * Meet with the API sponsors at the hackathon, particularly on Saturday morning 5 | * Communicate with the API sponsors via their [dedicated slack channel](http://bit.ly/reactathon2017-slack) 6 | 7 | 8 | # OpenTable 9 | #### Quick Description 10 | OpenTable is a leading marketplace for restaurants and diners. We love creating amazing dining experiences and we are expanding globally and across the dining space. 11 | 12 | ### Purpose 13 | OpenTable’s public API is a means to search for restaurants, availability slots, make reservations, modify or cancel reservations. There are two key forms of public API: 14 | 15 | ##### REST API endpoint: 16 | A more comprehensive API supporting all features required for interacting with OpenTable. 17 | 18 | ##### Graph QL endpoint (Alpha): 19 | A work in progress endpoint that provides information on restaurants, cuisines, offers etc. Transaction level capabilities are not yet available at this endpoint. 20 | 21 | ### Challenge 22 | We are looking for creative ideas and prototypes that are built using React family of technologies leveraging the public APIs thereby providing or enhancing the value for our diners. 23 | 24 | ### Docs 25 | 26 | ##### 1. REST API 27 | Functionalities exposed by token(Please refer documentation for details) 28 | 1. Get restaurant listings 29 | 2. Provision 30 | 3. Single/multi search 31 | 4. Make Reservation 32 | 5. Cancel reservation 33 | 6. Get Reservation 34 | 7. Promotions and offers 35 | 36 | Visit [this](https://platform.otqa.com/documentation/secure) link with the following credentials 37 | ```` 38 | PP Client ID / User Id : cpa_5069 39 | PP Secret / Password: aMrmcXH4BuUlLIyN6paPhseSlrzMh6Lz 40 | ````` 41 | Documentation [here](https://platform.otqa.com/documentation/secure) 42 | 43 | Step 1: Get an access token: 44 | 45 | ```` 46 | curl --user cpa_5069:aMrmcXH4BuUlLIyN6paPhseSlrzMh6Lz -X POST https://oauth-pp.opentable.com/api/v2/oauth/token?grant_type=client_credentials 47 | ```` 48 | 49 | Step 2: Access the API. This example gets availability for restaurant with id - 334879 50 | 51 | ```` 52 | curl -i -X GET -H "Content-Type:application/json" -H "Authorization:bearer TOKEN" "https://platform.otqa.com/availability/334879?start_date_time=2017-03-29T18%3A00&party_size=2&forward_minutes=120&backward_minutes=30" 53 | ```` 54 | 55 | where TOKEN - is the value you retrieve from step 1. 56 | 57 | You can get a list of all RIDs that are availability for this user ID through this api: 58 | 59 | ```` 60 | curl -i -X GET -H "Content-Type:application/json" -H "Authorization:bearer TOKEN" 'https://platform.otqa.com/sync/listings' 61 | ```` 62 | 63 | Lat/long based search: 64 | 65 | ```` 66 | https://platform.otqa.com/availability?latitude=42.360082&longitude=71.058880&party_size=2&radius=200&forward_minutes=180&backward_minutes=30&start_date_time=2017-03-13T20%3A00&include_unavailable=true 67 | ```` 68 | 69 | IMPORTANT NOTE: Replace *.opentable.com with *.otqa.com 70 | 71 | 72 | Few other RIDs that have availability info: 334879, 73 | 334882, 74 | 334885, 75 | 334888, 76 | 334891, 77 | 334894, 78 | 334897, 79 | 334900, 80 | 334903. 81 | 82 | ##### 2. Graph QL Endpoint(Alpha): 83 | 84 | Quickstart - [here](./opentable/graphql-quickstart.md) 85 | 86 | https://www.opentable.com/graphiql – For the API explorer 87 | https://www.opentable.com/graphql – The API endpoint 88 | 89 | Getting started with 90 | 91 | ### Video tutorial 92 | ##### 1. REST API: 93 | Not available yet. 94 | ##### 2. Graph QL API: 95 | [Youtube video link](https://www.youtube.com/watch?v=CNL_cgNsJEc) 96 | 97 | ### Prizes 98 | (Depending on the value of the product and number of winners) 99 | Xbox One S 500GB Console - Battlefield 1 Bundle 100 | Chrome Citizen Messenger Bag Black/Red, One Size 101 | Amazon Tap - Alexa-Enabled Portable Bluetooth Speaker 102 | 103 | *** 104 | 105 | # Netlify 106 | #### Quick Description 107 | Netlify provides [Continuous Delivery](https://www.netlify.com/docs/continuous-deployment), 1-click HTTPS, [Custom Domains](https://www.netlify.com/docs/custom-domains/), integrated prerendering, and a custom global CDN. 108 | 109 | ### Purpose 110 | [Progressive Web Apps](https://developers.google.com/web/tools/lighthouse/) are user experiences that are fast, secure, and engaging. Netlify helps you get there with our asset optimization and free SSL integration. 111 | 112 | Netlify improves your workflow with Deploy Previews that work by deploying every pull request from your git repository to a unique URL; completely different from the one your main site uses. You and your team can see how those changes look before they’re merged into the main branch and deployed to production. 113 | 114 | To help you discover Deploy Previews, we put those links where it helps your team the most, directly in the pull request as commit statuses: 115 | 116 | ![](https://cdn.netlify.com/4d4d418736774eaea776b4ab08ee07af4a0bc5a9/c6be8/img/blog/deploy-preview-success.png) 117 | 118 | We keep this preview up to date as you continue to work, committing new changes to the same branch. Our CDN takes care of invalidating the cache every time for you. 119 | 120 | ### Challenge 121 | We are looking for the most interesting apps leveraging the [JAMstack](https://jamstack.org/) and have a high [PWA](https://developers.google.com/web/tools/lighthouse/) rating on Google's [Lighthouse](https://jamstack.org/). All projects considered will need to be deployed to Netlify and with [Deploy Previews](https://www.netlify.com/blog/2016/07/20/introducing-deploy-previews-in-netlify/) enabled. 122 | 123 | ### Docs 124 | http://netlify.com/docs 125 | 126 | ### Video tutorial 127 | - [Getting Started with the UI](https://www.youtube.com/watch?v=9sfTsX03UgI&t=4s) 128 | - [Getting Started via the CLI](https://www.youtube.com/watch?v=vFtvhvgmgZE) 129 | 130 | ### Prizes 131 | $300 + Chromecast & Color-Changing Bluetooth Speakers 132 | 133 | *** 134 | 135 | 136 | # Serverless 137 | #### Quick Description 138 | 139 | **The Serverless Framework** – Build applications comprised of microservices that run in response to events, auto-scale for you, and only charge you when they run. This lowers the total cost of maintaining your apps, enabling you to build more logic, faster. 140 | 141 | The Framework uses new event-driven compute services, like AWS Lambda, Google CloudFunctions, and more. It's a command-line tool, providing scaffolding, workflow automation and best practices for developing and deploying your serverless architecture. It's also completely extensible via plugins. 142 | 143 | Serverless is an MIT open-source project, actively maintained by a full-time, venture-backed team. 144 | 145 | ### Purpose 146 | 147 | The framework was created to help developers focus on writing their application code rather than maintaining or scaling servers. 148 | 149 | ### Challenge 150 | We are looking for the most interesting apps leveraging the [Serverless Framework](https://serverless.com/framework/docs/). 151 | 152 | All projects considered will need to have a least one serverless function deployed via the framework! 153 | 154 | Stop by our table if you need help! 155 | 156 | ### Docs 157 | [Docs link](https://serverless.com/framework/docs/) 158 | 159 | ### Video tutorial 160 | 161 | [About the Serverless framework](https://www.youtube.com/watch?v=bFHmgqbAh4M) 162 | 163 | [Getting Started](https://www.youtube.com/playlist?list=PLIIjEI2fYC-C3NJF7a4-Cvh5hjdCmrVmN) 164 | 165 | [Setting up your AWS account for Serverless](https://www.youtube.com/watch?v=HSd9uYj2LJA) 166 | 167 | [Building a rest API](https://www.youtube.com/playlist?list=PLIIjEI2fYC-B0QxvWI6XnRB_ze0m0BKUj) 168 | 169 | ### Prizes 170 | 171 | - Amex gift card ($700) split between the team members 172 | 173 | *** 174 | 175 | # Overall Winners 176 | #### The top 6 teams will present to a panel of judges including representatives from Real World React, OpenTable, and Netlify. 177 | Note: "Overall" winners are separate from the "API winners". Each API sponsor will have their own challenges and prizes. 178 | 179 | ### Prizes 180 | * X Box One 181 | * Playstation 4 182 | * Smart TV 183 | * Chrome messenger bag 184 | * Amazon Echo Dot 185 | * Google Home 186 | * Roost Laptop Stands 187 | * Chromebook 188 | * Tickets to React Conf 189 | -------------------------------------------------------------------------------- /checklist.md: -------------------------------------------------------------------------------- 1 | # Hackathon Checklist 2 | 3 | - [ ] Make sure that you have an Eventbrite ticket 4 | - [ ] Sign up for the [Reactathon Slack Group](https://reactathon2017.slack.com/shared_invite/MTQ5MDc5ODc5MzkzLTE0ODg2NDYyMjMtN2FmZDRiYWE5Yw) 5 | - [ ] If applicable, add your team to the list at `teams.md` in this repo 6 | - [ ] Review the `README.md` file for further instructions and guidelines 7 | - [ ] Review the APIs on `apis.md` in this repo 8 | - [ ] Ask questions to API sponsors directly on their slack channel (i.e. `api_opentable`) 9 | - [ ] Bring a refillable water bottle 10 | - [ ] **IMPORTANT: BRING A POWER STRIP** to use and share with others! We recommend putting tape on it to write your name 11 | -------------------------------------------------------------------------------- /getting-started.md: -------------------------------------------------------------------------------- 1 | # Getting Started 2 | **If you want to learn the tools and resources necessary to be successful at this hackathon, consider attending one or more [workshops](https://realworldreact.eventbrite.com) to level up your skils.** 3 | Here are some tools and resources to help you get started: 4 | ## Docs 5 | 1. Beginners: [Thinking in React](https://facebook.github.io/react/docs/thinking-in-react.html) 6 | 2. Beginners: [ES6 Guide](https://mrzepinski.gitbooks.io/es6-guide/content/) 7 | 3. Beginner - Advanced: [Official React Docs](https://facebook.github.io/react/docs/hello-world.html) 8 | 4. Intermediate: [Official Redux Docs](http://redux.js.org/) 9 | 5. Advanced: [Intro to Reactive Programming](https://gist.github.com/staltz/868e7e9bc2a7b8c1f754) 10 | 6. Advanced: [RxJS Exercises](http://reactivex.io/learnrx/) 11 | 12 | ## Boilerplates 13 | Boilerplates are great to get started, and to learn how someone uses certain tech and architects in a specific way. However, since you didn't make these choices on your own, you lose the education of _why_ someone chose to build their app in this manner, and it may actually slow you down or frustrate you in the long run. 14 | **TLDR:** Boilerplates are great for hackathons, bad for production. Use with caution. 15 | ### 1. [Create-React-App](https://github.com/facebookincubator/create-react-app) 16 | This is the official boilerplate created by members of the React Core Team at Facebook with the help of open-source contributors. It is the easiest of all boilerplates, as it hides most of the configuration files to narrow your focus. You can get started in the CLI with: 17 | ``` 18 | npm install -g create-react-app 19 | create-react-app my-app 20 | cd my-app/ 21 | npm start 22 | ``` 23 | Create-React-App helps you to create a React project without worrying too much about configuration. To customize your boilerplate, you can "eject". Learn more about this and other features of create-react-app here https://github.com/facebookincubator/create-react-app 24 | 25 | ### 2. [React Static Boilerplate](https://github.com/iansinnott/react-static-boilerplate) 26 | We recommend this boilerplate, or something similar, especially if you're looking to use the APIs **Serverless** and **Netlify**. 27 | As with any boilerplate, it is opinionated. Fortunately the docs have descriptions and benefits of each of these choices, and you can easily change them, if you know what you're doing. If you're not comfortable with ES6, configuring webpack, architecting a React app, or controlling state with Redux, we recommend that you sign up for one of our [workshops](https://realworldreact.eventbrite.com). 28 | 29 | ### 3. [GraphQL Hackathon Kit](https://github.com/apollographql/react-graphql-hackathon-kit) 30 | If you've been itching to try out GraphQL, this kit gives you a `create-react-app` client and GraphQL server to start playing around with. The kit includes information in the READMEs about how the different components fit together, and how you can extend them to build the hackathon app of your dreams. 31 | -------------------------------------------------------------------------------- /judging-protocol.md: -------------------------------------------------------------------------------- 1 | # Judging Protocol & Schedule 2 | 3 | ### API Sponsors 4 | If you are using one of the sponsored API's/Services, please list your project [here](https://docs.google.com/spreadsheets/d/1-_5Eqf50zVhewO-NVNBrYfEV_L3rRCi_GtlMZVtcex0/edit?usp=sharing) 5 | 6 | ## Qualifying Pitches 7 | **3:00 - 5:00pm, Main Stage** 8 | 9 | * 2 minutes, **hard stop** 10 | * 1 minute Q + A 11 | * Bring your laptop or phone to demo 12 | * We recommend practicing your pitch. Cut out any fluff. 13 | * Arrive to stand in line at least 5 minutes before your scheduled start time. 14 | * Ensure that your demo is ready & working; you will not get another chance. 15 | * Got slides? Sure, that's ok. But likely only working prototypes will advance you to the next round 16 | 17 | 18 | Review where you are on the schedule here: **Posted at 2:00pm** 19 | 20 | We are using the US Navy Observatory Master Clock for time. If you're on a Mac, you should be synced to this, but it's worth verifying to make sure: 21 | http://www.usno.navy.mil/USNO/time/display-clocks/simpletime 22 | 23 | **If you are not present for your scheduled presentation, you will be disqualified from overall prizes/presentations.** 24 | 25 | #### The top 6 teams will move on to present on a judging panel, where we will discuss your project on video for around 10 minutes. 26 | 27 | Note that the top 6 teams are contending for the *overall* hackathon winers. API sponsors may opt to select winners outside of this top 6. 28 | 29 | **The top 6 teams will be present and take questions on video, which will be streamed to the televisions throughout the GitHub office. If you do not wish to be on video, you can opt to not join your team in your presentation.** 30 | 31 | ## Top 6 Teams Panel 32 | **5:30 - 6:30** 33 | 34 | Winners will be announced in the Slack channel #announcements around 5:00pm. 35 | 36 | ## Any commits after 6:00pm will disqualify you from overall prizes and presentations 37 | 38 | ## Dinner, Beer, & Wine 39 | **6:00** 40 | 41 | This is your time to stop coding, chill, eat, and watch the top 6 teams show off their projects on video 42 | 43 | 44 | ## Special Presentation 45 | **6:45, Main Stage** 46 | #### "React is a Business Decision" 47 | Ian Sinnott, Senior Engineer at TruStar 48 | 49 | ## Top 3 Teams Presentation 50 | **7:20, Main Stage** 51 | 52 | The top three teams will deliver 7-minute presentations on stage 53 | 54 | ## API Awards 55 | **7:45, Main Stage** 56 | 57 | API Sponsors will announce the winners of their prizes 58 | 59 | ## Overall Awards 60 | **8:00, Main Stage** 61 | 62 | The top 3 teams (presenting top 3) will be awarded their prizes. 63 | 64 | ## Mingling 65 | **8:10 - 9:00** 66 | 67 | Feel free to stick around and mingle for an hour or so 68 | 69 | 70 | # A note on time 71 | 72 | Once we get into the swing of things, actual times such as the API Awards and Presentations may vary. Please note that time for your **Qualifying Pitch** will **not** vary. 73 | 74 | # Top 3 Presentations: Presentation Guideline 75 | This is a guideline only, feel free to deviate as you wish 76 | 77 | ### The Setup (1 Min) 78 | Introduce: 79 | * Yourself 80 | * The Problem 81 | * The Solution 82 | 83 | ### The Demo (4.5 min) 84 | #### Your Product 85 | * Why it solves the problem 86 | * How it solves the problem 87 | * Show off your product 88 | * How you're using specific API's or services 89 | 90 | ### The Tech (1 minute) 91 | * What technologies did you use to build this? 92 | * What challenges did you face while building this? 93 | * How did you overcome those challenges? 94 | 95 | ## The Sign-off 96 | * Briefly: The problem 97 | * Briefly: Why your product solves it 98 | * Who you are and contact info, if desired 99 | -------------------------------------------------------------------------------- /judging.md: -------------------------------------------------------------------------------- 1 | # Rules 2 | If you are competing for prizes, you must: 3 | 4 | 1. Use React or React Native in a significant capacity 5 | 2. Max team size: 7 (Recommended team size: 2-5) 6 | 3. Abide by our code of conduct 7 | 8 | # Judging Criteria 9 | Your project will be judged on: 10 | 11 | 1. Project intrigue/novelty 12 | 2. Product Design & Functionality 13 | 3. Presentation/Pitch 14 | 15 | # No prizes 16 | If you don't want to compete for prizes, feel free to build whatever you want, with whatever technologies you want, and with a team as big as you'd like. 17 | -------------------------------------------------------------------------------- /opentable/documentation-explorer.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/realworldreact/reactathon2017/6d6420c1b8bbf4a1e79712850d0a04fcfa1b406b/opentable/documentation-explorer.png -------------------------------------------------------------------------------- /opentable/graphiql-intellisense.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/realworldreact/reactathon2017/6d6420c1b8bbf4a1e79712850d0a04fcfa1b406b/opentable/graphiql-intellisense.png -------------------------------------------------------------------------------- /opentable/graphql-quickstart.md: -------------------------------------------------------------------------------- 1 | The best way to learn how GraphQL works is to try it out. Let's start by playing with GraphiQL, a powerful developer tool for testing out queries: 2 | 3 | [https://www.opentable.com/graphiql](https://www.opentable.com/graphiql) 4 | 5 | Copy the following query into the editor and hit the execute button: 6 | 7 | ```graphql 8 | { 9 | restaurant(restaurantId: 1906) { 10 | name 11 | } 12 | } 13 | ``` 14 | 15 | You should get a JSON response which matches your query: 16 | 17 | ![Simple restaurant query](./simple-restaurant-query.png) 18 | 19 | Let's extend our restaurant query to get a feel for the GraphiQL editor; try pressing Ctrl-Space after the restaurant name to see what fields are available: 20 | 21 | ![GraphiQL intellisense](./graphiql-intellisense.png) 22 | 23 | How about getting the restaurant cuisines: 24 | 25 | ```graphql 26 | { 27 | restaurant(restaurantId: 1906) { 28 | name 29 | cuisines { 30 | name 31 | } 32 | } 33 | } 34 | ``` 35 | 36 | After executing the query you will see a list of cuisines for the restaurant: 37 | 38 | ![Restaurant with cuisines query](./restaurant-with-cuisines-query.png) 39 | 40 | GraphiQL's intellisense feature is an excellent way to discover the capabilities of a GraphQL API, but it's also worth taking a look at the Documentation Explorer by clicking on the "Docs" button in the top right corner: 41 | 42 | ![GraphiQL documentation explorer](./documentation-explorer.png) 43 | 44 | Have a play with the API, explore the schema and see what queries you can write. If you get stuck try adapting the following complex query: 45 | 46 | ```graphql 47 | { 48 | restaurant(restaurantId: 1906) { 49 | name 50 | cuisines { 51 | name 52 | } 53 | priceBand { 54 | name 55 | } 56 | country { 57 | name 58 | } 59 | metro { 60 | name 61 | } 62 | macro { 63 | name 64 | } 65 | neighborhood { 66 | name 67 | } 68 | messages { 69 | standardMessages { 70 | confirmation { 71 | message 72 | } 73 | } 74 | } 75 | menus { 76 | title 77 | sections { 78 | items { 79 | title 80 | } 81 | } 82 | } 83 | reviews(offset: 0, limit: 2) { 84 | description 85 | rating { 86 | overall 87 | } 88 | } 89 | } 90 | metro (metroId: 4) { 91 | name 92 | pointsOfInterest { 93 | name 94 | } 95 | } 96 | } 97 | ``` 98 | 99 | Learn more here: 100 | * [http://graphql.org/](http://graphql.org/) - A great high level overview as well as detailed documentation on writing queries. 101 | * [https://github.com/chentsulin/awesome-graphql](https://github.com/chentsulin/awesome-graphql) - The go to resource for everything that's going on in the GraphQL community. 102 | * [http://dev.apollodata.com](http://dev.apollodata.com) - A client library for GraphQL with excellent React.js support. -------------------------------------------------------------------------------- /opentable/restaurant-with-cuisines-query.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/realworldreact/reactathon2017/6d6420c1b8bbf4a1e79712850d0a04fcfa1b406b/opentable/restaurant-with-cuisines-query.png -------------------------------------------------------------------------------- /opentable/simple-restaurant-query.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/realworldreact/reactathon2017/6d6420c1b8bbf4a1e79712850d0a04fcfa1b406b/opentable/simple-restaurant-query.png -------------------------------------------------------------------------------- /schedule.md: -------------------------------------------------------------------------------- 1 | # Schedule 2 | 3 | ### Update: Day 2 has been revised. See judging-protocol.md for more info 4 | 5 | Note: This schedule is a guideline. Actual times may vary. Watch for announcements in the slack channel `announcements`. 6 | ## Saturday, March 11 7 | 9:00 - Doors open 8 | 9:00 - 10:00 - Check-in, coffee, mingle & form teams 9 | 10:00 - 10:45 - Welcome + Keynote (Main Stage) 10 | 10:45 - 1:00 - Hacking 11 | 1:00 - Lunch 12 | 1:00 - 6:30 - Hacking 13 | 6:30 - 7:00 - Closing Talk (Main Stage) 14 | 7:00 - 8:00 - Mingling 15 | 8:00pm - Doors close 16 | 17 | ## Sunday, March 12 18 | 9:00 - Doors open 19 | 9:00 - 10:00 - Check-in, coffee 20 | 10:00 - 10:45 - Welcome + Keynote (Main Stage) 21 | 10:45 - 12:30 - Hacking 22 | 12:30 - Lunch 23 | 1:00 - 6:30 - Hacking 24 | 3:00 - 4:30 - ~~Judges meet each team at their work station, hear pitches (3 minutes)~~ 25 | 4:30 - 5:30 - Judges decide top 6 teams, no order 26 | 5:30 - 6:30 - Judges interview top 6 teams for video 27 | 6:30 - Dinner 28 | 7:00 - 7:30 - Top 3 teams present (Main Stage) 29 | 7:30 - 8:00 - API Awards Announced 30 | 8:00 - 8:15 - Top 3 teams Awards Announced 31 | 8:15 - 9:30 - Mingling 32 | 10:00pm - Doors close 33 | -------------------------------------------------------------------------------- /teams.md: -------------------------------------------------------------------------------- 1 | # Hackathon Teams 2 | 3 | ### Create a PR and tag `@BerkeleyTrue` in the comments of that PR. 4 | 5 | STYLE GUIDE: 6 | ``` 7 | # Team name 8 | ### Less than 160 Characters describing what we're building. Include external links here if desired 9 | * Teammates: csv with your Reactathon Slack username. Get that [here](https://reactathon2017.slack.com/shared_invite/MTQ5MDc5ODc5MzkzLTE0ODg2NDYyMjMtN2FmZDRiYWE5Yw) 10 | * Seeking Teammates: Yes/No 11 | * [Project URL](https://github.com/your-profile/your-project-name) 12 | 13 | *** (be sure to include these three stars at the bottom for a horizontal rule) 14 | ``` 15 | *** 16 | 17 | # The Style Guide Exemplifiers 18 | ### We're a team that exists solely to show you how to edit this document. Fork this repo and make a PR to add your team at the bottom of the list! 19 | * **Teammates**: Benjamin Dunphy (@ben), Berkeley Martinez (@berkeley) 20 | * **Seeking Teammates**: No 21 | * [GitHub URL](https://github.com/your-profile/your-project-name) 22 | 23 | *** 24 | 25 | # TeamNoSleep 26 | ### We're a team that will make something awesome. 27 | * **Teammates**:Blake Wills (@baw25), John Kim (@soctkoren), Hyungjoon Kim (@Nubstick27), Julian Knodt (@julianknodt) 28 | * **Seeking Teammates**: We're set! 29 | * [GitHub URL] (https://github.com/Baw25/TeamNoSleepReactathon2017) 30 | 31 | *** 32 | 33 | # Raging Octopus 34 | ### Building seamless voice integration on top of the OpenTable API. 35 | * **Teammates**: Andrew Lee (@alee), Cyril Yu (@cyril), Jeff Christian (@15chrjef), Sherman Chen (@shermanc), Steve Zhou (@stevezhou) 36 | * Seeking Teammates: No 37 | * [GitHub URL](https://github.com/ragingoctopus/reactathon-ot) 38 | 39 | *** 40 | 41 | # WillCode4Food 42 | ### We're a team that will do whatever it takes to feed us and we're building something cool. 43 | 44 | * **Teammates**: Bryan Nguyen (@bryancnguyen), Bryan Garcia (@bryang), Nicole Zhou (@nicolezhou), Andrew Cordivari (@andrew_cordivari), Edmund Dao (@nimda), Eric Oliveira (@clapinton) 45 | * **Seeking Teammates**: Absolutely yes! 46 | * [GitHub URL] (https://github.com/Bryancnguyen/WillCode4Food) 47 | 48 | *** 49 | 50 | # Unravel Project 51 | ### Making Angular extinct one repo at a time. 52 | * **Teammates**: Zak (@zakarhino), Chris (@battenfield), Zack (@zsnydr), Sevda (@@astelvida), Sammi (@sammicodekat), Romain (@Talu58) 53 | * **Seeking Teammates**: No 54 | * [GitHub URL](https://github.com/unravel-project) 55 | 56 | *** 57 | 58 | # iReact 59 | ### Keep calm and React 60 | * **Teammates**: David Lopez-White (@davidlopezwhite), Vadim Dermanovskiy (@noodly), Trevor Scandalios (@scandalios), Howard Co (@hco), Joanne Xin (@joannexin), Jun Xiang (@junxiang), Sean Chen (@chenmeister) 61 | * **Seeking Teammates**: No 62 | * [GitHub URL](https://github.com/DavidLopezWhite/iReact) 63 | 64 | *** 65 | 66 | # React Bootie 67 | ### Whatever it is, it has to live up to its name. 68 | * **Teammates**: Victor (@tagoro9), Andres (@amonmor), Esau (@toolotf), Carlos (@carlosmuvi) 69 | * **Seeking Teammates**: No 70 | * [GitHub URL] (https://github.com/react-bootie) 71 | 72 | *** 73 | 74 | # FOODr3k 75 | ### Lazy!? Indecisive!? Let FOODr3k Pick a place for you to eat! 76 | * **Teammates**: Resdan (@resdanl), Robbie (@robbie.santos), Adian (@legaspi21) 77 | * Seeking Teammates: No 78 | * [GitHub URL](https://github.com/rezn5447/FOODr3k) 79 | 80 | *** 81 | 82 | # OpenChair 83 | ### We'll help you find an open chair! 84 | * Teammates: Kai (@kai), Chan (@ChanTheManCan), Cindy (@cindy0092), Samuel (@SamuelHe83), Forest (@), Efe (@) 85 | * Seeking Teammates: No 86 | * [GitHub URL](https://github.com/open-chair/openChair) 87 | 88 | *** 89 | 90 | # Allergic Reaction 91 | ### Is there a cream for this? 92 | * ** Teammates**: Bill Cheng (@billcheng), Chris Messer (@messerino), Kevin (@kevinferron), Jamison (@jamison.hyman) 93 | * Seeking Teammates: Yes 94 | * [GitHub URL](https://github.com/billcheng-ucla/allergic-reaction) 95 | 96 | *** 97 | 98 | # nobs 99 | ### Süding : Social Fooding, aka friend & event centric fooding. 100 | * Teammates: Anthony(@liuminosity), Alissa(@zeninspire) 101 | * Seeking Teammates: No 102 | * [Project URL](https://github.com/zeninspire/nobs) 103 | 104 | *** 105 | 106 | # reView 107 | ### The Digital Platform to Support and Coach Software Engineers in the interview process 108 | * Teammates: Arturo Romero (@arturo) JR Meunrath (@jmslcdev) chris bassano(@christo4b) Claudiu Andrei(@claudiuandrei) David Papp (@davidpapp) 109 | * Seeking Teammates: Yes 110 | * [Project URL](https://github.com/arturoromeroslc/review) 111 | 112 | *** 113 | 114 | # Al Dente 115 | ### SocialTable - Let's get together 116 | * Teammates: Teo Antonac (@simple), Ales Fakin (@faqini) 117 | * Seeking Teammates: No 118 | * [Project URL](https://github.com/TeoA/rwr-hackathon) 119 | 120 | *** 121 | 122 | # PackChat Team 123 | ### PackChat connects parents to their collective of caregivers to instantly solve every day crises that occur in real time. 124 | * Teammates: David Rothschild (@drothschild), Jose Vazquez (@zezemanolo), Elle A (@Elleyes), Sylvan Swierkosz (@nodatall), Angela Alarcon (@angelaamongstrangers), Jason Emberley (@jason00111) 125 | * Seeking Teammates: No 126 | * [Github URL (frontend)](https://github.com/nodatall/packChat) 127 | * [Github URL (backend)](https://github.com/nodatall/packChat_api) 128 | 129 | *** 130 | 131 | # Deploy React App 132 | ### Create and deploy a boilerplate React app with continuous deployment setup in less than a minute! 133 | * **Teammates**: Sam Samskies (@samsamskies) 134 | * **Seeking Teammates**: No 135 | * [GitHub URL](https://github.com/SamSamskies/deploy-react-app) 136 | 137 | *** 138 | 139 | # Breathee 140 | ### Productivity is meant to be inhaled 141 | * **Teammates**: Anh (@anh), Bonav (@bonav), Caleb (@caleb), Kevin (@kevin), Shivaji (@shivaji) 142 | * **Seeking Teammates**: Only if you're awesome 143 | * [GitHub URL](https://github.com/bonaventureduprat/reactathon) 144 | 145 | *** 146 | 147 | # Blind Table 148 | ### For the adventurous and hungry, find interesting people to try new food. 149 | * **Teammates**: Daniel Chang (@DanielLChang), David Hu (@davidhu2000), Edwin La (@laed37), Elif Sezgin (@elifsezgin), Raymond Lee (@rlee0525) 150 | * **Seeking Teammates**: No 151 | * [Frontend GitHub URL](https://github.com/davidhu2000/BlindTable_FE) 152 | * [Backend GitHub URL](https://github.com/davidhu2000/BlindTable_BE) 153 | 154 | *** 155 | 156 | # USafe? 157 | ### Do you live alone? Or do you often say "Text me when you are home"? Then USafe? is for you. 158 | * **Teammates**: Queenie Ho (@qho), Chris Rollins (@chris.rollins) 159 | * **Seeking Teammates**: Yes 160 | * [GitHub URL](https://github.com/qho-queenie/secret_app_react) 161 | 162 | *** 163 | 164 | 165 | # Bill Splitters 166 | ### Two clicks, pay, and on your way!! 167 | 168 | * **Teammates**: Ariana (@ari_rodriguez), Lorraine (@lchan912), Diana (@diana), Diego (@diegocaceres), Joseph (@joe_stowers) 169 | * **Seeking Teammates**: No 170 | * [GitHub URL](https://github.com/Reactathon2017) 171 | 172 | *** 173 | 174 | # fitness App! 175 | ### logs user's fitness stats ie distance, calories etc and the same for their friends so people can be competative. 176 | * **Teammates**: Jawad Bangash (@Jawadban) 177 | 178 | *** 179 | 180 | # Simplify 181 | ### A way to simplify your food wishes during a vacation 182 | * **Teammates**: Yaswanth jeganathan (@yaswanth360), Pradeep Keshary (@pkeshary),John (@johnjohn),ash (@ashcon),robert (@growthmindset) 183 | * **Seeking Teammates**: No 184 | * [GitHub URL](https://github.com/puntubabu/reacathon-2017) 185 | 186 | *** 187 | 188 | # ChatBite 189 | ### A service which provides restaurants to easily create a Facebook Messenger chatbot for their Facebook Page and allows customers to book reservations through the chatbot using OpenTable API. 190 | * **Teammates**: Jacopo (@JacopoDaeli), Sue (@suemeetsue), Grant (@grant), Cam (@camdenb) 191 | * Seeking Teammates: No 192 | * [GitHub URL](https://github.com/JacopoDaeli/chatbite) 193 | * [Web URL](https://chatbite.herokuapp.com) 194 | 195 | *** 196 | 197 | # Ronin Dev 198 | ### We are creating an app to make messaging even more personal and organic. 199 | * **Teammates**: Sonny Tosco (@sonnyt), Philip Vo (@spock), Elliot Young (@elliotsyoung), George Miranda (@georgem) 200 | * **Seeking Teammates**: No 201 | * [GitHub URL](https://github.com/FunkyGeorge/reactathonserver) 202 | 203 | *** 204 | 205 | # NannyNow 206 | ### Connecting caregivers to babies. 207 | * **Teammates**: Hieu Nguyen (@hieung02), Wesley Huang (@wesleyhuang23), Henry Qi (@henrysqi), Brian Muse (@musebc) 208 | * **Seeking Teammates**: No 209 | * [GitHub URL](https://github.com/starbucks-hackers/assist-now) 210 | 211 | *** 212 | 213 | 214 | # Meow Technologies 215 | ### Never eat lunch alone. With OpenSeat, meeting up for lunch has never been easier. 216 | * **Teammates**: Regina Galieva (@rg.galieva), Elvyn Mejia (@elvynmejia), Preston Phelan (@preston_phelan), Cesar Verastegui (@zes) 217 | * **Seeking Teammates**: No 218 | * [Netlify URL](https://openseat.netlify.com/) 219 | * [Frontend GitHub URL](https://github.com/rg-galieva/openseat) 220 | * [Backend GitHub URL](https://github.com/elvynmejia/yumyum.io) 221 | *** 222 | 223 | # Team GHKA 224 | ### Dynamic discounts for restaurants depending on occupancy. 225 | * **Teammates**: Geoff (@geoff), Hilary (@hilz), Karine (@trekare), Abdul (@afr114), Theo (@tdr) 226 | * **Seeking Teammates**: No 227 | * [GitHub URL](https://github.com/afr114/reactathon2017) 228 | 229 | *** 230 | 231 | # WebChef 232 | ### Easy way to build websites for restaurant owners using OpenTable 233 | * **Teammates**: Louie (@louisrowan), Kim (@kimstephenson), Kei(@keioka), George (@georgebabayan), Kelvin (@klvngnn) 234 | * **Seeking Teammates**: No 235 | * [Project URL](http://webchef.netlify.com/) 236 | * [GitHub FrontEnd](https://github.com/louisrowan/ReactathonClient) 237 | * [GitHub BackEnd](https://github.com/klvngnn/opentable-serverless) 238 | 239 | *** 240 | 241 | # TripTunes 242 | ### TripTunes uses your roadtrip to build a Spotify playlist of songs that mention cities along your route 243 | * Teammates: Jahlela Hasle (@jahlela), Alex Rattray (@rattrayalex), Razzi Abuissa (@razzi), John Rossberg (@rossi) 244 | * Seeking Teammates: No 245 | * [Project URL](https://github.com/jahlela/triptunes) 246 | 247 | *** 248 | 249 | # MASV (Massive) 250 | ### SurpriseAssist - your assistant to make surprise reservations! 251 | * **Teammates**: Mike(@mrap), Anuar(@anuar), Smitha(@smitha92), Vasu(@accessvasu) 252 | * **Seeking Teammates**: No 253 | * [Project URL](https://github.com/Reactathon2017-Masv) 254 | 255 | *** 256 | 257 | # AInvest 258 | ### A socially conscious investment platform powered by AI. 259 | * **Teammates**: Jie Wei (@jie), Conor Carey (@ccarey), Ryan Luginbuhl (@rdlreact), Elina Lin (@elina), Gregory Barcza (@greg), Jonathan Schwob (@jonathanschwob) 260 | * **Seeking Teammates**: No 261 | * [Github URL](https://github.com/AInvest) 262 | 263 | *** 264 | 265 | # BrokenTable 266 | ### Pay-per-view fights are too expensive. Find local broken tables on this React Native app instead. 267 | * **Teammates**: Michael Leung (@mileung), David Katz (@dtkatz) 268 | * **Seeking Teammates**: No 269 | * [Github URL](https://github.com/MiLeung/BrokenTable) 270 | 271 | *** 272 | 273 | # corner-team 274 | ### Rotten tomatoes for openTable (we are the hardmen of software!!!). 275 | * **Teammates**: Captain Andy (@captainAndy001), Jawad Bangash (@jawadban), Ibraheem Abdul-Malik (@ibraheem4) , Naveen (@naveenshankar) 276 | * **Seeking Teammates**: PLEASE!!!! 277 | * [Github URL](https://github.com/caseysiebel/corner-team) 278 | 279 | *** 280 | 281 | #Goldmine 282 | ### Scraping the world's data one company at a time. 283 | * **Teammates**: Michael Chen(@MikeTYChen), Tom Chen (@senluchen2015), Stephen Chan (@s-chan) 284 | * **Seeking Teammates**: No 285 | * [Github URL) (https://github.com/senluchen2015/goldmine 286 | 287 | *** 288 | 289 | # FCC-SF 290 | ### An easy way for groups to book reservations through OpenTable. 291 | 292 | * **Teammates**: Kenzo Mendoza(@kenzom), Sean Smith, Noel Gonzalez, Vien Tang, Tiffany Lam(@tymeart) 293 | * **Seeking Teammates**: No 294 | * [GitHub URL](https://github.com/sfcodecamp/reserve.io) 295 | 296 | *** 297 | 298 | # Anamik 299 | ### A way for people to find each other at Hackathons :) 300 | * Teammates: anieto, isayd 301 | * Seeking Teammates: No 302 | * [Project URL](https://github.com/ 303 | 304 | *** 305 | --------------------------------------------------------------------------------