Skip to content

Commit 180f3af

Browse files
committed
🔧 update URLs for new repo
1 parent 271a4e5 commit 180f3af

File tree

1 file changed

+13
-11
lines changed

1 file changed

+13
-11
lines changed

README.md

Lines changed: 13 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -1,29 +1,31 @@
11
# Django Features
22

3-
This is an example of a repository that contains the new feature ideas for
4-
the Django web framework. This repository is for display purposes only and
5-
should not be used.
3+
We are currently testing a way to propose new features to Django.
4+
5+
For browsing purposes you might like [the kanban view of this repo](https://github.com/orgs/django/projects/24/views/1) better.
6+
7+
The README on this repo is very much a work in progress and is likely to change according to the feedback we get as well as the teachings its usage will bring us.
68

79
## Have an idea for Django?
810

911
Please know, things in Django take a while. You will need to be patient.
1012

1113
Please start with reviewing the [new feature process in Django](#djangos-new-feature-process).
1214

13-
Next, go [create an issue in this repository](https://github.com/tim-schilling/new-features/issues/new).
15+
Next, go [create an issue in this repository](https://github.com/django/new-features/issues/new).
1416

1517
## Want to help steer Django?
1618

1719
There are three queues that need community involvement:
1820

19-
- [Is there community support?](https://github.com/tim-schilling/new-features/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22phase%20%2F%20is%20there%20community%20support%22)
21+
- [Is there community support?](https://github.com/django/new-features/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22phase%20%2F%20is%20there%20community%20support%22)
2022
- Review the open tickets in this queue. Please share support on this via emojis.
2123
- Please follow the [Emoji Reaction guide](#emoji-reaction-guide)
2224
- See [Is there community support?](#is-there-community-support) for more details
23-
- [Is a feature expected in Django core?](https://github.com/tim-schilling/new-features/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22phase%20%2F%20is%20this%20expected%20in%20core%22)
25+
- [Is a feature expected in Django core?](https://github.com/django/new-features/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22phase%20%2F%20is%20this%20expected%20in%20core%22)
2426
- Weigh-in on whether a feature should exist in Django core
2527
- See [Is this expected in Django?](#is-this-expected-in-django) for more details
26-
- [Needing volunteers to implement or implementation review](https://github.com/tim-schilling/new-features/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22phase%20%2F%20needs%20community%20DEP%22)
28+
- [Needing volunteers to implement or implementation review](https://github.com/django/new-features/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22phase%20%2F%20needs%20community%20DEP%22)
2729
- Help implement or design features
2830
- See [Can we do it?](#can-we-do-it) for more details
2931

@@ -208,7 +210,7 @@ every interval, but some ideas should constantly be moving forward.
208210

209211
### Triaging new ideas
210212

211-
- [Queue to review](https://github.com/tim-schilling/new-features/issues?q=is%3Aissue%20state%3Aopen%20(no%3Alabel%20OR%20label%3A%22phase%20%2F%20new%22))
213+
- [Queue to review](https://github.com/django/new-features/issues?q=is%3Aissue%20state%3Aopen%20(no%3Alabel%20OR%20label%3A%22phase%20%2F%20new%22))
212214
- Any relevant labels should be applied to the issue
213215
- If the issue is a duplicate of another, it should be closed and referred to the original
214216
- The concerns of triaging are:
@@ -218,7 +220,7 @@ every interval, but some ideas should constantly be moving forward.
218220

219221
### Determining consensus on community support
220222

221-
- [Queue to review](https://github.com/tim-schilling/new-features/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22phase%20%2F%20is%20there%20community%20support%22%20)
223+
- [Queue to review](https://github.com/django/new-features/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22phase%20%2F%20is%20there%20community%20support%22%20)
222224
- The issues should be reviewed to determine if the community has arrived at consensus
223225
- The question here is, “Does the community think this change is good for Django?”
224226
- People who expressed significant disagreement may be asked to explain their disagreement
@@ -234,7 +236,7 @@ every interval, but some ideas should constantly be moving forward.
234236

235237
### Determining is this expected in Django
236238

237-
- [Queue to review](https://github.com/tim-schilling/new-features/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22phase%20%2F%20is%20this%20expected%20in%20core%22)
239+
- [Queue to review](https://github.com/django/new-features/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22phase%20%2F%20is%20this%20expected%20in%20core%22)
238240
- The issue should be reviewed to determine if the idea is expected to be in Django
239241
- Features that should be merged into core Django are:
240242
- Proven to be integral to Django a significant number of applications
@@ -253,7 +255,7 @@ every interval, but some ideas should constantly be moving forward.
253255

254256
### Creating DEPs for expected features
255257

256-
- [Queue to review](https://github.com/tim-schilling/new-features/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22phase%20%2F%20needs%20SC%20DEP%22)
258+
- [Queue to review](https://github.com/django/new-features/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22phase%20%2F%20needs%20SC%20DEP%22)
257259
- The issue should have a DEP created at
258260
- It should contain the following sections:
259261
- Title

0 commit comments

Comments
 (0)