Closed as not planned
Description
It's difficult to observe potentially important maintenance policy decisions if they happen in another repo. That said, I don't think it's inherently more or less proper to have the discussion in
to be clear. As has already been mentioned by one participant in that discussion, while this is clearly an important discussion for the libc crate, it may have ecosystem-wide impacts. Thus, treating it as a discussion for the libs team in general seems appropriate in other ways. Nonetheless, I raise it as an issue here anyways, if only to accomplish the feat of providing a redirect. It's a potential bug in the human interface of this crate, rather than the machine interface.