Hello, I’m writing to get a discussion started regarding the future of PyPy infrastructure hosted with the PSF. This currently includes: - pypy.org <http://pypy.org/> - speed.pypy.org <http://speed.pypy.org/> - downloads.python.org/pypy <http://downloads.python.org/pypy> In April, I contacted pypy-sync on IRC to discuss how DNS records are handled for pypy.org as it has been a barrier to making changes to PSF infrastructure in the past. Because it is the only domain the PSF infrastructure team does not have access to change we have had trouble completing migrations that are related to this specific record. Two things were mentioned that clearly got misconstrued by one of the members of pypy-sync. 1) After noting scroll back mentioning some other domain, I mentioned that the PSF is always available to accept transfer of Python ecosystem domains and maintain their renewal in perpetuity 2) I said "on that note, i'm once again planning some migrations and the apex record pypy.org is once again... an annoyance. The PSF infrastructure is going to institute a policy in the coming months that for infrastructure we host/provide we need access to DNS to make changes to PSF Infra relevant records. who is best to discuss this with?” When I returned, I found that a discussion had ensued that presumed a lot of intent and was honestly hurtful. Since it occurred outside of a PSF online space, I didn’t really have any recourse and just left the channel, I have not returned. So here’s where we’re at: The PSF is always happy to provide any kind of service or resource to PyPy or any Python-related project, but we do need appropriate access to do that right. For example, we can't host services if we can't update DNS records in a timely manner. We need to either formalize a relationship between the PyPy team and PSF infrastructure or part ways for the hosted infrastructure listed above. This formalized relationship will need to have agreements regarding common access to some resources at a minimum and also agree to discuss/collaborate on infrastructure needs in a space governed by the PSF Code of Conduct. -Ee Durbin Director of Infrastructure Python Software Foundation