Website Team Meeting notes

Django Internals Website
1

24 Apr 2025

Attendees: Saptak, Storm, Jason, Sanyam, Alex, Sarah, Tobias and Paolo

Agenda

Action items

  • Saptak: Create a meeting poll for next month
  • Tobias: let us know about Security reporting process
  • Sarah: Onboarding the 2 new members
  • Saptak: Create a SECURITY.md and update README on how to report
  • Storm: to contribute a security.txt file
  • Jason: Triaging Process document
  • Triaging open PRs and currently open tickets
  • Everyone: Read through the UX analysis and other documents so we can discuss in next meeting
  • Tobias: Staging preview site
  • Request for access to Sentry/other analytics to ops@djangoproject.com
  • Research about aggregate traffic analytics

Notes:

  • Introductions!
    • Sarah: France, DSF, Django a11y team
    • Paulo: Italy, DSF, Also part of Python Italy
    • Saptak: Web Dev, India, Django a11y team
    • Storm: Based in netherlands, worked in Django for quite some time, Wagtail core team
    • Alex: based in Barcelona, Spain.
    • Jason: based in the USA, keeps calling himself ‘new to Django’ but has worked with it for the past three years
    • Sanyam: based out of Canada. Web developer since over a decade.
  • Agenda
    • What has been done before the working group
  • What are the responsibilities of the Website WG
    • Maintaining djangoproject.com
    • Triaging tickets
    • We do not handle the content of the website, there will likely be a new working group for that
    • The idea of the working group is to have a group of people responsible for these tasks
    • If there are tickets for new features, we can (help) develop those features
    • We can propose new features, create an issue for it
    • Example improvements
      • Images in blogs, markdown for posts
    • Right now, we are using GitHub issues
    • There is also a project of long-term goals for the website
      • Let’s discuss this in detail in another meeting
  • Things done before the WG

    • There are open PRs, some are almost ready to go

    • We hope to close some of these PRs during the DjangoCon Dublin sprint

    • Would be nice to define the process of triaging a ticket for the website

      • Using labels for tagging the issues
      • GitHub projects for triaging
      • Automatically close very old issues

    • If you have any opinions related to this, please reach out

    • UX study by 20tab: forum, PDF report, article by Thibaud

      • Study done by former employer of Paulo
      • Usability / accessibility issues uncovered
      • Survey with the community
      • Usability expert
      • Interview with user selected from Survey
      • Interview with someone from the DSF board
      • Sorted pain points in order
      • Example pain point: accessibility of dark theme
      • Helpful to read this, get everyone on the same page

    • New design for the website?

      • Previous design was made ~15 years ago, contributed by a company
      • Likely needs a sponsor for a new design

    • Design contribution discussions

      • Helpful to read this as well
      • Includes things like information architecture, inconsistent use of gray colors
  • Style guideline
    • Past contributions did not always follow this guideline, resulting in inconsistency
    • Turns out this style guideline document is hard to find
  • Probable next steps
    • Read through the documents
    • Look for a designer?
  • Tobias joins us from DjangoCon
    • Based in the USA, works at Caktus
  • Need of security reporting
    • There currently is no way of reporting security issues
    • Need to set up an email to receive reports
    • You should all have been invited to the GitHub website working group team, you should all have been invited to this team.
      • If not, please reach out to Sarah
  • Two new potential members we have to vote on
    • (adding members requires a vote from the team)
    • Ülgen Sarıkavak self nomination
      • Already a DSF member
      • Vote: accepted as member
      • Tobias abstained from voting
    • Adam Zapletal self nomination
      • Has contributions and was on the previous maintainer team:
      • Vote: accepted as member
      • Tobias abstained from voting
    • “Direct membership: new members may self-nominate; the WG will vote (50%+1) to approve/deny new members. The WG will vote for New Chair/Co-Chairs and decision to appoint will be based on gaining majority votes.”
  • Action items for next meeting
    • When to have the next meeting?
    • Timezones are a bit of an issue
    • Action: Saptak to organize a new poll for the next meeting
    • Meeting cadence: once a month
    • Discuss asynchronous on Slack
    • Action: Tobias security reporting process
    • Action for all: read the UX analysis of the website and other documents from this meeting (design contribution discussion, style guideline)
    • Triaging process document
  • Website OPS team (Tobias)
    • Deploying new versions of the website
    • Upgrading database
    • Anything related to the infrastructure
    • Do we have a staging environment?
    • We had a staging environment, but no one appeared to use it. Can bring it back.
    • Economic cost of having a staging environment?
    • We get sponsorships from AWS, we send an email once a year to receive credit
    • Need to set up CI/CD for automatic deployments
    • Any other questions around the infrastructure and deploying?
    • Do we have tracking on the website? Not sure
      • Thibaud mentioned Google Search Console
    • Do we need anyone else on the Sentry team?
    • Reach to ops@djangoproject.com for access to analytics / Sentry
  • Anyone okay with volunteering to start the triaging process document?
    • Jason volunteers
  • Use plausible for analytics?
    • Privacy friendly
    • Doesn’t require a GDPR consent banner
    • Self hosting? Generally we don’t do this and use sponsored accounts instead
    • Fastly sponsors us with free CDN services
  • Action: add a SECURITY.md file to the website
2 Likes
2

5 Jun 2025

Attendees: Sarah A, Ülgen, Mark, Storm, Alex, Saptak, Adam

Agenda

  • Review Action Items
  • UX analysis
  • Policy on PR approval and merge
    • Permissions of the team
  • Birthday of Django
  • Monthly meeting schedule

Review action items

  • Saptak: Create a meeting poll for next month
  • Tobias: let us know about Security reporting process
  • Sarah: Onboarding the 2 new members
  • Saptak: Create a SECURITY.md and update README on how to report
  • Storm to contribute a security.txt file
  • Jason: Triaging Process document
  • Triaging open PRs and currently open tickets
  • Everyone: Read through the UX analysis and other documents so we can discuss in next meeting
  • Tobias: Staging preview site
  • Request for access to Sentry/other analytics to OPS team
  • Research about aggregate traffic analytics

Action items

  • Storm: Update the security.txt PR
  • Everyone: Review security.md and security.txt PR
  • Jason: Triaging Process document
  • Saptak: Look at PRs to fix docker instructions
  • Adam: Triaging open PRs and currently open tickets
  • Sarah: Request for access to Sentry/other analytics to OPS team
  • Alex: Research about aggregate traffic analytics
  • Sarah, Alex: Look into how to improve Django fundraising UI/UX to make it more visible and appealing
  • Saptak: Create an issue and track about Django birthday banner
  • Saptak: Fix a time for monthly calls

Notes

  • Review Action Items

    • Saptak created the poll, that’s why we here
    • Sarah onboarded the new members
    • Saptak created a SECURITY.md PR
    • Storm created the security.txt PR, needs some rework to align with Saptak’s PR
    • Jason: triaging process document
      • Jason isn’t here, will ask on Slack and move to next meeting
    • Triaging open PRs – Adam
      • Created a document with open PRs
      • Many PRs are in an actionable state, closed a few that were not active
      • Adam happy to do some triage and (gently) ping people to review
      • Currently the djangoproject.com repo has a lot of open issues and PRs, which is generally not an amazing sign of good health
      • Saptak suggests using GitHub project boards more, let’s move the document to the board
      • We currently have a project board already but not in a useful state right now
      • Alex: Instructions for local setup are currently not correct, there is a PR that corrects the instructions. Can we prioritize this please.
    • Everyone read UX analysis
      • Website probably needs a lot of upgrades in the UX space (things like search)
      • How do we want to approach the UX improvements?
    • Tobias to setup staging preview site
      • done
    • Request for access to Sentry/other analytics to ops@djangoproject.com
      • Still ongoing
    • Research about aggregate traffic analytics
      • Storm got some screenshots for Django analytics from Thibaud
      • Are these analytics good enough? Do we want more analytics?
      • We need to determine what we are interested in gathering data about
      • Is anyone interested in taking this as an action to investigate further (what are we interested / what information do we have right now)

  • UX analysis

    • One pressing request from the fundraising working group about improving the fundraising page.
    • Pages are flatpages, meaning they have to be edited through the Django admin
    • What changes does the fundraising team want to make? A: expect issues on the repository soon
      • Make the fundraising page more visible by linking to it from elsewhere
    • From the study PDF: “perception of a lack of emphasis on the support and donations page”
    • Someone to take a look at Support Django and suggest improvements
      • Volunteers? Sarah/Alex
    • Flatpages like /foundation can only be edited through the admin. Can we give members of the working group access to the admin?
      • Work in progress, discussing with the Ops team
    • Feel free to suggest UX improvements for the site, please create an issue
    • For things that need a design, we need a design volunteer

  • Policy on PR approval and merge

    • Permissions of the team
    • Came up on Slack, some confusion on when something is good to merge
    • Right now, everybody on the working group has access and can merge PRs; it is not supposed to work that way. We want a dedicated mergers team but we need to set up that team on GitHub first.
      • This is described in the website working group proposal document
    • Baptiste has been merging a lot of PRs, will his role change?
      • Since the working group now exists and has members that can merge, he might be less active than before

  • Birthday of Django

    • The official birthday is in July (believe it is the 14th)
    • There has been discussion about placing a banner on the site or create a special birthday site
    • No design yet for a banner, but this all would need to happen before the birthday
    • There is already someone external to the working group working on the birthday site, check out the #birthday channel on the DSF slack if you are interested

  • Monthly meeting schedule

    • We are a large group, scheduling is hard
    • Will try to pick a date, like every last Thursday of the month
    • Does this day and time work for most of the people here in the call?
      • Looks like it
    • Anything for the structure of the meeting? Does this pattern of reviewing actions, and agenda work

  • Any other business? Some questions from Ülgen

    • How do we manage GitHub team memberships?

    • How do we manage rules (such as branch protection) for repos?

      • As mentioned earlier, the merge access will be restricted to a select group
      • Believe we have recently set up branch protections

    • Do we have the deployment process documented?

      • The OPs team manage deployment through an ansible playbook

    • Why do we have a blog on the website that looks like part of the documentation? Who can write on “weblog”? They look like “official” content.

      • The content of the weblog is not in the scope of the website working group
      • Not sure who has permission to write on the weblog
      • Ülgen asked the question because it looks like part of the official documentation
      • Weblog in question: News & Events | Django
      • It is all official content, but aside from release announcements it is now also used to publish more content, like information about Djangonaut Space. It is all official and sanctioned/endorsed by the board.
1 Like
4

3 Jul 2025

Attendees: Adam, Alex, Mark, Saptak, Sarah

Agenda

  • Review Action Items
  • Inactive members

Review action items

  • Storm: Update the security.txt PR
  • Everyone: Review security.md and security.txt PR
  • Jason: Triaging Process document
  • Saptak: Look at PRs to fix docker instructions
  • Adam: Triaging open PRs and currently open tickets
  • Sarah: Request for access to Sentry/other analytics to ops@djangoproject.com
  • Alex: Research about aggregate traffic analytics
  • Sarah, Alex: Look into how to improve Django fundraising UI/UX to make it more visible and appealing
  • Saptak: Create an issue and track about Django birthday banner
  • Saptak: Fix a time for monthly calls

Action items

  • Storm: Update the security.txt PR
  • Everyone: Review security.md and security.txt PR
  • Saptak: Triaging & reviewing process document
  • Alex & Ulgen: send the docker PRs already open and Ulgen can push a new PR that solves some of the old PR problems
  • Sarah: check access for the website with the ops team
  • Sarah: see details with the in-kind donor Fastly
  • Alex: Check with Stephanie regarding Django fundraising UI/UX
  • Saptak: Talk with Thibaud about the design of banner for Django birthday
  • Sarah: create a vote about removal of Eric
  • Sarah: Define what actually means inactive
  • Saptak, Alex & Ulgen: review the docker setup for the website
  • Saptak: Look into improving the contribution guidelines

Notes

  • Review Action Items

    • Triaging and reviewing process document: Saptak will create the document and everyone can review and improve it
    • Alex can send over old PRs on docker improvement to Saptak
      • Ulgen: The old docker PRs might be problematic, but has a working setup that he can create a PR
      • Saptak: Review the PRs for docker fix
    • Adam: trying to stay up with all the open PRs. Would like to discuss few PRs at the end of the PR
    • Sarah has sent an email for the analytics and is waiting for a response.
    • Sarah will check with ops related to access on admin
    • Alex: We don’t have the functionality, but we may have to update plan. We do have accesslogs of the server, but might be tricky to aggregate.
      • Sarah will check with Fastly about our plans
      • Alex will try to create an accesslog scrape and try to get an aggregated data
    • Django fundraising UI/UX
      • Alex talked with Stephanie, has a shared slack channel, and needs to ask what is the status and what needs to be done.

  • Inactive members

    • Few members are inactives, need to see if they are still happy to be part of the team
    • Sarah to improve the text to describe inactive members
      • We think only the working group needs to review.

  • Some PR discussion

    • There are 3 PRs which are trying to add link to the outdated banner.
      • Ulgen opened the first PR and the issue is assigned to them, but others are trying to open PR because of the good-first-issue label. THis is there with other PRs as well.
      • Alex: If it is assigned to someone, others can be closed maybe?
    • Don’t know about the power and responsibility?
      • Adam: Feels like we don’t have a lot of authority. Baptiste and Paolo were usually the one who made the final call. Should we be making the final call? Don’t know how to move forward with PRs, what to close and resolve the PR?
      • Mark: Have lost the ability to merge.
        • In the WG doc, its only the chair and co-chair but it might change after 6 months depending on activeness of some members
      • Ulgen: the project is not easily installable to actually test them locally? Docker thing is blocking so primarily focused on that. Would make it easier to contribute
      • Adam: don’t use docker personally but there is a lot of value on fixing up the docker setup and help onboarding
      • Alex: has docker setup working on my end, wants it to be good enough to push it
    • Contribution guidelines
      • Ulgen: there are some guidelines in the Django repository. Can we say somewhere, that Website is also following those guidelines.
      • Maybe if the good first issue is not urgent and unassigned, leave it for new contributors

  • Adam can share some PRs that we can look into every week beginning.

  • Adam has been maintaining a project board with ready to merge category.

  • Adam and Jason will be in DjangoCon US. Adam will try to do a lightning talk

5

7 Aug 2025

Attendees: Saptak, Sanyam, Ülgen, Sarah, Baptiste, Adam, Storm, Alex, Jason

Apologies: Paolo, Tobias

Agenda

Review action items

  • Storm: Update the security.txt PR

  • Everyone: Review security.md and security.txt PR

  • Jason: Triaging & reviewing process document Website Triage (draft)

  • Alex & Ulgen: send the docker PRs already open and Ulgen can push a new PR that solves some of the old PR problems

  • Sarah: check access for the website with the ops team

  • Sarah: see details with the in-kind donor Fastly

  • Alex: Check with Stephanie regarding Django fundraising UI/UX~~

  • Saptak: Talk with Thibaud about the design of banner for Django birthday~~

    • Thibaud said nothing as such was planned, hence no action was needed.

  • Sarah: create a vote about removal of Eric

  • Sarah: Define what actually means inactive

  • Saptak, Alex & Ulgen: review the docker setup for the website

  • Saptak: Look into improving the contribution guidelines

Action items

  • Storm: Update the security.txt PR

  • Everyone: Review and comment Website Triage (draft)

  • Sarah: check access for the website with the ops team

  • Baptiste: see about access to matrix with Fastly (for website stats) and can we ask for more access

  • Sarah: Define what actually means inactive

  • Saptak, Alex, Sanyam & Ulgen: review the docker setup for the website

  • Saptak: Look into improving the contribution guidelines

Questions

  • Do we have the deployment process documented?

    • If so, can we move it under the repo?

  • What do we think about the Djangonaut Space program?

Notes

  • New member: Baptiste Mispelon

    • You should have received access, if not talk to Saptak or Sarah

    • Intro: Baptiste is on the Django ops team, has maintained the website for a while before the Website WG was established

  • Review Action Items

    • Storm: Update the security.txt PR

      • Haven’t gotten around to it, sorry. Will do it soon after our meeting

    • Everyone to Review security.txt and security.md PR, the security.md PR has received feedback

    • Jason: triaging & reviewing process document

    • Alex & Ulgen: send the docker PRs already open

      • Saptak to take an action to review new PR

    • Sarah: check access for the website with the ops team

      • Can’t give our mailing list access, which would be the easiest way to include everyone on the team. Need to give out individual email addresses to the ops team

    • Sarah: see details with the in-kind donor Fastly

      • Access needs to be granted per account, not 100% sure how permissions work but it appears you get a lot of (unnecessary) access. We need to be careful with this.

      • Metrics are a separate product, not currently enabled for our account

      • During Django office hours, enabling analytics (google analytics / plausible) was discussed. Might be easier if the Fastly route turns out to be too hard.

      • Someone said they (Thibaud?) were going to check with Fastly and see if metrics can be enabled

    • Alex: Check with Stephanie regarding Django fundraising UI/UX

      • Currently, the only concrete thing the website working group can do is related to moving the diamond and platinum sponsors, see message from Catherine in #fundraising-and-website-wg in Slack

    • Saptak: Talk with Thibaud about the design of banner for Django birthday

      • Thibaud said nothing as such was planned, hence no action was needed.

    • Sarah: create a vote about removal of Eric

      • Done that on Slack, all in favor

    • Sarah: Define what actually means inactive

      • Haven’t done this yet

    • Saptak, Alex & Ulgen: review the docker setup for the website

      • Currently on Alex’s backlog of pull requests to review

      • Sanyam happy to help review

    • Saptak: Look into improving the contribution guidelines

      • Haven’t done this yet, added a new action item for next time

  • Fundraising Slack threads with Catherine Holmes (Adam)

    • Adam opened a PR for the social media links in the footer, PR #2152 is currently in a reviewable state

    • Should we open issues for the things she asked for and assign them?

    • Saptak: I would prefer we create issues

    • Can Catherine create the issues herself or does she not have GitHub access? Sarah will check

  • Issue clean up meetings? (Adam)

    • Could be productive if a small group of working group members could meet and discuss some of the old issues and find the way forward (close / clear doubts / give direction)

    • Anyone interested in helping out with this?

    • It is hard to make a dent if there are a lot of open issues, some are quite old and still valid. We can’t just close everything that is old.

    • Historical context: there used to be a stale issue closing bot, but it was removed as it was considered too aggressive

    • Maybe better if we go through the oldest issues and decided what to do with them every couple of months

  • Added flatpages-extra #2144 - Improvements to flatpages. (Baptiste)

    • Most of the code is in a separate package :wink:

    • Changing flatpages as a content editor is hard, this attempts to make the process smoother

    • Originally wanted to develop the improvements just for djangoproject.com, but might as well be a package

    • Haven’t received feedback from Catherine on this yet

    • Other related issue: history/changelog for a page isn’t great. Baptiste’s package improves this by allowing you to write a ‘git commit’-like message for your change.

    • Do we need to review the package code?

    • Currently in a GitHub repository, not as a PR. Not sure how easy it would be to review a repository

    • Can we preview changes like this one?

    • That’s the next agenda item, currently there is no way to do this.

  • Preview branch proposal (baptiste)

    • Essentially, there is a branch called ‘preview’ on the repository

    • The tooling would be changed to deploy the preview branch

    • Will this be automated? No, the current deployment script requires docker images that are only created for tags

    • Can we automate this?

    • The proposal tries to minimize changes to the deployment script, making it easier to implement, improve it later

    • For clarity: how would this work? If we merge the improvements to flatpages PR for example?

      • Merge to preview branch

      • Deploy preview branch, manual command that needs to be run

    • Who is going to be doing the deployments?

      • Ping Baptiste, or the operations team

    • Not ideal, very manual process, but this is the easiest way to begin making changes and utilize the preview server

  • Deployment process on staging

    • Same as above, staging/preview are the same thing

  • Any other questions / discussions?

    • Do we have the deployment process documented?

      • Baptiste: currently not documented, though the deployment script (ansible playbook) is in a private GitHub repository. Hard to give out access as it contains many secrets. It also exposes the way infrastructure isset up which the operations team would like to keep private.

      • Baptiste happy to jot down how the deployment process works from a high level

      • We should document that someone from ops needs to be pinged to deploy changes

      • Ülgen tried to improve/refactor the dockerfile, makes it hard to make changes if it is unknown how the docker image is used by the infrastructure

    • What do we think about the Djangonaut Space program? – Ülgen

      • Tim Schilling asked if we wanted contributions (to the djangoproject.com website)

      • We’d need a clearer backlog of issues and documentation around making contributions

      • Is this something we want to get involved with?

      • We could identify ‘easy / low hanging fruit’ issues and reserve them from the program. One of us (mentors) would check with the mentee what they are interested in and what they need to work on it.

    • Adam started a Javascript refactor for the site, together with Baptiste

      • Going well, but I need reviews.

      • There is a PR open Moved and simplified fundraising-heart.js #2143, small one to review

      • Striving to remove jquery usage next month

      • In short: more PRs coming soon

      • Some of them need to be deployed and checked on the staging site to make sure nothing breaks

6

4 Sept 2025

Attendees: Jason, Storm, Sarah, Alex, Baptiste, Adam, Tobias

Apologies: Saptak, Ülgen, Mark

Agenda

  • Review Action Items
  • Fundraising WG support request
  • Review PR Next Step

Action items

  • Everyone: review the security document PR
  • Everyone: Review and comment Website Triage (draft)
  • Sarah: check access for the website with the ops team
  • Baptiste: see about access to matrix with Fastly (for website stats) and can we ask for more access
  • Sarah: Define what actually means inactive
  • Saptak, Alex, Sanyam & Ulgen: review the docker setup for the website
  • Saptak: Look into improving the contribution guidelines
  • Sarah: review PRs to merge
  • Sarah: contact Fundraising WG for the Baptiste’s improvements for flatpages when it’s deployed
  • Tobias: update translations and instructions (#2174)

Review action items

  • Storm: Update the security.txt PR (done)
  • Everyone: review the security document PR
  • Everyone: Review and comment Website Triage (draft)
  • Sarah: check access for the website with the ops team
  • Baptiste: see about access to matrix with Fastly (for website stats) and can we ask for more access
  • Sarah: Define what actually means inactive
  • Saptak, Alex, Sanyam & Ulgen: review the docker setup for the website
  • Saptak: Look into improving the contribution guidelines

Questions

  • (add questions here)

Notes

  • ÂĄHappy birthday Alex! :confetti_ball:

  • Review action items

    • Storm: Update the security.txt PR (done)
    • Everyone: Review and comment Website Triage (draft)
      • Let’s review this next meeting together. We expect everyone to have read it by next meeting
    • Sarah: check access for the website with the ops team
      • Not fully done
      • Only Saptak and Sarah have access to Google Search Console
      • We can only provide access to individual accounts
      • If you have a need for access to the Search Console, please ask!
      • For the admin site, only Saptak and Sarah have access. Same applies, if you need access please ask
    • Baptiste: see about access to matrix with Fastly (for website stats) and can we ask for more access
      • Haven’t contacted Fastly yet
    • Sarah: Define what actually means inactive
      • Started a draft, but not finished yet
      • Intend to finish and share at the end of meet
      • Question: has Eric been removed? A: yes, but only charter needs to be updated
    • Saptak, Alex, Sanyam & Ulgen: review the docker setup for the website
      • Ulgen mentioned this on Slack, anyone aware of current status?
      • Waiting for push of working setup
      • There is also a PR for debian docker image update
      • Baptiste pushed above PR to preview server, but there are some issues with setting up Tract
        • Fun story: accidentally ran import query on production instead of preview server. All is good now
      • There are some quirks to figure out when updating the Ubuntu server that runs the production website
    • Saptak: Look into improving the contribution guidelines
      • Saptak is not here, skipping

  • Fundraising working group – Sarah

    • Pushing for page in editable HTML, because editing through the admin is hard
    • Baptiste has a PR in the works to make the flatpages easier to edit
    • Sarah will check with fundraising team to see if Baptiste’s PR works for them
    • Requires the PR to be deployed to preview server, seems doable to do this by the end of the week
    • If the updated flatpages doesn’t work out, we can swap this for editable HTML

  • Any other business?

7

As chair of the Website Working Group, I would like to acknowledge that the minutes of our meetings have not been updated for several months.
I appreciate everyone’s patience and am committed to getting things back on track.
Thank you all for your continued contributions and to those who take the time to read them.

8

2 Oct 2025

Attendees: Jason, Sanyam, Baptise, Adam, Tobias, Storm, Ülgen, Saptak, Alex
Apologies: Sarah

Agenda

Action from last meeting

  • Everyone: review the security document PR
    - And its sibling: Update security.txt PR
  • Everyone: Review and comment Website Triage (draft)
  • Sarah: check access for the website with the ops team
  • Baptiste: see about access to matrix with Fastly (for website stats) and can we ask for more access
  • Sarah: Define what actually means inactive
  • Saptak, Alex, Sanyam & Ulgen: review the docker setup for the website
    - https://github.com/django/djangoproject.com/pull/2207
  • Saptak: Look into improving the contribution guidelines
  • Sarah: review PRs to merge
  • Sarah: contact Fundraising WG for the Baptiste’s improvements for flatpages when it’s deployed
    - Baptiste: did you manage to deploy it?

Actions for next meeting

  • Everyone: review the security document PR
    - And its sibling: Update security.txt PR
  • Saptak: Address comments in the Triage document and finalize it. Check with Sarah where it lives.
  • Sarah: check access for the website with the ops team
  • Baptiste: see about access to matrix with Fastly (for website stats) and can we ask for more access
  • Sarah: Define what actually means inactive
  • Saptak, Alex, Sanyam & Ulgen: review the docker setup for the website
    - We still have one PR from Tobias, Saptak will review it
  • Saptak: Look into improving the contribution guidelines
  • Saptak, Sarah: Baptiste’s improvements for flatpages when it’s deployed https://github.com/django/djangoproject.com/pull/2144
  • Look more into site-breaking monitoring and bug reporting, Maybe cleanup sentry?
  • Baptiste: Bring up adding more Web people to Sentry
  • Saptak: Decision making docs
  • Everyone: https://github.com/django/dsf-working-groups/pull/55

Questions

Notes

  • Review Action Items
    • Everyone: review the security document PR and its sibling: Update security.txt PR
      • Storm approved, one comment about the github-only reporting process requiring a GitHub account. Acceptable?
    • Everyone: Review and comment Website Triage (draft)
      • Review as next agenda item
    • Sarah: check access for the website with the ops team
      • Unsure if this has happened
    • Baptiste: see about access to matrix with Fastly (for website stats) and can we ask for more access
      • No updates
    • Sarah: Define what actually means inactive
      • No updates
    • Saptak, Alex, Sanyam & Ulgen: review the docker setup for the website
      • Did see some activity
      • Some small issues left
      • Tobias has related PRs with open questions
        • Where the migrate command should run
        • Questions to run tests
      • Move to pyproject.toml
      • Things seem to be moving along
    • Saptak: Look into improving the contribution guidelines
      • Have not done that, moving this to next time
    • Sarah: review PRs to merge
      • Done
    • Sarah: contact Fundraising WG for the Baptiste’s improvements for flatpages when it’s deployed
      • Was this deployed?
      • https://github.com/django/djangoproject.com/pull/2144
      • Two comments
      • One about using a different package
      • Not sure about consensus
      • Baptiste keen to deploy to preview server to give people opportunity to test, but prefer not to if this is not the way we want to proceed
      • PR itself is not that big, because all the code is in an external package
  • Review triage documentation together
    • Lots of comments!
    • Where is this document going to live? In Google Docs or a GitHub Wiki?
      • GitHub wiki option is getting many +1 from team members present
      • Finalizing this document should still happen in docs
      • GitHub wiki does not appear to support pull requests, might make reviewing changes harder
    • Response time section, lets not do this
      • Seems like an unreasonable expectation
      • Get rid of this
    • Who is going to address the comments?
    • Issue templates
      • Things like: Feature request, bug report etc
      • Lets suggest some issue types and discuss this with the working group
    • Site breaking bugs / critical issues
      • How do we define this?
      • Do we have things like Sentry set up to keep track of server errors? Do we have monitoring?
        • We do have Sentry set up, bit reluctant to give out access because it might contain sensitive data
        • We can give access but it is quite messy with lot of messages (from documentation building, especially for the translation component)
          • Potential solution: configure Sentry to ignore these errors
          • Or try building the docs locally and figure them out
        • Have to do some housekeeping
        • Historically, we haven’t used Sentry for pro-actively fixing issues, we wait until someone reports it
        • We should be using Sentry more
        • Action for Baptiste: bring up adding more people to Sentry at next operations team meeting
      • https://django-dsf.slack.com/archives/C06U18AB7EY we have a slack channel where a bot posts when the site goes down, based on Grafana monitoring
        • People interested can join this Slack channel
        • The bot is quite accurate, it rarely gives false information about uptime
      • We also have https://status.djangoproject.com/ - looks like this is hosted externally
    • Document mentions issue triage meeting
      • What would this look like in practice?
      • Video meeting or asynchronously over Slack?
      • Idea: triaging duty that rotates
    • Policy for closing abandoned PRs
      • Closing a PR with a message after some amount of time without a response from the author
    • Next steps: apply improvements to document and resolve comments, get back to this next time
  • Website Redesign thread on forum
    • Django Homepage Redesign
    • djangoproject.com - User Research Report - v1.0.pdf
    • The forum thread is about the homepage and is quite long and holds opinions
    • Will the website get redesigned?
      • Yes, this is what the website working group
      • There are some steps before we can start writing code
      • Figure out how to collaborate with the Adam that started the forum thread
      • We do plan to be more transparent about the website redesign and the things that are happening behind the scenes, this is with Thibaud and [didn’t catch the name]
    • Questions
      • Will we be relying on volunteer resources or will we be using professional services?
        • Under discussion with the board, no clear answer
      • If we change the foundation of the site, many issues and PRs will get stale or obsolete
        • Aggressively triage and close open issues/PRs before the redesign starts.
        • We also still maintain the current website until the new website launches
      • Are we going to apply (parts of) the redesign Adam made into the current website?
        • Not drastic design changes that conflict with the current design
        • But updated content and some new blocks might be accepted
  • How to make decisions and resolve conflicts?
    • Consensus vs majority voting
    • Like the simplicity of majority voting
    • On the other hand, experience has learned that we are quite hesitant to make changes to things that are already in place. If we go with majority voting we will likely be making more conservative decisions.
      • [formulated and added later to support the above point: While we do not have an official authority hierarchy, majority voting may - at times - result in others following the opinion of someone they perceive as authoritative. Resulting in the ‘argument from authority’ fallacy, instead of compromising and making a decision everyone can be happy with]
    • Census voting is likely be a slower decision making process
    • Voting quorum? When is a decision valid? (because enough people have given their vote)
    • Saptak to write a document to describe our decision making process
  • Decisions regarding test coverage
  • We are at time
  • Last question, new member?
    • Discuss on Slack and maybe at next meeting
  • Thanks all!
9

This line is completely useless but I need to have it in order to post the meeting minutes because otherwise Discourse consider my body too similar to the previous one


6 Nov 2025

Attendees: Sarah, Saptak, Sanyam, Ülgen
Apologies: Baptiste, Storm, Alex, Mark, Adam

Agenda

Action from last meeting

  • Everyone: review the security document PR (Has been merged)
    - And its sibling: Update security.txt PR
  • Saptak: Address comments in the Triage document and finalize it. Check with Sarah where it lives.
  • Sarah: check access for the website with the ops team
  • Baptiste: see about access to matrix with Fastly (for website stats) and can we ask for more access
  • Sarah: Define what actually means inactive
    - Activity on Website WG
  • Saptak, Alex, Sanyam & Ulgen: review the docker setup for the website
    - We still have one PR from Tobias, Saptak will review it
  • Saptak: Look into improving the contribution guidelines
  • Saptak, Sarah: Baptiste’s improvements for flatpages when it’s deployed https://github.com/django/djangoproject.com/pull/2144
  • Look more into site-breaking monitoring and bug reporting, Maybe cleanup sentry?
    - We have a #djangoproject-uptime channel in slack
  • Baptiste: Bring up adding more Web people to Sentry
  • Saptak: Decision making docs
  • Everyone: https://github.com/django/dsf-working-groups/pull/55

Actions for next meeting

  • Saptak, Sarah: Review triage document comments
  • Baptiste: see about access to matrix with Fastly (for website stats) and can we ask for more access
  • Everyone: Review Activity on Website WG
  • Review cleanup PRs related to the Docker setup
  • Saptak: Look into improving the contribution guidelines
  • Ask Stephanie if she has been able to test the flat page improvements
  • Baptiste, Tobias: explain how we can use the Slack channel for Sentry monitoring
  • Saptak, Sarah: Decision making docs

Questions

Notes

  • Review action items
    • Everyone: review the security document PR
    • Saptak: Address comments in the Triage document and finalize it. Check with Sarah where it lives.
      • Still working on it
      • Saptak will discuss with Sarah to finalize stuff
      • Might simplify some of the points instead of being very explicit
    • Sarah: check access for the website with the ops team
      • Has a draft but has not sent the email yet. Almost done
    • Baptiste: see about access to matrix with Fastly (for website stats) and can we ask for more access
      • Not available in the call for update
    • Sarah: Define what actually means inactive
    • Saptak, Alex, Sanyam & Ulgen: review the docker setup for the website
      • We still have one PR from Tobias,
        • This has been merged
      • Saptak has still not done this
      • Ulgen has confirmed that it does work and there are some cleanups for which there can be further PRs and issues.
    • Saptak: Look into improving the contribution guidelines
      • Haven’t done it yet
    • Saptak, Sarah: Baptiste’s improvements for flatpages when it’s deployed
      https://github.com/django/djangoproject.com/pull/2144
      • Deployed to the preview server
      • Waiting on Stephanie for feedback from fundraising WG
      • Sarah will ping Stephanie to take a look at the preview server
    • Look more into site-breaking monitoring and bug reporting, Maybe cleanup sentry?
      • We have a #djangoproject-uptime channel in slack
      • The channel does show some updates. It shows 1 error in a month. It’s still not very clear if the integration is working fine and how to read and process the errors shown in the channel
      • Maybe someone from Ops team can explain the integration and how to process the errors that are shown in the slack channel
    • Baptiste: Bring up adding more Web people to Sentry
    • Saptak: Decision making docs
      • Haven’t done it yet but Saptak, Sarah will collab and come up with some decision making and conflict resolution docs
    • Everyone: https://github.com/django/dsf-working-groups/pull/55
      • Sarah asked them to provide a bit more info so that it can be used by folks to vote.
  • PR review:
  • What is our policy with GitHub integrations?
    • Fellows have mentioned that we will not enable any kind of integrations for new things
    • Currently Sentry and a few other things are there but there is no policy about adding new things.
10

4 Dec 2025

Attendees: Saptak, Jason, Alex, Ülgen,
Apologies:

Agenda

Action from last meeting

  • Saptak, Sarah: Review triage document comments
  • Baptiste: see about access to matrix with Fastly (for website stats) and can we ask for more access
  • Everyone: Review Activity on Website WG
  • Saptak: Look into improving the contribution guidelines
  • Sarah: Ask Stephanie if she has been able to test the flat page improvements
  • Baptiste, Tobias: explain how we can use the Slack channel for Sentry monitoring
  • Saptak, Sarah: Decision making docs

Actions for next meeting

  • Saptak, Sarah: Review triage document comments
  • Baptiste: see about access to matrix with Fastly (for website stats) and can we ask for more access
  • Everyone: Review Activity on Website WG
  • Saptak: Look into improving the contribution guidelines
  • Sarah: Ask Stephanie if she has been able to test the flat page improvements
  • Saptak, Sarah: Decision making docs
  • Baptiste, Tobias: explain how we can use the Slack channel for Sentry monitoring
  • Ülgen, Alex: Review https://github.com/django/djangoproject.com/pull/2305
    • (Removed the previous comment here, it was made for the wrong PR - Ülgen)
  • Jason: Rebase and review https://github.com/django/djangoproject.com/pull/2221
  • Saptak: Move next meeting to Jan 8th
  • Saptak, Sarah: Discuss with Ops about a more concrete deployment plan/ communication.

Questions

  • The next meeting is scheduled for January 1st, which I think is a holiday everywhere?
    - We will just move it to the next week

Notes

  • Baptiste, Tobias: explain how we can use the Slack channel for Sentry monitoring
    • Baptiste did mention that sentry has a lot of noise from docs and other stuff
    • We might still want to know more about things that we should be monitoring
11

8 Jan 2026

Attendees: Saptak, Jason, Ulgen, Paolo, AdamZ
Apologies: Alex, Sanyam, Baptiste, Storm, Sarah

Agenda

Action from last meeting

  • Saptak, Sarah: Review triage document comments
  • Baptiste: see about access to matrix with Fastly (for website stats) and can we ask for more access
  • Everyone: Review Activity on Website WG
  • Saptak: Look into improving the contribution guidelines (Haven’t done but someone did create a PR putting some ideas on improving contribution guidelines
  • Sarah: Ask Stephanie if she has been able to test the flat page improvements
  • Saptak, Sarah: Decision making docs
  • Baptiste, Tobias: explain how we can use the Slack channel for Sentry monitoring
  • Ülgen, Alex: Review https://github.com/django/djangoproject.com/pull/2305
  • (Removed the previous comment here, it was made for the wrong PR - Ülgen)

Actions for next meeting

Questions

  • Would we consider organizing office hours to discuss/review open issues and PRs? We have lots of PRs waiting for input, and other topics that could benefit from technical discussions. I’d allocate an hour every two weeks - Ülgen Sarıkavak
  • Do we need/want to keep pre-commit.ci integration active? We have the lint workflow active and working with GitHub Actions, and the automatic fixer seems to create more pollution/noise than it helps.
  • Are we good with creating a new label for “cleaning before the redesign” tasks? Any objections/blockers?
    • I was initially asking for a new project under this Slack thread. I’m good with a label, but a bit lost about what type of confirmation we need to move further with the redesign - Ülgen Sarıkavak
  • What is our approach for “good practice” issues/PRs?
    • Our current process doesn’t feel healthy. We ignored/rejected/postponed a bunch of “good practice” improvements in the past, saying we didn’t have the resources or that they weren’t beneficial to us, but now we are appreciating other work, saying, “It’s a good practice even if it is not beneficial.”

Notes

  • Ops deploy
    • Right now the deployment is not very systematic. More of a request basis
    • Weekly deploy might be fine
    • For more urgent, we can ping them
      • Maybe we can use feature flags for deployment?
    • Ops team sometimes might feel disconnected sometime but not high priority stuff mostly so weekly might be okay
    • Do we want to have a devops culture to make automated deploys?
      • Probably out of scope for website WG
      • Ulgen: If we had automated maybe ops team wont be responsibility, so maybe we wont need to depend on their availability
  • Restored search hotkey for desktop. #2355
    • Adam: Reducing the complexity was what was needed to reduce the number of search inputs needed.
    • Adam has reviewed the new PR.
    • Needs a little bit more frontend review (Saptak to do this)
    • 2 things to discus:
      • Design change:
        • Saptak likes the design change.
      • Playwright for frontend tests:
        • +1 for separating testing tool changes - Ülgen
        • Adam to comment about separating the playwright thing into a different PR
  • https://github.com/django/djangoproject.com/pull/2421
    • Adam: The team needs to decide more on modern JS, especially if we want this plugin.
    • Paolo: standardizing this tool can help us to format code especially for new contributors as well.
  • Python updates to 3.13-3.14?
    • Saptak mostly fine with updating
    • Need to check with Ops that no concerns on their part
  • Do we have any asks from the board?
    • Let’s add this as part of our agenda from the next meeting so people have some time to put some thoughts before the meeting
  • Have we ever talked about pinning requirements?
    • We currently dont have any pinning lock file. Do we want to do that?
    • Ulgen created a uv migration PR.
    • https://github.com/django/djangoproject.com/pull/2321/changes
    • Sideeffect: Dependabot doesn’t update uv lockfile
    • Paolo: 2 steps:
      • If there is some requirements file with no pinning, first create a compiled requirements.txt file using piptools or uv
      • Then we can further move to lockfiles.
  • Did we consider meeting across different WG?
    • Saptak thinks it might be a good idea to be on same page with everyone
    • Paolo thinks we can do the first one maybe before Djangocon EU?
    • Propose some topics that would be interesting for cross WG teams
  • What are the considerations for adding someone to WG?
    • Contributions? Which repo?
    • Add to documentation so people know what to put in their PR showing interest to be added in the WG
12

12 Feb 2026

Attendees: Saptak, Sarah, Jason, Tobias, Storm, Paolo, Alex, Adam, Sanyam
Apologies: Baptiste, Ron, Ülgen

Agenda

  • Review Action Items
  • Django Fellows merging things
  • Membership applications
  • Decision around people joining/leaving
    • Frequency?
    • Limit the number of members?
  • Recurring deployment plan
  • Issue/PR discussion time proposal
  • Front-end design review needs
  • Discuss Issue #1122
  • AI use disclosure?

Action from last meeting

Actions for next meeting

Questions

Notes

  • Review Action Items
    • Saptak, Sarah: Review triage document comments
      • Website Triage (draft)
      • Reviewed the document, focused more on the triage workflow
      • The document was slightly confusing for new people joining, the triage workflow wasn’t clear.
      • There is now a ‘triage workflow’ section, the working group should review this section
      • Restructured some of the other sections
      • Give everyone time to review the document, resolve all the pending comments and then we can consider this finalized
    • Baptiste: see about access to matrix with Fastly (for website stats) and can we ask for more access (Saptak ping Baptiste about this)
      • Saptak contacted Baptiste
      • What was the question again with the matrix? A: to gain insights through fastly analytics
      • Tobias to check this, Baptiste isn’t here
      • Update: Tobias can create read-only user accounts. Request access through the operations email, we need individual email addresses. Accounts need to set up 2FA though.
    • Everyone: Review Activity on Website WG
      • Saptak & Sarah made some changes
      • We have a lot of people on the working group, we should define expectations around activity
        • Like coming to meetings or apologizing if not,
        • Participate in discussions on Slack, Github etc.
        • Review / create a PR, triage and issue etc.
      • Should we remove people who don’t participate and have little to no activity?
      • Activity could also be more high level: like attending a conference
      • The Wagtail core team assigns an action for someone to reach out to an inactive member asking if they are okay and still want to be involved, usually this is a trigger for someone to review their membership.
    • Saptak: Look into improving the contribution guidelines (Haven’t done but someone did create a PR putting some ideas on improving contribution guidelines)
    • Sarah: Ask Stephanie if she has been able to test the flat page improvements
    • Saptak, Sarah: Decision making docs
      *
    • Baptiste, Tobias: explain how we can use the Slack channel for Sentry monitoring (Saptak ping them to ask more on this)
      • Sentry traffic doesn’t seem to be a lot.
      • It kind of gives information but we don’t have the details so we don’t know how to act on it.
      • It isn’t always clear if there is an error the website working group needs to act on
      • Alex: most errors are documentation or translation errors
      • The documentation generates a lot of sentry errors, this makes sentry less useful to review errors.
      • Overall, the number of errors seems to be fairly low (excluding docs errors)
      • Is it true that we don’t have a lot of errors or are errors missing?
      • Sentry might be more useful to figure out the underlying cause for 500 server errors if encountered, hopefully the summary in the Slack channel gives enough information to go on.
    • Saptak, Sarah: Discuss with Ops about a more concrete deployment plan/ communication.
      • Make a formal request to ops?
      • Not everyone is aware that there is a separate deployment process, when the working group merges a PR it doesn’t immediately go live.
      • Don’t want to ping operations on every merged pull request

      • Idea: set a schedule, like deploy pending changes once a week (unless something high priority comes up of course)
      • The django fellows can deploy too, they are around more than the ops team. Could be worth involving them in this discussion too
      • Sarah and Saptak to discuss this with operations and fellows
      • Most people find it surprising that there are no automatic deployments, might want to discuss this too
    • Jason: address comments and resolve conflicts: Rebase meeting minutes pr2221 #2384
      • Switched computers, will get it done
    • Everyone: Added esupgrade pre-commit hook
      • This makes it so javascript syntax is checked and upgraded to use new syntax
      • The package that makes this possible was authored by the contributor and is not widely used.
      • Paolo encouraged this person to make the contribution
      • So far everyone present at the meeting seems to agree this is a worthwhile change
      • The PR makes a ton of changes to the javascript to upgrade the syntax, this needs a more careful look to make sure it doesn’t introduce any regressions
      • We could introduce eslint as well
      • Next steps: review the PR for regressions in the changed JS code. Storm happy to volunteer
      • Decisions to make:
        • Do we want esupgrade in our pre-commit hooks?
        • Do we want to use eslint? (as a follow up)
      • Check if there is overlap between prettier and esupgrade
    • Saptak to ping Baptiste: Upgrade Python to 3.13 #2234
      • Haven’t done it yet
    • Everyone: Thoughts on lockfiles and pinning (Migrate to uv#2321)
      • Ulgen to rebase, and clean the PR for further discussion
    • Keep github actions up to date with dependabot #2427
    • Some more approvals from other members would be nice
    • Securityt.txt PR
  • Django Fellows merging things
    • Are people okay with the fellows merging PRs?
    • Sometimes there are PRs that are very specific to work a fellow is doing
    • Technically, fellows could merge PRs without waiting for an approval of someone else
    • Any objections to fellows merging things?
      • Storm: no objections, lets not create red tape and let the fellows do their thing
    • Please +1 the slack message so it is clear the working group is in agreement
  • Membership applications – Sarah
    • Both have been in djangonaut space
    • Johanan Oppong Amoateng
      • If they have not replied for some time, can we close it?
      • Has added more context
    • Velda Kiara
    • Let’s create two Slack polls to vote
    • Are they aware of the requirements we set for working group members? Yes
  • Paolo has to leave for a DSF board meeting
    • Anything to report to the board from our working group?
    • Nothing today
  • Decision around people joining/leaving
    • Frequency?
    • Limit the number of members?
    • Wagtail subteams have a 6 month membership, around the end of the cycle is the time to announce and attract new members. Members can also decide to renew their membership or leave.
    • Members in the meeting seem to be in agreement to let new people join/leave targeted around a specific frequency - a cadence
      • Six months seems to be the preference judging from reactions
    • Having a limit/target number of members seems like a good idea too. Sarah/Saptak to work this out a bit further
  • Recurring deployment plan – skipped because of time
  • Issue/PR discussion time proposal – Adam
    • We talked about this a few times
    • We can organize a session for everyone who can be there to triage/review PRs and issues
    • Adam happy to lead such a session, expect we need around 2-3 people to make this work
  • Front-end design review needs – Adam
    • We have a couple of PRs stacking up with CSS changes, Adam isn’t comfortable reviewing those.
    • There are PRs we could merge if we had more frontend review capacity
  • Discuss Issue #1122 – skipped because of time
  • AI usage disclosure?
  • Last minute addition: website redesign - status?
    • Check out the redesign meeting notes - redesign meeting
    • Next steps are waiting for the marketing working group to come up with a direction/goals for the redesign
13

5 Mar 2026

Attendees: Paolo, Alex, Johanan, Baptiste, Sarah
Apologies: Saptak, Adam, Storm, Ulgen, Jason, Ron

Agenda

Action from last meeting

Actions for next meeting

Questions

Notes

  • Welcome Johanan! :partying_face:
    • Quick intros, name, where are you based, work and what do you wanted to be when you were a kid
    • One scientist, one flight attendant and some astronauts here
  • Review Action Items
    • Eslint: find an alternative
    • Saptak, Sarah: Decision making docs
      • A doc has been created by Saptak, need to be reviewed
      • Process would be to any issue which tagged “Need decision”
        • the person who tag it would mention it on slack so we can discuss about it
        • If not agreement/consensus, proceed to a vote
  • Schedule deployment
    • Discussion with Natalia on slack
    • Schedule deployment since the Website WG team don’t deploy
      • Avoid ping randomly the ops team and fellows
      • Better if fellows/Ops decide the date and the Website WG team warn the team it’s good to deploy
      • Q: Is it really required to give a go from the website WG before to deploy?
        • A: Not sure, some deployments has happened without that and if the branch is not clean it’s a critical issue anyway
        • We could consider its ok by default and warn the ops/fellows if there is anything wrong
        • Baptiste is planning to raise the point at the ops level
  • Assignment issue system
    • Duplicate PRs for the same work, tricky to track who is working on what
    • How to mitigate people who ask to be assigned and disappear?
    • It was easy to track people who were working on issue previously
    • Assign folks and remove after some time automatically?
      • Which time?
    • Find balance between low contributions and contributors and coming back
  • psycopg-c issue
    • What should we do with this issue?
    • it’s still open for production and changed to binary for development
    • Doesn’t seems to be required the -c
    • Tobias might be the more knowledgeable, better to get his opinion on how to proceed
  • Security.txt for code.djangoproject.com
    • Q: Who should own it?
      • A: it’s under the website so it should be the Website WG but right now it’s not the case
    • Paolo: we might need documentation for every service and who is owner or responsible (ask Tim Schilling)
    • Alex: “Webinar on Trac”
    • Baptiste happy to share knowledge if people have specific questions
  • Deployment of the preview
    • Baptiste will deploy the search when he can, soon
    • Folks should test before to put it in prod :partying_face:
    • Q: the deployment could be automated?
      • A: not exactly, many script files and credentials, not easy to do
  • April fools maybe?
    • Some ideas were shared
1 Like
14

2 Apr 2026

Attendees: Sarah, Paolo, Ulgen, Adam, Alex
Apologies: Mark, Sanyam, Saptak, Storm, Ron

Agenda

  • Review Action Items
  • PR #2528 next steps
  • Slack issue/PR review meeting

Action from last meeting

Actions for next meeting

  • Sarah/Saptak: Send a request to Ops about having readonly access with individual emails
  • Saptak: Look into improving the contribution guidelines
  • Sarah: resolve comments and create vote with emojis on slack to approve last documents
    - Website Triage (draft)
    - Decision making steps
  • Adam: look into prettier for JavaScript upgrades
  • Sarah: reminder on slack for collecting questions related to Trac in case of sharing ownership

Questions

  • Paolo: a document with all services we have and the knowledge we have would be nice to have and could be shared with the board in order to see resources and potential improvements. Could I have some help from the team to create the document?
    • Sarah proposed to provide help on that

Notes

  • Review Action Items
    • Everyone: Review Website Triage (draft)
      • Q: Do we have a way to approve documents to consider this done?
      • A: One thing would be to vote on slack with emojis to consider as approved, Sarah wanted to solve the last comments before
    • Sarah/Saptak: Send a request to Ops about having readonly access with individual emails
      • Not done, need to check with Saptak
    • Saptak: Look into improving the contribution guidelines
      • Sarah: thoughts on that but no document yet from what I recall
    • Sarah: check for an alternative for formatting js
      • Biome.js to use as suggested by Johanan
      • It is also considered on Django core
    • Everyone: review Decision making steps
      • Sarah will create a vote on this doc
    • Jason: address comments and resolve conflicts: https://github.com/django/djangoproject.com/pull/2384
      • No updates, Sarah will do a reminder to Jason directly
    • Storm, Saptak: https://github.com/django/djangoproject.com/pull/2421
      • PR closed, a new one is open
    • Adam: look into prettier
      • Q: Do we remember the context of why exactly the look of the prettier? We have many discussions around tooling
      • Alex: it’s was related to JavaScript upgrades
    • Tobias: see what to do for psycopg-c issue
      • Baptiste mention in Ops team
      • Paolo and Alex confirmed that they were a discussion saying we should keep using the c package
      • Might need to review the ordering in the Dockerfile because of the last deployment failure
    • Everyone: collect questions related to Trac in case of sharing ownership
      • Q: Is there an issue with Trac? Sorry, missing the context
      • A: No issue, it’s more to clarify the ownership of Trac, right now it’s not owned by Website WG but it’s part of the website and only few people have knowledge and maintain it. If we have more people involved it would be better and also more people would have knowledge on it and opinions on what to do about Trac since right now the knowledge is limited to few folks and it’s hard to determine the maintainability of this repository and any changes that could be good to have.
      • Baptiste is happy to share knowledge from questions we may have. Sarah will do a reminder on slack for people to write down questions.
    • Baptiste: deploy the search in the preview server
      • Done with the new schedule process :tada:
  • PR #2528 next steps
    • This PR needs review in terms of design, and Saptak suggested some changes, unsure if we should do that in this PR or a separate one.
    • Sarah proposed to review it and see with Saptak if merging this one and do another PR for the improvements would be better or not
  • Slack issue/PR review meeting
    • Adam: thank you for participating, we closed many PRs, happy to do that again!
1 Like