On 4 February 2016 at 05:12, Aurelien Bompard <abompard@xxxxxxxxxxxxxxxxx> wrote: > >> > How sensible is the data stored in the DB? Too much to be made public? >> >> Yeah, I wondered the same. Could we sanatize any user auth/account data >> and just make the raw posts of all the public lists available? > > > Hmm, There's the issue of people's email addresses, it could become a gold > mine for spammers. Isn't that data available through other means? Either from posts to the lists, or logging in and seeing who is on the list in mailman2? Or from various other methods. I am bringing this up because we could go through all kinds of hoops here and the barn door has been open for years. > The export could replace those with the UUID that Mailman generates for each > user though, but that won't work for the email that was imported from > Mailman2 (unless the sender sent a mail though Mailman3 later). > > I know HyperKitty's REST API should be improved anyway, though :-) > > >> >> > Otherwise if it's for a one-off we could see to either let one of >> > sysadmin-main run the script or provide a DB dump to one person but I >> > guess this isn't quite sustainable if it's a regular script to run. >> > IIRC, so far I think somone in sysadmin-main ran the script when >> > needed. >> >> We do have a process for database dumps... they have to get 2 +1's from >> sysadmin-main folks and get dumped out by one of them and given to the >> person. So we could do that short term. > > > My understanding is that Matt wants to do this analysis periodically to get > usage statistics and tendencies. > > A. > > _______________________________________________ > infrastructure mailing list > infrastructure@xxxxxxxxxxxxxxxxxxxxxxx > http://lists.fedoraproject.org/admin/lists/infrastructure@xxxxxxxxxxxxxxxxxxxxxxx > -- Stephen J Smoogen. _______________________________________________ infrastructure mailing list infrastructure@xxxxxxxxxxxxxxxxxxxxxxx http://lists.fedoraproject.org/admin/lists/infrastructure@xxxxxxxxxxxxxxxxxxxxxxx
