TimelyDataflow / TimelyDataflow/timely-dataflow
Your documentation text is superb
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 3.6k
- Forks
- 293
- Avg merge
- 14h 46m
- Merged PRs (30d)
- 4
Description
The blog posts https://github.com/frankmcsherry/blog/blob/master/posts/2015-09-14.md are just an amazing example of straight forward and candid explanations of very technical topics.
Just wanted to say, thank you. We need more people with the abilities to condense and present hard concepts in a simple way.
Cheers.
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
Read the linked blog post at https://github.com/frankmcsherry/blog/blob/master/posts/2015-09-14.md for context. The issue is appreciative feedback and does not identify a file, test, requested change, or completion criteria, so there is no defined implementation path or measurable definition of done.
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
- 5/100