[PR #1155] [MERGED] Add Speakers #17001

New Issue

GiteaMirror · 2026-05-02T15:10:37-05:00

GiteaMirror commented

2026-05-02 15:10:37 -05:00

📋 Pull Request Information

Original PR: https://github.com/sindresorhus/awesome/pull/1155
Author: @karlhorky
Created: 12/3/2017
Status: ✅ Merged
Merged: 10/1/2018
Merged by: @sindresorhus

Base: master ← Head: add-conferences-and-meetups-section-and-speakers-link

📝 Commits (5)

2795399 Add conferences and meetups section, add speakers
eecc1d3 Merge branch 'master' into add-conferences-and-meetups-section-and-speakers-link
4927259 Update readme.md
99c5d11 Add description
c718cf9 Update readme.md

📊 Changes

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

View changed files

📝 readme.md (+1 -0)

📄 Description

https://github.com/karlhorky/awesome-speakers

Hi, I'm Karl and I'd like to help make it more transparent and easy to find speakers for meetups and conferences. I've started to compile a list of speakers that I'm aware of and the topics that they have spoken about. It has gotten some traction on Twitter and other people have started adding speakers to the list.

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

Please read it multiple times. I spent a lot of time on these guidelines and most people miss a lot.

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.
  - Either fullwidth or 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.
- Includes the Awesome badge.
  - Should be placed on the right side of the readme heading.
  - Should link back to this list.
- Has a Table of Contents section.
  - Should be named Contents, not Table of Contents.
  - Should be the first section in the list.
  - Should only have one level of sub-lists, preferably none.
- Has an appropriate license.
  - That means something like CC0, not a code licence like MIT, BSD, Apache, etc.
  - WTFPL and Unlicense are not acceptable licenses.
  - 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.
  - The link and description are separated by a dash.
    Example: - [AVA](…) - JavaScript test runner.
  - The description starts with an uppercase character and ends with a period.
  - 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/1155 **Author:** [@karlhorky](https://github.com/karlhorky) **Created:** 12/3/2017 **Status:** ✅ Merged **Merged:** 10/1/2018 **Merged by:** [@sindresorhus](https://github.com/sindresorhus) **Base:** `master` ← **Head:** `add-conferences-and-meetups-section-and-speakers-link` --- ### 📝 Commits (5) - [`2795399`](https://github.com/sindresorhus/awesome/commit/2795399ae4313ad4a2b5e681ef7cf594235ed29f) Add conferences and meetups section, add speakers - [`eecc1d3`](https://github.com/sindresorhus/awesome/commit/eecc1d387ec3920a2425d65235532c02dc25eb24) Merge branch 'master' into add-conferences-and-meetups-section-and-speakers-link - [`4927259`](https://github.com/sindresorhus/awesome/commit/49272596e8571fc1ffdde726cd2878859c198f70) Update readme.md - [`99c5d11`](https://github.com/sindresorhus/awesome/commit/99c5d11878caee1f282470c897c5169e15552ad7) Add description - [`c718cf9`](https://github.com/sindresorhus/awesome/commit/c718cf95c483de3c4f623fe2dde92ef87eb443d7) 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/karlhorky/awesome-speakers Hi, I'm Karl and I'd like to help make it more transparent and easy to find speakers for meetups and conferences. I've started to compile a list of speakers that I'm aware of and the topics that they have spoken about. It has gotten some traction [on Twitter](https://twitter.com/karlhorky/status/926243841933500416) and other people have started adding speakers to the list. # By submitting this pull request I confirm I've read and complied with the below requirements. **Please read it multiple times. I spent a lot of time on these guidelines and most people miss a lot.** - 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. - Either fullwidth or 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. - Includes the [Awesome badge](https://github.com/sindresorhus/awesome/blob/master/awesome.md#awesome-badge). - Should be placed on the right side of the readme heading. - Should link back to this list. - Has a Table of Contents section. - Should be named `Contents`, not `Table of Contents`. - Should be the first section in the list. - Should only have one level of sub-lists, preferably none. - 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.** - [WTFPL](http://www.wtfpl.net) and [Unlicense](http://unlicense.org) are not acceptable licenses. - 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. - The link and description are separated by a dash. Example: `- [AVA](…) - JavaScript test runner.` - The description starts with an uppercase character and ends with a period. - 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-05-02 15:10:37 -05:00

GiteaMirror closed this issue

2026-05-02 15:10:38 -05:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/awesome-sindresorhus#17001