[Zeek-Dev] Re: Discussion: the guidance we want to give to package authors on the tags they assign

2020-08-18 Thread Duffy OCraven
../../zeek/bin/zeek -NN | grep -i net output here, showing existing variation, so if there are nuances in points to be discussed, we have actual examples to compare and contrast. [Event] irc_network_info Zeek::Login - Telnet/Rsh/Rlogin analyzers (built-in) [Analyzer] Telnet

[Zeek-Dev] Re: Discussion: the guidance we want to give to package authors on the tags they assign

2020-08-18 Thread Duffy OCraven
Short postscript here, because I just learned there is more than one namespace involved, and that config.name in plugin.cc is probably where zeek -N picks up the string that it utilizes: The code has: namespace plugin { namespace Zeek_BACNET { Plugin plugin; } } using

[Zeek-Dev] Re: Discussion: the guidance we want to give to package authors on the tags they assign

2020-08-18 Thread Duffy OCraven
I'm wondering if we simultaneously want to strongly guide the package name capitalization, where for instance I see in the output of /usr/local/zeek/bin/zeek -N | grep -i net Zeek::Login - Telnet/Rsh/Rlogin analyzers (built-in) Zeek::NetBIOS - NetBIOS analyzer support (built-in) Zeek::BACNET -

[Zeek-Dev] Discussion: the guidance we want to give to package authors on the tags they assign

2020-08-17 Thread Duffy OCraven
I want to start a discussion here of the guidance we want to give to package authors on the tags they assign in zkg.meta, to ensure people have a chance to chime in, and we start-out with the benefit of multi-perspective group process, so we reach for the best result. My proposal is just to