> On Aug 5, 2016, at 6:37 PM, Siwek, Jon <jsi...@illinois.edu> wrote: > > >> On Aug 5, 2016, at 1:29 PM, Slagell, Adam J <slag...@illinois.edu> wrote: >> >> If we are going to rely on metadata, which I agree can be better as you can >> tag a package with multiple categories, we should probably have some basic >> requirements for this type of metadata. > > At a minimum, it’s useful to provide a list of “suggested keywords” that > people can choose from when tagging their packages so there’s at least a > common terminology to search within. > > Do you mean to require something more than that? E.g. “packages submitted to > the ‘bro’ package source MUST NOT use keywords outside the pre-approved list” > ? Or “packages submitted to the ‘bro’ package source MUST contain at least > one keyword tag” ? > I was thinking of requiring at least one keyword.
> - Jon _______________________________________________ bro-dev mailing list bro-dev@bro.org http://mailman.icsi.berkeley.edu/mailman/listinfo/bro-dev
