Wipe the Public Development Tracker

[Broda]

What does this suggestion change/add/remove:
Completely wipe and reset the development tracker of things dated back before 1st January 2025.

Has something similar been suggested before? If so, why is your suggestion different?:
Don't believe so.

Possible Positives of the suggestion (At least 2):
Enables content to refocus on new ideas and stop outdated suggestions from being implemented far too later on in the server's life cycle.

Possible Negatives of the suggestion:
May end up with some "new" suggestions of wiped things. But I'd argue that just shows interest in the things that players still want in the community.

Based on the Positives & Negatives, why should this suggestion be accepted:
Refer to this: https://github.com/orgs/civilnetworks-projects/projects/3/views/1

The github has 100s of old items on it that will never get done at the development speed we are currently experiencing within the community. An opportunity to refocus and unburden the developers/content team would be beneficial to the continuity of community health.

I want to stipulate that bugs should not be wiped from the tracker for obvious reasons.

Image below just highlights the problem

 

[Michael Dzhetnikov]

did you like, ask the devs about this

 

[Broda]

did you like, ask the devs about this

They have forum access and this is the purpose of suggestions. No suggestion is gatekept due to not asking people prior.

 

[Michael Dzhetnikov]

They have forum access and this is the purpose of suggestions. No suggestion is gatekept due to not asking people prior.

yeah but that does happen

 

[Aphex]

View attachment 21981

Kw1ll my beloved…

I agree with the sentiment of clearing older things on the public development tracker. As far as I can tell, anything older than 2 years ago is just seen as impossible (at least when I was CT). Also the oldest unfinished project on the public tracker is VNodeGraph… that has a 180 pound bounty or something.

 

[Dusk]

Over commitment bias is a real thing even for professionals.
I agree with the stance however I would probably filter out what actually needs removed and keep ones that are actually good.

 

[Emilia Foddg]

Definitely not me scraping the dev tracker for potential suggestion ideas that can be reformed, rephrased and recontextualised for basically free suggestion points

I see the benefits, but something rubs me wrong about this that I can't quite put my finger on. EDIT: Figured it out. Github Projects does not have a way to filter and/or sort cards by date in any form. You're basically asking someone to go through the entire dev tracker and sift through all the cards one by one to judge them based on something as arbitrary as time.

Plus, that's the public dev tracker. There is also a private dev tracker that we don't see for obvious reasons. I don't know the specifics, but I feel like this may actually prove to be more work than it's worth.

This is one of those things that grew into those huge beasts that even trying to sort it out becomes an issue in and of itself

Unless I'm wrong about date filtering/sorting. EDIT: Which as it turns out, I am.
+/- Neutral +Support

 

[Sanctum]

Github Projects does not have a way to filter and/or sort cards by date in any form.

It may be old, but its not that archaic.

 

[Emilia Foddg]

It may be old, but its not that archaic.

I see. I was experiencing a skill issue, then.

 

[Zen]

I'm fairly sure that this is part of CT's duties. They're supposed to go through the backlog now and then and update/remove things that are old/outdated/no longer wanted/need changes. iirc CT was told to do exactly this shortly before I left staff. Not sure if they're just not doing that, or have been told not to, or haven't been given permission to close tickets as needed or what.

 

[Jack G]

I'm fairly sure that this is part of CT's duties. They're supposed to go through the backlog now and then and update/remove things that are old/outdated/no longer wanted/need changes. iirc CT was told to do exactly this shortly before I left staff. Not sure if they're just not doing that, or have been told not to, or haven't been given permission to close tickets as needed or what.

There's a lot more to it than that, more so for SCP. First and foremost, both Content Team from USA and UK would need to meet to discuss what would need removing whilst also keeping on top of the suggestions there is currently.

I think for SCP, this is ALWAYS going to happen, purely with the output of suggestions compared to the amount of time a suggestion is gonna take to implement as a developer. It's just not feasible. Just look at the SCP Suggestions area for both servers, there's no way there won't be a backlog. It being only 2 years is a credit to being harsh with accepting suggestions, MRPs is backlogged 3/4 years with stuff that we genuinely want/need adding but we don't have the devs to pick up any work where there's still only 80 issues logged on there.

 

[Zen]

There's a lot more to it than that, more so for SCP. First and foremost, both Content Team from USA and UK would need to meet to discuss what would need removing whilst also keeping on top of the suggestions there is currently.

I think for SCP, this is ALWAYS going to happen, purely with the output of suggestions compared to the amount of time a suggestion is gonna take to implement as a developer. It's just not feasible. Just look at the SCP Suggestions area for both servers, there's no way there won't be a backlog. It being only 2 years is a credit to being harsh with accepting suggestions, MRPs is backlogged 3/4 years with stuff that we genuinely want/need adding but we don't have the devs to pick up any work where there's still only 80 issues logged on there.

That's a fair point. I honestly don't think it's actually a huge issue if there are old issues, as long as they're still wanted, and as long as urgent issues are being dealt with quickly. Would be nice to have more devs and more work done, but realistically there's only so much you can do with the number of devs available. For this suggestion, though, as far as I'm aware, CT do go over old suggestions now and then to check if anything needs removing or changing, I just am not sure how often that happens, nor how necessary it really is to be so thorough in removing things because "it's not high priority" or whatever (that's what tags and priority levels are for).

 

[Niox]

7722 chemical, to be added after silksong...
+Support