Context

This repository hasn't seen active maintenance in some time, and there are open PRs and issues that have gone unreviewed. The package still has users who depend on it, but the current state makes it difficult to get fixes merged - for example, basic packaging fixes needed for license-compliance tooling (#65), among others. @anderskm

Questions for the community

1. Is this repo effectively unmaintained? If the original maintainer is no longer able to maintain it, it would be helpful to know so the community can plan accordingly.
2. Should the repo be formally archived? Archiving would set clear expectations for users and contributors.
3. Would there be interest in a community-maintained fork? If so, we could coordinate on:
   • Where the fork would live (a new GitHub org, an existing one, etc.)
   • Who would be willing to help maintain it
   • Whether to publish under a new package name on PyPI or seek ownership transfer
   • Modernizing the packaging (e.g. migrating to pyproject.toml, switching from distutils to setuptools)

Why this matters

GPUtil is a useful utility that people still install as a dependency. Without maintenance, users are pinned to outdated packaging practices, unpatched bugs, and no path to getting improvements merged. A community fork would give the project a sustainable future.

If you're a user of this package or interested in helping maintain a fork, please chime in.(maybe @atarwn since your fork seems to have most stars?)