summaryrefslogtreecommitdiff
path: root/talermerchantdemos/blog/articles/en/ICT-for-prosperity.html
blob: b2ef491691d0303fdf95e7d634a83ff46bd0c117 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
<!--#include virtual="/server/header.html" -->
<!-- Parent-Version: 1.96 -->
<!-- This page is derived from /server/standards/boilerplate.html -->
<!--#set var="TAGS" value="thirdparty" -->
<!--#set var="DISABLE_TOP_ADDENDUM" value="yes" -->
<title>Shaping Collaborative ICT Development and Initiatives for
Global Prosperity - GNU Project - Free Software Foundation</title>
<!--#include virtual="/philosophy/po/ICT-for-prosperity.translist" -->
<!--#include virtual="/server/banner.html" -->
<!--#include virtual="/philosophy/ph-breadcrumb.html" -->
<!--GNUN: OUT-OF-DATE NOTICE-->
<!--#include virtual="/server/top-addendum.html" -->
<div class="article reduced-width">
<h2>Shaping Collaborative ICT Development and Initiatives for Global
Prosperity</h2>

<address class="byline">by Robert J. Chassell</address>

<div class="infobox">
<p>
From a presentation given at the <!-- <br />
<a href="http://www.globalknowledge.org.my/"> broken link, 1apr11 -->
Second Global Knowledge Conference 
in Kuala Lumpur, Malaysia, on 7&nbsp;March&nbsp;2000.
</p>
<!-- <p>
[For a more extended discussion, see my<br />
<a href="http://www.teak.cc/Access-speech.html">
Free Software: Access and Empowerment</a>.
</p> -->
</div>
<hr class="thin" />

<p>
The title of this presentation is &ldquo;Shaping
Collaborative ICT Development and Initiatives for Global
Prosperity&rdquo; and the themes of this conference are
&ldquo;access,&rdquo; &ldquo;empowerment&rdquo; and
&ldquo;governance.&rdquo;
</p>
<p>
What I want to do today is take one specific technology and talk about
the way we have shaped that technology to make it accessible and
empowering, how we have placed it in an economic and institutional
framework that encourages people to work collaboratively, and how to
use the technology for better governance.
</p>
<p>
The technology is software.  The shaping has to do with copyright
licensing terms&mdash;its legal and institutional framework.
</p>
<p>
As a founder of the Free Software Foundation, I have been working for
16 years with the legal and institutional framework in which we use
and develop software.  GNU/Linux, a complete software system, is
the outcome of these efforts.
</p>
<p>
ICT, the information and communications technologies, are
made up of hardware and software components.  I am speaking here only
of software.  However, I hope we can extend our experience from this
to other technologies.
</p>
<p>
When I speak of software, I am speaking both about the programs that
run the computer, that is to say, the operating system, 
and about applications, such as electronic mail and other
communications, spreadsheets, electronic commerce, writing tools,
sending and receiving FAXes, Web site creation, engineering, research,
mathematical computations, modeling, image manipulation, and
networking.
</p>
<p>
Over the last few years, the prices of computer and telecommunications
hardware have dropped to the point that many more people are using
them.  Indeed, our conference organizers estimate that as many as one
out of every thirty people in the world have computer-based, online
telecommunications access.
</p>
<p>
While one out of thirty is still a small portion of the world's
population, this technology is popular, growing, and becoming more
important in our daily lives.  In addition, we expect that 
computer and telecommunications prices will continue to drop for at
least another generation, so many who currently lack resources will
eventually benefit.
</p>
<p>
As with any technology, software can be employed well or badly.
</p>
<p>
At the moment we see both.  On the bad side, we see machines that
crash unnecessarily, email messages that waste their recipients money,
systems that are vulnerable to simple viruses, and programs that do
only part of what you want.
</p>
<p>
The key to good use of software is to ensure freedom.  In software,
this leads to collaboration, lower prices, reliability, efficiency,
security, and fewer barriers to entry and use.
</p>
<p>
For a good use of software technology, people must have the legal
right to copy, study, modify, and redistribute it.  All else flows
from this.
</p>
<p>
GNU/Linux software gives people these rights.  Programmers benefit,
and more importantly, people who are not programmers benefit.
</p>
<p>
For example, people in an area with lousy or no telephone service can
use a rugged package called UUCP for communications.  I recently read of
an Oxfam group that did this.
</p>
<p>
People with older machines, even with the very old 80386 chips, can
run efficient programs that do as much as programs that require a
modern Pentium chip and expensive memory.  And they can use these
machines as servers for Web pages and as routers&mdash;for
communications' infrastructure.
</p>
<p>
People with just one computer can attach one or two additional
terminals to it, and provide two or three seats in place of one, for
very little extra cost.  I have done this:  a friend visited and we
both wanted to work on my computer at the same time.  Email, Web
browsing, writing, remote system administration:  we did all these at
the same time.
</p>
<p>
A community group, or business, can set up its own mailing lists or
news groups, private or public.  The groupware is there.  Two or more
people can work on the same document at the same time, even if they
are in different countries.  The last time I did that, I was working
with a fellow on the other side of the Atlantic Ocean.
</p>
<p>
What script do you want to write in?  Hindi, Chinese, Thai?  All these
are possible, and in the same window as English or Cyrillic.
</p>
<p>
Individuals or groups can set up their own Web sites.  A publisher can
typeset his own books.  An accountant can analyze a budget.  Blind
people can listen to text read out loud to them by the computer.
</p>
<p>
You can enjoy choosing among several graphic user interfaces, a fancy
one, another that looks and behaves rather like Microsoft Windows, or
a third, that is simple and practical.
</p>
<p>
Except for the blind person's speech generation, which requires audio
that I never installed in my machine, every application I have just
mentioned runs on my home computer.  And people I know have installed
audio and listen to it.
</p>
<p>
All these applications came on a CD-ROM that was, as it happens, given
me at no charge.  I have also paid for CDs with a different version of
the software&mdash;sometimes it is more convenient just to buy.  And
if you have a fast Internet connection, you can readily download the
software, paying only your connection costs.
</p>
<p>
This wealth of software is available and can be used anywhere in the
world.
</p>
<p>
To return to the question of how this technology was shaped:  the key,
as I said, is freedom, the legal right to copy, study, modify, and
redistribute the software.
</p>
<p>
The specific legal tool we used to create these freedoms and the
resulting benefits is a specially drafted copyright license, the GNU
General Public License.
</p>
<p>
This license gives you more rights than plain copyright does, and more
rights than many other kinds of software license.  In essence, it
forbids you to forbid.  It permits you to do everything else.
</p>
<p>
Let me go through this list of rights:  copy, study, modify, and
redistribute.
</p>

<p>
First, the right to copy.
</p>
<p>
Not many people own a factory that would enable them to copy a car.
Indeed, to copy a car is so difficult that we use a different word, we
speak of &ldquo;manufacturing&rdquo; a car.  And there are not many
car manufacturers in the world.  Far fewer than one in thirty people
own or have ready access to a car factory.
</p>
<p>
But everyone with a computer owns a software factory, a device for
manufacturing software, that is to say, for making new copies.
Because copying software is so easy, we don't use the word
&ldquo;manufacturing&rdquo;; we usually do not even think of it as a
kind of manufacturing, but it is.
</p>
<p>
The right to copy software is the right to use your own means of
production (if you will pardon my use of an expression that has gone
out of fashion).  Millions of people, a few percent of the world's
population, own this means of production.
</p>
<p>
Naturally, there have been efforts to take away your rights to use
your own property as a factory that you own.
</p>

<p>
Second, the right to study.  This right is of little direct interest to
people who are not programmers.  It is like the right of a lawyer to
read legal text books.  Unless you are a lawyer, you probably wish to 
avoid such books.
</p>
<p>
However, this right to study has several implications, both for those
who program and for everyone else.
</p>
<p>
The right to study means that people in places like Mexico, or India,
or Malaysia can study the same code that people in Europe or the
United States use.  It means that these people are not kept from
learning how others succeeded.  
</p>
<p>
Bear in mind that many programmers work under restrictions that forbid
them from seeing others' code.  Rather than sit on the shoulders of
those who went before, which is the best way to see ahead and to
advance, they are thrown into the mud.  The right to study is the
right to look ahead, to advance, by sitting on the shoulders of
giants.
</p>
<p>
Moreover, the right to study means that the software itself must be made
available in a manner that humans can read.  
</p>
<p>
Software comes in two forms, one readable only by computers and the
other readable by people.  The form that a computer can read is what
the computer runs.  This form is called a binary or executable.  The
form that a human can read is called source code.  It is what a human
programmer creates, and is translated by another computer program into
the binary or executable form.
</p>

<p>
The next right, the right to modify, is the right to fix a problem or
enhance a program.  For most people, this means your right or your
organization's right to hire someone to do the job for you, in
much the same way you hire an auto mechanic to fix your car or a
carpenter to extend your home.
</p>
<p>
Modification is helpful.  Application developers cannot think of all
the ways others will use their software.  Developers cannot foresee the
new burdens that will be put on their code.  They cannot anticipate
all the local conditions, whether someone in Malaysia will use a
program first written in Finland.
</p>
<p>
Finally, of these legal rights, comes the right to redistribute.
</p>
<p>
This means that you, who own a computer, a software factory, have the
right to make copies of a program and redistribute it.  You can charge
for these copies, or give them away.  Others may do the same.
</p>
<p>
Of course, several existing, large software manufacturers want to
forbid you from using your own property.  They cannot win in a free
market, so they attack in other ways.  In the United States, for
example, we see newly proposed laws to take away your freedom.
</p>
<p>
The right to redistribute, so long as it is defended and upheld, means
that software is sold in a competitive, free market.  This has several
consequences.  Low price is a consequence.  This helps consumers.
</p>
<p>
But first and foremost, these legal and economic rights lead to
collaboration, one of themes of this conference.
</p>
<p>
This outcome is contrary to many people's expectations.  Few expect
that in a competitive, free market, every producer will become more
collaborative and that there will be no visible or felt competition
among competing businessmen.
</p>
<p>
The more competitive a market, the more cooperation you see.
This apparently counter-intuitive implication is both observed and
inferred.
</p>
<p>
This is because people are not harmed by doing what they want to do.
People like to help their neighbors.
</p>
<p>
Consider a small farmer, one among a million.  My friend George, back
in the United States, is one such.
</p>
<p>
His harvest is so small, that there is nothing he can do to effect the
world price.  His neighbor is in a similar situation.
</p>
<p>
Consequently, if George helps his neighbor, his neighbor benefits, and
George himself loses nothing on the price he receives for his harvest.
</p>
<p>
Since George will not hurt himself, he has every other reason to help
his neighbor.  Not only is George kindly, he also recognizes that when
he helps his neighbor, his neighbor is likely to return the favor.
</p>
<p>
This is what you see in a competitive free market: cooperation.
</p>
<p>
Visible competition indicates that the market is not fully free and
competitive.   Visible competition means that at most you have a
semi-free market.
</p>
<p>
Moreover, and this benefits people who are not programmers, if
software is sold in a free market, competition among vendors will lead
to a lower price.
</p>
<p>
Put another way, the price of software is determined primarily by
legal considerations: by the degree to which customers enjoy freedom.
If customers are forbidden to buy a product except at a high price,
and that prohibition is successfully enforced, the product will be
expensive.  This is what occurs with much proprietary software today.
</p>
<p>
On the other hand, if software is sold in a free market, competition
among vendors will lead to a lower price.
</p>
<p>
Indeed, in some circumstances the cost will be so low that companies
or other organizations will give away CD-ROMs containing the software;
others will make copies for their friends; and yet others will provide
downloads over the Internet at no charge.
</p>
<p>
This means that software itself, a necessary supporting part of a
business or community project, will be both inexpensive and legal.
</p>
<p>
Think of this from the point of view of a small business or community
supported group.  The organization can use restricted-distribution,
proprietary software, and either pay a lot of money it does not have,
or break the law and steal it.
</p>
<p>
On the other hand, free software is inexpensive and legal.  It is more
accessible.  It is also customizable in ways that restricted software
often is not.  This is empowering.
</p>
<p>
We shape the development of this technology, we create collaboration,
through the use of a legal tool, a license, that gives you more rights
than you would have otherwise, that forbids you to forbid, that in
this case, gives you the right to  copy, study, modify, and
redistribute the software.
</p>
<p>
Because of the freedoms associated with it, this software is called
&ldquo;free software.&rdquo;
</p>
<p>
While I am speaking of this phrase, let me clear up a verbal issue
that sometimes confuses English speakers.
</p>
<p>
The low price of free software leads some English speakers to think
that the word &ldquo;free&rdquo; in the phrase &ldquo;free
software&rdquo; means they can obtain it without cost.  This is not
the definition, which is about
<a href="/philosophy/open-source-misses-the-point.html">freedom</a>, but
it is an easy misunderstanding.  After all, I have been talking of
frugal use of resources, software that is inexpensive.
</p>
<p>
The English word &ldquo;free&rdquo; has several meanings.  As a
Mexican friend of mine&mdash;and leader, by the way, of a major free
software project&mdash;once said to me,
</p>
<blockquote><p>
English is broken; it does not distinguish between &ldquo;free
beer&rdquo; and &ldquo;free speech.&rdquo;
</p></blockquote>
<p>
Spanish, on the other hand, distinguishes between &ldquo;gratis&rdquo;
and &ldquo;libre.&rdquo;  Free software is &ldquo;libre&rdquo;
software.
</p>
<p>
Likewise, the language of our hosts, Bahasa Melayu, distinguishes
between &ldquo;pecuma&rdquo; and &ldquo;kebebasa.&rdquo;  Free
software is &ldquo;kebebasa&rdquo; software.
</p>
<p>
Incidentally, Eric Raymond and Bruce Perens invented the phrase
&ldquo;open source&rdquo; a few years ago as a synonym &ldquo;free
software.&rdquo;  They wanted to work around the dislike many
companies have of free markets.  The phrase is popular; Eric and Bruce
succeeded in their purpose.
</p>
<p>
However, I prefer the term &ldquo;free software&rdquo; since it better
conveys the goal of freedom; the proposition that every man and woman,
even a person who lives in a third world country, has the right to do
first rate work, and must not be forbidden from doing so.
</p>
<p>
I mentioned that a business or community can use software that is
inexpensive and legal.
</p>
<p>
Now let me turn to the software industry itself.
</p>
<p>
Because competition in a competitive market forces down the price of
free software, no one enters the software industry to sell software as
such.  Instead, and this is often not understood, a business enters
the industry to make money in other ways.
</p>
<p>
Companies and people in the &ldquo;software industry&rdquo; do not
sell software itself, but services associated with software or
hardware or other solutions.
</p>
<p>
This is what happens in the medical and legal professions.  Both
medical knowledge and law are freely redistributable.  Physicians and
lawyers sell their services to solve problems.
</p>
<p>
What services do I mean?  Most directly, help in using a computer, or,
to take more specific examples, help in setting up a packet radio
network where there is no telephone, or help in creating and nurturing
a warehouse data base.
</p>
<p>
Less directly, and increasingly, hardware companies that sell
telephones or desalinization plants, add software to their products to
make them more attractive to buyers.
</p>
<p>
Incidentally, programmers themselves write software for four main
reasons: first, because they are hired to solve a problem, just as a
lawyer is hired to draw up a contract.  Second, as part of another
project.  Third, because it enhances their reputation.  And fourth,
because they want to.
</p>
<p>
I have spoken about shaping this technology for collaboration.  The
key is freedom, and creating the legal framework that supports
freedom.
</p>
<p>
Now let me talk about initiatives that lead to prosperity.
</p>
<p>
One issue with development is resources, or rather, the lack thereof.
</p>
<p>
As I said earlier, free software reduces barriers to entry, both in
the software industry itself and in other industries and activities.
</p>
<p>
Free software, and the culture and ways people tend to think when they
collaborate, reduces operational costs. 
</p>
<p>
Let me take an example that comes directly from this conference.
First I should tell you that I have correspondents all over the world.
They are not all in rich countries.  They or their supporting
institutions are not always rich.
</p>
<p>
The first messages about this conference that I received took up more
than four and a half times the resources needed to convey the
information.  The messages were sent in a bloated form.
</p>
<p>
Next time you budget for a project, consider paying four and a half
times its cost.  Then consider whether you would fund it.
</p>
<p>
Next time you pay at a restaurant, take out four and a half times the
money&hellip;
</p>
<p>
For me the resource use was not an issue because I don't pay by the
minute for telecommunications, as many do.  But I know that my 
correspondents around the world prefer that I take care in my
communications that I do not waste their money or that of their
supporting institutions.
</p>
<p>
A notable feature of free software is that many applications run well
on older, less capable machines, as I mentioned earlier.  For example,
a couple of months ago I ran a window manager, graphical Web browser,
and an image manipulation program on my sister's old 486 machine.
These worked fine.
</p>
<p>
Text editors, electronic mail, and spreadsheets require even fewer
resources.
</p>
<p>
This frugality means that people can use older equipment that has been
tossed out by first world companies.  Such equipment is inexpensive and
often donated.  The computers need to be transported.  Sometimes
you need to start a local project to refurbish the hardware and load
it with inexpensive, customized, free software.  These machines 
cost the end user less than new machines.
</p>
<p>
At the same time, manufacturers are building modern, low end
computers that do as much as the older ones, and are not too
expensive.
</p>
<p>
There is no need to acquire expensive, new hardware to run your
software.
</p>
<p>
In conclusion&mdash;
</p>
<p>
I was asked to speak on
</p>
<p>
&ldquo;Shaping Collaborative ICT Development and
Initiatives for Global Prosperity&rdquo;
</p>
<p>
Over the past 16 years, I have worked with people who shaped software
through a legal tool that gives you many freedoms: the freedoms to
copy, study, modify, and redistribute the software.
</p>
<p>
This tool shapes software technology to make it more accessible and
more empowering; it encourages people to work collaboratively,
and provides a technology for better governance.
</p>
<p>
This legal tool means that companies in the ICT industry compete not
to sell software itself, but to sell services associated with it, or
to sell hardware, or other solutions.
</p>
<p>
This legal framework means that companies will provide more reliable
and efficient services.
</p>
<p>
Freedom, ensured by a proper license, means that people who use
computers and telecommunications as tools can enter their industry
more easily.
</p>
<p>
It means that all users can reduce their entry and operational costs.
It means that people in poorer countries are not shipping off their
money to a rich country, but are keeping their money in the local
economy.
</p>
<p>
Moreover, as I said above, restricted-distribution software licenses
often force people to choose between violating the law and paying
money they may not have.
</p>
<p>
As a matter of good governance, a country should not force people who
are trying to do a decent job into making such decisions.  Too often
an otherwise law-abiding person who lacks resources will choose to
violate the law.
</p>
<p>
Instead, a country should arrange matters such that acting in a
law abiding manner is without doubt the best action, for legal,
moral, and practical reasons.  People always hope their neighbors
will be law abiding and honest; free software encourages that.
</p>
<p>
Free software empowers people who previously were kept out.
</p>
</div>

</div><!-- for id="content", starts in the include above -->
<!--#include virtual="/server/footer.html" -->
<div id="footer" role="contentinfo">
<div class="unprintable">

<p>Please send general FSF &amp; GNU inquiries to
<a href="mailto:gnu@gnu.org">&lt;gnu@gnu.org&gt;</a>.
There are also <a href="/contact/">other ways to contact</a>
the FSF.  Broken links and other corrections or suggestions can be sent
to <a href="mailto:webmasters@gnu.org">&lt;webmasters@gnu.org&gt;</a>.</p>

<p><!-- TRANSLATORS: Ignore the original text in this paragraph,
        replace it with the translation of these two:

        We work hard and do our best to provide accurate, good quality
        translations.  However, we are not exempt from imperfection.
        Please send your comments and general suggestions in this regard
        to <a href="mailto:web-translators@gnu.org">
        &lt;web-translators@gnu.org&gt;</a>.</p>

        <p>For information on coordinating and contributing translations of
        our web pages, see <a
        href="/server/standards/README.translations.html">Translations
        README</a>. -->
Please see the <a
href="/server/standards/README.translations.html">Translations
README</a> for information on coordinating and contributing translations
of this article.</p>
</div>

<!-- Regarding copyright, in general, standalone pages (as opposed to
     files generated as part of manuals) on the GNU web server should
     be under CC BY-ND 4.0.  Please do NOT change or remove this
     without talking with the webmasters or licensing team first.
     Please make sure the copyright date is consistent with the
     document.  For web pages, it is ok to list just the latest year the
     document was modified, or published.
     
     If you wish to list earlier years, that is ok too.
     Either "2001, 2002, 2003" or "2001-2003" are ok for specifying
     years, as long as each year in the range is in fact a copyrightable
     year, i.e., a year in which the document was published (including
     being publicly visible on the web or in a revision control system).
     
     There is more detail about copyright years in the GNU Maintainers
     Information document, www.gnu.org/prep/maintain. -->

<p>Copyright &copy; 1996-1998, 2021 Free Software Foundation, Inc.</p>

<p>This page is licensed under a <a rel="license"
href="http://creativecommons.org/licenses/by-nd/4.0/">Creative
Commons Attribution-NoDerivatives 4.0 International License</a>.</p>

<!--#include virtual="/server/bottom-notes.html" -->

<p class="unprintable">Updated:
<!-- timestamp start -->
$Date: 2021/09/09 20:25:34 $
<!-- timestamp end -->
</p>
</div>
</div><!-- for class="inner", starts in the banner include -->
</body>
</html>