To veer off-course a bit, while improving the ease of code contribution is a Good Thing, I'd like to see some additional assurance put in place to help make sure contributed code gets reviewed. I've seen a lot of code rotting in Bugzilla because the author didn't know about the review process, or couldn't get r= when he solicited and gave up, etc., and I'm worried that soliciting new contributions may result in a lot of code going the same way. IMO, we should have some sort of periodic sweep (like BugDay perhaps, but monthly), wherein people hunt through bugs with the "patch" keyword (and attach the keyword, if they hit a bug with an attached patch) and ascertain the status of the patch, try to get review moving on it, &etc. -- Chris Hoess
- Making Contributing Code Easier Gervase Markham
- Re: Making Contributing Code Easier Henri Sivonen
- Re: Making Contributing Code Easier Axel Hecht
- Re: Making Contributing Code Easier Gervase Markham
- Re: Making Contributing Code Easier Neil
- RE: Making Contributing Code Easier Roland . Tepp
- Re: Making Contributing Code Easier Chris Hoess
- Re: Making Contributing Code Easier Fabian Guisset
- Re: Making Contributing Code Easier Mark Anderson
- Re: Making Contributing Code Easier Gervase Markham
- Re: Making Contributing Code Easier Gervase Markham
- Re: Making Contributing Code Easier Chris Hoess
- Re: Making Contributing Code Easier Esben Mose Hansen
- Re: Making Contributing Code Easier Heikki Toivonen
- Re: Making Contributing Code Easier Asa Dotzler
- Re: Making Contributing Code Easier Neil
- Re: Making Contributing Code Easier Gervase Markham
