reject TPA-RFC-15 (#40363)
authored
by
The rationale here is that we prefer to outsource the technical and staff risks to outside, because TPA is already pretty loaded. The problem, now, of course, is that we need to make a NEW RFC, but one thing at a time. For details, see tpa-team email with Message-ID: CAAA5PKyJBWX82MYmXPX-Uq8+U00tO8DDFDA0yoGjYAOOX8qTVw@mail.gmail.com