## Contributing In General
Our project welcomes external contributions. If you have an itch, please feel
free to scratch it.

To contribute notebooks or documentation, please submit a [pull request](https://github.com/IBM/ibm-envizi-emissions-api-nodejs-sdk/pulls).

A good way to familiarize yourself with the notebooks and contribution process is
to look for an issue in the [issue tracker](https://github.com/IBM/ibm-envizi-emissions-api-nodejs-sdk/issues).

Before embarking on a more ambitious contribution, please [raise an issue](https://github.com/IBM/ibm-envizi-emissions-api-nodejs-sdk/issues).

**Note: We appreciate your effort, and want to avoid a situation where a contribution
requires extensive rework (by you or by us), sits in backlog for a long time, or
cannot be accepted at all!**

### Proposing new features

If you would like to add a new notebook, please [raise an issue](https://github.com/IBM/ibm-envizi-emissions-api-nodejs-sdk/issues)
before sending a pull request so the contribution can be discussed. 

### Fixing bugs

If you would like to fix a bug, please [raise an issue](https://github.com/IBM/ibm-envizi-emissions-api-nodejs-sdk/issues) before sending a
pull request so it can be tracked.

### Merge approval

The project maintainers use LGTM (Looks Good To Me) in comments on the code
review to indicate acceptance. A change requires a LGTM from a repository maintainer
or from a notebook maintainer (in the area of the contribution).

For a list of the maintainers, see the [MAINTAINERS.md](MAINTAINERS.md) page.

## Legal

Each source file must include a license header for the Apache
Software License 2.0. Using the SPDX format is the simplest approach.
e.g.

```
/*
Copyright <holder> All Rights Reserved.

SPDX-License-Identifier: Apache-2.0
*/
```

We have tried to make it as easy as possible to make contributions. This
applies to how we handle the legal aspects of contribution. We use the
same approach - the [Developer's Certificate of Origin 1.1 (DCO)](https://github.com/hyperledger/fabric/blob/master/docs/source/DCO1.1.txt) - that the Linux® Kernel [community](https://elinux.org/Developer_Certificate_Of_Origin)
uses to manage code contributions.

We simply ask that when submitting a patch for review, the developer
must include a sign-off statement in the commit message.

Here is an example Signed-off-by line, which indicates that the
submitter accepts the DCO:

```
Signed-off-by: John Doe <john.doe@example.com>
```

You can include this automatically when you commit a change to your
local git repository using the following command:

```
git commit -s
```