Re: [Bro-Dev] CBAN naming

> On Jun 5, 2016, at 11:51 AM, Slagell, Adam J wrote: > > Regardless, it seems that you and Jon have irreconcilable differences that > eliminate plugin or package. And as the PI and implementer, I give high > weight to both of your opinions. Would either of you object to

Re: [Bro-Dev] CBAN naming

> On Jun 5, 2016, at 10:55 AM, Robin Sommer wrote: > > So what if we stepped back Yes, generally we may need to step back. I think this thread started based on the idea that the names of things are entirely subjective and separate from the technical design. But that’s not

Re: [Bro-Dev] CBAN naming

> On Jun 5, 2016, at 10:55 AM, Robin Sommer wrote: > >> To me, the important part of a the definition of a plugin for most >> software is that it is an externally contributed, self/contained >> add-on which extends functionality. > > Agree in principle, but "extending

Re: [Bro-Dev] CBAN naming

On Sat, Jun 04, 2016 at 20:40 +0200, Jan wrote: > But to me a bundle/package is something different: It's a deployment > unit, acting as some sort of container (usually enriched by metadata). > A plugin/script itself could be used with Bro but wrapping it into the > container allows to manage

Re: [Bro-Dev] CBAN naming

> On Jun 4, 2016, at 1:40 PM, Jan Grashöfer wrote: > > find a new name for the same thing. But to me a bundle/package is > something different: It's a deployment unit, acting as some sort of > container (usually enriched by metadata). A plugin/script itself could > be

Re: [Bro-Dev] CBAN naming

> On Jun 4, 2016, at 1:09 PM, Robin Sommer wrote: > > I really don't like calling these things "plugins", nor calling the > whole thing the "plugin manager". I'm with Jan here: I think that > would be quite misleading in terms of what I believe people associate > with "plugin”