Display few random issues on repo main page #2311

New Issue

GiteaMirror · 2025-11-02T04:32:15-06:00

GiteaMirror commented

2025-11-02 04:32:15 -06:00

Originally created by @njourdane on GitHub (Sep 8, 2018).

Let's put some entropy salt in our projects!

I like the random page function on Wikipedia, because it offer me the opportunity to learn something that I probably would never found by myself.

What about development platforms?

I suggest an option (eventually it could be deactivated in the repo options) to display 3 random open issues on the repository main page.

The random issues feature could be useful to highlight these kind of dusty issues who don't live for mouths/years, but still opened, in particular on big project where there are a lot of open issues.

I see several scenarios:

a project developer can see an issue waiting to be implemented and maybe say "Hey, this one is not so difficult and everyone is ok with that, I'm going to code it right now!";
a project enthusiast could see an interesting feature waiting for discussion, and participate to the debate;
some users could give their 👍 or 👎 to an issue, or asking for news, or even sharing the issue to friends;
a developer could, "by chance"*, see a difficult issue for which s.he knows exactly how to implement it;
seeing a random feature could motivate, somwhere, sometime, motivate someone to take part in the project.

* We have LEDs because some guy built a defective diode, which was unintentionally emitting some light. A lot of other inventions came to us with serendipity. Let's bring it on our projects.

Originally created by @njourdane on GitHub (Sep 8, 2018). Let's put some entropy salt in our projects! I like the *random page* function on Wikipedia, because it offer me the opportunity to learn something that I probably would never found by myself. What about development platforms? I suggest an option (eventually it could be deactivated in the repo options) to display 3 random open issues on the repository main page. The random issues feature could be useful to highlight these kind of dusty issues who don't live for mouths/years, but still opened, in particular on big project where there are a lot of open issues. I see several scenarios: - a project developer can see an issue waiting to be implemented and maybe say "Hey, this one is not so difficult and everyone is ok with that, I'm going to code it right now!"; - a project enthusiast could see an interesting feature waiting for discussion, and participate to the debate; - some users could give their :+1: or :-1: to an issue, or asking for news, or even sharing the issue to friends; - a developer could, "by chance"__*__, see a difficult issue for which s.he knows exactly how to implement it; - seeing a random feature could motivate, somwhere, sometime, motivate someone to take part in the project. __*__ We have LEDs because some guy built a defective diode, which was unintentionally emitting some light. A lot of other inventions came to us with [serendipity](https://en.wikipedia.org/wiki/Serendipity). Let's bring it on our projects.

GiteaMirror added the type/proposal topic/ui labels 2025-11-02 04:32:15 -06:00

GiteaMirror commented

2025-11-02 04:32:17 -06:00

@Larivact commented on GitHub (Jan 23, 2019):

I would find random issues on the main page seriously distracting. I think entropy could be more elegantly introduced with a new Random sort method. This would:

make it entirely optional and not distract or confuse anybody,
be more powerful because it works with filtering (e.g. by tag) and
work consistently across all repositories (instead of being disabled in some).

Side note: the random seed would need to be put in the URL so that pagination still works.

@Larivact commented on GitHub (Jan 23, 2019): I would find random issues on the main page seriously distracting. I think entropy could be more elegantly introduced with a new Random sort method. This would: * make it entirely optional and not distract or confuse anybody, * be more powerful because it works with filtering (e.g. by tag) and * work consistently across all repositories (instead of being disabled in some). Side note: the random seed would need to be put in the URL so that pagination still works.

GiteaMirror referenced this issue

2025-11-02 06:10:50 -06:00

crash: 1.11.1 randomly crash with SIGBUS when creating an issue #5009

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#2311