> please don't use python- prefix, use mkdocs-bootswatch. Note that binary > package is "mkdocs"
Ok, so I just call both source *and* binary packages mkdocs-bootswatch and mkdocs-bootstrap then? >> I plan to maintain this as part of the DPMT - Debian Python Modules >> Team. > > I think PAPT is more appropriate for mkdocs. I don't think it is also > appropriate for themes, but since mkdocs-bootswatch/mkdocs-bootstrap are > tightly related to another DPMT^W PAPT package, IMHO we can make an > exception in PAPT for them (but I'd prefer to have them outside the > team, TBH - DPMT/PAPT are not collab-maint replacements). mkdocs was required for a DPMT package - django-rest-framework - and this is the only reason I bother to package it. It is already in DPMT. Recent mkdocs has split up, and now requires these packages too. I tried to get access to PAPT (so I could fix another package), however so far haven't got a response. I would sooner maintain them in collab-maint rather then PAPT, because I don't really want to have to convert my git repositories to subversion. I believe subversion is still required by PAPT. -- Brian May <b...@debian.org>