netdev - Forking on MMSD

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <634e0debea558b90af2cebfc99518071f1d630e9.camel@talbothome.com>
Date:   Wed, 14 Apr 2021 14:21:04 -0400
From:   Chris Talbot <chris@...bothome.com>
To:     ofono@...no.org, netdev@...r.kernel.org,
        debian-on-mobile-maintainers@...oth-lists.debian.net,
        librem-5-dev@...ts.community.puri.sm, 982250@...s.debian.org,
        985893@...s.debian.org
Subject: Forking on MMSD

Hello All,

In talking to the Debian Developer Mr. Federico Ceratto, since I have
been unable to get a hold of the Ofono Maintainers, the best course of
action for packaging mmsd into Debian is to simply fork the project and
submit my version upstream for packaging in Debian. My repository is
here: https://source.puri.sm/kop316/mmsd/

I am sending this so the relavent parties are aware of this, and to
indicate that I no longer intend on trying to get a hold of upstream
mmsd to try and submit patches.

For the Purism Employees, I am additionally asking for permission to
keep hosting mmsd on https://source.puri.sm/ . I have been extremely
appreciative in using it and I am happy to keep it there, but I want to
be neighboorly and ask if it is okay for me to keep it there. If it is
not, I completely understand and I am fine with moving it to a new
host.

If you have any questions, comments, or concern, please reach out to
me.

-- 
Respectfully,
Chris Talbot