jgroups-extras / jgroups-extras/jgroups-aws
Magic number handling
Open
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 17
- Forks
- 12
- Avg merge
- 10d 15h
- Merged PRs (30d)
- 3
Description
Review whether we should we do the same here as we did here? https://github.com/jgroups-extras/jgroups-mongo/issues/6#event-22186350698
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 reading the jgroups-aws discovery protocol implementation and the referenced jgroups-mongo issue #6. Determine what “magic number handling” refers to here and whether the same decision applies. Done means the project has an agreed, clearly scoped change or a documented reason not to make one.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, java
- Domain
- cloud, distributed-systems
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100