[PR #954] [MERGED] Add Deep Learning Education #3791

New Issue

2026-04-15T11:23:19-05:00

GiteaMirror commented

2026-04-15 11:23:19 -05:00

📋 Pull Request Information

Original PR: https://github.com/sindresorhus/awesome/pull/954
Author: @guillaume-chevalier
Created: 5/8/2017
Status: ✅ Merged
Merged: 10/11/2017
Merged by: @sindresorhus

Base: master ← Head: patch-1

📝 Commits (2)

5ccd0b6 Added useful learning resources for Deep Learning
7031619 Update readme.md

📊 Changes

1 file changed (+1 additions, -0 deletions)

View changed files

📝 readme.md (+1 -0)

📄 Description

https://github.com/guillaume-chevalier/awesome-deep-learning-resources

Hi there! I have built an "awesome list" on how to learn to do Deep Learning learning. I also give this list a more "personal" flavor where users can take my list as a template. By personalized, I mean that they put their name on it in a way that they have very carefully reviewed (and found useful) all the content they have listed on their own sub-list (like I did - only awesome things are found in my list). I encourage forks and contribution to the awesome ecosystem. Also, on top of all I believe that the subject of deep learning is important, just take a look at how much "Machine Learning" and "Deep Learning" are trendy compared to "Computer Programming" on the Google Trends, it's through the roof! And it is promising (see link below). You could probably soon even have a complete section dedicated to Artificial Intelligence (that is including Machine Learning, Quantum Machine Learning, Deep Learning, Computer Vision, Speech and Natural Language Processing, and also this almost includes Data Science) - in fact the Computer Science title (under which I have put my new awesome list) could almost be renamed Artificial Intelligence if it wasn't of a few of those sub-lists which are not exactly about that. See https://www.google.ca/trends/explore?date=all&q=machine%20learning,deep%20learning,data%20science,computer%20programming

By submitting this pull request I confirm I've read and complied with the below requirements.

I have read and understood the contribution guidelines and the instructions for creating a list.
This pull request has a descriptive title.
For example, Add Name of List, not Update readme.md or Add awesome list.
The entry in the Awesome list should:
- Include a short description about the project/theme of the list. It should not describe the list itself.
  Example: - [Fish](…) - User-friendly shell., not - [Fish](…) - Resources for Fish..
- Be added at the bottom of the appropriate category.
The list I'm submitting complies with these requirements:
- Has been around for at least 30 days.
  That means 30 days from either the first real commit or when it was open-sourced. Whatever is most recent.
- It's the result of hard work and the best I could possibly produce.
- Non-generated Markdown file in a GitHub repo.
- Includes a succinct description of the project/theme at the top of the readme. (Example)
- The repo should have awesome-list & awesome as GitHub topics. I encourage you to add more relevant topics.
- Not a duplicate.
- Only has awesome items. Awesome lists are curations of the best, not everything.
- Includes a project logo/illustration whenever possible.
  - Placed at the top-right of the readme. (Example)
  - The image should link to the project website or any relevant website.
  - The image should be high-DPI. Set it to maximum half the width of the original image.
- Entries have a description, unless the title is descriptive enough by itself. It rarely is though.
- Has the Awesome badge on the right side of the list heading,
- Has a Table of Contents section.
  - Should be named Contents, not Table of Contents.
  - Should be the first section in the list.
- Has an appropriate license.
  - That means something like CC0, not a code licence like MIT, BSD, Apache, etc.
  - If you use a license badge, it should be SVG, not PNG.
- Has contribution guidelines.
  - The file should be named contributing.md. Casing is up to you.
- Has consistent formatting and proper spelling/grammar.
  - Each link description starts with an uppercase character and ends with a period.
    Example: - [AVA](…) - JavaScript test runner.
  - Drop all the A / An prefixes in the descriptions.
  - Consistent and correct naming. For example, Node.js, not NodeJS or node.js.
- Doesn't include a Travis badge.
  You can still use Travis for list linting, but the badge has no value in the readme.
Go to the top and read it again.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/sindresorhus/awesome/pull/954 **Author:** [@guillaume-chevalier](https://github.com/guillaume-chevalier) **Created:** 5/8/2017 **Status:** ✅ Merged **Merged:** 10/11/2017 **Merged by:** [@sindresorhus](https://github.com/sindresorhus) **Base:** `master` ← **Head:** `patch-1` --- ### 📝 Commits (2) - [`5ccd0b6`](https://github.com/sindresorhus/awesome/commit/5ccd0b6273110004abcc0c17ce532ffd31b58a70) Added useful learning resources for Deep Learning - [`7031619`](https://github.com/sindresorhus/awesome/commit/703161958e8ca5bb0e436de8a650a89dffaf8282) Update readme.md ### 📊 Changes **1 file changed** (+1 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `readme.md` (+1 -0) </details> ### 📄 Description **https://github.com/guillaume-chevalier/awesome-deep-learning-resources** **Hi there! I have built an "awesome list" on how to learn to do Deep Learning learning. I also give this list a more "personal" flavor where users can take my list as a template. By personalized, I mean that they put their name on it in a way that they have very carefully reviewed (and found useful) all the content they have listed on their own sub-list (like I did - only awesome things are found in my list). I encourage forks and contribution to the awesome ecosystem. Also, on top of all I believe that the subject of deep learning is important, just take a look at how much "Machine Learning" and "Deep Learning" are trendy compared to "Computer Programming" on the Google Trends, it's through the roof! And it is promising (see link below). You could probably soon even have a complete section dedicated to `Artificial Intelligence` (that is including `Machine Learning`, `Quantum Machine Learning`, `Deep Learning`, `Computer Vision`, `Speech and Natural Language Processing`, and also this almost includes `Data Science`) - in fact the `Computer Science` title (under which I have put my new awesome list) could almost be renamed `Artificial Intelligence` if it wasn't of a few of those sub-lists which are not exactly about that. See https://www.google.ca/trends/explore?date=all&q=machine%20learning,deep%20learning,data%20science,computer%20programming** # By submitting this pull request I confirm I've read and complied with the below requirements. - I have read and understood the [contribution guidelines](https://github.com/sindresorhus/awesome/blob/master/contributing.md) and the [instructions for creating a list](https://github.com/sindresorhus/awesome/blob/master/create-list.md). - This pull request has a descriptive title. For example, `Add Name of List`, not `Update readme.md` or `Add awesome list`. - The entry in the Awesome list should: - Include a short description about the project/theme of the list. **It should not describe the list itself.** Example: `- [Fish](…) - User-friendly shell.`, not `- [Fish](…) - Resources for Fish.`. - Be added at the bottom of the appropriate category. - The list I'm submitting complies with these requirements: - **Has been around for at least 30 days.** That means 30 days from either the first real commit or when it was open-sourced. Whatever is most recent. - It's the result of hard work and the best I could possibly produce. - Non-generated Markdown file in a GitHub repo. - **Includes a succinct description of the project/theme at the top of the readme.** [(Example)](https://github.com/willempienaar/awesome-quantified-self) - The repo should have `awesome-list` & `awesome` as [GitHub topics](https://help.github.com/articles/about-topics). I encourage you to add more relevant topics. - Not a duplicate. - Only has awesome items. Awesome lists are curations of the best, not everything. - Includes a project logo/illustration whenever possible. - Placed at the top-right of the readme. [(Example)](https://github.com/sindresorhus/awesome-electron) - The image should link to the project website or any relevant website. - The image should be high-DPI. Set it to maximum half the width of the original image. - Entries have a description, unless the title is descriptive enough by itself. It rarely is though. - Has the [Awesome badge](https://github.com/sindresorhus/awesome/blob/master/awesome.md#awesome-badge) on the right side of the list heading, - Has a Table of Contents section. - Should be named `Contents`, not `Table of Contents`. - Should be the first section in the list. - Has an [appropriate license](https://github.com/sindresorhus/awesome/blob/master/awesome.md#choose-an-appropriate-license). - That means something like CC0, **not a code licence like MIT, BSD, Apache, etc.** - If you use a license badge, it should be SVG, not PNG. - Has [contribution guidelines](https://github.com/sindresorhus/awesome/blob/master/awesome.md#include-contribution-guidelines). - The file should be named `contributing.md`. Casing is up to you. - Has consistent formatting and proper spelling/grammar. - Each link description starts with an uppercase character and ends with a period. Example: `- [AVA](…) - JavaScript test runner.` - Drop all the `A` / `An` prefixes in the descriptions. - Consistent and correct naming. For example, `Node.js`, not `NodeJS` or `node.js`. - Doesn't include a Travis badge. You can still use Travis for list linting, but the badge has no value in the readme. - Go to the top and read it again. --- 🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

GiteaMirror added the pull-request label 2026-04-15 11:23:19 -05:00

GiteaMirror closed this issue