Add Humane Technology

[aschrijver]

https://github.com/engagingspaces/awesome-humane-tech

Curated list for any open-source projects that improve society, i.e. dealing with ethics, privacy, transparency, health, etc. Related to recently founded The Center for Humane Technology

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.

[legodude17]

Putting the awesome badge next to every list in that bottom list looks kind of weird.

[aschrijver]

Yea maybe.. I wanted to create a clear distinction. Kinda like it also.

Is that hampering inclusion in top-level awesome?

[sindresorhus]

Hey, sorry for the lack of response, please see #1363.

[aschrijver]

Hi @sindresorhus

Great to hear you are incorporating the review system. It should be a great help making your life easier :)

I did a bunch of reviews just after our discussing this on June 5th (#1323 (comment)). Basically went for all PR's without comments, some of which are now visibile in my notifications because you added a comment:

• Add Amazon Web Services Alternatives #1090
• Add Decentralized Exchange list #1219
• Add Amazon Web Services Alternatives #1090
• Add Language Engineering #1149
• Add SailfishOS #1218

There are more I reviewed, but I'd have to open all PR's one by one to find them now.

I just resolved the merge conflict of other PR's that have been added since.

[sindresorhus]

Includes a project illustration whenever possible.
The image should be high-DPI. Set it to maximum half the width of the original image.

[sindresorhus]

It just looks noisy to use the Awesome badge here: https://github.com/engagingspaces/awesome-humane-tech#related-awesomeness

[aschrijver]

Thank you @sindresorhus !

I have removed the superfluous badges from the list. Also I have reviewed some additional PR's:

• Add Roslyn #1317
• Add Software Patreons #1319
• Add Question Answering #1385

I resolved the merge conflict again too.

[AvatarSenju]

complies with all the given guidelines

[aschrijver]

Thank you for reviewing @AvatarSenju !

[sindresorhus]

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