I could imagine it working like this : anyone that wants to author a plugin, forks ccrb-plugins, adds their plugin, and does a pull request.
we pull it...done. Jeremy On Sun, Jul 5, 2009 at 6:27 PM, Brian Guthrie <[email protected]> wrote: > Let's keep 'em together for now. If it starts to become ridiculous we > can always split everything up into its own project. > > Brian > > On Sun, Jul 5, 2009 at 2:41 PM, Chad Woolley<[email protected]> > wrote: > > On Sun, Jul 5, 2009 at 12:34 PM, Alexey > > Verkhovsky<[email protected]> wrote: > >> On Sun, Jul 5, 2009 at 1:23 PM, Chad Woolley <[email protected]> > >> wrote: > >>> > >>> Where on github should these live? > >>> > >>> I think that each plugin should be a separate project on the > >>> thoughtworks github account. > >> > >> I think the original motivation to keep it all together was so that it > was > >> easier to discover these things. > > > > Sure, it is fine for them all to stay in one project. I guess there > > are more reasons to keep them together than split them up. > > _______________________________________________ > > Cruisecontrolrb-developers mailing list > > [email protected] > > http://rubyforge.org/mailman/listinfo/cruisecontrolrb-developers > > > _______________________________________________ > Cruisecontrolrb-developers mailing list > [email protected] > http://rubyforge.org/mailman/listinfo/cruisecontrolrb-developers > -- Jeremy Lightsmith Coaching Teams & Creating Communities 312-953-1193 http://onemanswalk.com/ (blog) http://facilitationpatterns.org/ (book in progress) http://www.linkedin.com/in/jeremylightsmith
_______________________________________________ Cruisecontrolrb-developers mailing list [email protected] http://rubyforge.org/mailman/listinfo/cruisecontrolrb-developers
