...or at least, not any d-l contributor's fault any more than
anyone who reports RC bugs.
If an RC bug holds up release, it is arguably whoever created the
bug that "fucks up" debian's release, not the
reporter.
That's true whether it's non-free, some other policy violation or
some other grave data loss bug.
Don't shoot the messenger. Fix the bug.
We're not "RMS groupies" (in fact, that's so wrong for me as to be almost funny).
It's not a bloody crusade, either.
It is depressing that some developers have so much contempt for
those who usually knew a bit about copyright beforehand (from journalism,
in my case) and tried to learn enough about the special issues involved
with software to offer what I suspect is probably the biggest
public-archived copyright consultation service.
If some of the contributors are starting to feel under siege,
why not walk through the gates to help reduce the divide?
(Were you going to say "because I've no time and other important work"?
Big news: neither has anyone else, yet there
is still time and priority to fire unhelpful flames towards us?)
If done wrong, licence trouble can be deadly for debian.
Why don't debian-legal people just shut up shop, sod off home
and wait for the next "agressive enough" rights-holder to kill debian?
Because we care about it too, you know.
We want there to be debian releases for a long time to come.
Why don't Fedora and Gentoo have this trouble?
Well, Fedora doesn't make any promise about free software (AFAIK)
and I think Gentoo's promise is inadequate because it only covers a
very small part of the distribution and they reckon including ebuilds
for non-free is fine.
It's very hard to avoid getting non-free software automatically
installed on Gentoo without checking every licence yourself. Not fun.
The MPL hiccough isn't really a surprise and
I'll not be completely surprised to find that either d-l or Mozilla
have something a bit wrong.
The MPL seems a pretty old licence and seems to have avoided much public
scrutiny until now, as I said.
It's going to take some more thinking about.
For Mozilla itself, they've already started dual-licensing,
so it probably won't result in removing that from the distribution,
but there are other MPL-covered works.
Really, I think it's a shame that such a poster-child for OSI has
such a convoluted licence and that it is used by some people
when simpler licences would be better.
The whole sarge release vs social contract deathmatch farce
took me a bit by surprise.
It's the largest single reason why I am quieter in debian than before.
I probably did more work for/with/towards debian in the year before
starting NM (which took nearly a year IIRC) than since.
The FDL crap and the non-free logo are the next two largest,
so I guess you can tell I've been on debian-legal...
I'm amazed by the sheer amount of politicking that goes on and
quite depressed by that.
I am amazed that there are debian developers who claim they don't know what
the word software means, didn't understand or don't agree with what they
agreed to follow (yes, I know some joined pre-SC, but still there are
others) and feel that debian should change to fit their views.
For now,
I'll vote when asked, and likely flame people who screw up stuff I'm
trying to work on (some of which is involved with the MPL posts here),
but generally try to avoid the politicking.
The whole kernel source firmware thing is puzzling and ripping firmware
out of debian sources is one solution, but definitely not the best.
I don't know whether any better is possible, as
I'm not really part of that work.
Blaming "debian-legal" and trying to stop people regarding it as
a bug doesn't seem a solution, though.
If it's not a bug, explain why and close it properly.
Enough people seem to think it is a bug to need some sort of explanation
to avoid getting it rereported and escalated a long way.
If someone has been moving it, presumably a package maintainer,
maybe they think there is a problem too?