On Fri, Feb 05, 2016 at 06:09:11AM -0500, Matthew Miller wrote: > On Fri, Feb 05, 2016 at 10:03:15AM +0100, Aurelien Bompard wrote: > > Hmm yes I could create the users in Mailman3 even if they never sent an > > email in the new system. But I may have a better idea, here's what I could > > do: > > - get the old emails from Mailman2's mboxes and the new emails from Mailman3 > > - strip the non-text content > > - replace email addresses with hashes to hide them > > - generate mboxes or maildirs > > Since your tool works with mboxes (maybe maildirs?) that would give you > > something you could import and run stats on. Would it work for you? Am I > > missing something security-wise or privacy-wise? > > I can actually _already_ get hyperkitty to give me mbox files, and > those have the original, non-munged email addresses anyway. > > It actually _would_ be useful to have access to non-munged login names > so I can cross-reference mailing list activity with dist-git, bodhi, > etc. > > The problem is that this tool is kind of unwieldy, and it takes a long > time and creates fairly big local database. I was thinking it'd be > easier to just have access to the native, existing database and I can > figure out how to translate any existing sample queries to get the > results I want. (And also, share those queries, because as more people > move to mailman3, they might also want to do the same things without a > separate tool.) Is the tool just a few queries or is it more than this? Basically, I was wondering if it would be interesting to place these stats into HK itself, or as a separate small service (whose access to be restricted to a certain group). This would allow to not give direct access to the DB, offer this tool to other MM3/HK users as well as giving you access to the stats whenever you want/need :) Pierre _______________________________________________ infrastructure mailing list infrastructure@xxxxxxxxxxxxxxxxxxxxxxx http://lists.fedoraproject.org/admin/lists/infrastructure@xxxxxxxxxxxxxxxxxxxxxxx
