New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Move "buy a feature" feedback into GitHub tickets #4335

Open
nlhkabu opened this Issue Jul 22, 2018 · 0 comments

Comments

Projects
None yet
1 participant
@nlhkabu
Member

nlhkabu commented Jul 22, 2018

I recently ran some user research where users were able to provide feedback on what is most important to them on the project detail page.

One option was for the user to suggest something new.

Here is a list of all of the feedback we received. I have removed anything that 1) didn't give enough information to understand, 2) was already available, or 3) was not relevant.

We need to:

  • Go through this feedback and group it into common threads
  • Where a related issue already exists, add a comment to that issue
  • Where a related issue does not exist, open one

Feedback

  • GPG signatures
  • Report malicious packages
  • Way to display vulnerables releases and link to security details (CVE, etc...)
  • In my opinion the font size of headlines in the project description is too small and doesn't stick out well enough among the regular text
  • Similar packages (based on trove, tags, etc.)
  • CHANGELOG for releases
  • Has the product been verified free of malicious code
  • Examples/samples
  • An "examples" section with short, self-contained code samples, featured near top of page.
  • Eliminate the need for clicks for the details of the latest release (just as it was with the old page), including date, files, sha information, etc.
  • How many correctly answered Stack Overflow questions are there for this module?
  • Download statistics
  • Download statistics actually visible in the page, rather than requiring Google BigQuery
  • 2 features from the old PyPI: list of dependencies from install_requires and GPG signatures (Yes, I've read why they have been removed and I disagree).
  • An interactive shell with the library or tool installed in it so users can play around with it before deciding if it's the right tool for them. Would definitely have to be opt in on the project level, but I see this as something that would really set pypi.org apart from other repos.
  • Tutorial / HowTo / Documentation / Guide
  • Hosted or embedded documentation.. either integration with Readthedocs or another documentation provider.
  • Dependency tree - all deps, with links to their pypi pages
  • Table of Contents generated from Markdown Section Headings, Or Related Packages Section
  • Code samples
  • Number of downloads
  • Big Query Download aggregates ( I miss the old stats info )
  • Security Data regarding versions with known exploits and security fix history
  • List of dependents
  • Show download stats + graph like npm
  • sphinx hosting (like readthedocs)
  • Changelog entries, extracted from github releases or changes/history file
  • Documentation for continuous integration (CI) systems with complete examples for git hooks and Travis.
  • I'd show the downloads only for the source tarball. Wheels should be handle via pip install.
  • Pay for a quick feature/bug fix/customization.
  • Setup instructions
  • performance demand
  • The time between uploading a new version of a package and downloading that new version is around an hour. If I try to download my new version immediately after uploading I'll only receive the old version. I don't know if this is a problem on my end but if it is a consistent problem across most users I would make fixing this a priority.
  • Similarly-named projects (with stats for each); handle pyfoo vs foo, etc.
  • Number of downloads
  • A way to cleanly link back to a source repo. For example I fork the project for a personal project and want to actually release (we typically prefix it) it for our production needs. I would like a clean way to attribute the code to the original author(s) and respect licensing and usage.
  • Statistics about package downloads
  • A link to the documentation of the library,if available
  • Like good wine and cheese, some Python packages pair well together. Perhaps PyPI could identify which packages are downloaded together often, and recommend pairings. For example, if you download Django, you might also like Django REST Framework. I think there's a lot of potential for a "recommendation engine". Perhaps start with something simple, see if people like it, and grow from there. The easiest way would be to count paired downloads. Perhaps another way to approach this would be enhancing the search functionality. I often have a questions like, "What graphical user interface libraries are available in Python?". It would be nice if the search could tell me which are some of the most popular choices. Some metrics to distinguish which GUI library to choose would be awesome.
  • List of highest downloaded packages across different sections as in here - https://github.com/vinta/awesome-python. SO that newbies will get a fair idea what libraries should they be using.
  • it should also show a side list of similar modules
  • Force minimal description size
  • Please show "similar projects" to find alternatives to the package
  • A web based repl so we can test the lib in browser
  • Download statistics need to added then it will be great addition for who is created that package
  • Optional vendor namespace for packages.
  • A Short Description Who are all using this like influencers
  • Api Documentation Like Swagger
  • A better packaging CLI tools that come with the new website. Forget setup.py, setup.cfg and requirements.txt and pip in fact. There is too many people that don't use correctly. The workflow with cargo and dependency and lockfile is just how things should works.
  • Analyse code quality / complexity etc. on all packages and display them on the page
  • Integration with read-the-docs or something similar to link docs.
  • Links or autocreated documentation for packages.
  • Has new 'good' Python 3 version or old 'bad' Python 2 only version?
  • Common Issues for each Package
  • a remote link to install without write pip install
  • Render Quality/completeness/freshness score that may have been used in finding this package expanded in checklist form: README (that renders), homepage link, version string matches development status (indicates some level of semver), python3 support, license indicated, etc.
  • Copy requirements.txt latest format ie. package==1.2.3
  • If the homepage for the project is a GitHub repo, augmenting the GH status pane to show various commit activity statistics would be neat...'avg commits per day/week/month since the last release'. The current GH project status box gives an idea of the popularity of the project, but something like this would give an idea of the level of development activity on the project.
  • Download/Install Statistics
  • Favourite and create lists of repositories for different project templates
  • I wish to be able to search for entries given a time interval mostly search for all entries in the last 1 day.
  • App builder and app store
  • Bookmark (star) the project
  • dependencies
  • Popularity
  • I hope the list of package dependencies is available somewhere, not just distribution dependencies. That's one of the first considerations I make in depending on a project.
  • Whether the package is pure Python and if not what other languages are used
  • Compatibility (Windows, Jython, Cygwin, Linux, MacOS, etc.)
  • Link to latest "preview", or "There is a more recent preview package". Right if you don't click on "Release history", you don't know there is a preview version available.
  • Some kind of activity / liveness / maintained-ness / usage metric
  • Stats from github, gitlab, bitbucket
  • Kickstart and donations for new released
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment