Updating our project guidelines to minimise churn. #9130
Replies: 2 comments 2 replies
-
|
I think it would be valuable to display this at the top of the README, in the contributors guide for the docs, and also in the issue templates. Consider what the maintainers of
|
Beta Was this translation helpful? Give feedback.
-
|
I would be up for reviewing a pull request effecting this change. |
Beta Was this translation helpful? Give feedback.
-
|
I would be happy to start a draft PR. any pointer where to put them? |
Beta Was this translation helpful? Give feedback.
-
|
I want to add few points explicitly with what Tom mentioned:
|
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
My perspective is that Django REST framework is feature complete and has been for a while now.
Despite this, there's still a lot of issue/pr churn which isn't providing any value.
I'm opening this discussion because I'd suggest figure out what changes we need to make in order to communicate the project status clearly.
I strongly feel that only changes that we should be seeing in REST framework at this point in the project lifecycle are:
What changes would we need to make to the project to communicate this as clearly as possible, and reduce the ongoing churn that the project is currently seeing?
Beta Was this translation helpful? Give feedback.
All reactions