luarocks / luarocks/luarocks-site

Providing some additional stats on rocks would be very helpful.

Open
#83 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
MoonScript
Stars
201
Forks
50
PR merge metrics
No merged PRs in 30d

Description

@leafo It's great that you have created and maintained this as it is something the Lua community sorely needed. I'm sure you are familiar with the rubygems.org site as this seems somewhat modeled after it.

This is not a but/issue per se, but rather an enhancement request. It would be truly beneficial to add some stats similar to what Ruby Toolobox provides https://www.ruby-toolbox.com.

https://www.ruby-toolbox.com/search?utf8=%E2%9C%93&q=socket

Here when you search you will see additional details (First release date, Most recent release date, general dev activity measurement, etc...) These are very beneficial in helping decide which results someone should be considering. If a rock has only had 1 release and not been updated in 3 years, then maybe it isn't even compatible with versions of Lua and might not to waste my time take a closer look at that one. It really helps as a first level noise filter.

The other thing that happens on ruby-toolbox is that the libraries are categorized. So when you click on a particular library and go to it's detail page you will see it's categorization breadcrumb trail along the top.

https://www.ruby-toolbox.com/projects/eventmachine

By clicking on the categorization you will then see a full list of libraries that match that categorization. It is essentially a duplicate of the search results page, but the results shown are the category match rather than a search term.

https://www.ruby-toolbox.com/categories/Concurrent_Processing

Thanks for your consideration.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files, tests, or entry points are mentioned. First define the scope for release and activity statistics, rock categorization, category browsing, and how these should appear in search and detail pages; the work is done when those requested website behaviors are specified and implemented.

Written by the indexing model from the issue text.

Assessment

Tech stack
lua
Domain
analytics, search, web-dev
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.