Skip to content

Repository navigation

SUPPORT.md

Latest commit

 

History

History
68 lines (42 loc) · 2.98 KB

SUPPORT.md

File metadata and controls

68 lines (42 loc) · 2.98 KB
Raw

Support

Need help with an F5 DevCentral project? Here's how to find it.

Before Asking

A few places worth checking first. Most questions are answered faster this way:

  • The project's README for installation, quick start, and basic usage
  • The project's documentation (if linked from the README)
  • Existing issues: your question may already be answered: https://github.com/f5devcentral/{repository}/issues

Where to Ask

GitHub Issues

For project-specific help (bug reports, feature requests, and "how do I..." questions tied to a specific repository), open an issue on that project's GitHub page using the appropriate template.

Issues are good for:

  • Bug reports (use the bug report template)
  • Feature requests (use the feature request template)
  • Project-specific questions (use the question label)
  • Security vulnerabilities. Actually, don't open an issue for these. See SECURITY.md instead.

When asking for help, include:

  • What you're trying to do
  • What you expected to happen
  • What actually happened
  • Your environment (OS, versions, configuration)
  • Minimal reproducible example if applicable
  • Steps you've already tried

The more context you give, the faster you get useful answers.

F5 DevCentral Community

For broader questions that aren't tied to a specific repo (best practices, integration patterns, how F5 products work together, or just connecting with other folks doing similar things), head to community.f5.com.

The DevCentral community has been around since 2003 and brings together F5 users, partners, and engineers from all over the world. If your question is "how do other people approach X with F5?" rather than "is X broken in this repo?", community.f5.com is the better starting point.

Response Times

F5 DevCentral projects are maintained by a mix of F5 employees and community contributors, many doing this alongside other work. We'll do our best to respond promptly:

  • Critical security issues: as fast as possible; see SECURITY.md
  • Bug reports: as soon as maintainers can triage
  • Feature requests: as time and project priorities permit
  • Questions: community-driven, no guaranteed response time

If something is genuinely urgent and you're an F5 customer, your existing support channels are the fastest path.

Contributing Back

Found a solution to your problem? Pay it forward:

  • Answer questions in issues or on community.f5.com
  • Improve the documentation (submit a PR; see CONTRIBUTING.md)
  • Fix the bug you discovered

Code of Conduct

All support interactions are governed by our Code of Conduct. Be patient, be respectful, be constructive. We're all here to learn and build.

F5 DevCentral projects are community resources, not commercial products. If you're an F5 customer looking for commercial or enterprise support on F5 solutions themselves, see MyF5 and your existing support channels.