At recommendation of Quim, I've submitted this process 'bug' at http://bugs.meego.com/show_bug.cgi?id=1459 so we can track it better.
Maybe it'd be worth having a category for these kind of bugs/issues in order to help open development around? Regards, Carsten Munk 2010/4/28 Carsten Munk <[email protected]>: > Hi, > > I noticed the following lines in > http://meego.gitorious.org/meego-os-base/kernel-source/blobs/master/README#line120 > : > > * Unless the author identified in the From: tag has a @intel.com or > @linux.intel.com address, the patch must include a Signed-off-by: or > Acked-by: header which identifies the person in one of these domains > who feels responsible for the patch inside the company. > > Would it be possible to reword this in a manner so it does not sounds > as biased towards Intel employees? Ie, treating non-member > contributions with same process and review as member contributions. > > A suggestion could be referring to upstream approval by subsystem > maintainer or by someone responsible for the subsystem/architecture in > the MeeGo kernel maintainer team. > > Regards, > Carsten Munk > maemo.org distmaster > _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
