https://github.com/newrelic-experimental/futurehack

Getting started guide for FutureHack
https://github.com/newrelic-experimental/futurehack

hackathon newrelic

Last synced: 19 days ago
JSON representation

Getting started guide for FutureHack

• Host: GitHub
• URL: https://github.com/newrelic-experimental/futurehack
• Owner: newrelic-experimental
• License: apache-2.0
• Created: 2021-04-14T15:28:46.000Z (almost 4 years ago)
• Default Branch: main
• Last Pushed: 2022-03-15T07:26:13.000Z (almost 3 years ago)
• Last Synced: 2024-11-14T04:15:49.414Z (3 months ago)
• Topics: hackathon, newrelic
• Homepage: https://newrelic.com/futurestack
• Size: 896 KB
• Stars: 9
• Watchers: 5
• Forks: 5
• Open Issues: 1
• Metadata Files:
  • Readme: README.md
  • Contributing: CONTRIBUTING.md
  • License: LICENSE
  • Code of conduct: CODE_OF_CONDUCT.md

Awesome Lists containing this project

README

        
[![New Relic Experimental header](https://github.com/newrelic/opensource-website/raw/master/src/images/categories/Experimental.png)](https://opensource.newrelic.com/oss-category/#new-relic-experimental)

![FutureHack banner](https://github.com/newrelic-experimental/futurehack/blob/main/images/futurehack_logo.png)

## Getting Started

To get started using this repository navigate to the hackathon year folder you are participating in. Within each year's folder you will find a README containing top-level information, along with docs explaining the tracks, the hackathon agenda, judging criteria and the submission criteria.

- [2022](./2022/README.md)

- [2021](./2021/README.md)

## Contributing

We encourage your contributions to improve the FutureHack guide! Keep in mind when you submit your pull request, you'll need to sign the CLA via the click-through using CLA-Assistant. You only have to sign the CLA one time per project.

If you have any questions or to execute our corporate CLA, required if your contribution is on behalf of a company,  please drop us an email at [email protected].

**A note about vulnerabilities**

As noted in our [security policy](../../security/policy), New Relic is committed to the privacy and security of our customers and their data. We believe that providing coordinated disclosure by security researchers and engaging with the security community are important means to achieve our security goals.

If you believe you have found a security vulnerability in this project or any of New Relic's products or websites, we welcome and greatly appreciate you reporting it to New Relic through [HackerOne](https://hackerone.com/newrelic).

## License

FutureHack 2021 Guide is licensed under the [Apache 2.0](http://apache.org/licenses/LICENSE-2.0.txt) License.