When Firms Meet Free Software: How To Avoid Proprietarization? - - PowerPoint PPT Presentation

when firms meet free software how to avoid
SMART_READER_LITE
LIVE PREVIEW

When Firms Meet Free Software: How To Avoid Proprietarization? - - PowerPoint PPT Presentation

When Firms Meet Free Software: How To Avoid Proprietarization? Wednesday July, 10 th 2002 Bordeaux Libre Software Meeting Authors: Speaker: Thierry Pinon Julien Tayon Raphael Rousseau Julien Tayon When Firms Meet Free Software: How To


slide-1
SLIDE 1

When Firms Meet Free Software: How To Avoid Proprietarization?

Wednesday July, 10th 2002 Bordeaux Libre Software Meeting Speaker: Julien Tayon Authors: Thierry Pinon Raphael Rousseau Julien Tayon

slide-2
SLIDE 2

When Firms Meet Free Software: How To Avoid Proprietarization?

This document is under FDL everything being the invariant section http://www.gnu.org/licenses/fdl.txt And the latest corrected revision of this document is availlable on http://www.libroscope.org/

slide-3
SLIDE 3

Sc ch he ed du ul le e

a)When Firms Meet Free Software: How To Avoid Proprietarization? (30 minutes Julien Tayon) Questions & answers (15 minutes) b)a practical case. (15 minutes) c) Practical initiatives:

  • Entrouvert.org (10 minutes)
  • Ynternet.org (10 minutes)
  • Libroscope.org (10 minutes)

d) Conclusion e) free as a talk

slide-4
SLIDE 4

When Firms Meet Free Software: How To Avoid Proprietarization?

Roadmap New threats to Libre Software (LS) community. LS is not only a matter of license. Under-estimated values of LS community. Why, and how to share our knowledge. Can we avoid proprietarization of LS initiatives this way?

slide-5
SLIDE 5

In nt tr ro

  • d

du uc cti ion n

The success of «libre software»(LS)

*BSD/Linux presence on embedded platforms.

2002 GNU/Linux adopted by French and German administrations.

GNU/Linux, BSD, & other LS projects provided by resellers.

slide-6
SLIDE 6

In nt tr ro

  • d

du uc cti ion n

Newcoming threats to «libre software»(LS)

United Linux: an interesting initiative (consistent distribution). But non-collaborative way to build standard (as opposed to RFC).

SourceForge: SourceForge platform once a GPL'ed software is now -at least partially- based proprietary software.

slide-7
SLIDE 7

In nt tr ro

  • d

du uc cti ion n

These organizations have respected the license. The FS community feel betrayed, but cannot point out how. «Free Software»(FS) is not only a matter of license.

slide-8
SLIDE 8

LS S i is s n no

  • t

t on nl ly y a a m ma att tte er r o

  • f

f l lic ce en ns se e

What else is compliant with «Libre Software», while not using LS licenses?

Hactivism «Don't hate the media, become the media»: indymedia.net. Collaborative, decentralized, economicaly independant, peer-reviewed journalism on the Internet.

Ynternet.org: Non Governmental Organizations (NGO) dedicated to North/South cooperation sharing the knowledge relying on LS technologies and methods.

slide-9
SLIDE 9

LS S i is s n no

  • t

t on nl ly y a a m ma att tte er r o

  • f

f l lic ce en ns se e

Conclusion More than words (licenses&code) LS is a question of spirit (values&methods).

slide-10
SLIDE 10

LS S i is s n no

  • t

t on nl ly y a a m ma att tte er r o

  • f

f l lic ce en ns se e

Libre Software is not only liberating software, it is also liberating people. Well known LS practices/values.

Sharing the knowledge (GNU manifesto).

Transparency.

Equal opportunity to contribute.

«The culture of gift» (ESR).

Entrepreneurship & creativity.

slide-11
SLIDE 11

Th he e hi idd dde en n w we ea al lt th h i in n L LS S

How do we make these values respected ?

Equity: open archived mailing lists & netiquette (RFC 1855) = no hidden information.

Culture of gift: peer reviewing, transparency, and reputation.

Entrepreneurship & creativity: «action prevails».

slide-12
SLIDE 12

Th he e hi idd dde en n w we ea al lt th h i in n L LS S

Side effects

Share the knowledge.

Trust mechanisms based on reputation.

slide-13
SLIDE 13

Th he e hi idd dde en n w we ea al lt th h i in n L LS S

Conclusion Our values (side effects) are respected: they are associated to methods.

slide-14
SLIDE 14

LS S i is s n no

  • t

t on nl ly y a a m ma att tte er r o

  • f

f l lic ce en ns se e

Methods are not presented here. This is the subject of Georg Dafermos Conference. Instead we study the interest of our methods .

slide-15
SLIDE 15

Th he e hi idd dde en n w we ea al lt th h i in n L LS S

Libre Software licenses are a necessary element, but not sufficient to do LS.

The use of collaborative methods is another necessary condition. Why would a firm (or any other organization) adopt such methods?

slide-16
SLIDE 16

The e re ea as so

  • n

ns s t to

  • a

ad do

  • p

pt t LS S m me et th ho

  • d

ds s

Who might be interested? Knowledge intensive organizations (Karl E. Sveiby).

66% of GNP in OECD countries come from value-added services (firms).

Most of it is made by very few creative people (SUN).

Looking for new project-management methods.

Efficient information/knowledge propagation is strategic.

The value of trust

slide-17
SLIDE 17

The e r rea as son ns s t to

  • ado
  • p

pt t L LS S m me et th ho

  • d

ds s

What can we share? In which fields is LS community an expert?

Creativity Management (CM).

Collaborative methods.

Information management.

slide-18
SLIDE 18

The e r rea as son ns s t to

  • ado
  • p

pt t L LS S m me et th ho

  • d

ds s

Creativity Management (CM). The tree metaphor: leaves=information/knowledge trees=people who treat/create them. KM=storing and labelling the leaves. Information = valuable leaves. Creative people = valuable trees. CM=making the trees more fertile.

slide-19
SLIDE 19

The e r rea as son ns s t to

  • ado
  • p

pt t L LS S m me et th ho

  • d

ds s

Creativity Management (CM) Rather than new tools, we propose a new strategy:

Organizations don't need additional heavy-weight structures/tools

Organizations have the men & tools, they need a new methods.

slide-20
SLIDE 20

The e r rea as son ns s t to

  • ado
  • p

pt t L LS S m me et th ho

  • d

ds s

Information management Open collaborative networks

Large amount of information handled.

Getting rid of noisy information. Certified informations

One's reputation relies on accurate information.

Peer review. No hidden information

Reputation.

Culture of gift.

slide-21
SLIDE 21

The e r rea as son ns s t to

  • ado
  • p

pt t L LS S m me et th ho

  • d

ds s

Information management Rather than new tools, we propose a new strategy:

Organizations have the information & the people to treat it.

They don't need additional heavy-weight structures/tools.

They just need new methods.

See « Open Source Intelligence » (Felix Stadler & Jesse Hirsh on First Monday)

slide-22
SLIDE 22

The e r rea as son ns s t to

  • ado
  • p

pt t L LS S m me et th ho

  • d

ds s

Participative Strategy

«Action prevails» = equal opportunity.

Peer review.

Trust and reputation.

Involvement, motivation.

slide-23
SLIDE 23

The e r rea as son ns s t to

  • ado
  • p

pt t L LS S m me et th ho

  • d

ds s

The Value of Trust

Arthur Andersen: suspected of mis-acting = lost of a third

  • f their customers.

Enron, Worldcom, Vivendi are losing the trust of the share holders and their monetary value.

Democracy relies on the trust citizens have in their deputies and institutions (WTO, European commissions, NGO).

Glasnost, Free Software for E-Democracy by Emmanuel Raviart.

slide-24
SLIDE 24

The e r rea as son ns s t to

  • ado
  • p

pt t L LS S m me et th ho

  • d

ds s

Our credibility? (Why would any organization listen to us?) It comes from project management

Community is built around projects.

Well-known products

Real Quality Assurance (QA) : both users and producers in contact. (Debian QA)

slide-25
SLIDE 25

The e r rea as son ns s t to

  • ado
  • p

pt t L LS S m me et th ho

  • d

ds s

Our credibility? It comes from project management

Reactivity (security patches)

Large scale projects management/integration (savannah, vhffs 2.0, Linux/BSD distributions)

Focus on results.

slide-26
SLIDE 26

Ex xp pe ec ct te ed d b be en ne ef fi its s

Organizations

No heavy investments in sotware or hardware.

Earning the trust of the stake holders.

Developing involvement through an active community.

slide-27
SLIDE 27

Ex xp pe ec ct te ed d b be en ne ef fi its s

Organizations

Innovation, reactivity.

Improving workers' satisfaction and productivity.

slide-28
SLIDE 28

Ex xp pe ec ct te ed d b be en ne ef fi its s

LS Community

«Sincere» newcomers sharing the same values

More likely to share the knowledge.

Developing the field of expertise of the community (userfriendliness, bier brewing, finance) => new projects will raise.

New allies in our battle (such as software patents)

Respect of LS values especially licenses.

slide-29
SLIDE 29

Ex xp pe ec ct te ed d b be en ne ef fi its s

Everyone

LS methods are incompatible with proprietary methods (making someone dependant from information for example).

Whatever your field is you can use Libre Methods, because it does not only apply to code.

And above all, this is the expression of the culture of gift.

slide-30
SLIDE 30

Av vo

  • i

id di in ng g p pr ro

  • p

pr ri iet ta ar riz za at ti io

  • n

n. .

Spreading our methods. Ensuring the LS values & methods are understood properly. Howto? We have an expertise in sharing knowledge, it should not be difficult to apply our methods to fields other than coding :-)

slide-31
SLIDE 31

When Firms Meet Free Software: How To Avoid Proprietarization?

Roadmap New threats to Libre Software (LS) community. LS is not only a matter of license. Underestimated values of LS community (methods). Why, and how to share our knowledge. Can we avoid proprietarization by sharing our methods?

slide-32
SLIDE 32

Co

  • n

nc cl lu us si io

  • n

ns s

LS is not only a matter of license license. It is a also a matter of values Values are enforced through methods. Our methods are incompatible with proprietarization Avoiding proprietarization = sharing our methods not only in software engeneering.

slide-33
SLIDE 33

Co

  • n

nc cl lu us si io

  • n

ns s

And, this is the very moment to promote/adopt LS methods.

slide-34
SLIDE 34

Co

  • n

nc cl lu us si io

  • n

n

I have not spoken of hybridation yet, did I forgot something? Hybridation=understand the culture of the others and yours to dialog. Else, you cannot share the knowledge. This is the topic covered in the practical case.

slide-35
SLIDE 35

Re ef fer re en nc ce es s

Coming soon on www.libroscope.org

slide-36
SLIDE 36

Co

  • m

mi ing g s so

  • n

n. .. .. .

Questions & answers

Pause

A Practical case: a «Libre methods» cookbook

Conclusion

Pause

Proof by example: newcoming initiatives:

Libroscope

Entrouvert.org

Ynternet.org

Conclusion

slide-37
SLIDE 37

HOW WT TO O s sh ha ar re e th he e me et th ho

  • d

ds s? ?

Let's do a pratical case. A company named Pingot (a car manufacturer) hires a company X, Y, or Z for a mission : they want to improve the efficiency of their accounting department. The webmaster uses linux and pointed Free Software as an innovative solution far away from proprietary methods: they don't want to be heavily dependant of a company.

slide-38
SLIDE 38

HOW WT TO O s sh ha ar re e th he e me et th ho

  • d

ds s? ?

Three companies X, Y, Z visit the office and finds out:

Every workers has developed their own tools in either vbscript or with business object or else for their all day work.

Most of the scripts are buggy,

No one is able to use the code from some one else.

slide-39
SLIDE 39

A A p pr rac ct ti ic ca al l c ca as se

Option 1: Free Software has to be GPL X's diagnostic:

They don' t have the right tools (so to say GPL licensed software, that ensure the 4 freedoms of FS) to be able to share the knowledge.

Code production is not centralized and cannot therefore be maintained because no one knows who does what .

slide-40
SLIDE 40

A A p pr rac ct ti ic ca al l c ca as se

Option 1: Free Software has to be GPL X's solution : It is FS, so it is better than proprietary solution. (4 freedoms of FS)

An intranet using LAMPS (Linux Apache Mysql PHP||Perl||Python SSL) so that code can be centralized and easily maintained, and is OS independant and securely accessed.

Rewrite existing code in PHP.

They propose technical assistance and formations for the accounting department.

slide-41
SLIDE 41

A A p pr rac ct ti ic ca al l c ca as se

Option 1: Free Software has to be GPL Two month laters :

Those peoples' job is accounting, they do not wish to learn PHP.

They cannot improve these tools by themselves

X' s developers have no clue on accounting so they are not efficient.

Workers always complain to the webmaster it does not work (the way they want).

slide-42
SLIDE 42

A A p pr rac ct ti ic ca al l c ca as se

Option 1: Free Software has to be GPL Results one year later: The accounting department chooses to replace X ' s solution with sexy proprietary software they can use.

slide-43
SLIDE 43

A A p pr rac ct ti ic ca al l c ca as se

Option 1: Free Software has to be GPL Explanation

Pingot had no more undersanting of their own tools, and relied heavily on X for both infrastructures and services: X has achieved to do proprietary software with GPLed softwares.

They were not able to build efficient solution since they did not aquire/share the knowledge with Pingot accounting department

slide-44
SLIDE 44

A A p pr rac ct ti ic ca al l c ca as se

Option 2: we do (Free) Software Y's diagnostic :

Free Software is only about technology, what they need are methods for sharing their knowledge.

Free Software has good technologies to offer, but no methods.

slide-45
SLIDE 45

A A p pr rac ct ti ic ca al l c ca as se

Option 2: we do (Free) Software Six month laters :

They have less and less jobs,

Big corporations (IBM, the big 5 4,...) provide Free Software tehnologies and become their direct concurrents. One year later

The company is liquidated.

slide-46
SLIDE 46

A A p pr rac ct ti ic ca al l c ca as se

Option 2: we do (Free) Software Explanation : Y failed to evaluate Free Software assets correctly. They could have sold one of the Free Software most valuable asset: methods.

slide-47
SLIDE 47

A A p pr rac ct ti ic ca al l c ca as se

Option 3: we do Libre Software Z disagnostic :

They have the knowledge of their tools,

But they don' t have the methods to share it.

slide-48
SLIDE 48

A A p pr rac ct ti ic ca al l c ca as se

Option 3: we do Libre Software Z's solution:

Highlighting through pratical code reviewing the benefit

  • f sharing the code.

Setting up a a light CMS (Content Management System).

Coaching people for the use of it in full analogic technology (code reviewing, use of tools, coaching...).

Spot a gifted developer and coach him for animating the dynamics.

slide-49
SLIDE 49

A A p pr rac ct ti ic ca al l c ca as se

Option 3: we do Libre Software Six months later:

Pingot accountants, with the help of knowledge sharing, can focus on accounting.

A new release of their tools is out. For compatibility reasons with their suppliers they have to upgrade. Now their code is to be thrown: they are angry, and are studying the use of LAMPS.

slide-50
SLIDE 50

A A p pr rac ct ti ic ca al l c ca as se

Option 3: we do Libre Software Explanation: They tasted Libre Software methods of sharing, they are now ready to use and adopt it properly. At first LAMPS solution was GPL licensed softwares, now it is «Libre Software».

slide-51
SLIDE 51

Co

  • m

mi ing g s so

  • n

n. .. .. .

Pause

Proof by example: newcoming initiatives:

Libroscope

Entrouvert.org

Ynternet.org

Conclusion

slide-52
SLIDE 52

Pr roo

  • f

f b by y ex xa am mp pl le e

«La propagande par le fait» Newcoming initiatives:

Entrouvert.org

Libroscope.org

Ynternet.org

Conclusion

slide-53
SLIDE 53

Li ibr ros sco

  • p

pe e. .o

  • r

rg g

Structure Goals Methods Contents Conclusion Call for contributions

slide-54
SLIDE 54

Li ibr ros sco

  • p

pe e. .o

  • r

rg g

Structure :

1901 law association

SPIP CMS => libroscope.org

Collaborative ring of writers (3 friends at first).

slide-55
SLIDE 55

Li ibr ros sco

  • p

pe e. .o

  • r

rg g

Structure :

Collaborative project to identify and share experiences (pratical cases).

Developing reflexion on Free Methods.

Sharing references to understand one another.

Presenting the interest of Free Methods through the actuality.

slide-56
SLIDE 56

Li ibr ros sco

  • p

pe e. .o

  • r

rg g

Our values :

Collaborative methods.

Practical cases.

Plurality of contents

Applying to ourselves the methods we promote.

References.

slide-57
SLIDE 57

Li ibr ros sco

  • p

pe e. .o

  • r

rg g

Collaborative methods

Make them test free methods.

We say what we do, we do what we say, and peer review/transparency will ensure it (we apply the methods to ourself).

slide-58
SLIDE 58

Li ibr ros sco

  • p

pe e. .o

  • r

rg g

Practical case

This is an improved business school method for teaching.

They can choose their methods (practical cases do not rely on one best way)

We can seduce with success stories

We can promote LS projects.

slide-59
SLIDE 59

Li ibr ros sco

  • p

pe e. .o

  • r

rg g

The plurality of contents.

Ex: *BSD and Linux equaly representative of LS values but

  • pposed in organizational forms.

We learn more from our mistakes than our success (F. Nietzsche)

slide-60
SLIDE 60

Li ibr ros sco

  • p

pe e. .o

  • r

rg g

The plurality of contents.

Rules and values will emerge more easily from several projects than one.

We don' t want them to focus on cookbooks, but understand HOWTO do it.

slide-61
SLIDE 61

Li ibr ros sco

  • p

pe e. .o

  • r

rg g

The plurality of contents. There is no such thing as one best way, since there is more than one way to do it, so we give them the freedom .... to choose the choice of a GNU generation :)

slide-62
SLIDE 62

Li ibr ros sco

  • p

pe e. .o

  • r

rg g

Samples Reflexions : Is the Linux project an innovative form of organization?

slide-63
SLIDE 63

Li ibr ros sco

  • p

pe e. .o

  • r

rg g

Samples

  • Ynternet.org Free methods apply to fair trade and lasting

development (in 2 weeks)

  • SPIP The success of an easy to use CMS (in 1 month)
  • Tuxfamily.org the other side of shared infrastructure (in 1

month).

slide-64
SLIDE 64

Li ibr ros sco

  • p

pe e. .o

  • r

rg g

The future

English speaking articles.

LS experiences of success/failures in organization.

Increased collaboration with other initiatives.

slide-65
SLIDE 65

Pr roo

  • f

f b by y ex xa am mp pl le e con nc cl lu us sion n

Initiatives :

Today they are already new initiatives coming.

There is a demand for Libre Software methods (IEEE, tools à la savannah...)

This is the very moment for contributing to a Free Method initiative.

slide-66
SLIDE 66

Co

  • n

nc cl lu us si io

  • n

ns s

Proprietarization is a matter of methods «Don't beat the bad drum» : license is not the magic bullet against proprietary software. Our methods might not be the magic bullet either, but the first step to the license. «Don't beat the bad drum (bis)» : United Linux VS United Libre Software because values shared in Open Source and Free Software communities are the same.

slide-67
SLIDE 67

Co

  • n

nc cl lu us si io

  • n

ns s

Peopleware (Tony De Marco)

Companies want to have lasting technologies for sale or use.

New Technologies get outdated while men stay.

  • > Strong interest in adopting Free Software collaborative

methods.

slide-68
SLIDE 68

Co

  • n

nc cl lu us si io

  • n

ns s

La morale de la morale The Free Software community and companies have converging interest today (IP, DMCA...). This is the very moment to promote/adopt Free Software methods. Libre Software may prouve helpful for:

fair trades initiatives

N/S cooperation

Transparency (democracy, companies...). Methods is like software, so to say it is like sex, it' s better ... when it is free and fun.

slide-69
SLIDE 69

Re ef fer re en nc ce es s

Coming soon on www.libroscope.org