I've had this sat in my drafts for a while. Rather than let it sit on the shelf any longer I thought it better to share.
I've been thinking about recognising contributions recently. The main issue with the notes here is that it focuses on code rather than contributions to the wider Django ecosystem. However, if there are improvements that we could make here I think we should explore those, and maybe some of them could be used more widely.
Here are a few ideas of how contributions could be recognise following a peer review of other projects. Some are better than others, some are easier to implement than others. Hopefully something to prompt some discussion. What do folk think? How would you feel if you were recognised in one of these ways?
- Add Python style `contributed by` in the release notes. I'm not so sure about adding the ticket number (in fact I think I saw Nick Pope point to something today that says we don't ref tickets?). 
- For the headline features add names to the blog post . Could also add link to their blog / website /Twitter (less sure about this second part).
- The blog post (or another page) to include a long list of names of everyone who contributeted a commit in that release. I think it's fine if this is long, can probably use Simon W's GitHub-to-sqlite repo for this so it is sustainable. 
- For the headline features make a series of Twitter posts highlighting them and acknowledge contributors. I'm thinking something along the lines of what Adam Johnson did for the 3.2 release but include names & thank yous.
- A rust style thanks page  (but **not** the all time list, I don't think that's helpful and it's on GitHub anyway).
- A go style contributor summit. (I don't think this is feasible, even remotely. But I'll put it out there!). A slight variation on this could be folk who have contributed could apply for different coloured conference passes/lanyards. 
You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-develop...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/0174cb33-44e3-48f4-80dc-27b8f9fb8cb4n%40googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAFNZOJNob_gXZAVWHBoW2MF18%2B8sxEJQYMCuXZj8%2BBB_910U8w%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAMyDDM0Zh60Bz9qkr9mEMOcP67wxYxXQ7d7g0t0n%3DPPR6ay4YQ%40mail.gmail.com.