potential registry and server spec

[jonathanong]

here's my thoughts on a component registry and server. not sure what your current plans are @visionmedia

the main takeaways are:

• separated registry and server
• no pushing releases to a registry like npm - everything is pulled from a source (such as GitHub) or cached locally on a server

i've also included some notes on a potential no-build system. this is really only useful for JS since we rework/autoprefix our CSS anyways. the more i think about it though, the more complicated it gets, but i think it's the direction we'd go when implementing ES6 modules.

(note: i plan to remove everything in implementations.md once we move it out of the spec)

[tj]

I've got a bunch of the registry server related stuff done-ish other than polish and whatnot. I want to facilitate publishing similar to npm but the sugary behaviour of github integration on top for sure

[jonathanong]

Oh didn't know you already had stuff implemented. I'm -1 on an extra publishing step unless it's automatic when you tag a release or something.

How are you making it "more scalable"?

[jonathanong]

Wrote this assuming you haven't started and that I would implement this myself, but that's kind of pointless now since you're almost done. Haha

Still want to do the no-build stuff though

[tj]

yea no worries github people won't have to do anything special, I just don't want to restrict it to github only if we're going to bother with a registry, might as well make it open to everyone :D. just going to have a series of bots that act as the users in that sense, pulling the tars from github and publishing on their behalf, so it won't really be baked into the registry