ruby-concurrency / ruby-concurrency/concurrent-ruby
Promoting the Actor implmentation from edge to proper concurrent-ruby?
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 5.8k
- Forks
- 420
- Avg merge
- 20h 45m
- Merged PRs (30d)
- 4
Description
We've been using the Actor implementation from the edge in https://github.com/Dynflow/dynflow for a while and we've hit no issues. Seems like it might be ready to get promoted to the concurrent-ruby proper.
It would also help us with some obstacles we have right now when delivering our code on debian (see https://github.com/theforeman/foreman-packaging/pull/3438).
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 Actor implementation on the edge branch and how Dynflow uses it. Check the linked Foreman packaging pull request for the Debian obstacle and compare the requirements for promotion into concurrent-ruby proper. Done means the promotion scope and release or packaging changes are agreed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100