Page MenuHomeFreeBSD

security/ca_root_nss: release maintainership

Authored by jbeich on May 24 2015, 10:53 PM.
Referenced Files
Unknown Object (File)
Thu, May 2, 10:09 AM
Unknown Object (File)
Sun, Apr 28, 12:49 AM
Unknown Object (File)
Fri, Apr 26, 12:27 PM
Unknown Object (File)
Fri, Apr 26, 12:27 PM
Unknown Object (File)
Fri, Apr 26, 12:27 PM
Unknown Object (File)
Fri, Apr 26, 6:49 AM
Unknown Object (File)
Apr 19 2024, 10:14 AM
Unknown Object (File)
Dec 20 2023, 12:14 AM



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.

Diff Detail

rP FreeBSD ports repository
Lint Not Applicable
Tests Not Applicable

Event Timeline

jbeich retitled this revision from to security/ca_root_nss: release maintainership.
jbeich updated this object.
jbeich edited the test plan for this revision. (Show Details)
jbeich added reviewers: ports secteam, flo.
jbeich added subscribers: gecko, beat.
eadler added a reviewer: eadler.
This revision is now accepted and ready to land.May 24 2015, 11:41 PM

@jbeich is gecko still planning on dropping this port?

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?

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.