flutter/contributing.md

# Contribution Guidelines

Please note that this project is released with a [Contributor Code of Conduct](https://github.com/spring-projects/spring-framework/blob/master/CODE_OF_CONDUCT.adoc). By participating in this project you agree to abide by its terms.

- 35 stars minimum are required to apply, it mean your project hold interest
- Use a meaningful name to your commit or I'll close it instantly, Update source.md is NOT a name
- Does your app bring something really interesting ?
- Do not commit on README, use SOURCE.md !
- Is there a direct link so I we can check the details of your repo ?
- Flutter is all about UI, use screenshots and animated media for your widget
- Remember the team is giving its own time to help the community. This is not a paid job yet it take a lot of time to curate and review.

When your contribution is accepted you can add the Awesome Flutter Badge to your repository
thus signaling the quality of your work and linking to others authors Awesome projets

 <a href="https://stackoverflow.com/questions/tagged/flutter?sort=votes">
  <img alt="Awesome Flutter" src="https://img.shields.io/badge/Awesome-Flutter-blue.svg?longCache=true&style=flat-square" />
 </a>
 
 ``` 
<a href="https://github.com/Solido/awesome-flutter">
    <img alt="Awesome Flutter" src="https://img.shields.io/badge/Awesome-Flutter-blue.svg?longCache=true&style=flat-square" />
</a>
```
 

Ensure your pull request adheres to the following guidelines:

- Search previous suggestions before making a new one, as yours may be a duplicate.
- Suggested packages should be tested and documented.
- The pull request should have a meaningful title and include a link to the package / resource and why it's awesome.
- Make an individual pull request for each suggestion.
- Use the following format: `[resource](link) - Description by [Author](link to author)`
- Use [title-casing](http://titlecapitalization.com) (AP style).
- Additions should be added to the bottom of the relevant category.
- New categories, or improvements to the existing categorization are welcome.
- Keep descriptions short and simple, but descriptive.
- Don't mention `Flutter` in the description as it's implied.
- Start the description with a capital.
- Check your spelling and grammar.
- Make sure your text editor is set to remove trailing whitespace.

Thank you for your suggestions!
Create contributing.md 2017-05-10 15:14:12 -04:00			`# Contribution Guidelines`

Update contributing.md 2018-01-27 16:19:37 -05:00			`Please note that this project is released with a [Contributor Code of Conduct](https://github.com/spring-projects/spring-framework/blob/master/CODE_OF_CONDUCT.adoc). By participating in this project you agree to abide by its terms.`
Create contributing.md 2017-05-10 15:14:12 -04:00
Min required stars to apply 2021-11-08 11:22:05 -05:00			`- 35 stars minimum are required to apply, it mean your project hold interest`
Update contributing.md 2019-01-08 05:22:42 -05:00			`- Use a meaningful name to your commit or I'll close it instantly, Update source.md is NOT a name`
Clarifying rules 2020-05-29 07:42:47 -04:00			`- Does your app bring something really interesting ?`
Read rules first before commit to source.md 2022-02-02 03:09:18 -05:00			`- Do not commit on README, use SOURCE.md !`
Fix typo on contributing.md détails to details 2020-12-09 12:42:05 -05:00			`- Is there a direct link so I we can check the details of your repo ?`
Screenshots and animated media 2018-09-26 11:30:00 -04:00			`- Flutter is all about UI, use screenshots and animated media for your widget`
Be gentle a patient with the team 2020-11-08 11:45:24 -05:00			`- Remember the team is giving its own time to help the community. This is not a paid job yet it take a lot of time to curate and review.`
Create contributing.md 2017-05-10 15:14:12 -04:00
Badge 2018-09-27 16:21:51 -04:00			`When your contribution is accepted you can add the Awesome Flutter Badge to your repository`
			`thus signaling the quality of your work and linking to others authors Awesome projets`

			`<a href="https://stackoverflow.com/questions/tagged/flutter?sort=votes">`
			`<img alt="Awesome Flutter" src="https://img.shields.io/badge/Awesome-Flutter-blue.svg?longCache=true&style=flat-square" />`
			`</a>`
Badge Link 2018-09-27 16:23:19 -04:00
			```
Badge link update 2018-12-24 09:10:46 -05:00			`<a href="https://github.com/Solido/awesome-flutter">`
Badge Link 2018-09-27 16:23:19 -04:00			`<img alt="Awesome Flutter" src="https://img.shields.io/badge/Awesome-Flutter-blue.svg?longCache=true&style=flat-square" />`
			`</a>`
			```

Badge 2018-09-27 16:21:51 -04:00
Create contributing.md 2017-05-10 15:14:12 -04:00			`Ensure your pull request adheres to the following guidelines:`

			`- Search previous suggestions before making a new one, as yours may be a duplicate.`
			`- Suggested packages should be tested and documented.`
			`- The pull request should have a meaningful title and include a link to the package / resource and why it's awesome.`
			`- Make an individual pull request for each suggestion.`
update contributing rules -> source.md 2018-06-11 08:45:43 -04:00			- Use the following format: `[resource](link) - Description by [Author](link to author)`
Create contributing.md 2017-05-10 15:14:12 -04:00			`- Use [title-casing](http://titlecapitalization.com) (AP style).`
			`- Additions should be added to the bottom of the relevant category.`
			`- New categories, or improvements to the existing categorization are welcome.`
			`- Keep descriptions short and simple, but descriptive.`
Tweak wording instead of removing it.. 2020-10-22 16:00:16 -04:00			- Don't mention `Flutter` in the description as it's implied.
update contributing rules -> source.md 2018-06-11 08:45:43 -04:00			`- Start the description with a capital.`
Create contributing.md 2017-05-10 15:14:12 -04:00			`- Check your spelling and grammar.`
			`- Make sure your text editor is set to remove trailing whitespace.`

			`Thank you for your suggestions!`