High-level direction for log-forwarder. This is not a commitment schedule — priorities shift based on issues, PRs, and production feedback.
See open issues and Discussions for active work.
- Keep
maingreen: CI, coverage ≥80% perinternal/*package, Dependabot, smoke tests. - Document and stabilize the custom-binary extension model (
examples/custom/). - Operational hardening: watermarks, dead letter, hibernate/wake, metrics/readiness.
- Published GitHub Releases with notes from CHANGELOG.md (tags exist; release workflow TBD).
- Pre-built release binaries (GoReleaser or similar) for common platforms.
- Comparison and migration guides (Fluent Bit, Fluentd, Vector) on the wiki.
- Seed
good first issuetasks for new contributors.
- Additional built-in sinks or enrichers driven by community demand.
- OpenSSF Scorecard improvements and optional badge.
- Helm chart or Kubernetes operator (today: sidecar/DaemonSet docs on wiki).
- Multi-sink fan-out in a single process (by design: one process → one sink).
copytruncatelog rotation support.- Stable public Go API outside this module (extensions compile against
internal/*in-tree).
- Open a Discussion to propose an idea.
- If there is agreement, open a feature issue or PR.
- For large changes, discuss in an issue before a large PR.