Support
Thank you for your interest in the Pelicans Riding Bicycles Enthusiasts Club (PRBEC). This document describes where and how to get help.
Getting Help
| What you need | Where to go |
|---|---|
| A pelican isn’t rendering in my browser | Open a GitHub issue with [RENDER] in the title |
| I want to submit a new pelican | See CONTRIBUTING.md |
| I want to report a vulnerability | See SECURITY.md — do not open a public issue |
| I want to report a Code of Conduct violation | See CODE_OF_CONDUCT.md |
| I have a question about the license | See LICENSE.md, then open a discussion |
| I want to put a pelican on a t-shirt / sticker / mural | Go ahead. See LICENSE.md for attribution guidance |
| I want to use these pelicans for something that would harm a person | See LICENSE.md. The answer is no |
| I’d like to join PRBEC | Contribute a merged pelican. That makes you a contributor, which is better than a member |
| I have an actual pelican emergency | Contact your local wildlife rescue. We are not equipped |
Commercial Support
PRBEC does not offer commercial support, service-level agreements, uptime guarantees, or professional services. This is a repository of SVG files curated by hobbyists. There is no uptime to guarantee. The SVGs are files. They will be there.
Community
At present the community coordinates entirely through this repository’s issues and pull requests. There is no Discord, no Slack, no Matrix, no mailing list, no newsletter, no podcast, no Substack, no conference. There may be a conference one day. There will not be a podcast.
Response Times
Maintainers respond as time permits. Reasonable expectations:
- Bug reports on existing pelicans: within 2 weeks.
- PRs adding new pelicans: within 4 weeks.
- Security reports: within 7 days (see
SECURITY.md). - General questions: eventually.
Response times may be affected by the real-world migratory patterns of the maintainer, as well as the weather, the season, and whether the maintainer is on a bicycle at the moment you wrote in.