#35824: Improve patch_cache_control documentation
-------------------------------------+-------------------------------------
     Reporter:  Adam Johnson         |                    Owner:  Waqas
         Type:                       |  Younas
  Cleanup/optimization               |                   Status:  assigned
    Component:  Documentation        |                  Version:  dev
     Severity:  Normal               |               Resolution:
     Keywords:                       |             Triage Stage:  Accepted
    Has patch:  0                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------
Comment (by Ahmed Nassar):

 Hi there,

 I noticed this issue has been open for several months and doesn't seem to
 have active progress. I'm interested in contributing to this task.

 Could you please:
 - Confirm if this issue is still relevant?
 - If the issue is still valid, would you be open to having me work on it?
 - If you're no longer actively working on this, would you be willing to
 unassign yourself so I can take it over?

 I'm prepared to:
 - Carefully review the current documentation
 - Propose specific improvements
 - Submit a pull request following Django's contribution guidelines

 Thank you for your time and consideration.
-- 
Ticket URL: <https://code.djangoproject.com/ticket/35824#comment:3>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion visit 
https://groups.google.com/d/msgid/django-updates/01070195827e8a8f-82b459b3-ff14-4a17-8028-5e49bda64fb4-000000%40eu-central-1.amazonses.com.

Reply via email to