Removed reference to GitHub Issues and Discussions

[mbeijen]

as they are no longer activated
ref: https://github.com/orgs/encode/discussions/11#discussioncomment-12311196

[ulgens]

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.

[iTrooz]

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

[auvipy]

I'm not sure why discussion is deactivated!

[tomchristie]

Thank you @mbeijen, much appreciated.

Given that they are not currently activated it seems(?) reasonable enough to get the docs updated.

This pull request will remain in the history, and we can revert if/when appropriate at a later date.

[tomchristie]

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 option might 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.

[hyperstown]

@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?

[sethrh]

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.

[tomchristie]

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.

[tomchristie]

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.

[aliraad79]

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

[mbeijen]

Hi, there is also a reference to #5181 in this 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 ;-(

[auvipy]

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