Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Too many open issues #13874

Closed
numberZero opened this issue Oct 8, 2023 · 11 comments
Closed

Too many open issues #13874

numberZero opened this issue Oct 8, 2023 · 11 comments
Labels
Discussion Issues meant for discussion of one or more proposals @ Meta Not strictly related to MT development Possible close

Comments

@numberZero
Copy link
Contributor

1090 is a lot. A lot. Well enough to drown in. Even if one issue per day would be resolved it would still take 3 years to handle all of them—totally ignoring new ones. A better plan is needed.

@rubenwardy
Copy link
Member

*1091

@rubenwardy
Copy link
Member

There's probably a lot that can just be closed - duplicates and more. Just needs someone to go through it

@Zughy
Copy link
Member

Zughy commented Oct 8, 2023

Closing #13510 was counterproductive, now people will start asking about whether we chose a new name or not. I suggest to reply under the internal discussion instead of closing the issue

@rubenwardy rubenwardy added the Discussion Issues meant for discussion of one or more proposals label Oct 8, 2023
@rubenwardy
Copy link
Member

Just want to point out that anyone can look for duplicates or issues that should be merged

@Zughy
Copy link
Member

Zughy commented Oct 8, 2023

@numberZero there were 1097 issues until three days ago. I've been closing something here and there (and trust me, it's not a fun task) but we can't make miracles. We need more contributors, core devs, possibly bounties as incentive. The blog could suggest to focus on the 300+ bugs we have left open, but the blog is kind of dead at the moment (which brings us back to more contributors). Also, let's not forget that Minetest is a software with a lot of code debt, it takes time to navigate through that and fix it. Do you have any suggestions by the way? I'd be glad to hear it

@Zughy Zughy added the @ Meta Not strictly related to MT development label Oct 8, 2023
@Zughy
Copy link
Member

Zughy commented Oct 8, 2023

Also, we had already reached this number in the past, before I started cleaning the whole repo. Unfortunately, I don't know how much there is now left to clean

@numberZero
Copy link
Contributor Author

numberZero commented Oct 8, 2023

closing something here and there (and trust me, it's not a fun task)

I see. I’ve skimmed through some random issues years old, and each one looks legitimate.

but we can't make miracles.

Noone can.

We need more contributors, core devs,

That won’t help. At the current pace (+48−27 issues last month) 4.5 years of constant effort are necessary to handle everything. Even with 10x contributors and core devs that’d be still half a year.

@Zughy
Copy link
Member

Zughy commented Oct 8, 2023

I'm interested to hear some solution/alternative approach

@Zughy
Copy link
Member

Zughy commented Oct 8, 2023

@jeremyshannon
Copy link
Contributor

From what I've seen, the number of issues listed is less a problem for a project than the number of queued pull requests. Waiting for months while your PR sits around discourages contributors.

@Zughy
Copy link
Member

Zughy commented Oct 10, 2023

Since OP is agreeing on the latest comment, I'll close. If the topic wants to be discussed further, I suggest to use the forum

@Zughy Zughy closed this as not planned Won't fix, can't repro, duplicate, stale Oct 10, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Discussion Issues meant for discussion of one or more proposals @ Meta Not strictly related to MT development Possible close
Projects
None yet
Development

No branches or pull requests

4 participants