From: Nils Gillmann <ng0@n0.is>
To: Chris Marusich <cmmarusich@gmail.com>
Cc: 31307@debbugs.gnu.org, Nils Gillmann <ng0@n0.is>
Subject: [bug#31307] [PATCH] Add MAT, the Metadata Anonymisation Toolkit from Boum
Date: Wed, 2 May 2018 06:12:24 +0000 [thread overview]
Message-ID: <20180502061224.ob4bjgbbme2jvrfc@abyayala> (raw)
In-Reply-To: <87lgd21trg.fsf@gmail.com>
Chris Marusich transcribed 1.7K bytes:
> Chris Marusich <cmmarusich@gmail.com> writes:
>
> > We'll see what they say!
>
> Upstream has confirmed that the license is GPLv2:
>
> https://mailman.boum.org/pipermail/mat-dev/2018-April/000158.html
>
> They also confirmed the following:
>
> * MAT is not actively maintained and doesn't run under Python 3.
>
> * MAT2 is under development.
>
> * MAT has some known limitations, "like leaving metadata in file
> embedded in PDF, like images."
>
> That said, even upstream said that we should go with MAT, since there is
> no known better alternative, and later we can switch to MAT2. I think
> we should add it, without worrying about making the GUI work, and we
> should add these warnings to the package description.
>
> Thoughts?
Okay for me.
> --
> Chris
next prev parent reply other threads:[~2018-05-02 6:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-28 21:38 [bug#31307] [PATCH] Add MAT, the Metadata Anonymisation Toolkit from Boum Chris Marusich
2018-04-28 22:11 ` Nils Gillmann
2018-04-29 3:09 ` Chris Marusich
2018-04-29 8:18 ` Chris Marusich
2018-05-02 6:00 ` Chris Marusich
2018-05-02 6:12 ` Nils Gillmann [this message]
2018-05-05 20:33 ` Ludovic Courtès
2018-05-05 21:37 ` Chris Marusich
2018-05-06 19:26 ` Leo Famulari
2018-05-06 19:44 ` Leo Famulari
2018-06-15 7:06 ` Ludovic Courtès
2018-07-05 8:29 ` Chris Marusich
2018-06-16 13:42 ` Nils Gillmann
2021-09-13 2:26 ` Sarah Morgensen
2021-11-08 1:34 ` [bug#31307] [PATCH] Add MAT, the Metadata Anonymisation Toolkit Denis 'GNUtoo' Carikli
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180502061224.ob4bjgbbme2jvrfc@abyayala \
--to=ng0@n0.is \
--cc=31307@debbugs.gnu.org \
--cc=cmmarusich@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).