New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Smart Contracts #1094

Closed
wants to merge 1 commit into
base: master
from

Conversation

2 participants
@Overtorment

Overtorment commented Oct 16, 2017

https://github.com/Overtorment/awesome-smart-contracts

The list is about platforms where developers can create and run programs, known as Smart Contracts.

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.
      • 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.
@sindresorhus

This comment has been minimized.

Show comment
Hide comment
@sindresorhus

sindresorhus Nov 4, 2017

Owner

Looks like a good start and interesting topic, but I think the list needs more work.

Try again in a few months when the list is more mature.

Owner

sindresorhus commented Nov 4, 2017

Looks like a good start and interesting topic, but I think the list needs more work.

Try again in a few months when the list is more mature.

@sindresorhus

This comment has been minimized.

Show comment
Hide comment
@sindresorhus

sindresorhus Nov 4, 2017

Owner

This document is licensed WTFPL

This is not a good license. Use something better, per above guidelines.

Owner

sindresorhus commented Nov 4, 2017

This document is licensed WTFPL

This is not a good license. Use something better, per above guidelines.

@Overtorment

This comment has been minimized.

Show comment
Hide comment
@Overtorment

Overtorment Feb 21, 2018

@sindresorhus hi, the list is now more mature, and the license is changed. Can you please reopen PR and consider merging it? Thanks!

Overtorment commented Feb 21, 2018

@sindresorhus hi, the list is now more mature, and the license is changed. Can you please reopen PR and consider merging it? Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment