Bug#1109792: ITP: sr -- Role-based sudo alternative for privilege delegation

[Eddie Billoir <lechatp@outlook.fr>]

Package: wnpp
Severity: wishlist
Owner: Eddie Billoir <lechatp@outlook.fr>
X-Debbugs-Cc: debian-devel@lists.debian.org, lechatp@outlook.fr

* Package name    : sr
  Version         : 3.1.1
  Upstream Contact: Eddie Billoir <lechatp@outlook.fr>
* URL             : https://github.com/LeChatP/RootAsRole/
* License         : LGPL-3.0
  Programming Lang: Rust
  Description     : Role-based sudo alternative for co-administration

sr is the main tool of the RootAsRole project, providing a modern,
memory-safe alternative to sudo. The projects enforces a Role-based
access control model that allows precise delegation of administrative
tasks.
This package also includes chsr, a configuration utility designed to
simplify the definition and management of roles.
RootAsRole's design targets co-administration environments where several
administrators with disctinct responsibilities share control, enabling
separation of duties and limiting the privilege abuse. The overall projects
scope aims to enable a unified and flexible access control policy framework.

Hello, I'm the developer of RootAsRole, I worked on it all along my studies
and it is now a serious alternative to sudo. But beyond the sr tool, the
main objective of the project is to propose an orchestrator of low-level
access controls mechanisms for high-level access control policies.
As the main objective is to have more sophisticated access control policies,
it imply way more rules in the policy, so now I am quite happy that the 
tool currently outperforms sudo by a raw 77% and scales 40% better.
I use my own tool day-to-day on many Linux distributions, and I also
use it for writing some sophisticated Ansible deployements access control
policies, it works well and it's unit-tested.

I admit that already started to do the deployement of some dependencies
within the Rust Packaging Team conf tool, as I was a bit curious on the
work that has to be made. I can start the first deployment effort but it
miss several packages dependencies, so it's going to take some time. 
I don't know if I will have the time to both develop and maintain the
package deployments over all the wanted distributions, so yes I'm
looking for co-maintainers, it's always appreciated. And to answer the
last question : yes, I need a sponsor.