Debian Can Now Amend Social Contract, DFSG

An anonymous reader writes "The Debian Project, creators of the Debian GNU/Linux distribution, has voted to allow amendments to their Social Contract and Free Software Guidelines, as long as the developers agree with a 3:1 majority. The full text of the various amendments can be found in the original call for votes. Debian developer and XFree86 packager Branden Robinson has already proposed an amendment to the Social Contract that removes the requirement to maintain an archive for non-free software or "contrib" software (free software that depends on non-free software to work). Debian could still maintain this archive, but would no longer be required to do so. The proposal also updates the Social Contract to clearly require all works in Debian to meet the Debian Free Software Guidelines, not just software, which had come up repeatedly in the discussions over the non-free "GNU Free Documentation Licence". Both of these updates have been under consideration for some time, but were waiting on the ratification of the amendment procedure. The Debian Project voted on this amendment using their modified Condorcet voting procedure, which allows voters to rank the choices in order of preference, eliminating the "lesser of two evils" effect common to simple majority voting."

Comments

Non-Free Needs Its Own Organization

[Bruce Perens]

Debian is huge. It's long past the point that non-free could support its own organization.

When I created the original Debian Social Contract, non-free wouldn't have been self-supporting. But we've had this hypocracy about non-free since then. Non-free is not officially part of Debian, but is maintained as part of Debian, using all of the same facilities and within the same organization. Debian can now afford to be 100% Free Software and no exceptions, and can put non-free somewhere else with people who care about it. APT will handle this very easily, there's no overhead to the user except perhaps to change /etc/apt/sources.list once, which we can do for them with a script.

Bruce

Re:Non-Free Needs Its Own Organization

[Bruce Perens]

This is how I see it working.

Some time before non-free disappears from Debian's mirrors, we'd make some base package require a package containing an installation script that looks to see if the user is presently using the non-free repository. So, everyone who runs an upgrade would get this package, and it's script would run. If the user is using the non-free repository, the user gets a note that it's moving, and is asked if he'd like to reset his apt choices to the new location of non-free or to do without non-free from then on, in which case we'd present the list of packages that would be lost from the system.

Debian isn't about taking choice s away from people. But that doesn't mean that Debian can't make it's own choices and ask people to find what they want elsewhere.

Bruce

Re:Um.... what?

[Bruce Perens]

I agree. The Debian group would probably use this policy change to remove portions of the section that says

Programs That Don't Meet Our Free-Software Standards
We acknowledge that some of our users require the use of programs that don't conform to the Debian Free Software Guidelines. We have created "contrib" and "non-free" areas in our FTP archive for this software. The software in these directories is not part of the Debian system, although it has been configured for use with Debian. We encourage CD manufacturers to read the licenses of software packages in these directories and determine if they can distribute that software on their CDs. Thus, although non-free software isn't a part of Debian, we support its use, and we provide infrastructure (such as our bug-tracking system and mailing lists) for non-free software packages.

I don't see them using this power to loosen up on their standards for either software or documentation.

Bruce

Re:Seriously...

[Bruce Perens]

If you want to make a contribution, I'd counsel you to work on what excites you the most. If it puts you to sleep, you might be able to do without it and leave it to others.

I have some simple rules for licensing that you can use if you don't want to get in too deep. First, make sure that the copyright holders (that's you and anyone else who contribute) own what they are contributing. They can't have cut and pasted from elsewhere, they have to have written the code.

Then, use the GPL for stuff you do on your free time, and use the BSD license for stuff that someone else pays you for if they don't like the GPL.

The GPL is sharing with rules, the BSD license is a gift with almost no requirements upon the folks who get the code. It makes sense that if you do the work on your own time, people who modify the work should give you the same rights on their changes that you gave them on the original code - and the GPL requires that. But if you get paid to do the code, BSD is fine - because it's not a gift as far as you are concerned.

Thanks

Bruce