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