On 10/21/2011 12:11 AM, Greg Hellings wrote: > T. > > On Thu, Oct 20, 2011 at 5:00 PM, thron7<[email protected]> wrote: >> Greg, >> >>> Will the qooxdoo-contrib project be making the same move at some point? >> as I wrote in the weekly, this is open to discussion. But let's assume >> that for a moment, would it really make sense to subsume any number of >> contributions in a single repository on Github? Wouldn't you rather have >> one repo per contrib? Most people I know only use a few of the 80+ >> contribs we have in the repo today. Wouldn't it be easier and more natural >> to check them out, follow them, clone them, and create pull requests for >> them on a one-repo-per-contrib basis? > I think it makes much better sense than the current. Of course, at > present it's so wonderfully easy for me to say > "contrib://mycontrib/trunk/Manifest.json" rather than > "git://mygithosting.com/~blah/Contrib.git" and then specify a path > under that to the Manifest.json file. Not to mention the generator > would need to understand git:// hg:// bzr:// svn:// http:// (and > detect which VCS is under that HTTP location!) and more. So perhaps > it's still better to have the current one-repository-to-rule-them-all > structure. I was just wondering if it was going to move to github or > stay put for now.
Stays put for now. You might want to read the weekly, though, with its comments, there's some looking ahead. T. ------------------------------------------------------------------------------ The demand for IT networking professionals continues to grow, and the demand for specialized networking skills is growing even more rapidly. Take a complimentary Learning@Cisco Self-Assessment and learn about Cisco certifications, training, and career opportunities. http://p.sf.net/sfu/cisco-dev2dev _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
