List some common possible responses from the libs team

Author: joshtriplett

.github/ISSUE_TEMPLATE/api-change-proposal.md

@@ -41,3 +41,9 @@ Could this be written using existing APIs? If so, roughly what would that look l
 This issue is part of the libs-api team [API change proposal process]. Once this issue is filed the libs-api team will review open proposals as capability becomes available. Current response times do not have a clear estimate, but may be up to several months.
 
 [API change proposal process]: https://std-dev-guide.rust-lang.org/feature-lifecycle/api-change-proposals.html
+
+Some common possible responses from the libs team:
+
+- We like this specific solution, approved, you or someone else should implement this.
+- We think this problem is worth solving, but we don't think the proposed solution is the right solution. Here are some hints that might help shape a better solution.
+- We don't think this should be part of the standard library. This doesn't mean the problem is unimportant, but not everything belongs in the standard library.