[Bro-Dev] package manager progress

[Siwek, Jon]

> On Jul 25, 2016, at 6:53 AM, Jan Grashöfer <jan.grashoefer at gmail.com> wrote:
> 
>> * Add a way for package’s to define “discoverability metadata”.
>> 
>> E.g. following the original plan for this would involve putting something like a “tags” field in each package’s pkg.meta file, but the problem with this is the client would need to either download every package to be able to search this data or have a third-party periodically aggregate it.
> 
> I think this is a question about who should deal with the extra effort:
> On the one hand requiring to spread and sync information between two
> places introduces a burden for the contributors

The idea was not for contributors to have to keep syncing the information between two places, the “discoverability” metadata would just be located within the “package source” instead of the package itself.

My thinking is that discoverability metadata should be more of a property of a package source than the package itself — e.g. if a user is looking at discoverability data in a package’s pkg.meta file, it’s not that helpful because they’ve already found the package.

Also, some people may initially have no intention of sharing their package, so there’s no reason to put discoverability metadata in its pkg.meta.  If they later change their mind, and care enough to take the time to register it to a package source, then likely they don’t mind adding a few keywords to a new meta file as an optional part of the one-time registration process.

> One note: I think the documentation should contain a tremendous warning
> pointing out that the users are responsible for what they are
> installing

Thanks for the suggestion, I’ll do that.

- Jon