Lucky me, I just picked up git a couple days ago, with the help of the Pragmatic Programmer's Git book.
Thanks for the additional pointers! On Feb 13, 11:48 am, nwhite <[email protected]> wrote: > I'm in the same boat. The key is to get up to speed with git. I have been > avoiding this one for a while now. This weekend I am taking the plunge and > going to wrap my head around it. Some of the developers have put together > some great tutorials on how to get started. > > http://ayurweba.dinamis.com/entry/2008/jul/04/contributing-to-mootools/ > > If your comfortable with svn you might want to look at > this:http://subtlegradient.com/articles/2008/04/22/cloning-a-git-svn-clone > > if you use a mac this is a good place to > start:http://subtlegradient.com/articles/2008/02/21/install_git_leopardhttp://code.google.com/p/git-osx-installer/downloads/list?can=3http://blog.macromates.com/2008/git-bundle/ > > On Fri, Feb 13, 2009 at 2:41 PM, Shawn Van Ittersum <[email protected] > > > > > wrote: > > > Aaron suggests that anyone interested in contributing to Mootools > > development should drop a note here. So here I am. :) > > > I've actually kept using 1.1.1 because of some bugs and performance > > issues introduced in 1.2. But I really want to take advantage of the > > 1.2 stuff, and seeing the forward momentum into 1.3, I'm excited to > > get involved. I'm interested in patching bugs in 1.2 and contributing > > 1.3. > > > I'll start today by re-evaluting my projects in 1.2.1 vs. 1.1.1 and > > checking the bugs I encounter against the Lighthouse tickets. I know > > there was a severe performance degradation in 1.2 in drag-and-drop > > with multiple drop targets, due to a low-level change in how element > > boundaries were checked. I'm eager to see if that's been fixed, and > > if not, that may be my first contribution. :) > > > Please let me know how else I can be of help.
