From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:44181) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fTip7-0004Of-Sg for guix-patches@gnu.org; Fri, 15 Jun 2018 03:07:06 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fTip4-0006fZ-07 for guix-patches@gnu.org; Fri, 15 Jun 2018 03:07:05 -0400 Received: from debbugs.gnu.org ([208.118.235.43]:40891) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1fTip3-0006fN-Ri for guix-patches@gnu.org; Fri, 15 Jun 2018 03:07:01 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1fTip3-0000cP-Ll for guix-patches@gnu.org; Fri, 15 Jun 2018 03:07:01 -0400 Subject: [bug#31307] [PATCH] Add MAT, the Metadata Anonymisation Toolkit from Boum Resent-Message-ID: From: ludo@gnu.org (Ludovic =?UTF-8?Q?Court=C3=A8s?=) References: <87wowrj9kq.fsf@gmail.com> <877eohrgeu.fsf@gnu.org> <20180506194444.GB8038@jasmine.lan> Date: Fri, 15 Jun 2018 09:06:32 +0200 In-Reply-To: <20180506194444.GB8038@jasmine.lan> (Leo Famulari's message of "Sun, 6 May 2018 15:44:44 -0400") Message-ID: <8736xoy1dz.fsf@gnu.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-patches-bounces+kyle=kyleam.com@gnu.org Sender: "Guix-patches" To: Leo Famulari Cc: Chris Marusich , 31307@debbugs.gnu.org Hello, Leo Famulari skribis: > I see two different issues here: > > 1) The project is unmaintained (last release 2016) and the underlying > platform (Python 2) will become unmaintained in January 2020. > > I think these maintenance issues are not a blocker in this case. We > package lots of software that has been basically abandoned for longer > than MAT. Its source repo saw activity in March. On this subject, we > should think about building from HEAD since those new commits will > probably never be "released". > > 2) The software is not guaranteed to achieve its goals. > > I think the idea of "anonymizing" a file is always going to be > manifested as a goal rather than a full solution. No matter the level of > upstream maintenance, anonymity can never be guaranteed. > > So, I think it's okay to add the package with a big warning in the > description, maybe even saying something scary like "only recommended > for educational and research activity". Sounds reasonable to me. Chris, what would you like to do with this package? Ludo=E2=80=99.