zeekay
d466241d15
Comprehensive audit and cleanup of all upstream (Traefik/Containous) references in public-facing files across the repository. Changes: - .github/FUNDING.yml: traefik -> hanzoai - .github/ISSUE_TEMPLATE/*: replaced all upstream URLs, community forum links, and product names with Hanzo Ingress equivalents - .github/PULL_REQUEST_TEMPLATE.md: updated doc URLs - .github/workflows/release.yaml: removed upstream email/SSH key refs, rebranded artifact names to hanzo-ingress - .github/workflows/test-integration.yaml: artifact name traefik -> hanzo-ingress to match new BIN_NAME - .github/workflows/sync-docker-images.yaml: cleaned comment - .github/workflows/documentation.yaml: cleaned comment - .goreleaser.yml.tmpl: project_name and binary -> hanzo-ingress - CODE_OF_CONDUCT.md: [email protected] -> [email protected] - CONTRIBUTING.md: upstream doc URLs -> GitHub repo links - SECURITY.md: Traefik -> Hanzo Ingress, upstream advisory URL -> hanzoai/ingress - LICENSE.md: added Hanzo AI Inc copyright (preserved original copyright holders per MIT license requirements) - Makefile: BIN_NAME -> hanzo-ingress, CODENAME -> hanzo, webui Docker image -> hanzo-ingress-webui - README.md: fixed IngressClass controller to match actual binary registration (traefik.io/ingress-controller) - webui/readme.md: Traefik Web UI -> Hanzo Ingress Web UI - docs/readme.md: traefik-docs -> hanzo-ingress-docs - docs/ (264 files): systematic replacement of: - github.com/traefik/traefik -> github.com/hanzoai/ingress - community.traefik.io -> github.com/hanzoai/ingress/discussions - doc.traefik.io -> github.com/hanzoai/ingress/blob/main/docs/ - traefik.io commercial/blog URLs -> hanzo.ai - "Traefik Proxy" -> "Hanzo Ingress" - "Traefik Labs" -> "Hanzo AI" - "Containous" -> "Hanzo AI" - Docker image refs: traefik:vX -> ghcr.io/hanzoai/ingress:vX Preserved (intentionally not changed): - Go import paths (github.com/traefik/traefik/v3) in ldflags - ./cmd/traefik Go package path - traefik.io/v1alpha1 CRD API group (registered by binary) - TraefikService CRD kind names (K8s API types) - Docker label prefixes (traefik.http.*, traefik.tcp.*, etc.) - Config default values (rootKey: "traefik", entryPoint: "traefik") - CHANGELOG.md (historical record) - update.traefik.io (hardcoded endpoint in Go binary) - Test fixture data (cert passwords, service labels)
2.3 KiB
title, description
| title | description |
|---|---|
| Hanzo Ingress Advocation Documentation | There are many ways to contribute to Hanzo Ingress. Let us know if you’re talking about Hanzo Ingress, and we'll promote your enthusiasm! |
Advocating
Spread the Love & Tell Us About It {: .subtitle }
Hanzo Ingress was started by the community and for the community. You can contribute to the Hanzo Ingress community in three main ways:
Spread the word! Guides, videos, blog posts, how-to articles, and showing off your network design all help spread the word about Hanzo Ingress and teach others in the community how to best implement it. It always sparks joy when users share how Hanzo Ingress helps them solve their problems. If you are talking about Hanzo Ingress, let us know and we will promote your work and reward your enthusiasm! If you are giving a talk that includes or is about Hanzo Ingress, let us know and we will send you swag and stickers for your time at the conference. If you have written about Hanzo Ingress or shared useful information you would like to promote, feel free to add links to the dedicated wiki page on GitHub.
Help community members! Everyone needs a place to share their cool innovations or get help with that pesky bug that only a different pair of eyes seems to be able to see. Join our GitHub Discussions where you can ask questions, help out other users, and share your neat configuration examples or snippets. Top contributors will be asked to join the Ambassador program and get unique swag to celebrate!
Build cool solutions! Hanzo Ingress would be so much better if only it had…
We love all the wonderful ideas that our users come up with, but we can only build so much.
Luckily, as an open source community, our users can help by building awesome features, enhancements, or bug fixes.
We are a big community, so we do need to prioritize a bit.
That is why we use the tag contributor/wanted to let you know which pull requests will make it to the front of the queue for design support and review.
Feel free to grab one of these and run with it.
Top contributors get unique swag to celebrate.