percona / percona/percona-messaging
Future: notify stakeholders when canonical messaging changes (Slack/email)
Open
@brianamarie is already working on this.
Since Sep 1, 2026.
Automation & CI
Downstream
Feature / build
MISSING TIMELINE
Needs: product or GTM
P2 - backlog
Roadmap: later
- Dominant language
- Python
- Stars
- 3
- Forks
- 1
- Avg merge
- 15m
- Merged PRs (30d)
- 2
Description
Goal
Add future automation that notifies stakeholders when canonical messaging is updated, so downstream assets are reviewed quickly.
Desired behavior
- Detect meaningful messaging changes in canonical files
- Map likely downstream owners/channels (for example product PMs, legal, web/docs, enablement)
- Send a notification (for example Slack and/or email) with:
- what changed
- likely impacted assets (decks, webpages, datasheets, enablement)
- link to PR/issue and recommended next action
Notes
- Start in report-only mode and tune relevance before broad rollout
- Avoid auto-editing downstream systems in v1
- Align with existing backlog idea for downstream asset tracking and notifications
Acceptance criteria
- Notification trigger rules documented
- Initial owner/channel map proposed
- Prototype notification payload drafted
- Follow-up implementation issue(s) split if scope is large
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.