<sharkcz> puiterwijk: btw do we have a policy for decommissioning the hubs? should they stay up for some time after the EOL of the last release they produced?
<puiterwijk> sharkcz: I think the plan was to grab a database backup, put that on kojipkgs storage, and then just turn everything off.
<puiterwijk> A few days later we can then destroy the data if nobody found any serious issues
<sharkcz> same applies to the arm hub/stuff too ...
<puiterwijk> Yeah
<puiterwijk> That is, unless you see a reason to keep things around for longer?
<sharkcz> I'm thinking about possible legal obligations
<puiterwijk> Right, Well, we are keeping all the data.
<puiterwijk> Just not in an online koji environment
<puiterwijk> (and we keep all the data public as well)
<sharkcz> we might check with the council about it ...
<puiterwijk> How so? But okay, if you think so, that's fine with me..
<sharkcz> there could be edges we don't see, so I would prefer to get more eyes on it
<puiterwijk> Well, do note that I didn't come up with this plan, Kevin did, but as said, sure.
<puiterwijk> I personally think that keeping the dump available and then not maintaining the live koji instances anymore is the responsible way of dealing with it though.
<sharkcz> I don't disagree, looks as sane approach
* nirik isn't here, but I talked to legal and we can turn them off at EOL. ;) But I think we should keep the data around (umounted) until we need the space. 
* smooge stops the rm -rf 
<puiterwijk> My idea was to get an SQL dump and store it on kojipkgs.
<nirik> yep.
<nirik> well, I was thinking on backup01, but whatever.
<puiterwijk> I thought we can just publish the db dumps. That'd allow people who want to get info on our builds to get that info