├── .github └── ISSUE_TEMPLATE │ ├── bug_report.md │ └── hackathon-submission.md ├── FAQs.md ├── README.md └── rules.md /.github/ISSUE_TEMPLATE/bug_report.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: Bug report 3 | about: Create a report to help us improve 4 | title: '' 5 | labels: '' 6 | assignees: '' 7 | 8 | --- 9 | 10 | **Describe the bug** 11 | A clear and concise description of what the bug is. 12 | 13 | **To Reproduce** 14 | Steps to reproduce the behavior: 15 | 1. Go to '...' 16 | 2. Click on '....' 17 | 3. Scroll down to '....' 18 | 4. See error 19 | 20 | **Expected behavior** 21 | A clear and concise description of what you expected to happen. 22 | 23 | **Screenshots** 24 | If applicable, add screenshots to help explain your problem. 25 | 26 | **Desktop (please complete the following information):** 27 | - OS: [e.g. iOS] 28 | - Browser [e.g. chrome, safari] 29 | - Version [e.g. 22] 30 | 31 | **Smartphone (please complete the following information):** 32 | - Device: [e.g. iPhone6] 33 | - OS: [e.g. iOS8.1] 34 | - Browser [e.g. stock browser, safari] 35 | - Version [e.g. 22] 36 | 37 | **Additional context** 38 | Add any other context about the problem here. 39 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/hackathon-submission.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: Hackathon Submission 3 | about: Submit 4 | title: '' 5 | labels: submission 6 | assignees: '' 7 | 8 | --- 9 | 10 | ## Describe your submission 11 | 12 | ### [In what way did you change the template?](https://github.com/floss-and-code/stripe-hackathon#the-challenge) 13 | 14 | - [ ] Copy 15 | - [ ] Design 16 | - [ ] Improve 17 | 18 | ### [Team members](https://github.com/floss-and-code/stripe-hackathon/blob/main/FAQs.md#can-i-submit-as-a-team) 19 | 20 | _If you worked with others, please list their GitHub Handles (Limit 3)_ 21 | 22 | ### [Link to the Blog post describing your submission and experience](https://github.com/floss-and-code/stripe-hackathon/blob/main/rules.md#winner-selection-and-notification) 23 | 24 | _Submission must include a linkable blog post (more than 400 words) about your project hosted publically (i.e. Linked, Dev.to, etc)._ 25 | -------------------------------------------------------------------------------- /FAQs.md: -------------------------------------------------------------------------------- 1 | ## What is the FLOSS and Code? 2 | At GitHub, part of our vision is to impact positive and lasting change around the world through the products we help build. 3 | 4 | In keeping with the spirit of our mission to accelerate human progress through developer collaboration, we have partnered with Stripe and Vercel (Next.js) to host a hackathon to help build e-commerce applications and tools to assist communities and businesses affected by Covid-19. 5 | 6 | If your questions is not below, please ask it in [the Discussions tab](https://github.com/floss-and-code/stripe-hackathon/discussions). 7 | 8 | ## Where is it located? 9 | You can compete from anywhere in the world where GitHub is available. The live event will be hosted on 12/1/2020 at 930am PST [YouTube](https://youtube.com/github). 10 | 11 | ## When does hacking start? 12 | December 1st to December 20th, 2020 11:59 pm PST. 13 | 14 | ## How much does it cost to participate in GitHub Hackathon? 15 | Like open-source, the GitHub Hackathon is Free! 16 | 17 | ## Can I submit as a team? 18 | Yes. All submissions will need to be submitted by one user. Please list your team by linking directly to their GitHub profiles (limited to 3 plus the repo owner). Keep in mind GitHub and Stripe credits will be only provided 1 per team. A GitHub swag coupon will be provided for all team members. 19 | 20 | ## Can I work as a team or with other people? 21 | We ALWAYS encourage collaboration when coding and building ideas. Feel free to work with others, help one another, and build together. Just remember your project will need to be submitted by an individual. You will be judged as an individual, and prizes are for individuals. 22 | 23 | ## How many projects can I submit? 24 | There is a limit of one submission. 25 | 26 | ## Can I submit a repository from an organization? 27 | An organization repo can be submitted, but prizes can only be sent to indivudal GitHub users. 28 | 29 | ## If I have a question, or I’m stuck with my Project, who can I ask? 30 | Please reach out to the [github.community](https://github.community) or this repo for GitHub support. If you have Stripe, Supabase, or Vercel assistance please open a discussion in the https://github.com/thorwebdev/nextjs-subscription-payments repo. 31 | 32 | ## What programming language can I use? 33 | The [template provide](https://github.com/thorwebdev/nextjs-subscription-payments) is built using React and JavaScript, we encourage you to try new things and share your discoveries with the community. If you would like to re use the template using a different language, we encourage you to explore other [templates in different languages](https://github.com/stripe-samples). 34 | 35 | ## What hosting or cloud platforms can I use? 36 | You can use whatever you’d like. We do recommend checking out the deploy to Vercel link in the [starter repo](https://github.com/thorwebdev/nextjs-subscription-payments). 37 | 38 | ## What is the Topic/Theme of the competition? 39 | This hackathon is meant to encourage building e-commerce applications that assist communities and businesses affected by Covid-19. We encourage you to think of real business affected and build a project that would support them during this time. 40 | 41 | ## Who decides the winners? 42 | Team of GitHub employees. If the project improves on the existing starter it will be deemed valid and added to the winners list (limited to the first 50). 43 | 44 | ## When are the winners announced? 45 | December 14th. 46 | 47 | ## How will I know if I win? 48 | Winners will be notified by email, please make sure there is a visible and correct email on your GitHub profile. Good luck! 49 | 50 | ## Can I sponsor the GitHub Hackathon? 51 | We will not be accepting sponsorship for this hackathon. 52 | 53 | ## Can I hold an event for the GitHub Hackathon? 54 | Absolutely! We’d love you to hold any type of event you like for this hackathon. Be it a meetup to share ideas, code workshop to help each other build your project, or event to showcase what you build, we’d love you to spread the word to your communities. If you’re hosting an event, head over to the assets page and download some images you can use to promote your event. 55 | 56 | ## Can GitHub employees participate? 57 | GitHub employees, contractors, and immediate family members can compete, but are not eligible to win. 58 | 59 | ## Is there a code of conduct? 60 | Yes, please review it [here](https://github.com/floss-and-code/code_of_conduct). 61 | 62 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # FLOSS and Code: Stripe hackathon 2 | At GitHub, part of our vision is to impact positive and lasting change around the world through the products we help build. 3 | 4 | In keeping with the spirit of our mission to accelerate human progress through developer collaboration, we have partnered with Stripe and Vercel (Next.js) to host a hackathon to help build e-commerce applications and tools to assist communities and businesses affected by Covid-19. 5 | 6 | The hackathon will be hosted Tuesday, Dec 1 as a [GitHub Universe](https://githubuniverse.com) Orbital event, and it is open to all GitHub users. 7 | 8 | Agenda (All times are in PST) 9 | - 9:30 am Welcome from GitHub 10 | - 9:40 am Keynote speakers 11 | - 10:45 Hackathon Q & A 12 | - 11:30 Workshops (Stripe + Vercel) 13 | 14 | ## Attendee expectations 15 | This event is open to programmers from all levels of experience. Individuals are expected to have a basic understanding of programming and the ability to contribute to projects using GitHub. For those interested in attending but do not have that experience, they can take our [Introduction to GitHub course](https://lab.github.com/githubtraining/introduction-to-github). 16 | 17 | ## What is FLOSS? 18 | Free/libre open-source software (FLOSS) is software that can be classified as both free software and open-source software. That is, anyone is freely licensed to use, copy, study, and change the software in any way, and the source code is openly shared so that people are encouraged to improve the design of the software voluntarily. This is in contrast to proprietary software, where the software is under restrictive copyright licensing, and the source code is usually hidden from the users. 19 | 20 | ## How to get started 21 | 1. Fork or clone the starter, https://github.com/thorwebdev/nextjs-subscription-payments 22 | 2. Follow the setup instructions in the README. 23 | 3. Use the [GitHub Discussions](https://github.com/thorwebdev/nextjs-subscription-payments/discussions) to ask questions. 24 | 4. [Submit your project as an issue in this repo](https://github.com/floss-and-code/stripe-hackathon/issues/new?assignees=&labels=submission&template=hackathon-submission.md&title=) (limited to the first 50). 25 | 26 | ## The challenge 27 | Use the existing the [nextjs-subscription-payments 28 | ](https://github.com/thorwebdev/nextjs-subscription-payments) template. You will need to improve the template using the one of the following ways: 29 | 30 | - Use: Improve the copy with a real business. Keep in mind, adding copy should improve the context for the starter. Please try to use real examples or ideas if you can. 31 | - Design: Submit a new design for the starter template. Today, we would love to see examples representing (but not limited to) food delivery, apparel stores, or salon services. 32 | - Improve: Add a new feature to the starter using your fork or clone as an example. 33 | 34 | _winners are limited to the first 50 valid submissions_ 35 | 36 | ## Questions 37 | 1. FLOSS event [FAQs](https://github.com/floss-and-code/stripe-hackathon/blob/main/FAQs.md ) 38 | 2. [Questions about the Next.js template](https://github.com/thorwebdev/nextjs-subscription-payments/discussions/25) 39 | 40 | ## About GitHub Universe 41 | 42 | GitHub Universe (Dec. 8-10) is our annual marquee product and user conference. The three-day event brings together a global interconnected community with tens of thousands of viewers. From around the world developers, industry thought leaders, and executives tune in to hear what's next from GitHub, and learn about the tools and concepts that are pushing the software industry forward. 43 | 44 | The conference features insightful sessions and workshops from people who are defining the state of open source and the future of software development. 45 | 46 | https://githubuniverse.com 47 | -------------------------------------------------------------------------------- /rules.md: -------------------------------------------------------------------------------- 1 | # FLOSS and Code HACKATHON 2020 OFFICIAL RULES 2 | These rules were written by our lawyers (and help them sleep a little better at night). They’ve got a lot of important details, so please read them closely. 3 | 4 | ## SPONSOR 5 | 6 | These Official Rules (“Rules”) govern the operation of the FLOSS and Code Hackathon 2020 Contest (“Contest”). GitHub, Inc., 88 Colin P. Kelly Jr. Street, San Francisco, CA, 94107, USA, is the Contest sponsor (“Sponsor”). 7 | 8 | ## DEFINITIONS 9 | 10 | In these Rules, "GitHub", "we", "our", and "us" refer to Sponsor and “you”, "yourself", and “Participant” refers to a Contest participant. By entering you agree to be bound by these rules. 11 | 12 | ## ENTRY PERIOD 13 | 14 | The Contest starts at 12:01 a.m. Pacific Time (“PT”) on November 30th, 2020 and ends at 11:59 p.m. PT on Dec 11, 2020 (“Entry Period”). 15 | 16 | ## ELIGIBILITY 17 | 18 | To enter, you must be 18 years of age or older and have internet access. 19 | Employees and directors of GitHub and its subsidiaries, affiliates, and advertising agencies are not eligible, nor are persons involved in the execution or administration of this promotion, or the family members of each above (parents, children, siblings, spouse/domestic partners, or individuals residing in the same household). Void in countries/regions under sanctions by the United States, including Cuba, Iran, North Korea, Sudan, Syria, Region of Crimea. Void where prohibited or restricted by law. 20 | 21 | ## HOW TO ENTER 22 | 23 | To submit an entry, visit the Contest repository at https://github.com/floss-and-code/stripe-hackathon and follow the instructions to register and submit your web app (“Submission”). All required information must be provided for your Submission to be eligible. 24 | 25 | Submissions from your GitHub Enterprise Cloud, Business, or Server account are ineligible. 26 | There is no limit on participant entries; however only one prize can be received per household. 27 | Any attempt to obtain more than the stated number of Prizes by using multiple/different accounts, identities, registrations, logins, or any other methods will void your Submissions and you may be disqualified. Use of any automated system to participate is prohibited. 28 | 29 | We are not responsible for excess, lost, late, or incomplete Submissions. If disputed, Submissions will be deemed submitted by the “authorized account holder” of the GitHub account, GitHub alias, email address, social media account, or other method used to enter. The “authorized account holder” is the natural person assigned to either the GitHub account or an email address by an internet or online service provider, or other organization responsible for assigning email addresses. 30 | 31 | ## ELIGIBLE ENTRY 32 | 33 | To be eligible, a Submission must meet the following content/technical requirements: 34 | Your Submission must be your own original work; and 35 | Your Submission cannot have been selected as a winner in any other contest; and 36 | You must have obtained any and all consents, approvals, or licenses required for you to submit your Submission; and 37 | To the extent that your Submission requires the Submission of user-generated content such as software, photos, videos, music, artwork, essays, etc., you warrant that your Submission is your original work, has not been copied from others without permission or apparent rights, and does not violate the privacy, intellectual property rights, or other rights of any other person or entity. You may include GitHub trademarks, logos, and designs, for which GitHub grants you a limited license to use for the sole purposes of submitting a Submission into this Contest; and 38 | Your Submission may NOT contain, as determined by us in our sole and absolute discretion, any content that is obscene or offensive, violent, defamatory, disparaging or illegal, or that promotes alcohol, illegal drugs, tobacco or a particular political agenda, or that communicates messages that may reflect negatively on the goodwill of GitHub or its affiliates. 39 | USE OF YOUR ENTRY 40 | We are not claiming ownership rights to your Submission. However, by submitting a Submission, you grant us an irrevocable, royalty-free, worldwide right and license to use, review, assess, test and otherwise analyze your Submission and all its content in connection with this Contest and use your Submission in any media whatsoever now known or later invented for any non-commercial or commercial purpose, including, but not limited to, the marketing, sale or promotion of GitHub products or services, without further permission from you. You will not receive any compensation or credit for use of your Submission, other than what is described in these Official Rules. 41 | By entering you acknowledge that we may have developed or commissioned materials similar or identical to your Submission and you waive any claims resulting from any similarities to your Submission. Further you understand that we will not restrict work assignments of representatives who have had access to your Submission and you agree that use of information in our representatives’ unaided memories in the development or deployment of our products or services does not create liability for us under this agreement or copyright or trade secret law. 42 | Your Submission may be posted on a public website. We are not responsible for any unauthorized use of your Submission by visitors to this website. We are not obligated to use your Submission for any purpose, even if it has been selected as a winning Submission. 43 | 44 | ## WINNER SELECTION AND NOTIFICATION 45 | 46 | Pending confirmation of eligibility, potential prize winners will be selected by GitHub or their agent or a qualified judging panel from among all eligible Submissions received based on the following judging criteria: 47 | 48 | 49 | - Your submitted web app must include a License file 50 | - Your submitted web app must be published in a public repository owned by your GitHub account. 51 | - Your submitted web app must include you as the author in the git history. 52 | - Your web app must be Unique and be an improvement on the provided templates. 53 | - Submission must include a linkable blog post (more than 400 words) about your project hosted publically (i.e. Linked, Dev.to, etc). 54 | 55 | Winners will be selected within 7 business days following the close of the Entry Period. 56 | 57 | Winners will be notified within 7 business days following the close of the Entry Period with winner instructions, including a prize claim deadline. In the event of a tie between any eligible Submissions, an additional judge will break the tie based on the judging criteria described above. The decisions of the judges are final and binding. If we do not receive a sufficient number of Submissions meeting the entry requirements, we may, at our discretion, select fewer winners than the number of Contest Prizes described below. 58 | 59 | Winners will be notified via the contact information provided during the Entry Period no more than 7 days following judging with prize claim instructions, including Submission deadlines. 60 | 61 | Winners may be required to provide proof of identification and eligibility as required by Sponsor. If within 72 hours of GitHub sending winner notifications, a selected winner cannot be contacted, is ineligible, fails to claim a prize or fails to return any forms, the selected winner will forfeit their prize and an alternate winner will be selected, time allowing. If you are a potential winner and you are 18 years of age or older but are considered a minor in your place of legal residence, we may require your parent or legal guardian to sign all required forms on your behalf. Only three alternate winners will be selected, after which unclaimed prizes will remain unawarded. 62 | 63 | ## PRIZES 64 | 65 | The following prizes will be awarded: 66 | 67 | **Each submitted and approved web app will receive:** 68 | 69 | - 1 swag coupon email. Prize limited to first 50 winners. Approximate Retail Value (ARV) $34.00 USD. 70 | 71 | We will only award one (1) prize per household No more than the stated number of prizes will be awarded. No substitution, transfer, or assignment of prize permitted, except that GitHub reserves the right to substitute a prize of equal or greater value in the event the offered prize is unavailable. Prizes are awarded “AS IS” with no warranty of any kind, either express or implied, including but not limited to, the implied warranties or merchantability, fitness for a particular purpose, or non-infringement. Prizes will be sent no later than the timeframe stated in the winner notification. Prize winners may be required to complete and return prize claim and/or tax forms (“Forms”) within the deadline stated in the winner notification. Taxes on the prize, if any, are the sole responsibility of the winner, who is advised to seek independent counsel regarding the tax implications of accepting a prize. By accepting a prize, you agree that GitHub may use your entry, name, image and hometown online and in print, or in any other media, in connection with this Contest without payment or compensation to you, except where prohibited by law. 72 | 73 | ## ODDS 74 | 75 | The odds of winning are based on the number of eligible Submissions received. 76 | 77 | ## GENERAL CONDITIONS AND RELEASE OF LIABILITY 78 | 79 | To the extent allowed by law, by entering you agree to release and hold harmless GitHub and its respective parents, partners, subsidiaries, affiliates, employees, and agents from any and all liability or any injury, loss, or damage of any kind arising in connection with this Sweepstakes or any prize won. 80 | 81 | All local laws apply. Sponsor decisions are final and binding. 82 | 83 | We reserve the right to cancel, change, or suspend this Sweepstakes for any reason, including cheating, technology failure, catastrophe, war, or any other unforeseen or unexpected event that affects the integrity of this Sweepstakes, whether human or mechanical. If the integrity of the Contest cannot be restored, we may select winners from among all eligible Submissions received before we had to cancel, change or suspend the Contest. 84 | 85 | If you attempt or we have strong reason to believe that you have compromised the integrity or the legitimate operation of this Contest by cheating, hacking, creating a bot or other automated program, or by committing fraud in any way, we may seek damages from you to the full extent of the law and you may be banned from participation in future GitHub promotions. 86 | 87 | ## USE OF YOUR ENTRY 88 | 89 | Personal data you provide while entering this Contest will be used by GitHub and/or its agents and prize fulfillers acting on GitHub’s behalf only for the administration and operation of this GitHub and in accordance with the GitHub Privacy Statement. 90 | 91 | ## GOVERNING LAW 92 | 93 | This Contest will be governed by the laws of the State of California, and you consent to the exclusive jurisdiction and venue of the courts of the State of California for any disputes arising out of this Contest. 94 | 95 | ## WINNERS LIST 96 | 97 | Send email to blacktocats@github.com with the subject line “FLOSS and Code Hackathon 2020 winners” or visit https://github.com/floss-and-code/stripe-hackathon/issues by Dec 15, 2020 to receive or view a list of winners that received a prize worth $34.00 or more. 98 | 99 | --------------------------------------------------------------------------------