Hey Jesse, I'd like to talk about the plugin discovery mechanism that you mentioned. I've been working on setting up a couchdb instance locally, and pulling a bunch of code from npm to come up with a solution for this, including a site front end. I think I recall Fil mentioning that you were in the planning stages for this. Would like to chat more so we can coordinate better, ya dig?
-Mike On Mon, Oct 1, 2012 at 5:29 PM, Jesse <purplecabb...@gmail.com> wrote: > A few reasons for the existing structure : > > - the repo was singular to help users discover plugins > - moving to individual repos would destroy commit histories for > plugins ( so we should minimize the number of times we move them ) > - the repo itself has grown far beyond what was expected, it was meant > to be a 'for now' solution to be re-addressed when we had solidified a > better plugin installation/discovery mechanism ( in progress, but > overdue based on this repo ... ) > > Cheers, > Jesse > @purplecabbage > > On Mon, Oct 1, 2012 at 2:23 PM, Mike Reinstein <reinstein.m...@gmail.com> > wrote: > > @Bryan: I believe each plugin basicallly does have its own repo, and this > > is mirrored in our "official" repo. > > > > @Don: great, thanks for adding your plugin info! > > > > > > > > On Mon, Oct 1, 2012 at 5:19 PM, Bryan Bishop <kanz...@gmail.com> wrote: > > > >> On Mon, Oct 1, 2012 at 3:59 PM, Mike Reinstein < > reinstein.m...@gmail.com > >> >wrote: > >> > >> > - popularity of plugins is unclear because the git stars is for the > >> > whole repo, not individual plugins > >> > > >> > >> Is there any reason each plugin shouldn't have its own separate repo? > >> > >> - Bryan > >> http://heybryan.org/ > >> 1 512 203 0507 > >> > > > > -- > @purplecabbage > risingj.com >
