@stigtsp and @timlegge has discussed a little, I have done a little research but not much change. Hope to contact the CVE folks next week to initiate the process
@sjn – Clarify the purpose of the mailing list. Who may join? What may (not) be discussed? How do we accept new signups? How do we decide if someone must leave? How do we change who gets to decide the above? Communicate this to the Perl NOC folks
@stigtsp – Applications to internal lists are coming in.
@stigtsp puts together draft rules.
@sjn wants to add joining instructions to the charter under the “how to join” heading.
@sjn (or @book, if he can come) – HTTPS/TLS-out-of-the-box project for perl5.42. PSC mentioned @leont may want to lead the project as a CPANSec thing? (need confirmation)
We’ll also need to decide who is our single point of contact to PSC.
can we manage a review of options
if so, add a project under our GitHub
is there grant money to fund something like this?
PSC wants to have suggestions by September
Long term commitment/fail graceful implementation required
Official commitment CPANSec is confirmed.
@BooK takes the project management job, with commitment to complete the whole project by PSC’s deadline
@leont maps out implementation options
Progress reports during bi-weekly meetings
@stigtsp – securing cpanm has slow progress
@miyagawa is onboard
@tux - Test::CVE
docs improvements / illustrations in progress
Upcoming events and deadlines
@sjn – TPRF community representatives meeting Friday May 17th @ 17:30 UTC
