Hi there,
I noticed that we use folders like draft/accepted/final for DEPS or other governance proposals in git.
Sadly, this leads to many links being broken, especially from the blog, Exhibit A: Django Enhancement Proposal 14: Background Workers | Weblog | Django
It’s also bad for search engine indexes. You “google” for a certain DEP, and you’ll eventually just go to GitHub, find the repo, and look for the file. It’s not really a beginner-friendly workflow.
Does anyone have ideas on how to improve this? I can’t be alone with this, can I?
I was thinking about soft links, but those are not spectacular on GitHub.
Anyhow, I thought I’d raise the issue.
Cheers,
Joe
2 Likes
I wonder if we could solve this issue along a similar lines to what the Board have done with their meeting minutes (and I would like to happen with the minutes from other WGs/Teams). Could we have a simple static site for DEPs which then provide a more canonical URL to reference?
I have added this thread to the OCWG idea about automating meeting minutes: Automate the communication of meeting minutes · Issue #34 · django/online-community-working-group · GitHub
and to one about DEPs as well. Increase visibility of DEP/WG/etc repo activity · Issue #24 · django/online-community-working-group · GitHub
I’m definitely plus one on some easy wins here
3 Likes
I had Claude build something this morning: https://tranquil-pavlova-402378.netlify.app
It could do with some tweaks, but I think probably good enough to start?
1 Like
Oh, that’s cool. It’d need to be part of the djangoproject.com website, though. We need an “official” permalink. But that shouldn’t be too challenging to contribute. If you care to contribute something similar with a little more human oversight to the official website, I’d be happy to review it.
I’m thinking the next steps would be to get this reviewed and merged as part of the DEP repo. While the prototype I shared is not related to the repo, it’s just a github action with github pages for hosting. It could then live at django.github.io/deps, in a similar manner to the current DSF minutes microsite.
Moving these back to the current website, to my mind at least, ought to take a wider view of which github repos in the Django organisation would want pages on the website. These would want to fit into the wider redesign that’s been proposed in terms of the information architecture of the site itself. I have created an issue to start this discussion.
True, I didn’t even think of that. I was mostly concerned with having too many apps and domains.
1 Like