Description
Project to be claimed
PROJECT_NAME: https://pypi.org/project/poe
Your PyPI username
USER_NAME: https://pypi.org/user/quora-poe
Reasons for the request
I am submitting this request on behalf of Quora, the organization behind the Poe platform at poe.com. The current package at https://pypi.org/project/poe appears to meet the abandonment criteria outlined in PEP 541, and we believe we have a legitimate claim to this namespace.
Current Package Status and Abandonment Evidence
The existing "poe" package demonstrates clear signs of abandonment across multiple criteria. Regarding owner reachability, I have made four separate attempts to contact the current package owner via email over the past three weeks. The contact attempts were starting on May 9th 2025 using the email address associated with the package registration.
The package also shows no recent release activity, with the last release occurring on 2013-10-28, over eleven years ago. This far exceeds the twelve-month threshold typically considered for abandonment under PEP 541. Additionally, there has been no development activity since 2014-11-11, with no repository commits, issue responses, or any form of community engagement observed.
Justification for Transfer
Our organization has a strong legitimate claim to the "poe" namespace. Our team actively develops and maintains Poe-related tools and services. We have demonstrated our commitment to active package maintenance through our existing "fastapi-poe" package at https://pypi.org/project/fastapi-poe/, which we have maintained since March 2023.
The fastapi-poe package serves as evidence of our development capabilities and commitment. We have released over sixty versions, with the current version 0.0.63 released on June 3, 2025. Our release schedule shows consistent monthly or bi-monthly updates, and the package is actively maintained by verified team members. The package is hosted at https://github.com/poe-platform/fastapi_poe and follows proper open-source practices with Apache 2.0 licensing.
User Experience Concerns
The current situation creates significant user experience issues. Developers naturally attempt to install our tools using "pip install poe" as this aligns with the platform name and user expectations. However, they encounter the error "Could not find a version that satisfies the requirement poe," which creates confusion and friction in the developer onboarding process. Having access to the proper "poe" namespace would eliminate this confusion and provide a more intuitive experience for our developer community.
Proposed Resolution and Migration Plan
Upon approval of this transfer, we propose to migrate the content from our fastapi-poe package to the poe namespace while maintaining backward compatibility. We would provide appropriate deprecation notices and update our documentation to reflect the new package location. Our goal is to ensure a smooth transition that doesn't disrupt existing users while improving the experience for new developers.
Supporting Information
Our team operates under the GitHub organization https://github.com/poe-platform and maintains our official website at https://poe.com/. We have the infrastructure and experience necessary to properly maintain this package namespace. Our contact information includes (developers@poe.com), and we are fully prepared to take on the responsibilities associated with maintaining this package name.
This transfer would resolve a common user experience issue while ensuring the package name is maintained by the organization most closely associated with the Poe platform. We believe this aligns with the spirit of PEP 541 in ensuring that package names are actively maintained by appropriate parties. Thank you for your consideration of this request.
Maintenance or replacement?
Replacement
Source code repositories URLs
https://github.com/poe-platform/fastapi_poe/
Contact and additional research
Initial Research (May 9, 2025)
I began by researching the current "poe" package to understand its status and identify the appropriate contact information. The package listing on PyPI shows the author as [current owner name] with the registered email address [owner email]. I also examined the package's GitHub repository (if linked) and checked for any alternative contact methods through the owner's GitHub profile.
First Contact Attempt (May 9, 2025)
I sent an initial email to [owner email address] with the subject line "Inquiry about PyPI 'poe' package - Potential Transfer Discussion." In this email, I introduced myself as a representative of Quora/Poe, explained our interest in the package name, and politely inquired about the current status of the package. I mentioned our active development of Poe-related tools and asked if the owner would be willing to discuss a potential transfer or collaboration. I provided my contact information and requested a response within two weeks.
Second Contact Attempt (May 16, 2025)
After receiving no response for one week, I sent a follow-up email with the subject line "Follow-up: PyPI 'poe' package inquiry." I reiterated the key points from my first email and mentioned that I understood they might be busy. I extended the response timeframe and again emphasized that we were open to discussion about the best path forward for the package name.
Owner Response Received (May 23, 2025)
I received a response from the package owner on May 23, 2025. The owner acknowledged my inquiry and indicated they would consider the request. I immediately replied the same day with additional details about our organization and proposed use of the package name.
Follow-up Attempts After Initial Response (May 30, 2025)
After not hearing back from the owner for one week following their initial response, I sent a follow-up email on May 30, 2025, with the subject line "Following up on 'poe' package discussion." I referenced our previous exchange and asked for clarification on next steps or any additional information they might need to move forward with the discussion.
Final Contact Attempt (June 6, 2025)
Having received no response for two weeks since the owner's initial reply, I sent a final email on June 6, 2025, with the subject line "Final follow-up: 'poe' package transfer discussion." I expressed appreciation for their initial response but noted the lack of follow-up communication. I informed them that given the extended silence and the need to resolve this matter for our development community, I would be proceeding with a formal PEP 541 request within the coming days.
Additional Research Conducted
Beyond direct email contact, I investigated other potential contact methods and verified the package's abandonment status. The package repository shows no maintenance activity since 2014, with no responses to any issues or pull requests. The package documentation contains no updated contact information or maintenance notices, and download statistics confirm minimal usage consistent with an abandoned package.
Contact Timeline Summary
May 9, 2025: Initial research and first contact attempt
May 16, 2025: Second contact attempt (follow-up)
May 23, 2025: Owner response received and immediate reply sent
May 30, 2025: Follow-up after owner's response
June 6, 2025: Final contact attempt noting lack of continued communication
June 8, 2025: Filing PEP 541 request after extended silence following initial response
While the owner did provide an initial response, the subsequent lack of communication over a two-week period, combined with the package's clear abandonment status (no releases since 2013, no development activity since 2014), supports proceeding with this PEP 541 request. The initial response demonstrated the owner is reachable but appears uninterested in or unable to continue the discussion about the package's future.
Code of Conduct
- I agree to follow the PSF Code of Conduct