LWN.net Logo

LPC: Fitting into the kernel ecosystem

LPC: Fitting into the kernel ecosystem

Posted Sep 19, 2008 14:46 UTC (Fri) by bboissin (subscriber, #29506)
In reply to: LPC: Fitting into the kernel ecosystem by dowdle
Parent article: LPC: Fitting into the kernel ecosystem

Actually I for example use Ubuntu on my laptop, develop for upstream projects.
Ubuntu is quite a nice distro but I'm not really happy with their relations wrt upstream. In fact for the packages in universe/multiverse, I prefer reporting the bug directly to debian otherwise I'm not sure if it will land in debian or upstream.

I would really prefer if ubuntu did less hacks to "fix" stuff, but instead worked with upstream to find the proper fix. I know it's harder and it takes more time but it benefits more people (and there are less chances for the fix to create a regression).


(Log in to post comments)

LPC: Fitting into the kernel ecosystem

Posted Sep 19, 2008 21:18 UTC (Fri) by rahulsundaram (subscriber, #21946) [Link]

If you are not happy with your distribution's relationship to upstream, you should really express it to them especially if you are a upstream developer yourself. It is really important that distributions get the message that upstream contributions are the key to a healthy ecosystem and play a important part in it. Otherwise switch to a distribution which understands this.

LPC: Fitting into the kernel ecosystem

Posted Sep 19, 2008 23:22 UTC (Fri) by jspaleta (subscriber, #50639) [Link]

Here's a question I have for you. How much of your discomfort over how "fixes" are handled in Ubuntu is there because of previous actions taken by Canonical employees specifically versus Ubuntu community volunteers or for that matter Ubuntu contributors who are employeed to work on Ubuntu packages by other companies.

Are the problems you see systemic in to the entire Ubuntu contributor base. Or are the problems you see associated with only the manhours that Canonical as a corporate entity has direct influence over how they are spent?

If you think the problem is systemic you should see if you can start a discussion inside Ubuntu to look at reforming at the package maintainership model that is being used. A systemic problem could be addressed by adjusting the team concept Ubuntu is using to add more individual accountability. For example teams could grow a specific tasking to just deal with upstream patch submission and sheparding and make a specific individual accountable for that in some way...if that sort of thing isn't there already. I'm thinking some sort of public flogging for failure to push patches upstream... or maybe a form of gladiatorial combat. Lot's of options really.

-jef

Copyright © 2013, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds