(replies inline) On Mon, 26 Mar 2018, Daniel Beck wrote:
> > > On 22. Mar 2018, at 22:04, R. Tyler Croy <[email protected]> wrote: > > > > I think we already have some groups, which are almost informal SIGs, such as > > Security, GSoC, Infra, etc. The aspects of SIGs which I really would like to > > formalize, and support from a community infra standpoint are: > > > > * Clear problem domain/focus area. > > ??? > > > > Some SIGs which I would love to see for starters, would be: > > > > * Security, lead by Daniel > > What's the intended relation between existing teams and SIGs? > > I'm asking mostly about security, which is more narrow in scope that what a > potential 'security SIG' would be. > > Would there be a security team with the narrow scope, and a security SIG with > much wider scope? I'm curious why you assume that the security SIG would be broader in scope than the present day CERT? Based on the Kubernetes project's descriptions of SIGs, I think cERT is more or less a SIG already :P Cheers - R. Tyler Croy ------------------------------------------------------ Code: <https://github.com/rtyler> Chatter: <https://twitter.com/agentdero> xmpp: [email protected] % gpg --keyserver keys.gnupg.net --recv-key 1426C7DC3F51E16F ------------------------------------------------------ -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/20180326151341.gywu5lmjltsxcadf%40blackberry.coupleofllamas.com. For more options, visit https://groups.google.com/d/optout.
signature.asc
Description: PGP signature
