Thank you, this is helpful, I want to work on some of them:

• Use gzip compression by default
• Make it easy to add a user-agent header and give examples of a good one in the documentation for it (see https://meta.wikimedia.org/wiki/User-agent_policy)
• Add Python 3 compatibility (this is in progress for the core branch)
• Package pywikibot for installation from PyPI via pip install
• Make the initial installation process lighter-weight:
  • Design pwb.py with user experience in mind, particularly valuing feedback from new or one-time users during the redesign process
  • Make it possible to install into a virtualenv without putting a config file in the home directory
  • Make it possible to run import pywikibot without having to log in
• Iterating over a list and calling the API for each item is an inefficient use of API calls. Efficiency in API usage is an important feature of a gold standard library. If you are interested in gold standard status, consider making this more efficient by combining API calls as much as possible (e.g. using generators and combining resultstitle=title1|title2|...). One option may be a constructor method that collects Page requests and enables larger, less frequent API calls. It may be possible to take advantage of the database-like structure of the MediaWiki API and help users save bandwidth.

Process-related

• Foster a hospitable attitude on pywikipedia-l, especially to new and/or inexperienced users. Consider agreeing on community standards for interaction; the Hacker School social rules may be a useful starting point.
• Create more centralized and updated documentation, including:
  • Easy-to-find, complete, and intuitive installation instructions, including installing via pip and into virtual environments
  • Code samples for common tasks, including queries and edits
  • Documentation for people who aren't running bots with existing scripts (particularly researchers and beginning/intermediate bot writers)
  • Links in method documentation to the corresponding API subpages
• Streamline or add more resources to the patch review process to reduce the backlog of unreviewed patches

If someone is willing to help out, let's work!