security/ca_root_nss: release maintainership

[jbeich]

Summary

gecko mainly maintains ports around www/firefox, not everything Mozilla-related that may have some code from there e.g., lang/spidermonkey*. As security/ca_root_nss neither affects www/firefox nor security/nss let's slightly reduce the scope of mostly inactive team.

Bug 189811 demonstrated the port needs an agressive/active maintainer. So, back out rP283208. The only thing to lose is gecko may not be able to sync-update together with security/nss.

[eadler]

@jbeich is gecko still planning on dropping this port?

[delphij]

I think this is a mostly "maintenance mode" port, but have high impact if not handled with care so it's probably a good idea to have ports-secteam@ take over this one with an explicit approval for gecko@ to update it when needed?

[beat]

Sounds reasonable. Let's change the maintainer to ports-secteam@ with explicit approval for gecko@ in case of an update of nss to keep them in sync.