# Contribute ## Introduction First, thank you for considering contributing to `images-responsiver`! 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, console logs, etc.) - **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/nhoizey/images-responsiver/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. ## 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](https://oncletom.io/2013/the-55-commits-syndrome/) 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? ## Questions If you have any questions, [create an issue](https://github.com/nhoizey/images-responsiver/issues/new/choose) (protip: do a quick search first to see if someone else didn't ask the same question before!). ## Credits ### Contributors Thank you to [all the people who have already contributed](https://github.com/nhoizey/images-responsiver/graphs/contributors) to `images-responsiver`!