Hey Tim.
> As an infrequent contributor these days, I'm not seeking any more
recognition
> from my contributions, nor would more recognition encourage me to
contribute
> more. I'd rather the Django team spend their efforts on building software
> than on publicity.
Recognising contributions, in
Just to expand on my question a little bit with a comment, I think it would
help to make the ticket corresponding to a release note easier to find
because it would give people an easier way to answer the question, "what is
the reasoning / background / discussion for this change?" Currently, ther
I started including ticket numbers in patch releases because there aren't
too many changes there and every change has a release note. I think the
ticket numbers are useful to quickly identify the cause of some change or
regression in a patch release where upgrades should generally be safer and
Related to this discussion, what's the current policy / practice around
linking to tickets from the release notes? It looks the release notes for
patch releases already link to tickets, e.g.
https://docs.djangoproject.com/en/dev/releases/3.2.6/
However, for feature release, it looks like the tic
Hey David.
Thanks for the follow-up here.
I think at least for 4.0 we should focus on adding callouts/recognition to the
release blog post, rather than the release notes.
For one, release notes only contain new features, and we want to call out all
the different contributions that don’t fal
Hi All,
Just coming back to this again (time flies), although we've got a while
until 4.0 is released so no rush here.
I've got a few different thoughts here:
*Data*
I had a look at the various tools discussed above to see if any give us
what we need. While on that journey I came accross git'
This is something I've been thinking about a bit as well.
Mostly I think adding authors to the release notes is probably the best
bang for buck in terms of recognition. This is what I was mostly thinking
about myself. The release notes are (I believe) very widely read,
especially in comparison wit
I'm all for exposing names in more places.
Linking through to PR's from the release notes would also be useful for
"pulling back the curtain" and making Django's code a bit less magical.
Plus it could help the workflow for current contributors.
On Mon, 5 Jul 2021 at 16:07, Tom Forbes wrote:
> P
Perhaps we could do this as part of a Sphinx plugin? Right now each entry
in the release notes is only implicitly tied to the pull request that adds
it.
If we could add some kind of pull request ID marker to the release note
entries we could create an inline link to the PR (which might be very
use
Hi David,
Thanks for this. Yes.
Let's assume the 2020-2021 time filter is in place.
Mariusz recently picked up James' PR to add the list of Core Contributors
(back) to the website, which is/was part of the DEP 10 governance changes.
https://github.com/django/djangoproject.com/pull/1099
The
10 matches
Mail list logo
