Monday, February 26, 2018

Python package maintainers, help test the new PyPI!


Warehouse is a next-generation Python Package Repository which will replace the existing code base that currently powers PyPI. (See the source code on GitHub, and roadmap for details.) We are seeking maintainers of projects on PyPI to test it and send us bug reports, and we're seeking new contributors to Warehouse.

Since Warehouse must be a reimplementation of the existing PyPI, please focus initially on any differences, missing features, or incorrect behavior that is exhibited on pypi.org that affect your workflows for account management and package maintainership. We'll be soliciting feedback on other concerns soon! Feedback on user experience, accessibility, and overall ease of use are welcome. Go to the pre-production deployment at pypi.org and try it out!

Background


Last year, the PSF's Packaging Working Group successfully applied for a grant from Mozilla's Open Source Support program. Mozilla awarded USD 170,000 to get PyPI upgraded. The team's been working since early December—see our progress reports and roadmap—and pypi.org now has the essential features that package maintainers, and most other users, need.


Guidelines for Particpation


By participating, you agree to abide by the PyPA Code of Conduct.
You should sign up for the PyPI Announcement Mailing List for updates.

Things to test


Most of these you can test on pypi.org, using the same login as you use on pypi.python.org (legacy PyPI). For testing destructive actions, like removing an owner, deleting a project, or deleting a release, please use test.pypi.org, which has an entirely separate package index.

Workflows


  • Add/Remove Maintainer
  • Add/Remove Owner
  • Transition Ownership
  • User Registration and Confirmation
  • Login/Logout
  • Password Reset
  • Remove a project
  • Remove a release
  • View Journals for a Project
  • View Journals for a Release
Warehouse has handled new projects and new release uploads since last summer, so those workflows are not the most important to test now. The list of workflows above are the ones we request you to exercise.

Security


If you find any potential security vulnerabilities, please follow our published security policy. Please don't report security issues in Warehouse via GitHub, IRC, or mailing lists. Instead, please directly email one or more of our maintainers.

IRC livechat hours


Warehouse developers will be in IRC, in #pypa-dev on Freenode, and available to talk about problems you run into, or about how to hack on Warehouse:
  1. Tuesday Feb 27th: 1700 UTC / noon-1pm EST
  2. Tuesday Feb 27th: 2300 UTC / 6pm-7pm EST
  3. Thursday March 1st: 1700 UTC / noon-1pm EST
  4. Thursday March 1st: 2300 UTC / 6pm-7pm EST
Feel free to drop in!

Notice


We're working hard on nearly every aspect of the Warehouse codebase to get it ready for production deployment and we are shipping features nearly every day, so check back and maybe even try using pypi.org for your maintainer activities full time. Due to the rate of change some errors, downtime, and outright broken features may occur. We have some automated reporting of the scenarios in place, but let us know!

Reminder: Sign up for the PyPI Announcement Mailing List to be kept in the loop as we continue this process.

Dive into the code


We've improved Warehouse's developer experience substantially in the last few months. We have several open "good first contribution" issues and a guide to getting started. One of our maintainers, Ernest W. Durbin III, wants to help you dive in and to give you Warehouse stickers, and has 30-minute 1:1 slots available to mentor you. We'll also be running a sprint at PyCon North America in May!

Contact us



Thank you for testing Warehouse! You're helping us launch sooner and future users of PyPI will appreciate it.

— The PyPI Team



Photo © Mark Hunter