Where did the Github Discussions for Django Rest Framework go?

[Michiel Beijen]

Hi,

in several places in the documentation of Django Rest Framework there are links to the 'Discussions' topic on Github. Only if I follow the link, I get a HTTP 404.

https://github.com/encode/django-rest-framework/discussions

Was this turned off deliberately or is this a mistake?

--
Michiel

[Luis Saavedra]

Same with issues... why?

[Florian D]

Hi everybody!

I was reading through the changelog of the 3.15 series in preparation for an upgrade and came across this vague change note:

> Revert number of 3.15.0 issues which included unintended side-effects. See [#9331]

... with a broken github issue link!

this creates a rather big gap in the changelog... i have no way of finding out what previously added changed were reverted.

please reactivate issues to be able to follow changes better.

[Kanishk Pachauri]

Please reference this discussion, it state why they closed the  Discussions and issues for Django Rest Framework

https://github.com/encode/.github/discussions/11#discussioncomment-12311196

[Matthias Mair]

So, do I understand the subtext correctly in that there are no bug fixes or bug discussions anymore? Only updates for security issues?
Some of my OSS projects have heavy reliance on DRF and this seems like something that more or less forces us to move away with the next audit. There seem to be no / very limited official comms on these topics - which is also a worrying sign.

[Florian D]

Hi!

Thanks for pointing out that GitHub discussion!

I just wanted to write again to say how much I have appreciated all the work and effort put into Django Rest Framework over the years!

It is not only a useful library/framework in general, but its adaptable/extendable structure/style and beautiful documentation have been a guideline and motivator for me to write useful, beautiful, adaptable code myself for a long time. Maintaining code in the open is hard work, and the quality delivered in this project has always been outstanding!

Thank you very much to Tom Christie and everybody else who helped!

My two cents about comments regarding the lack of discussion or further development: I personally very much appreciate feature-complete software. There can and should be a point where something is done and useful for years to come. I actually prefer it over too much change and feature bloat just to appear active. Django Rest Framework is excellent as it is, in my opinion, and if there are only security patches and updated CI to cover newer Django/Python releases, I could not be happier.

A blog post or short announcement in the README about the intentions behind closing issues might have helped, but we have this thread here now. :)

I am not sure if it really works, but maybe we can get the issues back to read-only using this trick: https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository#configuring-the-template-chooser

...and if not, that's okay. Thank you!