On 2010-04-29, 16:06 +0800, Dave Neary wrote: > What people are taking issue with is that (a) being an employee of Intel > is not sufficient to make you a MeeGo kernel maintainer and (b) in > theory, at least, being an employee of Intel is not required to be a > MeeGo kernel maintainer either. > > Thus, requiring a signoff by "someone with an intel.com or > linux.intel.com email address" does not fulfill your reasonable > expectation that a package maintainer sign off on patches.
Hi folks, As Greg have said, the reason that we put @intel.com or @linux.intel.com in the check was fully in terms of tracking purpose, and the intention was to have someone to "blame" and we can push to work when issues raised. :) We have no problem to add others outside of Intel into the MeeGo kernel maintainer team, actually we welcome that, as long as he can take the responsibilities. We've changed the words in README, and checking script will be updated soon. Thanks for the comments. Cheers, Kangkai _______________________________________________ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
