I strongly encourage folks who want to work on Test::More to fork the project on github and issue pull requests instead of mailing in patches. Why? Github gives me a lovely view of the work going on in the Test::More forks. http://github.com/schwern/test-more/forkqueue
This means I can never drop a patch on the floor, have it get lost in my inbox, or buried in an old ticket. It also means the patches will be easier to keep up to date with trunk changes. The fork queue also features automatic merging and cherry picking making it much easier, and thus much more likely, that I will integrate the patch. Most amazing of all, I can integrate a change before you even submit it! Full squeeing here: http://use.perl.org/~schwern/journal/38478 Don't think of it as "forking the project" in the traditional sense, but rather a branch on steroids, riding a pony and covered in glitter. -- 124. Two drink limit does not mean first and last. -- The 213 Things Skippy Is No Longer Allowed To Do In The U.S. Army http://skippyslist.com/list/
