Gem staleness indication
Nobody has claimed this yet.
- Dominant language
- SCSS
- Stars
- 26
- Forks
- 32
- PR merge metrics
- No merged PRs in 30d
Description
Now that MRuby has been around for a number of years it's a bit tricky to sort through gems to know what's possibly up-to-date and what's likely abandoned and no longer compatible. Is there any interest in adding a bit of metadata to mgems.yml to make it easier to highlight what's likely maintained and what's likely not?
https://fundamental-code.com/mruby-timeline/ is something I put together with a bit of git log parsing. There are plenty of short lived gems from 2016 and earlier which I'd wager likely have some compatibility issues with how MRuby has evolved over the years.
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
Review the existing mgems.yml metadata and the linked mruby timeline, including its git-log parsing, to understand what staleness signals are available. Define the metadata and presentation requirements with maintainers; done means the proposal has an agreed scope for identifying and highlighting likely-maintained or abandoned gems.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- developer-experience
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100