Testimonials
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 74
- Forks
- 9
- PR merge metrics
- No merged PRs in 30d
Description
I came across @jvns 's rbspy repo and noticed in the docs there is a way for developers to add testimonials via a main testimonial ticket 💕
Not really sure if/how people are finding and using node-cpp-skel outside of mapbox, but could be cool to have a place to (optionally) capture use-cases and success stories.
cc @mapbox/core-tech
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 repository's existing documentation and contribution entry points, then compare them with the proposed testimonial approach linked in the issue. Done means establishing whether use cases and success stories belong in the project documentation and documenting a clear place or contribution path if they do.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, node.js
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100