|
|
Subscribe / Log in / New account

Shuttleworth: On cadence and collaboration

From:  Mark Shuttleworth <mark-AT-ubuntu.com>
To:  debian-project-AT-lists.debian.org
Subject:  On cadence and collaboration
Date:  Wed, 05 Aug 2009 10:21:38 +0100

Hi folks

I've stayed quiet in this discussion, though several folks have invoked my
name and ascribed motivations to me that were a little upsetting. I'm not
responding to that here, instead I'd like to focus on what we can achieve
together, and how we can lead a very significant improvement in the health
of the whole free software ecosystem.

Apologies in advance if this mail is lengthy and not particularly witty!

Imagine you are the leader of a key upstream component. You care about
your users, you want them to appreciate and love the software you write.
But you also know that most users won't get the code from you - your code
will land in most users hands through one or other distribution - maybe
RHEL, maybe Fedora, maybe Debian or Ubuntu or Gentoo. And you can maintain
a few personal relationships with distribution-space that help to
straighten things out, but more often than not, users will get your code
from a distribution with whom you have little contact. To make things
worse, at any given time, different distributions may be shipping wildly
different versions of your code. That makes all the bug reports harder to
evaluate, and all the patches harder to apply. It also makes it harder to
know where to commit precious resources to stable version maintenance.

I hear this story all the time from upstreams. "We'd like to help
distributions, but WHICH distribution should we pick?" That's a very
difficult proposition for upstreams. They want to help, but they can't.
And they shouldn't have to pick favorites.

Adopting a broad pattern of cadence and collaboration between many
distributions won't be a silver bullet for ALL of those problems, but it
will go a very long way to simplifying the life of both upstreams and
distribution maintainers. If upstream knows, for example, that MANY
distributions will be shipping a particular version of their code and
supporting it for several years (in fact, if they can sit down with those
distributions and make suggestions as to which version would be best!)
then they are more likely to be able to justify doing point releases with
security fixes for that version... which in turn makes it easier for the
security teams and maintainers in the distribution.

We're already seeing a growing trend towards cadence in free software,
which I think is a wonderful move. Here, we are talking about elevating
that to something that the world has never seen in proprietary software
(and never will) - an entire industry collaborating. Collaboration is the
primary tool we have in our battle with proprietary software, we should
take the opportunities that present themselves to make that collaboration
easier and more effective.

OK, so that's the theory. How do we get there? How do we get many
distributions to sit down and explore the opportunities to agree on common
base versions for major releases?

Well, the first thing is to agree on the idea of a predictable cadence.
Although the big threads on this list are a little heartbreaking for me to
watch, I'm glad that there hasn't been a lot of upset at the idea of a
cadence in Debian so much as *which* cadence. We can solve the latter, we
couldn't solve the former. So I'm happy at least at that :-)

The second thing is to find the opportunities that are most likely to be
successful. That depends as much on psychology and practical interaction
as anything else.

As pointed out on this list, Debian and Ubuntu share a great deal. We have
largely common package names (imagine what a difference that will make to
practical discussions over IRC ;-)) and we have established relationships
between folks who care about most of the major components already. We have
lots of people with shared experience in both projects (most of the
strongest Ubuntu contributors are or have been very strong Debian
contributors too, and many new Debian maintainers have come to the project
through Ubuntu). When I look over the commentary on debian-devel and in
debbugs and on #debian-devel, I see a lot of familiar names from Ubuntu,
especially on the deep, hard problems that need solving at the core. I'm
proud of that.

So, practically, we would be in a good position to collaborate.

Psychologically, I don't know so much. Have you ever noticed how family
disputes can be the most bitter? Or how neighboring countries that share
the same food, the same dress, the same values, can often be the bitterest
feuds? Some days I think that applies between us. I see mails on this list
saying it would be easier and better for Debian to coordinate with
distributions that I think would be almost *impossible* to work with
practically, but somehow they are more attractive because they are not
family. Perhaps we know each other too well. It's hard to be a prophet in
your home town.

How do I think it could work in practice? Well, if Debian and Ubuntu went
ahead with the summit in December, where we reviewed plans for 2010 and
identified opportunities to collaborate, I think we would get (a) several
other smaller distributions to participate, and (b) several upstreams to
participate. That would be a big win. It would set us off on a good
course. If we delivered, then, we would virtually guarantee that almost
all the distributions and key upstreams would participate the next time
around. And if *that* worked, we'd win RHEL over too.

A December summit is not about tying anybody's hands. It's about looking
for opportunities, where they exist naturally, and communicating those
more widely. At the moment, if we happen to ship the same version, it's
partly an accident, and upstream doesn't know about it till afterwards.
With an effort made on reviewing and thinking about it, we should get much
better information and communicate much better. Which is a win, right?

So, I'd like to address some of the comments and ideas expressed on this
list recently.

First, there has been no secret cabal or skunkworks effort to influence
Debian. As best I can tell, folks from both Debian and Ubuntu who have
deep insight into release management established a shared interest in
working together better, at many levels, and this was one idea that came
forward. The fact that those discussions were open and ongoing was no
secret - I wouldn't have talked about it in the media if it were!
(Ironically, someone suggested that the fact that I was talking publicly
about something in Debian implied there was a secret cabal. Aiieee.)

I have always tried to make sure that I speak regularly with the DPL -
some DPL's have not responded to that at all, others have been happy to
speak. Steve and I have spoken about every quarter, which is great, and we
focus those conversations on ways we can make collaboration better.
Finding teams we can introduce to one another. Finding ways to communicate
better. This was again, one of the things that came up, as was the idea of
a joint sprint on boot process, which was very successful.

In both cases, the individuals and teams concerned have a mandate from
their organisations to think problems through and speak for the project.
Large organisations can't work any other way. I was stunned when I saw the
announcement of a "decision" because I know that Debian works by building
steady consensus (and by small groups who Just Do It now and then, but
that won't work on something like this). I had expected there would be
more of a proposal for discussion. As far as I can tell, that's what
happened at DebConf, but the announcement afterwards was abrupt. A pity,
because the discussions have been colored by the perception of an imposed
decision, when they needn't have been.

Second, this is not about Debian changing to meet the needs of Ubuntu.

As I've said elsewhere, Ubuntu would be happy to reach a compromise if
needed to work with Debian and others. I think there's agreement on a two
year cadence, and if needed we can change one of our cycles to help bring
multiple distributions into line. Alternatively, with Debian specifically,
we can contribute resources to help Debian meet a stretch (or squeeze ;-))
goal. From my perspective, committing Canonical employees to help Debian
freeze in December, or stretching our one cycle to get us both onto a two
year cadence, are roughly the same. It would be unreasonable to expect us
to do BOTH of those, but I'm happy to work one either basis. Compromise
requires some give from both parties, though.

But most importantly, this whole thing will have it's best and biggest
impact if it goes beyond Ubuntu and Debian. The debate on this list has
mostly been about "Ubuntu vs Debian", which misses the real goal: let's
send a signal to upstreams that they can participate and help shape the
way end users will experience their software. To do that, we need to get
multiple distributions. And looking at it that way, a December summit
gives us a much stronger ability to influence multiple distributions that
are planning releases in 2010. Based on the feedback from the Debian
release team that they liked the idea, I've been reaching out to other
distributions to try to get more of them together. This gets much more
powerful the more of them we bring to the same forum. I'm saddened that
the aggressive tone of this debate has thrown the exercise into question -
I think largely because of unfortunate communications after the
discussions at DebConf. C'est la vie.

Third, I think we need to call on the people who are not fundamentally
prejudiced to speak out.

I see many mails on this list from people who are clearly absolutely
certain in their minds that "Ubuntu is an evil thief of Debian's work". I
don't see any way to change their minds. No matter how many positive
examples of effort made by Ubuntu folks to collaborate we find, they will
always find examples that reinforce their view. If that view dominates the
discussion, we can never improve the situation, because that view says
"don't bother doing anything different, don't look for opportunities to
collaborate, don't make any offer to compromise". How can we achieve
anything from that basis? Debian is made up of hundreds of contributors,
many stay silent. I'm saddened that the loudest voices seem to be those
who are vociferous in their opposition to Ubuntu, rather than those who
are finding ways to make things better. I'm saddened that a good idea - a
sounder basis for collaboration, backed by real investment and effort -
gets crushed on the rocks of hate from folks who do not make the bulk of
the contribution.

It's not hard to tell if someone is expressing an opinion based on
prejudice or one based on openness. Anyone who says, definitively, that a
whole organisation or hundreds of people is "bad", is making a
generalisation that can only be harmful to relationships. I enjoyed Linus
Torvalds' recent interview where he talked about prejudice against
Microsoft in the Linux community, and how poisonous it is. The same is
true of prejudice against Ubuntu here in Debian.

There are very good people, with long histories in Debian, who have
pointed out the positive things that have come from Ubuntu. Listen to
them. Ubuntu is in a great position to help with big and deep changes that
need to be made. Look at the folks who have been instrumental in
discussions around multi-arch, or the move to event-based booting, for
recent examples, and you'll see people who work effectively in both
projects. Neither project can claim credit for all the good work that goes
on, but it would be very wrong to make a sweeping statement that Ubuntu
makes no contribution.

As for my motivations - I love free software and want it to win. If it
wins properly, it will not come in a single package branded "Debian" or
"Ubuntu" or "Red Hat", it will come in a coordinated diversity. I have no
interest in seeing anything bad happen to Debian. Quite the reverse, I've
acted in the ways I thought would carry the greatness of Debian into new
places in the most effective way possible. I'm sorry that some folks have
responded to that as if it were a threat, and sought to create divide and
disharmony. I stayed away from DebConf this year - the first time in six
years - because I didn't want to be a flashpoint for division, when there
are so many positive threads of collaboration under way. I hope this mail
doesn't turn into a magnet for flies and pus. If it suits your brain to
think that I'm an evil capitalist thieving pig, so be it, I doubt there's
anything I could do to change your mind. Paranoia will only get you so
far. But if you're open minded, take the time to look again at what I've
done and said, and ask if it's made a positive difference to Debian and
free software in the last five years, and make your own mind up.

Rather than turning this into a debate on the integrity of individuals or
organisations or projects, let's look at how to make a big improvement in
the free software ecosystem.

In summary (and thank you to anyone who made it this far :-)):

To achieve anything together, we'll both need to work together, we'll need
to make compromises or we'll need to contribute effort to the other side.
If the Debian community is willing to consider a December freeze, then
Ubuntu (and Canonical) will commit resources to help Debian meet that
goal. It means we'll get less done in Ubuntu, but the benefits of having a
schedule which could attract many other distributions would outweigh that.
I think multiple other distributions, who tend to think in financial years
(2010) and plan accordingly, will join a December freeze summit, and there
are significant benefits to Debian to being part of that rather than on a
different schedule.

This is a good faith offer of help and support in order to reach a tough
but noble and achievable goal. It won't be easy, the first time or the
next, but it will kickstart a process that will bring dividends to Debian,
and to the whole broader ecosystem. Ask upstreams what they think, and
whether they would want to participate, and you'll hear a very positive
response.

Mark



to post comments

Shuttleworth: On cadence and collaboration

Posted Aug 5, 2009 15:55 UTC (Wed) by kragil (guest, #34373) [Link] (6 responses)

The elephant in the room is the definition of "freeze".

Debian freezes stable releases in Testing.

Ubuntu freezes from sid and adds a lot of newer alpha/beta/RC software (e.g. Kernel, Gnome, OO.org )

I will give Mark the benefit of the doubt and assume he wants to ship 10.4 with the same version of Gnome as 9.10 .. otherwise this will be a very hard sell for the Debian folks.

As we say in Germany: "The devil is in the details"

Shuttleworth: On cadence and collaboration

Posted Aug 5, 2009 22:15 UTC (Wed) by davi (guest, #18853) [Link] (5 responses)

Mark Shuttleworth (mark @ ubuntu.com) wrote:
"We're already seeing a growing trend towards cadence in free software, which I think is a wonderful move. Here, we are talking about elevating that to something that the world has never seen in proprietary software (and never will). Collaboration is the primary tool we have in our battle with proprietary software, we should take the opportunities that present themselves to make that collaboration easier and more effective."

Ubuntu is only partially free software because it is made of many programs; some are free and some are not. So trying to convince us talking about "our battle with proprietary software" is ...

That guy is an idiot or think we are idiots.

Shuttleworth: On cadence and collaboration

Posted Aug 5, 2009 23:06 UTC (Wed) by epa (subscriber, #39769) [Link] (3 responses)

Not at all. He thinks the best way to win against proprietary software is to get more users running Linux today. If a non-free video card driver is what's needed to persuade people to run Linux instead of Windows or Mac OS, then it would be foolish to push people away from Linux by not offering that option. You don't have to be a purist on the RMS level to support free software.

Shuttleworth: On cadence and collaboration

Posted Aug 6, 2009 18:22 UTC (Thu) by dmarti (subscriber, #11625) [Link]

Sure, you don't have to be a purist, but you do have to be a fairly large scale employer of kernel hackers in order to ship a kernel that's too far away from mainline. AFAIK the only place you can get real support for the full "Nvidiux" is from HP's workstation people.

Offtopic: on distribution of proprietary software

Posted Aug 11, 2009 10:19 UTC (Tue) by pjm (guest, #2080) [Link] (1 responses)

He may think that, though one might also reasonably not think that. It depends in part on what one's goals are. Having more users who are willing to install proprietary drivers will certainly increase the availability of proprietary drivers, but if one's principle aim is to increase the availability of free drivers, then one wants to give a sales advantage to those hardware vendors who do ensure that free drivers are available.

However, I don't see how this is relevant to whether the proposal is good or not.

Offtopic: on distribution of proprietary software

Posted Aug 11, 2009 19:06 UTC (Tue) by dlang (guest, #313) [Link]

it can be argued that allowing the use of proprietary drivers can increase the use of free drivers as well

remember that if someone wouldn't use linux due to the lack of a free driver for some component they aren't going to be using the free drivers for everything else in their system. so allowing for one proprietary driver can cause a dozen free drivers to be used that otherwise wouldn't be used.

Shuttleworth: On cadence and collaboration

Posted Aug 6, 2009 13:10 UTC (Thu) by RainCT (guest, #57473) [Link]

What you are talking about is the "Debian Import Freeze" which is completely unrelated to the whole topic, which is about "Feature Freeze".

Assesment

Posted Aug 5, 2009 16:41 UTC (Wed) by atoponce (guest, #57402) [Link] (15 responses)

I agree generally with what Mark is trying to accomplish. It's clear he wants two things:

1. Single collaboration from all the distributions on a single version of softawre.
2. Ubuntu hatred removed from the Debian project.

Both should be applauded, but the details tell a different story.

First, operating systems package software, apply their branding, patches, etc, and ship it with the distribution. As a result, users shouldn't be going upstream for bugs, as much as they should be going to the distribution. THEN, the package maintainer should take the concerns upstream. After all, he took a specific package version, and should be able to communicate to the developer clearly.

Imagine if every distribution sourced a single upstream version. First, each operating system will package the software (differently, that is- RPM, TAR.GZ, DEB, etc) with their patches that work with their operating system. They'll apply their branding, and such. At this point, it's not the same as upstream. It's already different. So, where do the end users go for support? If they go upstream, it might just be a packaging issue, perhaps a conflict with another package. If they go to the package maintainer, then we're back to square one, where no one benefits from collaboration.

It's a bit short sighted, if you ask me. The concern really shouldn't be about collaborating packages together, but when building packages from upstream, not creating mini-forks, if you will. Keep it pristine. I should be able to take a DEB for Ubuntu, and install it on Debian. I should be able to take apart the DEB, and build an RPM that installs on Fedora, RHEL or even SUSE. Hell, I should be able to make a TAR.GZ, and install on Arch or Slackware.

No, the issue isn't distributions collaborating interdependantly, a noteworthy goal, but the distributions should be applying as little as possible to the packages to make it as close to a specific upstream version as possible. This is where FreeBSD and Arch shine. It's the upstream source, packaged in a tarball, and compiled|installed on the end user's machine.

I look at Ubuntu, and the contributions they've made to GNU/Linux, and it's impressive. However, they've also diverged so much from upstream, that it's difficult to take the Ubuntu packages and install them on a Debian system, or otherwise. It's becoming wholly Ubuntu-dependent. Other distributions shouldn't be following suit, creating distribution-specific patchwork. Other distributions should be working with upstream closely, making sure their software is kept as pristine as possible. Let upstream determine the version that the distribution maintains.

Assesment

Posted Aug 5, 2009 17:38 UTC (Wed) by DOT (subscriber, #58786) [Link]

Not only 'other distributions' should work more closely with upstream, Ubuntu (and Debian, by the way) should do that to. And I think that's implicit in this 'cadence' plan. When you go out of your way to have upstream select a 'best version' for downstream, then you're not going to apply a whole bunch of patches. Any downstream patch will undermine the idea of what Shuttleworth and the Debian folks are trying to accomplish here.

Assesment

Posted Aug 5, 2009 17:45 UTC (Wed) by bfields (subscriber, #19510) [Link] (1 responses)

Imagine if every distribution sourced a single upstream version. First, each operating system will package the software (differently, that is- RPM, TAR.GZ, DEB, etc) with their patches that work with their operating system. They'll apply their branding, and such. At this point, it's not the same as upstream. It's already different. So, where do the end users go for support? If they go upstream, it might just be a packaging issue, perhaps a conflict with another package. If they go to the package maintainer, then we're back to square one, where no one benefits from collaboration.

I think you're trying to make a black-and-white distinction out of something that's actually a continuum. Making packages more similar to upstream may still improve the opportunities for collaboration between distributions even if it doesn't eliminate *every* distro-specific issue.

Sure, you probably can't eliminate distro-specific package maintainers entirely, but you may be able to simplify their job significantly: for example, if they find a bug in their package, and report it upstream, there may be a greater chance that their report matches a report from another distro, and hence that work done on one benefits both.

Assesment

Posted Aug 5, 2009 18:21 UTC (Wed) by tajyrink (subscriber, #2750) [Link]

Indeed, ideally there are no distro-specific patches, and part of every maintainers' job is to reduce the delta. I wouldn't say Fedora version of a typical package is really much different from Debian version. It's a bit different for huge ones like OO.o (with Sun and go-oo...), but still. Every difference from upstream means more maintaining burden for the distro, which is best avoided.

Assesment

Posted Aug 5, 2009 20:32 UTC (Wed) by dmaxwell (guest, #14010) [Link] (2 responses)

I look at Ubuntu, and the contributions they've made to GNU/Linux, and it's impressive. However, they've also diverged so much from upstream, that it's difficult to take the Ubuntu packages and install them on a Debian system, or otherwise. It's becoming wholly Ubuntu-dependent.

Largely true but I'll note a bright spot. The way Debian source packages are handled and installed aren't very different between the two. I won't pin an Ubuntu binary package into a Debian machine or vice versa but I often build source packages from one on the other. For instance, at one point Ubuntu had the most recent release of SpamAssassin but neither Volatile or Backports had it for Stable. So I rebuilt the Ubuntu source packages for it and installed that on my stable machine. It worked a treat. All the config and init files went where they should and it basically Just Worked. Sure I could convert and build say a Fedora package but the chances of it working correctly without a lot of surgery were not good.

This basically is the same process used at backports.org to bring newer stuff to Stable in a sane fashion.

Conversely, I'll sometimes see something tasty in Sid and build it for one of my Ubuntu desktops.

It isn't too awful to do usually:

1. Put a deb-src line from the "foreign distro" into sources.list. Note well "deb-src" ONLY.

2. apt-get build-dep package_of_interest.

The things you need to build the package come from your native distro and this is what will keep what you're building from pulling in uptizillion foreign libs and doing things like replacing your libc. If this fails then you'll need to apt-get build-dep additional-dependency and the apt-get source additional-dependency and build and install it first. I don't bother if this part starts getting ridiculous. Building something from say Jaunty on a Stable that is two years old increases the chance of excessive pain at this point. If your porting from a current Sid to Jaunty as of today then you'll probably have everything you need in your own binary depos.

3. apt-get source package_of_interest
4. cd package_of_interest_source_dir
5. fakeroot dpkg-buildpackage -b

If all goes well an installable port of the package will show up one directory upwards.

Assesment

Posted Aug 6, 2009 14:24 UTC (Thu) by tdwebste (guest, #18154) [Link]

I agree with everyone here, syncing up release dates doesn't do much to improve collaboration between debian and ubuntu. What is need is collaborative bug tracking and package source control.

The Ultimate Debian Database helps show ubuntu/debian package relationships.
http://udd.debian.org/
http://wiki.debian.org/UltimateDebianDatabase

Unfortunately Debian and Ubuntu use incompatible bts systems. Currently Ubuntu's launchpad based bug tracking system _bts_ is lacking accessible package version information. Bug tracking information tied to package version is essential for debian where packages go through many version iterations between releases.

This was part of the original design for Launchpad Bugs, but it never came to fruition. The very earliest bug still open on Launchpad Bugs asks for this:
https://bugs.launchpad.net/malone/+bug/424

Up to and including Hardy, ubuntu used apt-listbugs which referred to debian's bts with package version tracking. Even though this pulled bug information from the debian bts, it gave a reasonable indication of what packages contained significant bugs. apt-listbugs was withdrawn, because ubuntu package customization increasing has made the related debian bts irrelevant.

Topic branches and trees are ways by which package customization can be tracked.

In order to meet the Debian Collaboration Team's objective the launchpad bts must interface with the debian bts. Only this way developers benefit from the topic branches, trees of distributed package source control. To collabate bugs must be tracted across both debian and ubuntu and be accessable to both native debian and ubuntu developers.


Assesment

Posted Aug 6, 2009 21:57 UTC (Thu) by langagemachine (guest, #56890) [Link]

Sorry, did not follow you here (apt newbie inside) :
> The things you need to build the package come from your native distro and this is what will keep what you're building from pulling in uptizillion foreign libs and doing things like replacing your libc.

So, what will happen if the package depends on other libs, in a more recent version than installed on the system ? Will these be fetched from source, then locally installed ?

Assesment

Posted Aug 5, 2009 20:44 UTC (Wed) by jspaleta (subscriber, #50639) [Link] (8 responses)

"Let upstream determine the version that the distribution maintains."

So what does "maintain" mean when you complicate the packagescape with optional mini-repositories like Ubuntu specific PPAs? Aren't those PPA's "maintained?" They may not be official but does that matter to end users who are configuring their system to use PPAs? Doesn't the existence of PPAs break some of the fundamental assumptions here about the benefits of sticking with a specific upstream release. There are a lot of Ubuntu binaries built in launchpad PPAs, no one is talking about versioning-locking the PPA space are they? How many Ubuntu users configure at least one optional Ubuntu PPA for something in order get a newer version of some application? How widespread is the use of PPA binaries on Ubuntu LTS releases?

If Shuttleworth were really serious about the benefits of cross-distro version-locking, then I think he would need to rethink the policy on how PPAs are allowed to be used in the scope of just Ubuntu because they greatly undermine any sort of concept of an upstream preferred version which get priority attention.

-jef

Assesment

Posted Aug 5, 2009 21:25 UTC (Wed) by beuno (guest, #44010) [Link] (2 responses)

People will install random software on their computers no matter where it comes from. Be that getdeb.net, random debs or building from tarballs. This has absolutely nothing to do with the issue at hand. PPAs address (and improves) those use cases, as well as helping developers and cutting-edge users test out new versions to stabilize them.

The majority of users (way above 90%) will never use a PPA, or install newer versions of the software that's available by default or in the official repositories.

This means that whatever gets frozen in the archive is what the vast majority of the users experience, and distribution developers focus their time on those packages. This is what the efforts are geared towards.

PPAs have nothing to do here. You are plain out wrong and sensationalist.

Assesment

Posted Aug 5, 2009 22:19 UTC (Wed) by jspaleta (subscriber, #50639) [Link] (1 responses)

I am sensationalist..that is true. I very much enjoy sensations.. don't you?

90% of all users will never touch a PPA? Is that an emotional shoot from the hip estimate or is that a fact based analysis? I'd rather like to avoid emotional statistics if at all possible. So if you can back that up with some verifiable data analysis, please do so.

I do not question that PPAs serve a useful purpose. Having users out there making use of each and every version released by an upstream developer is a very good thing. One could argue that having as many users as possible testing the newest releases as they become available maximizes the benefit to upstream developers. This is at odds with the stated benefits of cross-distro syncing for "preferred" versions. If every release that upstream developers make needs testing..then every release needs to find its way into the hands of users for widespread testing and feedback. Having distributions stagger what they distribute is one way to see a continuum of release testing.

If all the major distros version lock you are more likely to get boom-bust testing cycles where a lot of bugs go unnoticed across multiple releases instead of a flow of bugs and fixes for each upstream release. The natural feedback loop of the release early release often model is at odds with the concept of preferred version-locking.

Perhaps the reality is the fact that version locking that some distributions feel compelled to do for stability reasons is the underlying problem and not the solution. Since upstream development for many projects moves at a fast clip, the multi-year promise by distributions to keep versioning static retards the natural feedback cycle of release early release often that upstream project development makes use of.

-jef

Assesment

Posted Aug 6, 2009 5:44 UTC (Thu) by dfarning (guest, #24102) [Link]

>I am sensationalist..that is true. I very much enjoy sensations.. don't you?

I guess that depends on ones goals. Do you want to be perceived as a developer who looks at the technical pros and cons of a decision or as a marketer gathering support for your product.

One role requires sensationalism the other does not.

david

Assesment

Posted Aug 7, 2009 14:34 UTC (Fri) by daniels (subscriber, #16193) [Link] (4 responses)

Let's rephrase: 'if Red Hat were serious about RHEL, they'd ban Livna, rpmfind, and people.fp.o from existence'.

In other words, what are you on about?

Assesment

Posted Aug 7, 2009 16:26 UTC (Fri) by jspaleta (subscriber, #50639) [Link] (3 responses)

That's just silly talk. Red Hat doesn't control these other repositories so there is no way Red Hat could be expected to speak for those organizations if Red Hat were to agree to cross-distro version locking.

Canonical most definitely control PPAs as they are part of the Launchpad service running on Canonical funded infrastructure. Canonical could turn off the Ubuntu specific PPAs tomorrow. And of course there are the Canonical's OEM specific partner repositories for Ubuntu pre-installs.
I just want it to be clear as to what Canonical is actually willing to agree to from their end as to how far version locking will go and how big an impact that will have on end-user.

Canonical could easily agree to some sort of cross-distro version locking on core components in main and then break the spirit of that agreement by making use of the PPA infrastructure they control and encouraging users to pull enhanced versions of core components from PPAs or OEM partner repositories they directly control.

But you are right, they don't need to use PPAs to break the spirit of any cross-distro version locking agreement. They could also ship multiple versions of core components in Ubuntu proper like they are planning on doing with the kernel in order to get Android emulation support out to people in Karmic. Would shipping an optional 2.6.29 kernel with Android enhancements be considered a breach of a cross-distro version-locking agreement if everyone agreed to shipping a 2.6.31 version?

-jef

Assesment

Posted Aug 7, 2009 17:42 UTC (Fri) by daniels (subscriber, #16193) [Link] (2 responses)

Sigh. I guess by that logic, OpenSUSE (sorry, Novell -- I forgot about the obsession with the controlling companies) are responsible for everything built with their build service, so they're definitely out. And Red Hat definitely control people.fedoraproject.org, so they're out as well.

As for the rest of the comment, it seems to be your standard 'someone said something about Ubuntu, let's slam them on ten thousand semi-related points and see how often I can use the word Canonical and bring up their financial backing of Ubuntu' spiel. Getting pretty dull now.

You seem to have extrapolated from 'let's get the main distributors to agree on which versions they'll ship as part of their primary releases' to 'anything put on a private package repository is part of the Ubuntu release and Canonical is responsible and this is why it's going to all fall apart'; at least, that's the most coherent summary I could come up with. Words honestly fail me. If you're actually genuinely confused about this and not just coming up with reasons to slam Ubuntu into the ground once again, you might want to check up on what a release actually comprises of. Hint: it's not random stuff on the web that happens to share the same base domain.

Anyway, by the same logic, Rawhide is not allowed to exist. Have fun selling that one.

-daniels, running Fedora on his primary laptop for the time being and Debian on his other machines, not affiliated with either Ubuntu or Canonical, etc, etc

Assesment

Posted Aug 7, 2009 18:33 UTC (Fri) by jspaleta (subscriber, #50639) [Link] (1 responses)

Novell isn't pushing for cross-distro syncing publicly. If they went on record supporting the idea...then yes I would want to know how they viewed the role of their build service in light of any sort of syncing agreement. Because their build service would be just as useful to break the spirit of a 2 year cadence agreement. But thanks for bringing it up. It points to how difficult such a cadence would be to maintain in practise. As Novell derives more revenue from Studio in the future, breaking the spirit of such a syncing agreement with customized Suse remix appliances could essentially nullify some of the stated benefits to upstreams because we'd still see a continuum of versioning in long term deployments. Especially if Novell chooses to support some of those remixes with enterprise level support.

But this isn't Novell's idea...its Shuttleworth's meme. If Canonical doesn't think that PPAs nor OEM repositories that they control would be considered part of the agreement, that should be said as early on as possible to prevent any later re-interpretation.

Let's be clear at the outset as to what the boundaries are for each distributor....no implicit assumptions. It would be far far worse if one of the other distros who decided to work with Shuttleworth on this cried foul about Canonical controlled addon repositories after the agreement was in place.

-jef

Assesment

Posted Aug 8, 2009 8:15 UTC (Sat) by daniels (subscriber, #16193) [Link]

If Canonical doesn't think that PPAs nor OEM repositories that they control would be considered part of the agreement, that should be said as early on as possible to prevent any later re-interpretation.

Why would they? He said part of the release. PPAs are not part of releases. No-one has ever even suggested they are, except for you, who apparently considers Rawhide and people.fedoraproject.org to be a part of RHEL.

A release is defined fairly strictly by virtue of what's in the repositories for that release, which is a finite and well-known set of packages. You're the only one on the planet who seems to think that just because something has the same domain name or is funded by the same people, it's also magically part of the release, which is provably false. This argument is getting incredibly dull.

Shuttleworth: On cadence and collaboration

Posted Aug 6, 2009 8:08 UTC (Thu) by rkklinux (guest, #42417) [Link]

Excellent! I truly support you Mark on your views! In a troubled situation
only positive look and approach will turnaround things for all good! Just
leave behind negatives and one day these negatives will be attracted by all
the good positive things that you are doing. Never worry about such people!
Debian & Ubuntu, I use both of them & I love the best software that is freely
available to run on my system!

Shuttleworth: On cadence and collaboration

Posted Aug 6, 2009 18:22 UTC (Thu) by branden (guest, #7029) [Link] (3 responses)

"Cadence".

Good metaphor.

Very military.

Shuttleworth: On cadence and collaboration

Posted Aug 6, 2009 19:50 UTC (Thu) by Cato (guest, #7643) [Link] (2 responses)

Amazingly enough, you've managed to pick the one possibly negative meaning out of all the options at http://www.google.co.uk/search?q=define%3Acadence

I'm sure this was entirely coincidental ...

Shuttleworth: On cadence and collaboration

Posted Aug 6, 2009 23:31 UTC (Thu) by ofeeley (guest, #36105) [Link]

Heh. When I first read it my cycling background made me assume that it was a delicate euphemism for "spinning madly".

Shuttleworth: On cadence and collaboration

Posted Aug 7, 2009 17:41 UTC (Fri) by branden (guest, #7029) [Link]

What's negative about the military?

Shuttleworth: On cadence and collaboration

Posted Aug 6, 2009 21:52 UTC (Thu) by oak (guest, #2786) [Link] (1 responses)

Any chance that Debian would harmonize with Ubuntu on how to handle debug
packages? It really sucks that Debian doesn't have debug packages for all
the libraries & binaries (on Ubuntu they're built automatically and put to
separate repo similarly to what's done on Red Hat).

Shuttleworth: On cadence and collaboration

Posted Aug 7, 2009 0:28 UTC (Fri) by pabs (subscriber, #43278) [Link]

There is a GSoC student working on that this year.


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