Bower private packages & stats

[rayshan]

Hi Polymer team, I've been wondering about what to do w/ Polymer & its components' stats.

Currently the Bower CLI is collecting the stats: https://twitter.com/rayshan/status/484516581314007040

However all polymer bower packages are marked as private: true, and aren't in the registry. You guys are taking advantage of Bower CLI's github resolver to allow people to install.

The correct behavior for Bower should be to respect package's privacy and not record / display stats. But this will mean you won't see anything Polymer-related on http://bower.io/stats.

Would you like Bower to respect your privacy? Or register everything in the Bower registry? Or should I whitelist everything Polymer related?

cc @robdodson @addyosmani since they asked me about this previously

[robdodson]

Is it possible to whitelist everything that comes from github.com/polymer
and github.com/polymerlabs?

On Thu, Aug 14, 2014 at 4:13 PM, Ray Shan [email protected] wrote:

Hi Polymer team, I've been wondering about what to do w/ Polymer & its
components' stats.

Currently the Bower CLI is collecting the stats:
https://twitter.com/rayshan/status/484516581314007040

However all polymer bower packages are marked as private: true, and
aren't in the registry http://bower.herokuapp.com/packages. You guys
are taking advantage of Bower CLI's github resolver to allow people to
install.

The correct behavior for Bower should be to respect package's privacy and
not record / display stats. But this will mean you won't see anything
Polymer-related on http://bower.io/stats.

Would you like Bower to respect your privacy? Or register everything in
the Bower registry? Or should I whitelist everything Polymer related?

cc @robdodson https://github.com/robdodson @addyosmani
https://github.com/addyosmani since they asked me about this previously

—
Reply to this email directly or view it on GitHub
#711.

[rayshan]

Yes I think we can manage that.

Note that when we have a per-package API & page available for bower packages, Polymer & related packages won't show up. At the minimal I would recommend registering Polymer.

[robdodson]

Hm, are you planning to have individual pages on the bower site that go
into greater details about a package or something?

On Thu, Aug 14, 2014 at 5:20 PM, Ray Shan [email protected] wrote:

Yes I think we can manage that.

Note that when we have a per-package API & page available for bower
packages, Polymer & related packages won't show up. At the minimal I would
recommend registering Polymer.

—
Reply to this email directly or view it on GitHub
#711 (comment).

[rayshan]

Yes, if we expost a per-package API, it would be pretty easy to wire one up. Not too different than npm: https://www.npmjs.org/package/bower

[nevir]

I think part of the trouble is that we probably shouldn't be polluting the Bower namespace with core-*, etc; but we do want components installed into paths based on those names

[nevir]

Re: registering polymer; it is registered, but pointed to the wrong repo.

bower/bower#120 (comment)

[rayshan]

@nevir @azakus polymer is now mapped to git://github.com/Polymer/polymer.git in the bower registry. Sorry for the delay as we're trying to build a more accessible publisher management backend.

I don't see an issue with the core- or whatever namespace. I don't believe we officially support namespacing, but we also don't place strict restrictions on names. What we do need is some sort of anti-squatting policy.

[rayshan]

Polymer packages are no longer blacklisted due to being private. They don't have any github info yet due to lack of mapping, just need to scrape them.