Page MenuHomeFreeBSD

security/ca_root_nss: release maintainership

Authored by jbeich on May 24 2015, 10:53 PM.



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
Automatic diff as part of commit; lint not applicable.
Automatic diff as part of commit; unit tests not applicable.

Event Timeline

jbeich updated this revision to Diff 5667.May 24 2015, 10:53 PM
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 accepted this revision.May 24 2015, 11:41 PM
eadler added a reviewer: eadler.
This revision is now accepted and ready to land.May 24 2015, 11:41 PM
eadler added a comment.Jun 6 2015, 3:50 AM

@jbeich is gecko still planning on dropping this port?

delphij added a subscriber: delphij.Oct 3 2015, 1:25 AM

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 added a comment.Oct 3 2015, 9:30 AM

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.