sphinxcontrib-spelling 4.3.0

sphinxcontrib-spelling is a spelling checker for Sphinx-based documentation. It uses PyEnchant to produce a report showing misspelled words.

What’s new in 4.3.0?

  • Logging: use warning() instead of its deprecated alias (contributed by Sergey Kolosov)
  • Support additional contractions (contributed by David Baumgold)
  • require sphinx >= 2.0.0
  • declare support for python 3.6

sphinxcontrib.datatemplates 0.4.0

sphinxcontrib.datatemplates is an extension for Sphinx to render parts of reStructuredText pages from data files in formats like JSON, YAML, XML, and CSV.

NOTE: This release deprecates the “datatemplate” directive in favor of source-specific variants in the datatemplate domain. See the documentation for details.

What’s new in 0.4.0?

  • deprecate the datatemplate directive in favor of the directives in the domain
  • Wrap directives in minimal domain (contributed by Jan Brohl)
  • Add directive “datatemplate” for backwards compat (contributed by Jan Brohl)
  • Split datatemplate directive by file type (contributed by Jan Brohl)
  • Ignore venv, vscode settings (contributed by Jan Brohl)
  • add option for encoding (contributed by Jan Brohl)

sphinxcontrib.datatemplates 0.3.0

sphinxcontrib.datatemplates is an extension for Sphinx to render parts of reStructuredText pages from data files in formats like JSON, YAML, XML and CSV.

What’s new in 0.3.0?

  • Add dialect support, better dotumentation (contributed by Jan Brohl)
  • Use yaml.safe_load (contributed by Jan Brohl)
  • Add XML support (contributed by Jan Brohl)
  • Add CSV support (contributed by Jan Brohl)

imapautofiler 1.8.0

imapautofiler applies user-defined rules to automatically organize messages on an IMAP server.

What’s new in 1.8.0?

  • use yaml safe loader
  • drop python 3.5 and add 3.7 support
  • perform substring matches without regard to case

sphinxcontrib.datatemplates 0.2.0

sphinxcontrib.datatemplates is an extension for Sphinx to render parts of reStructuredText pages from data files in formats like JSON, YAML, and CSV.

What’s new in 0.2.0?

  • Use sphinx.util.logging for logging calls (contributed by Sean McGinnis)
  • optionally exec the conf.py file and pass settings to the template
  • make test-template support python 2 and 3
  • update to python 3.5
  • add license file
  • Add links to repo and docs from README and docs frontpage (contributed by Christoph Deil)
  • add a command line tool to make testing templates easier

sphinxcontrib-spelling 4.2.1

sphinxcontrib-spelling is a spelling checker for Sphinx-based documentation. It uses PyEnchant to produce a report showing misspelled words.

What’s new in 4.2.1?

  • fix remaining logging issue (contributed by Timotheus Kampik)
  • Remove usage of deprecated logging API (contributed by Tim Graham)

openstack-summit-counter 0.3.0

openstack-summit-counter is a plugin for python-openstackclient, the command line tool for interacting with OpenStack. This plugin helps you answer the summit registration question about how many summits you have attended in the past.

What’s new in 0.3.0?

  • Add events for the Stein cycle (contributed by Colleen Murphy)

Planting Acorns

This post is based on the closing keynote I gave for PyTennessee in February 2018, where I talked about how the governance of an open source project impacts  the health of the project, and some lessons we learned in building the OpenStack community that can be applied to other projects.

OpenStack is a cloud computing system written in Python. The project is 8 years old. During that time we have had 18 major releases, and to give you an idea of the size of the community, during 2017, we had 2,500 people contribute more than 65,000 patches. The age and size of the project means our community has been through several transitions and challenges that other smaller projects may not yet have encountered, and my hope is that by thinking about them early, you can prepare for them, and your communities will be able to grow in a healthier way.

I started working on OpenStack in 2012, 2 years after the project had been launched and right at the beginning of a period of increased interest and contributions. It was the leading edge of the up-slope for our hype curve. I started looking at the code with my team at Dreamhost, but my first significant exposure to the community was at a Design Summit, an in-person event for organizing the teams working on different parts of the software. It was an energizing experience.

I had been to conferences before, including open source conferences like PyCon and PyTennessee, but never anything quite like this. We had hundreds of contributors gathered together in one place for a week of meetings, discussions, arguments, decision making, and, just as importantly, socializing. The enthusiasm of the participants was amazing, and the event led me to dive deeper and deeper into the project over the following 6 years.

At that summit I was part of starting two new teams, one based on metering cloud use for billing and one based on building a set of reusable libraries for the different OpenStack services. My experience with trying to help launch those teams within the community sparked my ongoing interest in open source project governance — not just how to build open source software, but how to build the communities around it — in part because, at the time, OpenStack had no system in place for expanding the scope of the project, and the community struggled to work out how to do it. Today, I want to share 9 themes that may help you avoid pitfalls when considering governance in your own projects.

Continue reading “Planting Acorns”