---
title: Contributing to NEAR
sidebar_label: 'Contributing To NEAR'
sidebar_position: 1
---

# Contributing to NEAR

:::info on this page
* NEAR welcomes contributions from interested individuals
* There are numerous open issues across repositories, and bounties are regularly posted
* For developers, there is a Developer Contributions walkthrough that explains the contribution flow
* The contributor program is available for those who want to get formally involved with continuous contributions
* Contributors in the program get early access to new bounties, exclusive support, and feedback, and can earn tokens for their contributions
* There are several developer channels available to ask questions
NEAR's GitHub repositories are available for exploration
:::

## Overview

Welcome! If you are in this repository, you are probably interested in contributing to NEAR's development.

We have tons of open issues across repositories and regularly post [bounties](https://github.com/near/bounties).

To learn more about the contribution flow for developers, please head over to the [Developer Contributions walkthrough](development/how-to-contribute.md).

## Contributor Program {#contributor-program}

If you like contributing to NEAR and would like to get formally involved with continuous contributions, the [contributor program](https://pages.near.org/ecosystem/community/) is the right place for you.

As part of the NEAR contributor program

- You are the first to hear about new bounties
- You are invited to our bi-weekly engineering calls with contributors
- You receive exclusive support and feedback
  and you have the option to earn tokens for your contributions.

<!-- ## Example Contributions {#example-contributions} -->

#### Testing {#testing}

If you are interested in testing our documentation, guides and developer tools, head over to the following pages. We would love to jump on a call and get to know your insights, or you can submit directly issues in the respective repositories on GitHub. For more information on where and how to file issues, please head over to our [developer contribution section.](development/how-to-contribute.md)

- [Developer tools](https://docs.near.org/develop/welcome)
- [Local development](https://near-nodes.io/validator/running-a-node)
- [Introduction to near-api-js](https://docs.near.org/develop/integrate/frontend)

#### Development {#development}

- We are always looking for more example applications. If you are interested in building a dApp, we would love to help you along the way and see the final result.
- Create a walk-through example of how to use the [NEAR-explorer](https://docs.near.org/tools/indexer-for-explorer) or highlight different aspects of the [NEAR CLI](https://docs.near.org/tools/near-cli). An example walkthrough of the wallet can be found on the [Creating a NEAR Wallet](overview/tokenomics/creating-a-near-wallet.md) page. Please submit your example to the [docs repository](https://github.com/near/docs).

#### You can always ask questions on either of our developer channels {#you-can-always-ask-questions-on-either-of-our-developer-channels}

- [StackOverflow](https://stackoverflow.com/search?q=nearprotocol)
- [Telegram Developer group](https://t.me/neardev)
- [Discord](http://near.chat/)

Checkout our [GitHub repositories](https://github.com/near).

:::note Got a question?
**[Ask it on StackOverflow!](https://stackoverflow.com/questions/tagged/nearprotocol)**
:::