README.md

[gniumg-source]

@beccasaurus #3275
@AustinWise #3277
@jskeet #3280
@suztomo #3281
@chingor13 #3282

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.
• If you work for a company that wants to allow you to contribute your work,
  then you'll need to sign a corporate
  CLA.

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.

Setting Up An Environment

For instructions regarding development environment setup, please visit the documentation.

Contributing A Patch

1. Submit an issue describing your proposed change to the repo in question.
2. The repo owner will respond to your issue promptly.
3. If your proposed change is accepted, and you haven't already done so, sign a
   Contributor License Agreement (see details above).
4. Fork the desired repo, develop and test your code changes.
5. Ensure that your code adheres to the existing style in the sample to which
   you are contributing.
6. Ensure that your code has an appropriate set of unit tests which all pass.
7. Submit a pull request.

Style

The Google Cloud Samples Style Guide is considered the primary
guidelines for all Google Cloud samples.

Samples in this repository also follow the framework coding
style.
This is enforced using CodeFormatter.

Starting a new sample set

When starting a new sample, match the file and directory layout in the
KMS Samples and KMS Samples Tests. KMS samples and tests are
the canonical example of how samples in this repo should be structured.

PR size

In general prefer small PRs over bigger ones. A good rule of thumb is, no more than 10 new/modified files per PR.
This is particularly relevant when starting a new sample set, when all files are new.

• Reviews of smaller PRs are faster.
• Time to merge is faster, both incrementally and overall.
• Feedback and issues found in a first small PR can be more easily applied to subsequent small PRs.

Contributor Code of Conduct

As contributors and maintainers of this project,
and in the interest of fostering an open and welcoming community,
we pledge to respect all people who contribute through reporting issues,
posting feature requests, updating documentation,
submitting pull requests or patches, and other activities.

We are committed to making participation in this project
a harassment-free experience for everyone,
regardless of level of experience, gender, gender identity and expression,
sexual orientation, disability, personal appearance,
body size, race, ethnicity, age, religion, or nationality.

Examples of unacceptable behavior by participants include:

• The use of sexualized language or imagery
• Personal attacks
• Trolling or insulting/derogatory comments
• Public or private harassment
• Publishing other's private information,
  such as physical or electronic
  addresses, without explicit permission
• Other unethical or unprofessional conduct.

Project maintainers have the right and responsibility to remove, edit, or reject
comments, commits, code, wiki edits, issues, and other contributions
that are not aligned to this Code of Conduct.
By adopting this Code of Conduct,
project maintainers commit themselves to fairly and consistently
applying these principles to every aspect of managing this project.
Project maintainers who do not follow or enforce the Code of Conduct
may be permanently removed from the project team.

This code of conduct applies both within project spaces and in public spaces
when an individual is representing the project or its community.

Instances of abusive, harassing, or otherwise unacceptable behavior
may be reported by opening an issue
or contacting one or more of the project maintainers.

This Code of Conduct is adapted from the Contributor Covenant, version 1.2.0,
available at http://contributor-covenant.org/version/1/2/0/

Política de seguridad
Para informar un problema de seguridad, utilice g.co/vulnz .

El equipo de seguridad de Google responderá dentro de los 5 días hábiles posteriores a su informe en g.co/vulnz.

Usamos g.co/vulnz para nuestra admisión y hacemos la coordinación y divulgación aquí usando GitHub Security Advisory para discutir y solucionar el problema de forma privada.

[gemini-code-assist]

Note

Gemini is unable to generate a summary for this pull request due to the file types involved not being currently supported.

[amanda-tarafa]

Closing as spam

[jskeet]

@amanda-tarafa I've already reported this user, and GitHub is looking into it. Will block them from the org as well though.

[amanda-tarafa]

Thanks, I've reported the user as well.