ATC Collaborators for October 2023

[asf-ci-trafficcontrol]

This PR uses .asf.yaml to assign the GitHub Triage role to non-committer contributors who fixed 2 or more Issues in the past 31 days:

• @AbdelrahmanElawady fixed 4 Issues:
  • Set uncacheable delivery services in Varnish config #7770, fixed by Configure uncacheable delivery services in Varnish #7771
  • Document how to run Varnish with CIAB #7724, fixed by Add section for how to run Varnish #7783
  • Add support for HTTPS requests to Varnish cache #7722, fixed by Add HTTPS support to Varnish cache using Hitch #7725
  • Create separate profiles for Varnish cache in CIAB #7721, fixed by Add separate profiles for Varnish cache #7727
• @srijeet0406 fixed 2 Issues:
  • API v5 client.CreateDeliveryServicesRequiredCapability 404s #7801, fixed by Removing v5 client methods for Delivery Service Required Capabilities #7804
  • TR should default to using TO API 5.0 #7658, fixed by Changing Traffic Router to point to Traffic Ops api version 5.0 #7757

Congrats! For the month of October, @AbdelrahmanElawady and @srijeet0406 will have the ability to

• Apply labels to Issues and Pull Requests
• Assign a user to an Issue (note that non-committers can be assigned to an Issue after commenting on it)
• Add a user as a Reviewer of a Pull Request, which will send a request to them to review it
• Mark Issues and Pull Requests as a duplicate

---

These privileges will expire at the end of October. If you want to be an Apache Traffic Control collaborator next month:

1. Read our contribution guidelines
2. Find an Issue to work on (recommended issues have the good first issue label) and ask to be assigned
3. Get coding! For questions on how to contribute, you can reach the ATC community on
   • The #traffic-control channel of the ASF Slack (invite link)
   • The ATC Dev mailing list (archives)

---

Which Traffic Control components are affected by this PR?

• Other: .asf.yaml

What is the best way to verify this PR?

Verify that the fixed Issues listed above are linked to PRs from the past 31 days

PR submission checklist

• This PR has tests
• This PR has documentation
• This PR has a CHANGELOG.md entry
• This PR DOES NOT FIX A SERIOUS SECURITY VULNERABILITY (see the Apache Software Foundation's security guidelines for details)