Add Chalice

[ghost]

https://github.com/chalice-dev/awesome-chalice#readme

Chalice is a framework for writing serverless Python applications on AWS Lambda.

I reviewed:

• Add Web Effect #1983
• Add Full-Text Search #1954

https://github.com/chalice-dev/awesome-chalice#readme

This is an awesome list of need-to-know links relating to AWS Chalice, a previously hidden gem for writing serverless Python applications on AWS Lambda.

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.

Requirements for your pull request

• Don't waste my time. Do a good job, adhere to all the guidelines, and be responsive.
• You have to review at least 2 other open pull requests.
  Try to prioritize unreviewed PRs, but you can also add more comments to reviewed PRs. Go through the below list when reviewing. This requirement is meant to help make the Awesome project self-sustaining. Comment here which PRs you reviewed. You're expected to put a good effort into this and to be thorough. Look at previous PR reviews for inspiration. Just commenting “looks good” or simply marking the pull request as approved does not count! You have to actually point out mistakes or improvement suggestions.
• You have read and understood the instructions for creating a list.
• This pull request has a title in the format Add Name of List.
  • ✅ Add Swift
  • ✅ Add Software Architecture
  • ❌ Update readme.md
  • ❌ Add Awesome Swift
  • ❌ Add swift
  • ❌ add Swift
  • ❌ Adding Swift
  • ❌ Added Swift
• Your entry here should include a short description about the project/theme of the list. It should not describe the list itself. The first character should be uppercase and the description should end in a dot. It should be an objective description and not a tagline or marketing blurb.
  • ✅ - [iOS](…) - Mobile operating system for Apple phones and tablets.
  • ✅ - [Framer](…) - Prototyping interactive UI designs.
  • ❌ - [iOS](…) - Resources and tools for iOS development.
  • ❌ - [Framer](…)
  • ❌ - [Framer](…) - prototyping interactive UI designs
• Your entry should be added at the bottom of the appropriate category.
• The suggested Awesome list complies with the below requirements.

Requirements for your Awesome list

• 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.
• Don't open a Draft / WIP pull request while you work on the guidelines. A pull request should be 100% ready and should adhere to all the guidelines when you open it.
• Run awesome-lint on your list and fix the reported issues. If there are false-positives or things that cannot/shouldn't be fixed, please report it.
• The default branch should be named main, not master.
• Includes a succinct description of the project/theme at the top of the readme. (Example)
  • ✅ Mobile operating system for Apple phones and tablets.
  • ✅ Prototyping interactive UI designs.
  • ❌ Resources and tools for iOS development.
  • ❌ Awesome Framer packages and tools.
• It's the result of hard work and the best I could possibly produce.
  If you have not put in considerable effort into your list, your pull request will be immediately closed.
• The repo name of your list should be in lowercase slug format: awesome-name-of-list.
  • ✅ awesome-swift
  • ✅ awesome-web-typography
  • ❌ awesome-Swift
  • ❌ AwesomeWebTypography
• The heading title of your list should be in title case format: # Awesome Name of List.
  • ✅ # Awesome Swift
  • ✅ # Awesome Web Typography
  • ❌ # awesome-swift
  • ❌ # AwesomeSwift
• Non-generated Markdown file in a GitHub repo.
• The repo should have awesome-list & awesome as GitHub topics. I encourage you to add more relevant topics.
• Not a duplicate. Please search for existing submissions.
• Only has awesome items. Awesome lists are curations of the best, not everything.
• Does not contain items that are unmaintained, has archived repo, deprecated, or missing docs. If you really need to include such items, they should be in a separate Markdown file.
• Includes a project logo/illustration whenever possible.
  • Either centered, 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.
    • Can be placed centered if the list has a centered graphics header.
  • 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 nested lists, preferably none.
  • Must not feature Contributing or Footnotes sections.
• Has an appropriate license.
  • We strongly recommend the CC0 license, but any Creative Commons license will work.
    • Tip: You can quickly add it to your repo by going to this URL: https://github.com/<user>/<repo>/community/license/new?branch=main&template=cc0-1.0 (replace <user> and <repo> accordingly).
  • A code license like MIT, BSD, Apache, GPL, etc, is not acceptable. Neither are WTFPL and Unlicense.
  • Place a file named license or LICENSE in the repo root with the license text.
  • Do not add the license name, text, or a Licence section to the readme. GitHub already shows the license name and link to the full text at the top of the repo.
  • To verify that you've read all the guidelines, please comment on your pull request with just the word unicorn.
• Has contribution guidelines.
  • The file should be named contributing.md. Casing is up to you.
  • It can optionally be linked from the readme in a dedicated section titled Contributing, positioned at the top or bottom of the main content.
  • The section should not appear in the Table of Contents.
• All non-important but necessary content (like extra copyright notices, hyperlinks to sources, pointers to expansive content, etc) should be grouped in a Footnotes section at the bottom of the readme. The section should not be present in the Table of Contents.
• 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.
  • Consistent and correct naming. For example, Node.js, not NodeJS or node.js.
• Doesn't use hard-wrapping.
• Doesn't include a Travis badge.
  You can still use Travis for list linting, but the badge has no value in the readme.
• Doesn't include an Inspired by awesome-foo or Inspired by the Awesome project kinda link at the top of the readme. The Awesome badge is enough.

Go to the top and read it again.

[ghost]

unicorn

[TheaMorin]

Your PR doesn't suffer from most of the mishaps that I see from other awesome lists, but there are a couple things that I picked up on.

I'll defer to the repository maintainers for whether it must be changed as I lack experience for judgment here. Take this feedback with a huge grain of salt.

---

From the manifesto, there's this quote:

Comment on why something is awesome

Apart from suggesting a particular item on your list, you should also inform your readers why it's on the list and how they will benefit from it.

I think the spirit of that isn't present in a lot of the link descriptions… which read more as descriptions rather than recommendations. For example:

---

I also think that the "Blogs" section may be better titled as "Blog Articles". Again, I'll defer to the actual maintainers of awesome as to whether or not you should also include text on why those blog articles are critical background reading.

Hope this is helpful!

[ghost]

This is an advanced awesome list. Devs will know if they need paid tracing or hard encryption, and why that's awesome (I'm also not seeing that I have to explain what's awesome about hard encryption, which would take a lot of space). The last three sections don't have additional descriptions, because they have descriptive titles.

[ghost]

For comparison, this is a sister list: https://github.com/kolomied/awesome-cdk

[TheaMorin]

I think that sister list does a good job of balancing descriptions between why and what.

[ghost]

Specific examples would help. You highlighted paid tracing. In your opinion, what more should be said about paid tracing? There is free tracing on the list, and the paid tracing options are all worth evaluating. PR's accepted.

[TheaMorin]

I'll say again that I'm speculating with my feedback. I think @sindresorhus could tell me if I'm off-base and maybe this is ready to merge as-is.

I'd imagine that the description should be whatever distinguishes them from each other within the market.

In the cdk list, I've highlighted the two lines that were most similar in description:

Maybe it's as simple as "A commercial tracing system using <sentry.io>"

[ghost]

I removed them from the list because I can't include a cost/benefit analysis, which depends on your use-case. Thanks.

[sindresorhus]

Header: Blogs => Blog posts or Articles

[sindresorhus]

The list header looks weird. The top part is right-aligned and then left-aligned.

[ghost]

Fixed and fixed

[sindresorhus]

It looks weird to have both a graphic header and also text header saying the same. You should pick one.

[ghost]

Fixed

[ghost]

I went with the text header version instead, seems to look much better, than awesome+chalice logos side-by-side.

[sindresorhus]

Tweet: https://twitter.com/awesome__re/status/1384075183342854147