open-feature / open-feature/flagd
[DOCS] Establish and publish flagd communication policy
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 998
- Forks
- 136
- Avg merge
- 4d 8h
- Merged PRs (30d)
- 11
Description
Define official channels (GitHub Releases, Release Notes) and supplementary channels (Slack, website blog)
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.
Research direction
Start by reviewing the requested communication channels: GitHub Releases, Release Notes, Slack, and the website blog. Define which channels are official versus supplementary, then publish the resulting flagd communication policy and verify that each named channel is covered.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100