django-rest-framework: No issues and discussions

[q0w]

Where have all the discussions and issues gone?

[isik-kaplan]

Yeah, when searching for problems on google issues/discussions pops up indexed by google but the actual pages themselves are all 404, any reason nuking all previous content?

I remember reading something like DRF considered feature-complete (I disagree but that's not the point) and will only get bugfixes and django version updates but that shouldn't warrant deleting all past issues/discussions imo.

Maybe you can bring back the existing(if they still exists somewhere) issues and discussions but lock everything so nothing new can be created? (Even though I think bug reports still should be allowed).

I searched if the issue tracker or the repo itself is moved (like django-allauth switching services to host the repo) but couldn't find any information about that either.

[tomchristie]

Hi, yep... so issues and discussions are currently disabled. The issues are still there and we can re-enable them if needed.
REST framework will still be accepting security updates and essential versioning changes.

Maybe you can [...] lock everything so nothing new can be created?

We can only do that through policies and enforcing boundaries.

Currently I'm putting the volume dials to low to create less unnecessary churn.

[mbeijen]

Hi, yep... so issues and discussions are currently disabled. The issues are still there and we can re-enable them if needed. REST framework will still be accepting security updates and essential versioning changes.

The CONTRIBUTING guide for django-rest-framework states:

Apart from minor documentation changes, the GitHub discussions page should generally be your starting point. Please only raise an issue or pull request if you've been recommended to do so after discussion.

I opened a discussion on there to update the HTTP constants in DRF to use the codes defined in RFC9110. The discussion did not get any traction, but I still feel it is important for Django Rest Framework even if it is 'feature complete' to implement the 'modern' naming for these status codes. I actually already created a small commit for this last year: mbeijen/django-rest-framework@b413bc0 But now the discussion is gone. What would be the best way to get this in? Or should I just not bother?

(requests also has this - psf/requests#6680 and Python, since 3.13, and so on)

[ldeluigi]

It makes no sense to hide the tabs. There will be always new bugs and stuff to talk about there.

[tomchristie]

Something that is genuinely important is being able to respect clearly stated boundaries.

REST framework is stable and will accept significant security patches if required.

[mbeijen]

Hiding the existing discussions tab while still pointing to said tab in the documentation and other places is not a “clearly stated boundary”, it is just confusing to me

[tomchristie]

"Hi @tomchristie, thanks for your work on this project. I was surprised that you've choosen to currently disable the discussion board, but I assume that you've probably got good reasons for doing so. Perhaps I could help with a pull request updating the contribution guide to reflect the current stance."