I’ve just put the slides of my talk on Debian and Ubuntu online.
Don’t hesitate to post comments to ask for clarifications where needed (it might be difficult to understand some parts of the slides without being in the room).
Clarifications:
- In slide 15, I wrote that Ubuntu had a newer X. During the presentation, I think I said that I wasn’t sure if it was still the case. Indeed, it’s no longer the case (and hasn’t been for a long time ; Ubuntu has been mostly following Debian for X). I apparently remembered a change a long time ago that was picked by Ubuntu from the Debian X svn/git (xlibs-dev removal, I think), and that caused a number of FTBFS in Ubuntu. However, clearly, the best example of such changes made first in Ubuntu are newer GCC versions.
How come that the X-Strike-Force of debian was looking for Contributers and had only one? or two people in it some time(2-4 weeks) ago?
Are there coops build up between the camps in this space?
It isn’t really a good idea to advocate use of testing, until the testing security team starts supporting it again.
I forgot to mention that the Debian installer also suggests installation of proprietary software – mostly firmware blobs. The defaults are to install it too IIRC.
That was a good talk Lucas, I enjoyed the LCA version quite a bit.
@Paul: I think that there are different levels of non-freeness (proprietary firmware vs proprietary X drivers, for example)
You should additional search for bugs reported by people with @ubuntu.com email address to get a better number for bugs filed in Debian by Ubuntu developers.
I am interested in the number of packages that are maintained by Ubuntu developers in Debian and that are synced from Debian to Ubuntu. For example, I maintain 29 packages in Debian. 15 of them are directly synced to Ubuntu.
Hello again Lucas,
I like your slides. I feel sure that Ubuntu, bzr, launchpad didn’t need to be created for Debian / Ubuntu to be the success that it is. Now that the toothpaste is out of the tube, I don’t know what to do.
But you guys who are closer can come up with lots of ways to work better together. It seems one key is to minimize the number of separate teams maintaining the same packages. Documentation can also be shared.
I really like the idea of Debian-testing. I don’t like to upgrade my OS every 6 months and even though I do that, I’m constantly out of date: FF 3.5, etc.
Warm regards,
-Keith