Manifest Solution

[krisbulman]

After talking with @ericam at CSS Dev Conf, I was pointed to your repo, nice work! I think this is the right path. @carwin and I have been throwing around this idea as a side project and had a few iterations of a Sass registry (first with a sinatra+json solution like Bower, then with a github based registry solution), but I think it might be a good idea to join forces with some other like minded people and generate some discussion around the best approach going forward.

The idea that seems to make the most sense is that of a manifest describing the component, dependencies, etc. and a command-line util as the workhorse for registry search, installing, and version management. Building any sort of form based solution seems to be a bit overkill to me and catering to the wrong crowd, at least initially.

The original inspiration I had for a similar util came out of a post Anthony Short made around package management and Sass and components, which is why I also think this is the right approach as it builds on concepts popular package managers have already established (Bower, Component, etc).

http://anthonyshort.me/2012/10/using-bower-with-sass-and-compass
http://anthonyshort.me/2012/12/building-projects-with-component (Component, but related)

And there is a lot of great inspiration to be drawn from Fonzie, a npm command line package builder & accompanying registry. Not necessarily referring to the npm implementation, but some of the existing functionality and ideas could be really useful in a solid ruby command-line util.

https://github.com/fonzie/fonzie
https://github.com/fonzie/server

I like what you're doing here, and I think we could build on this idea if you're interested in discussing it more here.

//cc @jhardy @hatefulcrawdad

[krisbulman]

moved my thoughts over to the official repo, feel free to contact me if you want to organize some work around it.

[jhardy]

@krisbulman awesome man, will be getting in touch soon.

[carwin]

ditto regarding work on this.