Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
25 changes: 11 additions & 14 deletions CONTRIBUTING.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,31 +2,28 @@

Please note that this project is released with a [Contributor Code of Conduct](CODE-OF-CONDUCT.md). By participating in this project you agree to abide by its terms.


## Table of Contents

- [Adding to This List](#adding-to-this-list)
- [Updating Your Pull Request](#updating-your-pull-request)


## Adding to This List

Please ensure your pull request adheres to the following guidelines:

* Search open and closed PRs to avoid duplicate suggestions.
* Specify why the presentation is a must-watch, e.g., what did you learn from it, how will this be of value to developers?
* Use the following format: <pre>`[**Talk Title**](link): Presenter, Event` &#96;Duration&#96;</pre>
- For multiple presenters use a serial comma as appropriate, e.g., Marcia, Jan, and Cindy.
- Don't use an ampersand with the serial comma, e.g., Greg, Peter, & Bobby.
- If the presentation is a screencast or playlist use `(screencast)` or `(playlist)` in lieu of `Event`.
- The duration should be surrounded by backticks (&#96;), e.g., &#96;28:30&#96;.
* Use the correct title of the presentation (don't rely on the title uploaded to YouTube, Vimeo, et al.).
* Use [title-case](https://titlecaseconverter.com/).
* Add suggestions to the end of the appropriate year block; if re-ordering is needed the project maintainer will make a final determination.
- Search open and closed PRs to avoid duplicate suggestions.
- Specify why the presentation is a must-watch, e.g., what did you learn from it, how will this be of value to developers?
- Use the following format: <pre>`[**Talk Title**](link): Presenter, Event` &#96;Duration&#96;</pre>
- For multiple presenters use a serial comma as appropriate, e.g., Marcia, Jan, and Cindy.
- Don't use an ampersand with the serial comma, e.g., Greg, Peter, & Bobby.
- If the presentation is a screencast or playlist use `(screencast)` or `(playlist)` in lieu of `Event`.
- The duration should be surrounded by backticks (&#96;), e.g., &#96;28:30&#96;.
- Use the correct title of the presentation (don't rely on the title uploaded to YouTube, Vimeo, et al.).
- Use [title-case](https://titlecaseconverter.com/).
- Add suggestions to the end of the appropriate year block; if re-ordering is needed the project maintainer will make a final determination.

Thank you for your suggestions!


## Updating Your Pull Request

Sometimes a maintainer will ask you to edit your pull request before it's included. This is normally due to spelling errors or because your PR didn't match the above guidelines guidelines. [This write-up](https://github.com/RichardLitt/knowledge/blob/master/github/amending-a-commit-guide.md) covers the different ways you can change a pull request
Sometimes a maintainer will ask you to edit your pull request before it's included. This is normally due to spelling errors or because your PR didn't match the above guidelines. [This write-up](https://github.com/RichardLitt/knowledge/blob/master/github/amending-a-commit-guide.md) covers the different ways you can change a pull request