Hi @meyersbs! I noticed that the following package(s) don't yet have maintainers:

• openmm

Are you interested in adopting any of these package(s)? If so, simply add the following to the package class:

    maintainers("meyersbs")

If not, could you contact the developers of this package and see if they are interested? You can quickly see who has worked on a package with spack blame:

$ spack blame openmm

Thank you for your help! Please don't add maintainers without their consent.

You don't have to be a Spack expert or package developer in order to be a "maintainer," it just gives us a list of users willing to review PRs or debug issues relating to this package. A package can have multiple maintainers; just add a list of GitHub handles of anyone who wants to volunteer.

Haven't had a chance to test yet; looking like a Monday task at this point.

@adamjstewart LGTM; installed and tests passing

@spackbot fix style

Let me see if I can fix that for you!

I was able to run spack style --fix for you!

==> Running style checks on spack
  selected: isort, black, flake8, mypy
==> Modified files
  var/spack/repos/builtin/packages/openmm/package.py
  var/spack/repos/builtin/packages/py-meldmd/package.py
==> Running isort checks
  isort checks were clean
==> Running black checks
reformatted var/spack/repos/builtin/packages/py-meldmd/package.py
All done! ✨ 🍰 ✨
1 file reformatted, 1 file left unchanged.
  black checks were clean
==> Running flake8 checks
var/spack/repos/builtin/packages/py-meldmd/package.py:66: [E501] line too long (102 > 99 characters)
  flake8 found errors
==> Running mypy checks
Success: no issues found in 573 source files
  mypy checks were clean

I've updated the branch with style fixes.