On Thu, Apr 29, 2010 at 2:47 AM, Greg KH <[email protected]> wrote: > I'll throw it back the other way, is there any decision made that all > packages must go through such a process to determine the owner of them?
To my knowledge this is suppose to apart of what the TSG covers, and to my knowledge, the TSG is suppose to be on top of the relative hierarchy. While to my knowledge no decision has been made as to how the MeeGo project designates ownership of things, I don't think there has really been a decision made against it. Which is why we're discussing this in the first place, no? >> Just in case you haven't noticed, MeeGo intends to be an open project, > > "intends" :) > You raise a valid point here. > I'm not disagreeing, just your description seems to not be what is > currently happening. Look at the kernel package, the bugs, and who is > checking what in. Right, my description is not whats currently happening. Which is exactly the reason we are discussing this, right, to try and change this so that other people outside Intel can contribute to the MeeGo kernel, as well as (make/become?) apart of the MeeGo kernel maintainer team. Of course, the whole sentiment is that it doesn't really matter because the general policy is to be working upstream (and/or forking the MeeGo kernel for personal needs). But this would just be yet another thing that seems to be happening under lock and key in regards to the MeeGo project. > good luck, > > greg k-h Cheers, Bradley Smith _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
