No public documentation on why "--classic" is required (or desired)
Open
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 32
- Forks
- 5
- Avg merge
- 14h 17m
- Merged PRs (30d)
- 1
Description
Pages that came up through an initial Google search for answers:
- https://www.ruby-lang.org/en/news/2018/11/08/snap/
- https://snapcraft.io/ruby
- https://snapcraft.io/install/ruby/ubuntu
- https://www.ruby-lang.org/en/downloads/ (this site doesn't even mention snap "Ways of Installing Ruby" section)
Contributor guide
No contributing guide indexed for this repository
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 comparing the linked Ruby and Snap pages, especially the Ruby downloads page and the snap installation instructions, to determine where the missing explanation belongs. Document why the Ruby snap requires or recommends --classic, with the change complete when public installation guidance explains that choice clearly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100