Page MenuHomeFreeBSD

security/ca_root_nss: release maintainership
ClosedPublic

Authored by jbeich on May 24 2015, 10:53 PM.
Tags
None
Referenced Files
Unknown Object (File)
Dec 20 2023, 12:14 AM
Unknown Object (File)
Nov 14 2023, 9:52 PM
Unknown Object (File)
Nov 14 2023, 4:51 AM
Unknown Object (File)
Oct 26 2023, 4:47 AM
Unknown Object (File)
Aug 10 2023, 6:37 PM
Unknown Object (File)
Aug 10 2023, 4:06 PM
Unknown Object (File)
Jul 26 2023, 7:33 AM
Unknown Object (File)
Jul 26 2023, 7:15 AM
Subscribers

Details

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.

Diff Detail

Repository
rP FreeBSD ports repository
Lint
No Lint Coverage
Unit
No Test Coverage

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.