Re: [Bro-Dev] CBAN naming

> On Jun 4, 2016, at 1:09 PM, Robin Sommer wrote: > > The primary way we've used "plugin" so far is as a compiled, > binary extension. I'm not sure we all have or that the project has used it consistently in that way. It is new enough to Bro I'm not bothered if we shift it

Re: [Bro-Dev] CBAN naming

So are you saying that the "bpm" command wouldn't have a way to show all plugins that were installed via the bpm command? I assumed that is what "bpm list" would show. From: Siwek, Jon Sent: Saturday, June 04, 2016 10:49 AM To: Thayer, Daniel N Cc:

Re: [Bro-Dev] CBAN naming

> On Jun 4, 2016, at 11:27 AM, Slagell, Adam J wrote: > > I still strongly disagree with ALL metadata being optional, unless it is > automatically cleaned up if they never “finish” putting in required data. Sorry, I was just talking about in terms of interoperability w/

Re: [Bro-Dev] CBAN naming

> Sorry, I was just talking about in terms of interoperability w/ the client: > all metadata is optional and doesn’t magically turn a plugin into something > else that can now work with it. > [...] > - it would create another term for what is already named a “plugin”. Having > two words for

Re: [Bro-Dev] CBAN naming

>> 3) CBAN becomes something like “Bro Plugin Manager” because it is dealing >> with plugins, not packages. In fact, “plugin" is probably more descriptive >> about what is going on. In general, a plugin just means any form of >> extending a software’s functionality without having to directly

Re: [Bro-Dev] CBAN naming

> On Jun 3, 2016, at 2:39 PM, Slagell, Adam J wrote: > > So what would you do, call it the tool bro-bpm, the project “Bro Plugin > Manager” (BPM), and the objects being managed plugins? Yeah both the tool and the project are "Bro Plugin Manager” (or some variant of BPM

Re: [Bro-Dev] CBAN naming

> On Jun 3, 2016, at 2:48 PM, Thayer, Daniel N wrote: > > I like this idea better than anything else I've heard so far, but > one small issue is we would need to be a bit careful to distinguish between > "Bro plugins" (as seen by running "bro -N"), and > "Bro plugin

Re: [Bro-Dev] CBAN naming

> On Jun 4, 2016, at 4:27 AM, Jan Grashöfer wrote: > > From my perspective scripts do not extend Bro. Scripts get executed by > Bro to provide extended functionality. Calling Bro-scripts plugins for > Bro is somehow like calling python-scripts plugins for the python >

Re: [Bro-Dev] CBAN naming

> On Jun 4, 2016, at 10:45 AM, Siwek, Jon wrote: > > My last understanding is that we’re starting out w/ metadata being entirely > optional and seeing how it goes. This also makes it more convenient for > people to use the tool to manage plugins they have no intention of