Skip to content

Latest commit

 

History

History
141 lines (93 loc) · 5.63 KB

CONTRIBUTING.md

File metadata and controls

141 lines (93 loc) · 5.63 KB
Raw

Contributing to Shields

Shields is a community project. We invite your participation through financial contributions, issues, and pull requests!

Ways you can help

Financial contributions

We welcome financial contributions in full transparency on our open collective. Anyone can file an expense. If the expense makes sense for the development of the community, it will be "merged" into the ledger of our open collective by the core contributors and the person who filed the expense will be reimbursed.

Contributing code

This project has quite a backlog of suggestions! If you're new to the project, maybe you'd like to open a pull request to address one of them:

GitHub issues by-label

Contributing documentation

You can help by improving the project's usage and developer instructions.

  • When you read the documentation, you can fix mistakes and add your own thoughts.
  • When your pull request follows the documentation but the practice changed, consider pointing this out and change the documentation for the next person.

Helping others

You can help with code review, which reduces bugs, and over time has a wonderful side effect of making the code more readable and therefore more approachable. It's also a great way to teach and learn. Feel free to jump in! Be welcoming, appreciative, and helpful. You can perform first reviews of simple changes, like badge additions. These are usually tagged with service badge.

Please review these impeccable guidelines.

You can monitor issues and the chat room, and help other people who have questions about contributing to Shields, or using it for their projects.

Feel free to reach out to one of the maintainers if you need help getting started.

Suggesting improvements

There are a lot of suggestions on file. You can help by weighing in on these suggestions, which helps convey community need to other contributors who might pick them up.

There is no need to post a new comment. Just add a 👍 or ❤️ to the top post.

If you have a suggestion of your own, search the open issues. If you don't see it, feel free to open a new issue.

Spreading the word

Feel free to star the repository. This will help increase the visibility of the project, therefore attracting more users and contributors to Shields!

We're also asking for one-time $10 donations from developers who use and love Shields, please spread the word!

Getting help

There are three places to get help:

  1. If you're new to the project, a good place to start is the tutorial.
  2. If you need help getting started or implementing a change, open an issue with your question. We promise it's okay to do that. If there is already an issue open for the feature you're working on, you can post there.
  3. You can also join the chat room and ask your question there.

Badge guidelines

  • Shields.io hosts integrations for services which are primarily used by developers or which are widely used by developers
  • The left-hand side of a badge should not advertise. It should be a lowercase noun succinctly describing the meaning of the right-hand side.
  • Except for badges using the social style, logos should be turned off by default.

Badge URLs

  • The format of new badges should be of the form /SERVICE/NOUN/PARAMETERS/QUALIFIERS.format. For instance, /gitter/room/nwjs/nw.js.svg. The vendor is gitter, the badge is for rooms, the parameter is nwjs/nw.js, and the format is svg.
  • For services which require a hostname, the badge should be of the form /SERVICE/SCHEME/HOST/NOUN/PARAMETERS/QUALIFIERS.format. For instance, /discourse/https/discourse.example.com/topics.svg.

Coding guidelines

Prettier

This project formats its source code using Prettier. The most enjoyable way to use Prettier is to let it format code for you when you save. You can integrate it into your editor.

Whether you integrate it into your editor or not, a pre-commit hook will run Prettier before a commit by default.

Tests

When adding or changing a service please write tests.

When opening a pull request, include your service name in brackets in the pull request title. That way, those service tests will run in CI.

e.g. [Travis] Fix timeout issues

When changing other code, please add unit tests.

To run the integration tests, you must have redis installed and in your PATH. Use brew install redis, yum install redis, etc. The test runner will start the server automatically.

Code organization

There is a High-level code walkthrough describing the layout of the project.

Logos

We have documentation for logo usage which includes contribution guidance