FM / nodemailer

/var/www/greso.tech/server/nsm/node_modules/nodemailer/

/var/www/greso.tech/server/nsm/node_modules/nodemailer

Name	Size	Mode	Actions
lib/	-	0755	rm
.gitattributes	95	0644	edit dl rm
.ncurc.js	121	0644	edit dl rm
.prettierrc.js	156	0644	edit dl rm
CHANGELOG.md	25333	0644	edit dl rm
CODE_OF_CONDUCT.md	3351	0644	edit dl rm
CONTRIBUTING.md	4650	0644	edit dl rm
LICENSE	935	0644	edit dl rm
package.json	1274	0644	edit dl rm
postinstall.js	3068	0644	edit dl rm
README.md	5534	0644	edit dl rm
SECURITY.txt	1044	0644	edit dl rm

Edit: /var/www/greso.tech/server/nsm/node_modules/nodemailer/CONTRIBUTING.md (4650B)

# Contribute

## Introduction

First, thank you for considering contributing to nodemailer! It's people like you that make the open source community such a great community! 😊

We welcome any type of contribution, not only code. You can help with 
- **QA**: file bug reports, the more details you can give the better (e.g. screenshots with the console open)
- **Marketing**: writing blog posts, howto's, printing stickers, ...
- **Community**: presenting the project at meetups, organizing a dedicated meetup for the local community, ...
- **Code**: take a look at the [open issues](https://github.com/nodemailer/nodemailer/issues). Even if you can't write code, commenting on them, showing that you care about a given issue matters. It helps us triage them.
- **Money**: we welcome financial contributions in full transparency on our [open collective](https://opencollective.com/nodemailer).

## Your First Contribution

Working on your first Pull Request? You can learn how from this *free* series, [How to Contribute to an Open Source Project on GitHub](https://egghead.io/series/how-to-contribute-to-an-open-source-project-on-github).

## Submitting code

Any code change should be submitted as a pull request. The description should explain what the code does and give steps to execute it. The pull request should also contain tests.

## Code review process

The bigger the pull request, the longer it will take to review and merge. Try to break down large pull requests in smaller chunks that are easier to review and merge.
It is also always helpful to have some context for your pull request. What was the purpose? Why does it matter to you?

## Financial contributions

We also welcome financial contributions in full transparency on our [open collective](https://opencollective.com/nodemailer).
Anyone can file an expense. If the expense makes sense for the development of the community, it will be "merged" in the ledger of our open collective by the core contributors and the person who filed the expense will be reimbursed.

## Questions

If you have any questions, create an [issue](https://github.com/nodemailer/nodemailer/issues) (protip: do a quick search first to see if someone else didn't ask the same question before!).
You can also reach us at hello@nodemailer.opencollective.com.

## Credits

### Contributors

Thank you to all the people who have already contributed to nodemailer!
<a href="graphs/contributors"><img src="https://opencollective.com/nodemailer/contributors.svg?width=890" /></a>

### Backers

Thank you to all our backers! [[Become a backer](https://opencollective.com/nodemailer#backer)]

### Sponsors

Thank you to all our sponsors! (please ask your company to also support this open source project by [becoming a sponsor](https://opencollective.com/nodemailer#sponsor))

cmd: