I'll ask forgiveness in advance if this is a stupid observation-- I've not worked on many project like this:
On Mon, Feb 3, 2014 at 7:58 AM, Schaufler, Casey <[email protected]>wrote: > Put the burden of getting a review on the developer. Is that really what you want to do, if you're having a hard time finding enough developers? It's already a pretty arcane system (at least, to me!)--maybe not to someone using it every day... To me, a reviewer risks a bit of their reputation every time they +1 a change; it's not clear to me what the benefit to them (the reviewer) might be? Ultimately, the maintainer is one person whos interests align with getting (good) changes checked in but probably more people than that are required. Paul Paul Hanchett ------------------- Infotainment Engineer MSX on behalf of Jaguar Land Rover One World Trade Center, 121 Southwest Salmon Street, 11th Floor, Portland, Oregon, 97204 Email: [email protected] ------------------- Business Details: Jaguar Land Rover Limited Registered Office: Abbey Road, Whitley, Coventry CV3 4LF Registered in England No: 1672070
_______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
