I don't think that issues and discussions are deactivated for good, this is more of a temporary thing until the project gains its momentum back. Removing the references seems not ideal.

Wish we could at least see the old issues/discussions. So much knowledge lost

I'm not sure why discussion is deactivated!

I'm not sure why discussion is deactivated!

Some reasons here...

• I feel that the project's discussion working space doesn't present the kind of environment I'd like to be working in.
• Much of the discussion and issue space isn't being properly directed at the moment and feels to me like its creating a distraction/drag on attention, rather than being genuinely valuable.

An optionmight be to make them public again, but put interaction limits on the repository to prevent ongoing churn. That would resolve the second part of my concerns but doesn't address helping clean up the initial part.

@tomchristie would it be possible to make issues and discussions read only for now? I believe those had a lot of useful information that currently is not accessible.

Also does that also mean that project currently doesn't accept any new features? Only bug/security fixes?

My team just started using DRF, and we're two months in on a major project. It's really unsettling to see a huge source of information about how real people use the framework (bug reports) just disappear.

As a developer, particularly one new to the framework, I rely on issue lists to see if problems I'm running into are correct or incorrect behavior, known issues, if other people have encountered them, if I'm doing it wrong, etc.

I'm not sure what the reasons are for turning off issues here on GitHub, but if there's some problem, please consider turning the issues back on while the problem is resolved.

Yes, tho...

The issue here is that there a problematic environment across the entire GitHub ecosystem that's become normalised.

Anonymous contributors demanding attention in ways that both intentionally and unintentionally end up as a DDOS on project maintainers.

I'm putting a hard limit on this at the moment to reset expectations.

would it be possible to make issues and discussions read only for now?

I have been considering this yes. GitHub doesn't really have controls to allow that, tho it does have a work around in the form of interaction limits.

Hi, there is also a reference to#5181 inthis link you should consider deleting this too

Hi, there is also a reference to#5181 inthis link you should consider deleting this too

Thanks, I've updated my PR.

Unfortunately, my updating the PR removed the approval by@tomchristie and also it's not merged yet. I'm sorry for the extra work ;-(

can we make them collaborators only or read only if possible?

I'm not sure why discussion is deactivated!

Some reasons here...

• I feel that the project's discussion working space doesn't present the kind of environment I'd like to be working in.
• Much of the discussion and issue space isn't being properly directed at the moment and feels to me like its creating a distraction/drag on attention, rather than being genuinely valuable.

An optionmight be to make them public again, but put interaction limits on the repository to prevent ongoing churn. That would resolve the second part of my concerns but doesn't address helping clean up the initial part.

@tomchristie Sorry for the interruption, but I had a thought on this subject that might help.

It sounds like you can limit the interaction with them, and that resolves your second concern.

As for your first concern: If there is no longer any new issues or interactions happening in them, then it means you would have no reason or need to work/examine them any longer. I am thinking that it may resolve your first concern, as you would have no reason to be working in/on the issues since nothing new could be posted in them?

I also remember seeing something on this project recently (not sure if it was a discussion/issue or somewhere else, can't seem to find it anymore) that talked about how this project was in a mature state and generally only changes that helped adapt the DRF to changes in the last Django versions would be the ones generally being accepted/merged in.

It seems like making the discussions public but read-only/non-interactive would be in that same general spirit, ie: keeping things how they are, not adding new features, and only adapting to changes in the framework's dependencies.

Background:

Some of the issue had generally useful information in them. I am thinking making it visible in some way would be a greater benefit than hiding them.

Yes, it does hide the non-useful discussion, but the cost is hiding all of the genuinely useful ones as well. I remember a number of very useful discussions that helped me use this framework over the years. I would love to see them visible again so I can continue to reference them.

To make issues ready-only I searched and found this hacky solution:https://github.com/orgs/community/discussions/64600#discussioncomment-8713177.

I createda repo to test it: it prevents creation of new issues and doesn't prevent commenting on the ones which are already open, but we could lock all existing ones. I don't think it's easy to do in bulk via the UI, but we could script that with thegh command line/their API...

Hi, GitHub's interactions limit feature might be helpful here, though it does not have so much granular control. It allows you to temporarily restrict contributions to a specific group, still allowing others to access to the precious knowledge base. I think this feature was created for a situation like this. I hope this helps for healthy open source maintenance 🙂

• Limiting interactions for your personal account - GitHub Docs -https://docs.github.com/en/communities/moderating-comments-and-conversations/limiting-interactions-for-your-personal-account

Going to merge this as is as it's reflecting the current state of the project 👍🏻 Thanks everyone