Improve sorting of entries on 'Compliant projects' page #88

Open
opened 2024-03-08 13:42:30 +00:00 by seabass · 0 comments
Contributor

The vast majority of repositories that are registered with api.reuse.software and that are determined to be REUSE-compliant are from a select set of organizations, and some of these projects in very active development. Because the sorting method currently selects recently-updated repositories first, the repositories from organizations like SAP dominate the first few pages. Whilst such commitment to REUSE is admirable and appreciated, this sorting order perhaps doesn't present the REUSE project in the best possible light to the full range of potential interested parties.

I would suggest changing the default order that projects are shown in, possibly also adding a feature that allows the sorting field to be changed by the user in order that the current method can still be chosen.

My concrete suggestion for a replacement order would be by date of first being registered on the service, as this would give a more balanced indication of which developers are adopting REUSE. Unfortunately, it doesn't look like we have this data for existing entries.

The vast majority of repositories that are registered with api.reuse.software and that are determined to be REUSE-compliant are from a select set of organizations, and some of these projects in very active development. Because the sorting method currently selects recently-updated repositories first, the repositories from organizations like SAP dominate the first few pages. Whilst such commitment to REUSE is admirable and appreciated, this sorting order perhaps doesn't present the REUSE project in the best possible light to the full range of potential interested parties. I would suggest changing the default order that projects are shown in, possibly also adding a feature that allows the sorting field to be changed by the user in order that the current method can still be chosen. My concrete suggestion for a replacement order would be by date of first being registered on the service, as this would give a more balanced indication of which developers are adopting REUSE. Unfortunately, it doesn't look like we have this data for existing entries.
Sign in to join this conversation.
No Milestone
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: reuse/api#88
No description provided.