Hi, > > On June 9, 2015 at 1:59 AM Robert Simmons <rsimmo...@gmail.com> wrote: > > > On Mon, Jun 8, 2015 at 7:31 PM, Xin Li <delp...@delphij.net> wrote: > > On 06/08/15 14:37, Robert Simmons wrote: > >> I'm sure that the reason these questions have not been answered is > >> simply because they may have gotten lost in the volume of traffic > >> on freebsd-ports. In the following thread, there are a number of > >> folks with enough passion to volunteer time to help with the Ports > >> Secteam, but we're having difficulty getting a few basic questions > >> answered. > >> https://lists.freebsd.org/pipermail/freebsd-ports/2015-May/099268.html > >> > >> Here are the basic questions: > >> > >> Who are the members of the Ports Secteam? > > > > Current members include the current security officers (who act as a > > fallback when needed and a contact for liaison for sensitive and > > embargoed information) and: > > > > Eitan Adler (eadler@); > > Jason Helfman (jgh@); > > Martin Wilke (miwi@); > > Eygene Ryabinkin (rea@); > > Sofian Brabez (sbz@); > > Simon L. B. Nielsen (simon@, clusteradm@ liaison); > > Steve Wills (swills@); > > Wesley Shields (wxs@); > > Ryan Steinmetz (zi@); > > > >> How does one join the Ports Secteam? > > > > Per previous discussion with portmgr@, members are volunteers selected > > by the Security Officer from active ports committers who have made > > commits in the ports tree in the last 90 days. > > Excellent. Thanks for the quick reply! > > So, if membership requires committership, what is the next best way to > help the team? > _______________________________________________ >
I think that actively sending patches would help in getting in information sooner. A PR with the patch would greatly assist in that. Cheers Remko _______________________________________________ freebsd-security@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-security To unsubscribe, send any mail to "freebsd-security-unsubscr...@freebsd.org"
