ATC Collaborators for May 2022

[asf-ci]

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:

• @ericholguin fixed 3 Issues:
  • Can create a server with a profile belonging to another CDN #6781, fixed by Fix internal server error and false positive when creating a server  #6782
  • /api/3.0/servers POST request with no profile key returns Internal Server Error  #6779, fixed by Fix internal server error and false positive when creating a server  #6782
  • Document API stability changes  #6700, fixed by Document API Stability changes #6783
• @jpappa200 fixed 2 Issues:
  • t3c should use secondary parent if there is no ONLINE primary parent #6780, fixed by if no parents exist t3c will use secondary parents if configured  #6673
  • T3C keeps using old cookies on user change #6722, fixed by Fix t3c cookie issue when user changes #6725

Congrats! For the month of May, @ericholguin and @jpappa200 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 May. 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)