OXIESEC PANEL

Name	Size	Modified	Perms
📁 ..	-	12/09/2024 05:26:03 PM	rwxr-xr-x
📄 .gitignore	9 bytes	05/02/2024 02:34:49 PM	rw-r--r--
📄 CONTRIBUTING.md	1.22 KB	05/02/2024 02:34:49 PM	rw-r--r--
📄 LICENSE	11.09 KB	05/02/2024 02:34:49 PM	rw-r--r--
📄 MANIFEST.in	16 bytes	05/02/2024 02:34:49 PM	rw-r--r--
📄 README.md	2.17 KB	05/02/2024 02:34:49 PM	rw-r--r--
📁 gcs_oauth2_boto_plugin	-	02/11/2025 08:19:49 AM	rwxr-xr-x
📄 requirements.txt	285 bytes	05/02/2024 02:34:49 PM	rw-r--r--
📄 setup.cfg	35 bytes	05/02/2024 02:34:49 PM	rw-r--r--
📄 setup.py	2.93 KB	05/02/2024 02:34:49 PM	rw-r--r--
📄 test-requirements.txt	29 bytes	05/02/2024 02:34:49 PM	rw-r--r--

Editing: CONTRIBUTING.md

# How to become a contributor and submit your own code

## Contributor License Agreements

We'd love to accept your patches! Before we can take them, we have to jump a couple of legal hurdles.

Please fill out either the individual or corporate Contributor License Agreement (CLA).

* If you are an individual writing original source code and you're sure you own the intellectual property, then you'll need to sign an [individual CLA](http://code.google.com/legal/individual-cla-v1.0.html).
* If you work for a company that wants to allow you to contribute your work, then you'll need to sign a [corporate CLA](http://code.google.com/legal/corporate-cla-v1.0.html).

Follow either of the two links above to access the appropriate CLA and instructions for how to sign and return it. Once we receive it, we'll be able to accept your pull requests.

## Contributing A Patch

1. Submit an issue describing your proposed change to the repo in question.
1. The repo owner will respond to your issue promptly.
1. If your proposed change is accepted, and you haven't already done so, sign a Contributor License Agreement (see details above).
1. Fork the desired repo, develop and test your code changes.
1. Submit a pull request.
~