Update documentation to reflect RabbitMQ developments
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 35/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Stale
- Tech stack
- rabbitmq
- Domain
- documentation
Research direction
Start with the Getting Started page linked in the issue and locate its source in the repository. Update the documentation to recommend RabbitMQ over ActiveMQ, then check the rendered page to confirm the preference is clear.
Written by the indexing model from the issue text.
Description
In particular, the Getting Started page should emphasise using RabbitMQ in preference to ActiveMQ.
- Dominant language
- Python
- Stars
- 6
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
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.
More from DiamondLightSource/python-zocalo
-
Dependency Dashboard Open
Difficulty 5/5 Over a week Newbie friendliness 10/100
All issues in DiamondLightSource/python-zocalo
Similar issues
-
documentation help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
simonw/sqlite-utils#872 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100