Bug#819816: ITP: debops -- Ansible based server management utility

[Maciej Delmanowski <drybjed@drybjed.net>]

Hello,

The base repository contains just scripts which are a frontend and glue
between Ansible and playbooks/roles. Any ideas how the rest of the project,
meaning the playbooks and roles themselves, should be handled, if at all, in
Debian?

Having a .deb package per role (separate git repository) seems a little
overkill, and the number of roles would only grow over time. On the other
hand, preparing a 'debian/' directory for easier packaging of all of the roles
should be easily doable. The roles could alternatively be bundled some broad
categories which would reduce number of packages involved, however that might
be tricky when each role is tracked separately with its own version tags.

Is there any precedence in Debian similar to this issue?

Thanks,
Maciej