README is outdated about obtaining releases
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 88/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- markdown
- Domain
- documentation
Research direction
Open README.md and find the section on obtaining BrailleBlaster that says no production-ready release exists and points users at version 2.1. Rewrite that section so it states BrailleBlaster 3.2.5 is available and ready for production use, keeping the surrounding wording and formatting intact. Done when the section no longer contains the outdated 2.1/no-release claims and renders correctly on the repository landing page.
Written by the indexing model from the issue text.
Description
The README.md which is displayed on the GitHub repository page has outdated information. In the section about obtaining BrailleBlaster it states there is no production ready release of the open-source BrailleBlaster and suggests users after a production ready version to use the 2.1 version. This information should be updated to reflect the situation where BrailleBlaster 3.2.5 is available and is considered ready for production use.
- Dominant language
- Kotlin
- Stars
- 15
- Forks
- 11
- Avg merge
- 14h 34m
- Merged PRs (30d)
- 29
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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 aphtech/brailleblaster
-
Linux: Braille View shows ASCII because APH_Braille_Font .otf files aren't installedPossibly taken @mnstewart232 claimed this 3 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
aphtech/brailleblaster#188 · 1 assignee ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
aphtech/brailleblaster#152 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
aphtech/brailleblaster#151 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
aphtech/brailleblaster#149 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
aphtech/brailleblaster#145 ·
Maintainers usually reply within 1 day
All issues in aphtech/brailleblaster
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
SimonHalvdansson/Harmonic-HN#399 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
[Request] 李跳跳Openrequest-adaption
Difficulty 2/5 Under an hour Newbie friendliness 78/100
BetterAndroid/android-notification-icon-project#799 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
ProdigyV21/ARVIO#832 ·
Maintainers usually reply within 1 day