Skip to content

Add the new feature ideas tracker to the new ticket readme #262

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 4 commits into from
May 1, 2025
Merged

Add the new feature ideas tracker to the new ticket readme #262

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
ffc54fd
Add the new feature ideas tracker to the new ticket readme
LilyAcorn Apr 27, 2025
7b7422c
Update link to create a new feature idea
LilyAcorn Apr 28, 2025
a024b87
Clarify that "here" means on Trac
LilyAcorn Apr 28, 2025
51448bd
Remove stray .
LilyAcorn Apr 28, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions trac-env/templates/custom_ticket.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,9 +12,9 @@ <h2>Please read this first:</h2>
Report bugs and suggest documentation changes using this ticket tracker.
</li>
<li>
New feature proposals should first be discussed on the <a href="https://forum.djangoproject.com/c/internals/5">Django Forum</a>.
Once feedback has been gathered, you can use this ticket tracker to open a ticket for the new feature.
New feature proposals should be created on the <a href="https://github.com/django/new-features/issues/new/choose">new feature idea tracker</a>. The <a href="https://github.com/orgs/django/projects/24">project board view</a> can be used to view existing ideas and their progress.
Please include links to relevant discussions from the forum (or other sources).
If the feature is approved for Django core, a feature ticket may be created here on Trac.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

(nitpick 1) Is "Django core" a well-defined concept? On Trac, "core" is mostly used in the "component" field in opposition to "contrib". Personally I also associate the word with the "core team" which does not exist anymore.

(nitpick 2) What does "approved" mean here exactly? Approved by whom? Per the description of this PR the "new features" project board is experimental, but this proposed sentence makes it sound like it's now a required step in getting a new feature ticket open. Did I misunderstand something?

Copy link
Contributor Author

@LilyAcorn LilyAcorn Apr 28, 2025 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nitpick 1: I guess we could say github.com/django/django instead. I'm not sure if that's better. I'm also open to other suggestions.

Nitpick 2: Approved via the new feature tracker or a DEP is what I had in mind. In either case that's currently down to the Steering Council reflecting the community opinion on the proposal. I'm not really sure how much to emphasise or downplay the experimental nature of this process here. I think for the duration of the experiment we're basically treating the new process as the way to do this. If we realise after a while that it's also not working, we'll revisit.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nitpick 1: If it helps provide context, the new features process is encompassing feature ideas within the whole Django ecosystem. Not just repos that the DSF controls. This is why we're needing to define something about what is in django/django and what's not.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the additional context! I don't have an alternate proposal so I'm going to merge this as-is and we can circle back to it in the future or if we get feedback that this isn't clear.

No need holding back this (positive) change 👍🏻

</li>
<li>
Don't use the ticket system for
Expand Down
Loading