Just making sure this doesn't get forgotten about.

I think the only good way to do this is to hand off notifications of changes to a notification server. Everything else is going to be slow because we're going to have to query FAS to decide if a person is active or not.

Since we don't know when that will be available, I think what we'll need to do short term is have a cron job that queries fas for status information and then sets acls that are approved to a new status, "inactive".

That will solve acls but it won't solve ownership. Hopefully, though, FESCo will give a clear mandate on what to do with package ownership that has lapsed tomorrow.

By kasal in ticket:1316

Shouldn't such pkgdb records be suspended automatically, after several weeks? Or shouldn't the
package-foo-owner@ aliases behave more sanely, so that they skip these?
Actually, it would be nice if pkgdb ACL list showed which of the accounts are disabled, as an overview who has access to the package.

Here's a plan:

• cron job to sync active/inactive information into the pkgdb from FAS. inactive people won't be in the package-owner@fp.o email aliases.
• UI update to either not show inactive accounts or to segregate them at the bottom of the list of acls or similar.

I think this is all fixed now. I see some old aliases that weren't there are now back. cworth for example.