My question with this is, why restrict repositories just to github? There are other hosting repositories out there that people and companies use (Let's just completely overlook the fact that GH is the biggest and most likely won't be going away anytime soon.) Unless there is something specific tied to github then it could be best named as "repo" or "repository" as compared to a github attribute.
-Garbee On Monday, April 8, 2013 3:02:19 PM UTC-4, Eric Bidelman wrote: > > Inspired by Mike K's great idea of self documenting custom elements, I've > written a proposal to formalize the effort. > We have a great opportunity here to come up with best practices early on. > > *Proposal: Self Documenting Custom Elements <http://goo.gl/X5DxO>* > - prototype <http://goo.gl/0pdSW> - a custom element that uses this > method. > - it's <wc-documentation> <http://goo.gl/qzW7P> (best viewed in > Chrome Canary to get ::distributed()). > > [image: Inline image 1] > > Things I like about this approach: > > - The delivery mechanism is <link rel="import">. > - Becomes the "view source of custom elements". Click an import's link -> > get its docs. > - The docs themselves are custom elements > - works reasonably well in other modern browsers, especially if the > toolkit polyfills are included. > > Looking for everyone's feedback. > > Eric Bidelman > Follow Polymer on Google+: plus.google.com/107187849809354688692 --- You received this message because you are subscribed to the Google Groups "Polymer" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/polymer-dev/7a1292e2-8d9f-4a81-916b-16e74d895d35%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
