I am not a maintainer or developer but an active user if debain and
keepass. I would be willing to take this in depending on timeframe. I have
time starting next week to devote to this. I have built packages in the
past so this is not a huge issue for me

On Feb 14, 2017 5:45 PM, "KeePassXC Team" <t...@keepassxc.org> wrote:

> Package: wnpp
> Severity: wishlist
>
> * Package name    : keepassxc
>   Version         : 2.1.1
>   Upstream Author : KeePassXC <packag...@keepassxc.org>
> * URL             : https://keepassxc.org
> * License         : GPLv2, GPLv3
>   Programming Lang: C++
>   Description     : Community fork of KeePassX, a free and open-source
> cross-platform password manager.
>
> KeePassXC aims to incorporate many pull requests as well as additional
> newly developed features that have never been merged into KeePassX.
> Besides many bug fixes and other minor changes, the current version
> (2.1.1) already contains the following additional features:
>
> - Autotype on all three major platforms (Linux, Windows, OS X)
> - Stand-alone password generator
> - Password strength meter
> - Use website's favicons as entry icons
> - Merging of databases
> - Automatic reload when the database changed on disk
> - KeePassHTTP support for use with PassIFox in Firefox and chromeIPass
> in Google Chrome and Chromium
>
> More features will come in 2.2.0. (e.g. Yubikey support, Twofish cipher
> support, a welcome screen redesign, general user interface improvements
> etc.)
>
> At the time of the fork, KeePassXC built upon the latest but never
> released KeePassX source tree, which included the switch to Qt5.
>
> I'm writing you as one of the main developers of KeePassXC. We would
> like to get KeePassXC into the official Debian repositories and from
> there into other derivatives such as Ubuntu. We would be willing to
> package KeePassXC ourselves, but since none of us developers is an
> active Debian user, we would like to ask first if someone else would be
> willing to package it for us. In the interest of package quality, this
> would likely be best. Packaging KeePassXC is (and for the foreseeable
> future will be) quite similar to packaging KeePassX, so maybe the
> original KeePassX maintainer could handle this if he's willing to? He's
> on X-Debbugs-Cc.
>
> Thanks and regards
> Janek
>
>

Reply via email to