chainguard-dev / chainguard-dev/dfc
What Sort of Support Should a User Expect?
Open
Nobody has claimed this yet.
documentation
- Dominant language
- Go
- Stars
- 103
- Forks
- 29
- PR merge metrics
- No merged PRs in 30d
Description
It might be helpful to add this to the documentation. How fast a response on issues and PRs? Or "best effort" or something similar?
Contributor guide
No contributing guide indexed for this repository
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
No documentation file, test, or entry point is named. First identify the repository’s documentation location and existing support or contribution guidance; done means adding an agreed response-time or best-effort support policy.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100