I noticed that Jockey is on the list of Ubuntu contributions--I didn't know it originated with Canonical. It is a pretty slick system for dealing with binary drivers.
I think the Ubuntu contributions get under-represented because of the practice of tying Launchpad issues to the upstream bug tracker. This makes it easy to submit resolutions directly upstream. That is the way many issues I have followed reach resolution. Ubuntu also works very closely with Debian. Many Ubuntu issues are addressed by submitting new packages into Debian unstable. I suspect that some of the contributions attributed to Debian actually originated with Ubuntu developers. I don't think treating Ubuntu separate from the Debian community it is a part of is exactly fair. Ubuntu has been a force in Debian pushing it to innovate in ways that improve polish and integration for the end user. At first it was a real challenge for Debian to adjust to the Ubuntu contributions, but the last couple of years it seems to happen so smoothly that it goes largely unnoticed. I have no statistics to back me up, but if you want me to I'll go ahead and quote some. Contributions to Linux plumbing are essential, but I don't believe that this is the only metric for determining if a distribution is "parasitic". Richard On Tue 24 November 2009 11:44:40 Andrew McNabb <[email protected]> wrote: > On Tue, Nov 24, 2009 at 09:08:17AM -0700, Robert LeBlanc wrote: > > > > As far as Ubuntu not giving back to the community. I would say this is > > false. Many times looking through Debian's PTS, I see bug reports and > > patches submitted by Ubuntu users. The Ubuntu community also tries to get > > packages in Debian where it fits Debian's model. > > Ubuntu indeed contributes some bug fixes back (which is great). > However, the number of Ubuntu-originated bug fixes is quite small > considering its market share, and the number of big contributions is > negligible. <snip> -------------------- BYU Unix Users Group http://uug.byu.edu/ The opinions expressed in this message are the responsibility of their author. They are not endorsed by BYU, the BYU CS Department or BYU-UUG. ___________________________________________________________________ List Info (unsubscribe here): http://uug.byu.edu/mailman/listinfo/uug-list
