-
Notifications
You must be signed in to change notification settings - Fork 54
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.
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
Add the new feature ideas tracker to the new ticket readme #262
Conversation
Add a sentence explaining the project board view. Co-authored-by: Tim Schilling <[email protected]>
Co-authored-by: Tim Schilling <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice change, thanks for taking the time 👍🏻
I've left two comments, but only the first one (the duplicated .
) is important. The second one is not a blocker and I'm happy to merge this PR without resolving it, I just thought I'd raise the issue.
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. |
There was a problem hiding this comment.
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?
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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 👍🏻
Co-authored-by: Baptiste Mispelon <[email protected]>
Updates the new ticket readme to point users to use the experimental new feature idea tracker introduced by the Steering Council.