mirror of
https://github.com/flutter/samples.git
synced 2026-04-19 21:41:43 +00:00
docs: fix typos in CONTRIBUTING.md (#2800)
Fix a few minor typos in the contributing documentation. Thanks! ## Pre-launch Checklist - [x] I read the [Flutter Style Guide] _recently_, and have followed its advice. - [x] I signed the [CLA]. - [x] I read the [Contributors Guide]. - [ ] I have added sample code updates to the [changelog]. - [ ] I updated/added relevant documentation (doc comments with `///`). If you need help, consider asking for advice on the #hackers-devrel channel on [Discord]. <!-- Links --> [Flutter Style Guide]: https://github.com/flutter/flutter/blob/master/docs/contributing/Style-guide-for-Flutter-repo.md [CLA]: https://cla.developers.google.com/ [Discord]: https://github.com/flutter/flutter/blob/master/docs/contributing/Chat.md [Contributors Guide]: https://github.com/flutter/samples/blob/main/CONTRIBUTING.md [changelog]: ../CHANGELOG.md Co-authored-by: Eric Windmill <eric@ericwindmill.com>
This commit is contained in:
@@ -20,7 +20,7 @@ _See also: [Flutter's code of conduct]_
|
|||||||
## Is this the right place for your sample?
|
## Is this the right place for your sample?
|
||||||
|
|
||||||
In most cases, if you've written a great sample app, it should be maintained
|
In most cases, if you've written a great sample app, it should be maintained
|
||||||
in your own repoistory. You can maintain your sample app in your own repo
|
in your own repository. You can maintain your sample app in your own repo
|
||||||
(or with another source control provider) and still be as important a part of
|
(or with another source control provider) and still be as important a part of
|
||||||
the Flutter-verse as anything you see here.
|
the Flutter-verse as anything you see here.
|
||||||
|
|
||||||
@@ -99,7 +99,7 @@ Validate your idea against the following criteria:
|
|||||||
|
|
||||||
1. **The sample solves a single problem or set of tightly coupled problems.** <br/>
|
1. **The sample solves a single problem or set of tightly coupled problems.** <br/>
|
||||||
If not, you're either writing a Demo app or an extended sample. These might
|
If not, you're either writing a Demo app or an extended sample. These might
|
||||||
still be appropriate for the samples repos, but need to be justified.
|
still be appropriate for the sample repos, but need to be justified.
|
||||||
|
|
||||||
2. **The target audience for the sample isn’t beginners.**
|
2. **The target audience for the sample isn’t beginners.**
|
||||||
3. **The sample code isn’t so complex that it needs video or text explanation.** <br />
|
3. **The sample code isn’t so complex that it needs video or text explanation.** <br />
|
||||||
@@ -115,10 +115,10 @@ Validate your idea against the following criteria:
|
|||||||
6. **The topic doesn’t have crossover with any existing samples.** <br />
|
6. **The topic doesn’t have crossover with any existing samples.** <br />
|
||||||
If it does, ensure that it wouldn't be better to update the existing sample.
|
If it does, ensure that it wouldn't be better to update the existing sample.
|
||||||
|
|
||||||
## What are your ongoing maintenance resposibilities?
|
## What are your ongoing maintenance responsibilities?
|
||||||
|
|
||||||
All sample code has an unbound maintenance cost. If you cannot commit to maintaining a sample
|
All sample code has an unbound maintenance cost. If you cannot commit to maintaining a sample
|
||||||
(for the forseeable future, barring changes in life circumstances), then you should talk to the
|
(for the foreseeable future, barring changes in life circumstances), then you should talk to the
|
||||||
[primary maintainers] of this project, particularly @ericwindmill, before submitting a PR.
|
[primary maintainers] of this project, particularly @ericwindmill, before submitting a PR.
|
||||||
|
|
||||||
Any new sample **must** have a CODEOWNER, and that owner is most likely you (the author).
|
Any new sample **must** have a CODEOWNER, and that owner is most likely you (the author).
|
||||||
|
|||||||
Reference in New Issue
Block a user