Page MenuHomePhabricator

Inventory of FSdata and Glesys
Closed, ResolvedPublic


We have migrated most of our things over to Banhof and it is now a bit unclear what is left on FSdata and Glesys. This is especially important from an GDPR point of view as we'll likely only have a personuppgiftsbiträdesavtal with Banhof.

We should take an inventory of what is left on them an categorise it as "migrate" or "discard".

Once they are empty we can cancel our contracts (or in the case where it is sponsored us the machine only for dev-work)

Event Timeline

FS Data

From what's in www. B means now redirected at Binero. B - dead B - dead B B - up for grabs B - parked - Loopia redirect to Bahnhof server B - custom search page for Wikipedia B B

Moved to ~old/ to not make it accessible. It seems to be used last June '15 and I don't know if there's anything in there worth backing up.

GDPR aside on FSdata from

"Från den 25 maj 2018 kommer vi följa GDPR. Personuppgiftsbiträdesavtalet är en del av våra allmänna villkor. Personuppgiftsbiträdesavtal för kunder till FS Data AB finns på denna länk: Personuppgiftsbiträdesavtal"

Quick initial dive into GleSYS:

Under glesys1 (donera):

  • phpMyadmin
  • db for

Under glesys2 (wlm):

  • mailman /internal mailing lists (/etc/mailman is a good entrypoint)
  • umepedia
  • styrelsewiki

GleSYS sent a personuppgiftsbiträdesavtal.

Based on the above I'll specify the following as types of personal data.

  • Kontaktinformation
  • Användarnamn och lösenord
  • Kommunikation mellan användare
  • Födelsedatum (i.e. date of birth for the artists)

Left in this task. Make a more complete register of what is on the machines (also part of T194157: Set up maintenance routine for servers and websites) and sort them into "migrate", "discard" (and possibly "keep"). The personuppgiftsbiträdesavtal ensure we don't have to have all of this done before May 25th

As part of this inventory we should set up a task (or workboard column) for tracking the backlog of our IT-maintenance. I've been creating individual tasks for a few but it would be good to tie them together.

I've cleaned up Fsdata's domains a bit. I removed the domains that didn't work or were covered by Loopia. isn't working even though there is a redirect at Loopia. Hopefully it's just a matter of time for it to take affect. Remaining domains on Fsdata are:

  • - redirects to
  • - somehow redirects to, couldn't find anything for on Fsdata
  • [sic] - same as
  • and - still lives on Fsdata