Comment 9 for bug 1853001

I would suggest to start by familiarizing yourself with the upstream codebase.

Looks like the official location of the code is in bzr on launchpad, but Dustin has a mirror of it in github:

    bzr branch lp:powernap
    https://code.launchpad.net/~powernap/powernap/trunk

    https://github.com/dustinkirkland/powernap/commits/master

Where to start kind of depends on where you feel most comfortable with your skills, and what you feel is most important for the project, but if it were me here's a grab bag of ideas I might consider doing if it were me:

  * Create a branch in github
  * Add a setup.py
  * Convert it from python2 to python3
  * Add pytest and test cases
  * Add code docs where needed
  * Add a README.md, AUTHORS.md, and LICENSE.md
  * Look at the three pull requests in github to include
  * Look at the three MPs in launchpad
  * Look at the eight bug reports in launchpad
  * Contact Dustin (he's still around) to offer taking over maintainership
  * Create a new release (maybe make version 3.0 mark the python3 conversion?)
  * See if it might be useful to Debian or other linux distros

The codebase also has a debian/ directory included since historically Dustin maintained the package as well as the upstream codebase. It's actually a bit more typical to handle those completely separately, so if you're not comfortable maintaining the Ubuntu packaging you could consider focusing on just the upstream python code and leave the packaging to others to maintain.