On Wed, Apr 28, 2010 at 2:10 PM, Greg KH <[email protected]> wrote: > > I'm saying that Intel is currently the owner of the MeeGo kernel > package, and that if you create a bug in the meego bugzilla against the > kernel package, it gets automatically assigned to an Intel developer. ... > Hopefully in the future there is a way to handle assigning arm-specific > kernel bugs to a Nokia person, but I don't see that happening at the > moment, do you?
Is it the intention of MeeGo to have ownership of packages such as the kernel tied to a particular company or external entity? It seems like it might be much more fruitful to have ownership of MeeGo packages restricted to individuals or to Meego-defined groups of individuals. That way if someone works on, say ARM kernel bugs, they have the opportunity to grow into a position of equal responsibility and power with other ARM kernel devs, regardless of their affiliation with a company or non-MeeGo group. I might be repeating someone else here, but using the example of Intel owning the kernel package, why not create a Meego.kernel group, transfer ownership of the kernel package to it, populate it with all of the Intel people currently authorized to work on the Meego kernel, and then add/remove individuals from that group as appropriate? --R _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
