Re: [Bro-Dev] CBAN naming

[Jan Grashöfer]

>> I like "bro-pkg," though I wonder whether it could be even shortened to
>> "bpkg" or "bkg." 
> 
> It could be, and bpkg is what I original suggest, but I thought you and 
> Justin liked bro-org better.

The point here was that bro-pkg would align to bro-cut. Although I still
like brow, I would prefer bro-pkg or bropkg to bpkg and bkg. While
b(p)kg could be anything bro-pkg is clearly bro-related.

Best regards,
Jan
___
bro-dev mailing list
bro-dev@bro.org
http://mailman.icsi.berkeley.edu/mailman/listinfo/bro-dev

Re: [Bro-Dev] CBAN naming

[Slagell, Adam J]

> On Jun 2, 2016, at 3:37 PM, Matthias Vallentin  wrote:
> 
>> So with that said, I propose bro-pkg, but will leave this open for
>> another day if there are strong opinions.
> 
> I like "bro-pkg," though I wonder whether it could be even shortened to
> "bpkg" or "bkg." 

It could be, and bpkg is what I original suggest, but I thought you and Justin 
liked bro-org better.

--

Adam J. Slagell
Chief Information Security Officer
Director, Cybersecurity Division
National Center for Supercomputing Applications
University of Illinois at Urbana-Champaign
www.slagell.info

"Under the Illinois Freedom of Information Act (FOIA), any written 
communication to or from University employees regarding University business is 
a public record and may be subject to public disclosure." 









___
bro-dev mailing list
bro-dev@bro.org
http://mailman.icsi.berkeley.edu/mailman/listinfo/bro-dev

Re: [Bro-Dev] CBAN naming

[Matthias Vallentin]

> So with that said, I propose bro-pkg, but will leave this open for
> another day if there are strong opinions.

I like "bro-pkg," though I wonder whether it could be even shortened to
"bpkg" or "bkg." This would be the name for the command line client.
How would we call the whole thing? The Bro Package Manager? Or asked
differently, what would be the replacement name for CBAN? Personally, I
think nothing speaks against BPM (even though there exists a bpm-tools
Linux package) since we're not using it as the name for the executable.

Matthias
___
bro-dev mailing list
bro-dev@bro.org
http://mailman.icsi.berkeley.edu/mailman/listinfo/bro-dev

Re: [Bro-Dev] CBAN naming

[Slagell, Adam J]

> On Jun 2, 2016, at 10:56 AM, Siwek, Jon  wrote:
> 
>> 
>> On Jun 1, 2016, at 5:30 PM, Slagell, Adam J  wrote:
>> 
>> These are variants of #1, which I now substitute with bro-pkg
> 
> Related to “pkg” or “package” naming: if that terminology gets used, what 
> would be done about the classic/existing usage of the term “package” within 
> Bro?
> 
> “Package” is currently used to refer to any collection of Bro scripts within 
> a common directory.  Just scripts, nothing else.  Meaning a “package”, as it 
> exists now, isn’t something that the new "package manager” would know how to 
> deal with.
> 
> I don’t think it’s a good idea to let the term be overloaded in the 
> documentation and possibly internal naming conventions in Bro code.  Not that 
> it can’t be changed, but just wondering if it’s already been decided that 
> making those changes would not be a big deal.

It looks like that term is just used here for “Script packages” and on all the 
auto generated subpages. We can just rename that as I don’t it is not a widely 
used term. I do want to do that before 2.5 if we do it, though.

So with that said, I propose bro-pkg, but will leave this open for another day 
if there are strong opinions.

--

Adam J. Slagell
Chief Information Security Officer
Director, Cybersecurity Division
National Center for Supercomputing Applications
University of Illinois at Urbana-Champaign
www.slagell.info

"Under the Illinois Freedom of Information Act (FOIA), any written 
communication to or from University employees regarding University business is 
a public record and may be subject to public disclosure." 









___
bro-dev mailing list
bro-dev@bro.org
http://mailman.icsi.berkeley.edu/mailman/listinfo/bro-dev

Re: [Bro-Dev] CBAN naming

[Slagell, Adam J]

> On Jun 2, 2016, at 10:56 AM, Siwek, Jon  wrote:
> 
> Related to “pkg” or “package” naming: if that terminology gets used, what 
> would be done about the classic/existing usage of the term “package” within 
> Bro?
> 
> “Package” is currently used to refer to any collection of Bro scripts within 
> a common directory.  Just scripts, nothing else.  Meaning a “package”, as it 
> exists now, isn’t something that the new "package manager” would know how to 
> deal with.
> 
> I don’t think it’s a good idea to let the term be overloaded in the 
> documentation and possibly internal naming conventions in Bro code.  Not that 
> it can’t be changed, but just wondering if it’s already been decided that 
> making those changes would not be a big deal.

Good question. Let me look into how hard it would be to change that.

--

Adam J. Slagell
Chief Information Security Officer
Director, Cybersecurity Division
National Center for Supercomputing Applications
University of Illinois at Urbana-Champaign
www.slagell.info

"Under the Illinois Freedom of Information Act (FOIA), any written 
communication to or from University employees regarding University business is 
a public record and may be subject to public disclosure." 









___
bro-dev mailing list
bro-dev@bro.org
http://mailman.icsi.berkeley.edu/mailman/listinfo/bro-dev

Re: [Bro-Dev] CBAN naming

[Siwek, Jon]

> On Jun 1, 2016, at 5:30 PM, Slagell, Adam J  wrote:
> 
> These are variants of #1, which I now substitute with bro-pkg

Related to “pkg” or “package” naming: if that terminology gets used, what would 
be done about the classic/existing usage of the term “package” within Bro?

“Package” is currently used to refer to any collection of Bro scripts within a 
common directory.  Just scripts, nothing else.  Meaning a “package”, as it 
exists now, isn’t something that the new "package manager” would know how to 
deal with.

I don’t think it’s a good idea to let the term be overloaded in the 
documentation and possibly internal naming conventions in Bro code.  Not that 
it can’t be changed, but just wondering if it’s already been decided that 
making those changes would not be a big deal.

- Jon

___
bro-dev mailing list
bro-dev@bro.org
http://mailman.icsi.berkeley.edu/mailman/listinfo/bro-dev