On 9 Jun 2016, at 13:29, Matthias Vallentin wrote: >> I see benefits in two separate repos: > > Yep. > >> client: bro-pkg >> community packages: bro-pkg-community > > I'm not sure if I understand the -community suffix. The client bro-pkg > makes sense to me. But the first association I have with > bro-pkg-community is a community-version of bro-pkg (i.e., the > client). > How about just "packages?" Forking github.com/bro/packages feels like > a > natural and understandable descriptor.
And to throw another idea in that is in line with this - what about calling the community package repository "packages" like matthias said and the client repository "package-manager"? github.com/bro/package-manager also seems quite clear :) Johanna _______________________________________________ bro-dev mailing list bro-dev@bro.org http://mailman.icsi.berkeley.edu/mailman/listinfo/bro-dev
