ATC Collaborators for August 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:

• @TaylorCFrey fixed 2 Issues:
  • Incorrect response from associating zero or more Federation Resolvers with a Federation #6795, fixed by Remove wrapper around response object #6956
  • Extraneous field erroneously included in Server Capability and Topology creation/modification responses #6792, fixed by Prevent RequestedName field from being returned in Topologies and Ser… #6970

Congrats! For the month of August, @TaylorCFrey 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 August. 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)