Arjan wrote: > > It's not Intel solely being responsible. > [...] > > Also I don't understand what the beef is.
The problem, as I see it, is that *any* Intel employee can bypass the sign-off procedure for the MeeGo kernel, whereas no-one else can. Intel may have internal processes that prevent that, but it's not something the *MeeGo* project should rely on. I'm fine with a defined group of Intel engineers being the initial gatekeepers of the MeeGo kernel, but an @intel.com email address shouldn't let you bypass those gatekeepers - which is the point that started this thread. Cheers, Andrew -- Andrew Flegg -- mailto:and...@bleb.org | http://www.bleb.org/ Maemo Community Council chair _______________________________________________ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
