New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Zeek renaming: bro-pkg #241

Open
jsiwek opened this Issue Jan 11, 2019 · 7 comments

Comments

Projects
None yet
6 participants
@jsiwek
Copy link
Member

jsiwek commented Jan 11, 2019

This is similar to #239, but also requires doing something about the name of project on PyPI. Haven't looked into possibilities for renaming, but I imagine we may have to maintain a duplicate upload under the old bro-pkg name after choosing a new one.

Also open to suggestions on what to name it, zkg seems short/easy and what I'll go with if there's no other strong candidates.

@sethhall

This comment has been minimized.

Copy link
Member

sethhall commented Jan 22, 2019

@0xxon

This comment has been minimized.

Copy link
Member

0xxon commented Jan 22, 2019

I like zkg too - nice and short.

@JonZeolla

This comment has been minimized.

Copy link
Collaborator

JonZeolla commented Jan 22, 2019

+1 to that

@mavam mavam referenced this issue Jan 30, 2019

Merged

Rename Bro to Zeek #396

4 of 4 tasks complete
@thinrope

This comment has been minimized.

Copy link

thinrope commented Feb 4, 2019

There is no (sane) link between zeek and zkg, short does not mean simple always.

What is wrong with zeek as package name? It is generally both user and package maintainer frustration to find "which software are you referring to" by using one name, why add another?
I think, given the new name, all places should use the name zeek and nothing else (except platform specific, e.g. under Gentoo that will (soon!) be net-analyzer/zeek) .

Now, I get it... there is already unrelated pkg with that name https://pypi.org/project/zeek/ coming originally from @kristianperkins https://github.com/kristianperkins/zeek ..
The next best will be zeek-pkg then (and contact ask @kristianperkins for a link in URL? And add one to his project?).

In the same train of thoughts, may be we should ask @jathanism to retract his unrelated bro package from PyPI and github, given that it has no actual release, and code for that matter, for 3 years.

@jsiwek

This comment has been minimized.

Copy link
Member Author

jsiwek commented Feb 4, 2019

@thinrope you're probably confused since this issue is filed in the zeek repo, but it's actually referring to a different package management tool, currently named bro-pkg:

https://github.com/zeek/package-manager

So we obviously can't name both the package manager (bro-pkg) and the network analysis tool (bro, soon to be zeek) to be zeek. The other bro/zeek projects you mention aren't harmful to just let be IMO.

@thinrope

This comment has been minimized.

Copy link

thinrope commented Feb 4, 2019

Oh well, yes indeed, a bit :-D

bro -> zeek and bro-pkg ->zkg makes sense, iff you rename the repo zeek/package-manager to zeek/zkg (and probably this issue must have been in the zeek/package-manager list to begin with)

@kristianperkins

This comment has been minimized.

Copy link

kristianperkins commented Feb 7, 2019

Hi, thanks for @-ting me in. The zeek package I created a long time ago probably doesn't have a lot of usage these days (I personally haven't used zookeeper in years).

I'm not sure what the rules on recycling projects on PyPI are (if there are any) but if the owners of this project are interested in taking over "zeek" on PyPI for this project, that's ok with me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment