> -----Original Message----- > From: meego-dev-boun...@meego.com > [mailto:meego-dev-boun...@meego.com] On Behalf Of Dave Neary > Sent: Thursday, April 29, 2010 4:06 PM > To: Greg KH > Cc: meego-dev > Subject: Re: [MeeGo-dev] Kernel process comment > > So your argument is that the people who are doing the maintainership of > the kernel must sign off on patches to the kernel. That seems perfectly > reasonable. > > 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. > > To be concrete for a second, how many people are we talking about? If > there are 5 or 6 people who can sign off on patches, then list them - > and be done with it. They may all be Intel people to begin with, but > that doesn't prevent someone from Nokia, Novell or an independent from > stepping up to the plate and earning maintainership status (and as you > say, you agree that this *should* be the case, but isn't right now - so > why not set up processes to reflect both what is, *and* what should be?) >
Hi Guys, This is indeed a documentation bug and we will fix it. No Intel employees will bypass the process. All changes, including those from Intel employees, will be scrutinized by MeeGo kernel maintainer team which only consists of a few Intel employees at this moment for the obvious reasons I believe people all understand. We have no problems having people from Nokia and the community joining the team over time and that will certainly be determined based on one's contributions to MeeGo kernel. In addition, I cannot second more Arjan's suggestions on the best way of contributing to MeeGo kernel. People are highly encouraged to submit the patches you want to be part of MeeGo kernel upstream. Thanks -Yong _______________________________________________ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev