Sunday, December 17, 2006

Orthodoxy and orthopraxy in open source

I was reading an account of the Mormon pioneers this morning, and specifically the Martin and Willie Handcart companies. The stories are often repeated here in Utah, but most others haven't heard of them.

In a nutshell, they were pioneers making their way to Utah, and started too late to avoid the winter storms. The result was terrible. As Martha Robinson Blackham related in her journal about the crossing of the Platte River:

The waist-deep water "put them into shock. . . . Upon reaching the other side a tremendous storm of snow, hail, and fierce winds hit the company. . . . That night 13 pioneers died from exposure. . . . Deaths came frequently [in the next few days] and the dead were found . . . holding hands, or sitting by the fire, or while eating crusts of bread or when singing hymns.
In Salt Lake City, Brigham Young heard about their plight and quickly called for volunteers to make the several hundred-mile trek to find the handcart companies, declaring:
I will tell you all that your faith, religion, and profession of religion, will never save one soul of you in heaven, unless you carry out just such principles as I am now teaching you. Go and bring in those people now on the plains, and attend strictly to those things which we call temporal, or temporal duties, otherwise your faith will be in vain; the preaching you have heard will be in vain to you,...unless you attend to the things we tell you.
Such is my feeling, as well, in most things, including open source. It's not what you say or believe, but what you do.

Orthopraxy, not orthodoxy. Correct practice, not correct doctrine/thinking.

Without straining the analogy too far (and certainly the stakes are far lower), there's currently a debate raging about attribution licenses and open source. Zack Urlocker has nicely summarized it. I've also written on the topic before.

Some in the open source community, as found on the license-discuss list, believe that open source burdens distribution, and so violates the Open Source Definition. I understand this point, but mostly reject it. I don't believe that attribution burdens distribution any more than the GPL does, and arguably does less so.

(In fact, I'm not a big fan of attribution precisely because it doesn't require enough. I'd prefer a stronger "freedom burden" such as the GPL requires. In other words, the MPL + attribution is far too easy on downstream users of the code. That's why I've long been a GPL advocate.)

Regardless of all this, and back to my original line of reasoning, one thing that bothers me in this debate is all the talk and theorizing I hear from some in the open source community who complain about attribution. Most of them contribute little or no significant code to any particular project, yet they have crowned themselves the arbiters of what open source means. On the other hand, you have corporations and projects that are churning out prodigious amounts of code - code that can be freely used by anyone - and asking for almost nothing in return. Yet these are being branded "pseudo-open source."

By whose definition?

Yes, there is a concern that "open source" can come to be meaningless if we don't hold the term to a set of standards. But my personal feeling is that the "wisdom of crowds" works just fine in separating the wheat from the chaff. And I'm betting that this wisdom would side with attribution right now, because attribution is responsible for a huge amount of exceptional code being channeled into the open source code pool.

These companies and code writers are doing, not just saying. Praxy, not merely doxy.

Which would you rather have?

4 comments:

Christer Edwards said...

While the comparison might be a stretch and, as you say, the stakes are far lower I think you have a very good point.

I advocate Open Source software and Linux just about everywhere I go and the thing that gets me the most is so called "advocates" who don't even use it themselves.

I long ago made the decision that if I was going to support this I was going to do it in action as well. You won't find me using non-oss software. Practice what you preach might be another way to wrap it all up.

Roberto said...

It's an hold story...

"Quia suam uxorem etiam suspiciore vacare vellet" (Caesar's wife may not be suspected).
The expression like Caesar's wife refer to someone who is pure and honest in morals, where he divorced her.
That's our condemn, as "diverse" developers/entepreneurs we must sound honest and pure, to be like that it's not enough..

Taran Rampersad said...

Orthopraxy. I hadn't heard that in a very long time, and it certainly fits Open Source on many different levels.

russ danner said...

Matt,

I was thinking about this blog tonight:

one thing that bothers me in this debate is all the talk and theorizing I hear from some in the open source community who complain about attribution. Most of them contribute little or no significant code to any particular project, yet they have crowned themselves the arbiters of what open source means. On the other hand, you have corporations and projects that are churning out prodigious amounts of code

I was thinking of this comment in particular. Who gets to define open source? As you point out... There are many who don't contribute much to open source beyond opinions; it doesn't seem right to hand the definition of open source over to the sophists.

But does the definition belong to the contributors? As contributors we can put out whatever product / business model we want but the consumers/users ultimately determines the fate.

I guess all I am saying is: the market seems the likely arbiter.

How many people have said they don't care for Sugar's "on-ramp" flavor of open source? Looks to me like their market has spoken and it's open source enough for them.