F. Questier, FOSS - Free and Open Source Software Workshop, 2015-2017

1. FOSS
Free & Open Source software
Prof. dr. Frederik Questier - Vrije Universiteit Brussel
Presented at:
Moi University, Kenya, 02/2015
Jimma University, Ethiopia, 06/2015
Arba Minch University, Ethiopia, 03/2017
Bahir Dar University, Ethiopia, 04/2017

2. This presentation can be found at
http://questier.com
http://www.slideshare.net/Frederik_Questier

4. Werken met portfolio's
04/10/05 | pag. 4

5. 5
FLOSS user since 90's / FLOSS-only since 2003
Co-founder, former Research & Innovation Director of Chamilo

6. 7
FOSS workshop
I. FOSS: what and why?
II. FOSS experiences worldwide
FOSS tools for universities
III. Strategies for institutional FOSS migrations
IV. Suggesting, voting and ranking priorities for
your university

7. 8
PART I
Free Open Source Software:
What & Why?

8. Early software days
➢ In the 1950s and into the 1960s almost all software
was produced by computer science academics and
corporate researchers working in collaboration.
➢ Source code was generally distributed with the
software
➢ IBM “SHARE” user group
➢ Digital Equipment Computer Users' Society
(DECUS)
Source code: if encrypt(password) == encryptedpassword, then login=1, end
Compiled code: 00100101110101001100110000111101100011000111000110101

9. Open Letter to
Hobbyists:
“Your sharing is
stealing”
Bill Gates, 1976

10. Monopoly abuse
US justice department 1999:
“Microsoft is a monopolist and
it engaged in massive
anticompetitive practices
that harmed innovation
and limited consumer choice”

11. 12
"The most fundamental
way of helping other
people,
is to teach people
how to do things better
or how to better their
lives.
For people
who use computers,
this means sharing
the recipes
you use on your
computer,
in other words
the programs you run."

12. 13
1980's: Stallman defined
“Free Software”
The freedom to
➢ use
➢ study
➢ distribute
➢ improve
the program

13. Free Software Licenses
➢ The freedoms are guaranteed and enforced by licenses, e.g.
➢ GNU GPL (General Public License)
➢ The 4 freedoms + copyleft (share alike)
➢ if binary offered, source code must be offered too
➢ (on request, at low cost)
➢ must stay GPL.
➢ BSD (Berkeley Software Distribution)
➢ Attribution
➢ No copyleft requirements for distribution
➢ BSD code often in closed source software (MS, Mac, ...)
➢ Apple Public Source License v2

14. 1998: “Open Source” sounds
better than “Free Software”?

15. 16
The software Freedoms
require access to the source code
→
“Open Source Software” (OSS)
Free Open Source Software (FOSS)
Free Libre Open Source Software (FLOSS)

16. Software categories
➢ Anti-features are features that users don’t want, including:
➢ Copy-protection
➢ DRM = Digital Rights/Restrictions Management
➢ Data lock-in because of secret file formats
➢ Time-limit / Planned obsolescence
➢ Artificial limitations (e.g. limited RAM, HD and max 3 concurrent programs in MS Windows Vista Home)
➢ Advertisements
➢ Tracking / Spyware

18. 1991 comp sci
student
Usenet posting to the
newsgroup
"comp.os.minix.":
“I'm doing a (free)
operating system (just a
hobby, won't be big and
professional like gnu) for
386(486) AT clones.”

19. 13594 developers from >1300 companies
have contributed to Linux kernel

20. 21
Linus Torvalds
“Making Linux GPL'd
was definitely
the best thing I ever did.”

21. 22
“Open Source ... it's just a
superior way of working together
and generating code.”
“Like science, Open Source
allows people to build on a solid
base of previous knowledge,
without some silly hiding.”
“you can obviously never do as
well in a closed environment as
you can with open scientific
methods.”
Linus Torvalds (2007-03-19). The Torvalds
Transcript: Why I 'Absolutely Love' GPL Version 2.

22. "Congratulations, you're on the winning team.
Linux has crossed the chasm to mainstream adoption."
➢ Jeffrey Hammond, principal analyst at Forrester Research, LinuxCon, 2010
“Linux has come to dominate almost every category of
computing, with the exception of the desktop”
➢ Jim Zemlin, Linux Foundation Executive Director, 2011

23. 99.4% of top 500 supercomputers run Linux

24. Android, a mobile version of Linux,
has overall largest market share

25. Android

26. Top 20 of 301 Linux Distributions
tracked by distrowatch.com

27. 28

31. Browser wars

32. FLOSS browsers dominate!

33. Most used web browser by country
June 2013, according to Statcounter

34. Most used web browser by country
June 2015, according to Statcounter

35. ➢ Compatible with MS Office
➢ Cross-platform (Win, Linux, Mac, ...)
➢ Open document Format (ODF)
➢ XML based, OASIS & ISO standard
➢ PDF & Flash export
➢ Bibliographic manager

36. OpenOffice history and forks

38. Werken met portfolio's
04/10/05 | pag. 39
Build and Manage
a Community?

39. 40
Development
Linus Torvalds' style
Release early and often
Delegate everything you can
Be open to the point of promiscuity
Linus' Law
"given enough eyeballs,
all bugs are shallow."

40. 41
Book published under
Open Publication License
19 lessons for open source
development
Commercial development
= Cathedral style
Open Source development
= Bazaar style

41. 42

42. 43

43. 44
The Cathedral and the Bazaar
about developers
1. Every good work of software
starts by scratching a developer's personal itch.
2. Good programmers know what to write.
Great ones know what to rewrite (and reuse).

44. 45
The Cathedral and the Bazaar
about users
6. Treating your users as co-developers is your least-hassle
route to rapid code improvement and effective debugging.
7. Release early. Release often. And listen to your customers.
8. Given a large enough beta-tester and co-developer base,
almost every problem will be characterized quickly
and the fix obvious to someone.
11. The next best thing to having good ideas is
recognizing good ideas from your users.
Sometimes the latter is better.

45. 46
The Cathedral and the Bazaar
about development
17. A security system is only as secure as its secret.
Beware of pseudo-secrets.
18. To solve an interesting problem,
start by finding a problem that is interesting to you.
19. Provided the development coordinator
has a medium at least as good as the Internet,
and knows how to lead without coercion,
many heads are inevitably better than one.

46. 47
What does the competition say?
➢ Microsoft:
➢ “Linux is a cancer” (Steve Ballmer, CEO)
➢ “Windows (Total Cost of Ownership) is cheaper than Linux”
➢ “Linux violates at least 228 patents”
➢ “GPL is viral”

47. 48
What does the competition
REALLY think?
➢ We get a good idea about what they really think from
their “Halloween documents”, which comprise a
series of confidential Microsoft memoranda on
potential strategies relating to free software, open-
source software, and to Linux in particular.

48. “Halloween Document I” (1998)
Microsoft confidential memo:
➢ “OSS poses a direct, short-term revenue
and platform threat to Microsoft,
particularly in server space.”
➢ “Additionally, the intrinsic parallelism and
free idea exchange in OSS has benefits
that are not replicable with our current
licensing model and therefore present a
long term developer mindshare threat.”
➢ FUD tactics can not be used to combat it.

49. “Halloween Document I” (1998)
Microsoft confidential memo:
➢ “Recent case studies (the Internet) provide very
dramatic evidence ... that commercial quality can
be achieved / exceeded by OSS projects.”
➢ “Linux and other OSS advocates are making a
progressively more credible argument that OSS
software is at least as robust -- if not more -- than
commercial alternatives. The Internet provides an
ideal, high-visibility showcase for the OSS world.”
➢ “OSS is long-term credible”

50. “Halloween Document II” (1998)
Microsoft confidential memo:
➢ “Linux represents a best-of-breed UNIX, that is
trusted in mission critical applications, and - due to
it's open source code - has a long term credibility
which exceeds many other competitive OS's.”
➢ “Most of the primary apps that people require
when they move to Linux are already available for
free. This includes web servers, POP clients, mail
servers, text editors, etc”
➢ “Consumers Love It.”
➢ “The effect of patents and copyright in combatting
Linux remains to be investigated.”

51. “Halloween Document VII” (2002)
Microsoft confidential survey results:
➢ 81% were at least 'somewhat' familiar with OSS
➢ 78% of those had a favorable impression of OSS
➢ 77% were at least 'somewhat' familiar with Linux
➢ 86% of those had a favorable impression of Linux
➢ most compelling reasons to support OSS:
➢ 40%: “Low total cost of ownership”
➢ 34%: “Alternative to Microsoft”

52. “Halloween Document VIII” (2002)
Microsoft confidential memo:
➢ Microsoft tries to develop an emergency-
response team to cope with Linux
conversion announcements

53. “Halloween Document X” (2004)
Microsoft confidential memo:
➢ Shows how Microsoft gave money under the
table to SCO to attack Linux with copyright
claims.
➢ 2007 & 2010: court ruled that Novell, not
SCO, is the rightful owner of the copyrights
covering the Unix operating system.
➢ Novell announced "We don't believe there is
Unix in Linux"

54. Werken met portfolio's
04/10/05 | pag. 55
Why use FLOSS?

55. Assignment
➢ Why would you use FLOSS?
➢ As an individual?
➢ As an institution?

56. Row 1 Row 2 Row 3 Row 4
0
2
4
6
8
10
12
Column 1
Column 2
Column 3
Our social responsibility:
how open is the future?

57. ➢ "Africa can bridge the digital divide
➢ by adopting open source
➢ thus narrowing the effect of techno-colonialism"
➢ “Need for technology
➢ that is controlled by local communities
➢ and not by foreign companies,
➢ that is public property
➢ and empowers people to be self-reliant”

58. Stay in control!
If you don't control the program,
the program controls you!
W
hy?

59. Would you accept
tools with these rules?
➢ You are forbidden to
➢ modify this paper-clip
➢ let other people use your hammer
➢ use this hammer for removing nails
➢ tell others what is written in this book

60. Why do you accept such rules
for software tools?
➢ You are forbidden to
➢ copy
➢ reverse engineer
➢ modify
➢ use in certain circumstances
➢ use in certain countries
➢ ...

62. Stay secure!
You can't trust software
if its source code is hidden
W
hy?

63. “Our products just aren’t engineered for security.”
Brian Valentine, Microsoft senior vice-president Windows Engineering, 2002

65. ➢ From the European Parliament investigation into the Echelon system (05/18/2001):
“If security is to be taken seriously, only those operating
systems should be used whose source code has been
published and checked, since only then can it be determined
with certainty what happens to the data.”

66. ➢ Cryptographer, computer security expert Bruce Schneier:
“Secrecy and security aren't the same, even though it may
seem that way. Only bad security relies on secrecy; good
security works even if all the details of it are public."
“If researchers don’t go public, things don’t get fixed.
Companies don't see it as a security problem; they see it as a
PR problem.”
“Demand open source code for anything related to security”

67. The Borland Interbase example
➢ 1992-1994: Borland inserted intentional back door into
Interbase (closed source database server) allowing local or
remote users root access to the machine
➢ 07/2000: Borland releases source code (→ Firebird)
➢ 12/2000: Back door is discovered

70. Avoid:
data lock in
vendor lock in
Improve interoperability
W
hy?

71. Secret data formats
Secret protocols
➢ Vendor and data lock-in
➢ (changes) force us/others to buy (and buy again)
➢ → viral
➢ vendors don't want us to talk together or to share data
➢ vendors want us to use buy their products
➢ no free competition
➢ no guarantee eternal access

72. Easy localization and customization
W
hy?

73. FLOSS tools are
most often cross-platform
W
hy?

74. FLOSS tools are
most often cross-platform
CPU architectures supported by
➢ Microsoft Windows
➢ x86, ARM
➢ Linux
➢ Alpha, Blackfin, ARM, Atmel AVR32, Axis Communications' ETRAX
CRIS, Texas Instruments TMS320, 68k, Fujitsu FR-V, Qualcomm
Hexagon, HP PA-RISC, H8, IBM System/390, IBM Z/Architecture, IA-64,
x86, M32R from Mitsubishi, Microblaze from Xilinx, MIPS, MN103 from
Panasonic Corporation, OpenRISC, Power Architecture, SPARC,
UltraSPARC, SuperH, Synopsys DesignWare ARC cores, S+core, Tilera,
Xtensa from Tensilica, UniCore32, ColdFire
W
hy?

75. FLOSS tools are
most often cross-platform
Operating systems supported by
➢ Microsoft Internet Explorer
➢ Windows
➢ Mozilla Firefox
➢ Linux, Android, Firefox OS, FreeBSD, NetBSD, OpenBSD,
(Maemo/Meego), OpenIndiana, OpenSolaris, webOS, Darwin, Solaris,
webOS, HP-UX, Risc OS, SkyOS, AmigaOS 4, OS X, Windows, (iOS)
W
hy?

76. Fun
Learning
W
hy?

77. Study on the Economic impact of open source software on innovation and the competitiveness of the
Information and Communication Technologies (ICT) sector in the EU, 2006, R.A. Ghosh, UNU-MERIT, NL.
et al., 287 pp.

78. Study on the Economic impact of open source software on innovation and the competitiveness of the
Information and Communication Technologies (ICT) sector in the EU, 2006, R.A. Ghosh, UNU-MERIT, NL.
et al., 287 pp.

79. Possibility to involve students
W
hy?

80. The (Unix) philosophy of
connectable and reusable
modular components
→ best modules are most reused
→ get most feedback
→ survival of the fittest
→ quality
W
hy?

81. “Linux is the benchmark of quality”
Coverity Report 2012
W
hy?

82. Modularity and lightweight solutions
allow to use small or old devices
W
hy?

83. Save energy!
Don't use personal operating systems
in multi-user environments
W
hy?

84. Esperenza Computer Classroom with software sponsored by Microsoft
1 computer per user?

85. One (library catalog) computer per user?

86. 87
Free yourselfFree yourself
from dogmas!from dogmas!

88. (K12)LTSP
Linux Terminal Server Project
Networked classrooms
Fat server
runs the applications
Thin clients
visualize the applications
need no hard disk
can be 15 years old PC's

89. Reduce costs
W
hy?

93. Free license = eternal !
Avoid:
License management burden
License compliance issues
“Piracy”
W
hy?

95. Business opportunities
W
hy?

96. 97
"Seven open source business strategies for competitive advantage”
John Koenig, IT Manager's Journal, 2004
“Companies continue to
waste their development
dollars on software
functionality that is
otherwise free and available
through Open Source. They
persist in buying third-party
proprietary platforms or
creating their own
proprietary development
platforms that deliver
marginal product
differentiation and limited
value to customers”
Picture reproduced with permission

97. 98
Success in FLOSS requires you to serve
➢ those who spend time to save money
➢ those who spend money to save time
-- Mårten Mickos, CEO MySQL

98. Software freedom allows you to tap into
innovation power and network effects
otherwise not available
Mårten Mickos, CEO MySQL

99. “Companies should work with Open Source
for the value of the ecosystem and community,
not just the value of the code”
Eric Brewer, Google vice-president of infrastructure, 2017

100. Better support
Support is often core
of the FOSS business model
+ fair competition of service providers
Easier troubleshooting
Because of transparency
W
hy?

101. Assignments
In your institution...
➢ how much money is spent yearly on software
licensing?
➢ how much effort (FTE) is put into license
management?
➢ how much unlicensed software is in use?
➢ which proprietary software is still in use?
What is the FLOSS policy of your country,
institution, …?

102. 103
PART II
FLOSS experiences worldwide
FLOSS tools for universities

103. There are FLOSS solutions for all
computational tasks

104. 105
>430000 FLOSS projects
on one development site

105. 106

106. Servers
Internet / Institution
➢ Operating systems: Linux, BSD, OpenSolaris, ...
➢ Domain Name Resolving: BIND
➢ Web server: Apache, nginx
➢ Mail: Sendmail, Postfix, Cyrus, Exim
➢ CMS: Drupal, Joomla, Wordpress
➢ E-learning: Moodle, Chamilo, Dokeos, Open Edx
➢ Helpdesk: Open Ticket Request System, RT
➢ ERP / HRM: Compière, SugarCRM / OrangeHRM
➢ Library: ABCD, Greenstone, Koha, Evergreen
➢ Institutional repository: Greenstone, Dspace, Eprints, Fedora
➢ ...

107. The infrastructure of the largest companies
is built on top of FLOSS
and they are contributing to it
Facebook, Google, IBM, Apple, ...

112. Increasingly governments demand
Open Standards
Source code

113. Some places have done broad Linux migrations
Extremadura in Spain
Kerala in India
or have expressed the desire to do so
China, Russia, Cuba

116. Regional example: Extremadura
➢ poorly developed region → economic revival
➢ based on FLOSS (customized GNU/LinEx)
➢ computer access for every student
➢ saved >18M € on initial 80,000 school computers
➢ total software cost: 1.08 Euro/PC/year
➢ bigger project
➢ stimuli for companies, centres for citizens
➢ economic revival -> European regional innovation award

117. 118
Belgium

118. 119
➢ Free software in
education.
➢ Published by Flemish
ministry of education,
under a free license.

119. 120
My personal experience

120. 121
1998: how it started
➢ In a Belgian University
➢ many people were frustrated
by the inflexible, non-free elearning systems
they had to use
➢ Prof. dr. Thomas Depraetere
➢ starts the Claroline e-learning platform
➢ publishes it as Free Software
➢ got grants for it

121. 122
2004: fork 1
original author wants to break free
➢ Growing number of users
➢ outside the university
➢ requesting professional services
➢ Prof. dr. Thomas Depraetere
➢ starts a company, Dokeos
➢ can't call it Claroline, cause university has trademark
➢ can reuse software code, as it is Free !!!

122. 123
2010: fork 2
the community wants to break free

123. 124
Automated Chamilo analysis
by Ohloh.net

124. 125

126. Drupal meeting
Antwerp 2005

127. Drupalcon DC 2009

128. Drupal
Content Management Platform
➢ Powers 2% of websites
➢ USA White House, MTV UK, Sony Music, Al Jazeera, ...
➢ >2000 themes
➢ >30000 modules
➢ >37000 developers
➢ >1.2M registered users on drupal.org
➢ 2M/month unique visitors on drupal.org

130. ➢ Commercial Open Source company
➢ Founded 2007
➢ $118.5 million venture capital
➢ 3800 enterprise customers
➢ 500 employees
➢ Fastest Growing Private Technology Company in
North America, 2013

132. Belgian FLOSS repository

133. VUB/ULB Hydra
High Performance Compute Server
➢ ~1200 CPU cores, 8960 GB RAM
➢ Linux
➢ Open MPI
➢ Perl, Python, Ruby, GCC, Java, Fortran, Erlang
➢ R, PETSc, AUTO
➢ NWChem, Octupus, AIMPAC, NCI Plot
➢ NCBI Blast, PyNAST, FastTree, RDP Classifier,
cdhit, GATK, NAMD, Garli, mothur, Genovo,
NAMD, SAMtools
➢ GMT, CDO, Ferret, OpenFOAM, Geant
➢ Gnuplot, Pbrt, pfstools, Texlive
➢ ...

138. ➢ 28 question types
➢ Roles: admin, researchers, respondents
➢ Anonymous or with a token
➢ Simple analysis or export
➢ Opportunity: survey.ju.edu.et
➢ Service for researchers and thesis students
➢ Avoid predatory commercial offerings!

143. 144
PART IV
Strategies for effective use of FOSS
in academic environments

144. Reports on assignments
In your institution...
➢ how much money is spent yearly on software
licensing?
➢ how much effort (FTE) is put into license
management?
➢ how much unlicensed software is in use?
➢ which proprietary software is still in use?
What is the FLOSS policy of your country,
institution, …?

146. Why are you not using
(only) FLOSS?

147. Perceived barriers?
➢ Following the herd?

148. Perceived barriers?
pre-installation of non-free software

149. Perceived barriers?
➢ Fear, Uncertainty and
Doubt about
➢ features?
➢ quality?
➢ sustainability?
➢ support?
➢ requirement to participate in
the community?

150. Perceived barriers?
➢ anti-competitive behaviour
➢ monopoly abuse
➢ secret formats
➢ secret protocols
➢ data and vendor lock-ins

151. Perceived barriers?
➢ transition costs
➢ limited in house expertise
➢ plethora of choice?

152. When people can't judge the quality of something,
they look at the price,
because they expect price and quality to be correlated
Perceived barriers?

153. 154

154. 155

155. 156

156. What is infuencing
FLOSS useby school staf?

157. Context
➢ Belgian education is organized by communities
➢ Flanders: Flemish community / ministry of education
➢ Schools & teachers select software
➢ Government supports
➢ ICT coordinators
➢ FLOSS guide book
➢ Few FLOSS trainings
➢ Microsoft contract

158. Research methodology
➢ Interviews
➢ Model conceptualization
➢ Pilot survey
➢ Web based survey
➢ Model validation

159. Basis for conceptual model
➢ Unified Theory of Acceptance and Use of Technology
➢ Theory of Reasoned Action
➢ Technology Acceptance Model
➢ Motivational Model
➢ Theory of Planned Behaviour
➢ Combined TAM & TPB
➢ Model of PC Utilization
➢ Innovation Diffusion Theory
➢ Social Cognitive Theory
➢ Innovation diffusion Model

160. innovation diffusion model
➢ Rogers, E. M. (2003). Diffusion of innovations (5th edition). New York, NY: Free Press

161. UTAUT model

162. Our conceptual model

163. Validated acceptance model for
Free Software in (Flemish) schools

164. Do you think it is desirable
to use FLOSS in education?

165. Which free software
do you use at school?

166. Which free/non-free software
do you use at school?

167. What is your motivation
to use Free Software?

168. What is holding back the
adoption of FLOSS in your school?

169. 170
Conclusions
of the study
➢ FLOSS is being used, but not as a routine
➢ Lack of knowledge
➢ Misconceptions
➢ (Perceived) barriers
➢ Support needed!

170. 171
Recommendations
of the study
➢ For (teacher education) schools
➢ Develop FLOSS vision, plan, expertise
➢ Teach students how to share
➢ For government and managing structures
➢ Give central role to ICT-coordinators
➢ Create an expertise network
➢ Improve FLOSS information
➢ Define a FLOSS policy

171. 172
Strategies for institutional FLOSS migrations

172. 173
0. Allow innovators &
early adopters to use FLOSS
➢ Replace any institutional software
incompatible with FLOSS.

173. 174
1. Organize yourself
➢ Institutional FLOSS expertise center?
➢ Interuniversity FLOSS expertise center?
➢ FLOSS user group?
➢ ...

174. 175
2. Create awareness
➢ Involve all stakeholders
➢ Including
➢ highest management
➢ teachers
➢ students

175. 176
3. Expertise & capacity building
➢ Resources for experimentation &
innovation

176. 177
4. Provide support &
sustainability
➢ Offer
➢ FLOSS repository
➢ local downloads of recommended FLOSS?
➢ Caveat: updates
➢ documentation
➢ training
→ certification

177. 5. Establish institutional
FLOSS policies
➢ Purchasing policies
➢ FLOSS, except if no good alternative
➢ Ask
➢ argumentation
➢ which alternatives considered
➢ Build or buy?
➢ Open standards
➢ Open courseware
➢ Free & Open Licenses

178. My proposal of VLIR-UOS software policy
(not approved yet)
➢ VLIR-UOS wants to encourage the use of Free Libre Open
Source Software (FLOSS) in the South partner institutions.
➢ VLIR-UOS will only support the implementation and
training of FLOSS, unless proprietary software is
demonstrated to be significantly superior and necessary for
the required tasks. Whenever VLIR-UOS funds are used
for proprietary software, reasons must be provided
(including a list of FLOSS alternatives considered) and
approved by [the ICT/OLL expert group or the VLIR-UOS
FLOSS Advisory Board].

179. My proposal of VLIR-UOS software policy
(not approved yet)
➢
In the case VLIR-UOS funded hardware for South partner
institutions comes with proprietary software pre-installed, it must
be demonstrated that the maximum is done to convince the
manufacturer or supplier to only deliver FLOSS. Suppliers that
are willing to provide hardware with FLOSS are to be preferred
above those that don't.
➢
Software developed with VLIR-UOS funds must be published
under a FLOSS license, where possible, in order to maximize its
usefulness for other developing countries.
➢
VLIR-UOS advises new IUC programmes to include a work
package around FLOSS awareness creation, expertise building,
policy definition, training, support and implementation.

180. How to handle
the plethora of choice?
➢ define requirements
➢ indicators of high quality & sustainability
➢ mature, stable software?
➢ active community?
➢ recent releases?
➢ availability of support & documentation?
➢ need / possibility to change the code?
➢ need / possibility to participate in the community?

181. Openness in
checklist for software selection?

182. When to migrate?
➢ Time transitions
➢ at the end of existing contracts
➢ at hardware / software upgrade times
➢ Consider migrating in phases
1. servers
2. desktop applications
→ multi-platform
→ web-based
3. desktop OS

183. Key success factors
for migration & implementation
➢ Resources to experiment
➢ An evidence-based choice
➢ Involvement of both technical and non-technical users in the
selection process
➢ Choice for a new system which is in all aspects at least as good
and easy as the previous one
➢ Reporting detailed migration plan to management and get their
approval and support
➢ In-house expertise with open source software and communities
➢ Contact with the developers and users community
➢ Constant communication with all stakeholders

184. Advantages of being a
contributing community member
➢ Co-decide the direction of development
➢ Create extensions
➢ user requested
➢ research driven innovation
➢ More contacts with other educational institutions
➢ Programming projects for students
➢ Better knowledge of the system
➢ Better trouble solving
➢ Possibilities for grants

185. OpenPatentOffice.org
Protect your freedom to operate
by sharing your innovative ideas

186. 187
PART V
FLOSS priorities and activities
for YOUR University
(discussion and voting)

187. Nominal group technique
What should your university do about FLOSS?
1.Silent generation of ideas
2.Sharing ideas
3.Discussion
for clarification of ideas if needed
4.Ranked voting (priority 1, 2, 3)
5.Ranking

188. Results for Bahir Dar University 2017
Votes Ideas
40 Awareness creation and continuous (expert) training about / on FLOSS
36 Training and awareness for BDU experts / ICT staff
21 Build programmer team under IUC project
14 Identify the best FLOSS and develop
9 establish FLOSS groups
6 smart data center for FLOSS
5 develop different FLOSS
5 Migrate all BDU client computers to Linux
4 Engaging our ICT staff in open source
2 True conf software for videoconference
2 Emphasize security
0 FLOSS in writing projects among application developers

189. Results for Moi University 2015
Votes Ideas
54 Increase awareness & trainings on FLOSS & OER
30 Develop FLOSS & OER & OA policies
19 Create a FLOSS community/taskforce/incubation center
10 Get support/funding from management for FLOSS adoption & implementation
9 Engage (staff & students of all departments & schools) in FLOSS projects
9 Establish a data center
8 Acquire & install FLOSS & OER
7 FLOSS repository on intranet
6 Motivate scholars & teachers to publish as Open Access or OER
5 Annual FLOSS & OER events
5 Review of the curriculum in comp sci
4 Perform FLOSS survey & promote FLOSS research
2 Incentives for MU FLOSS & OER champions
0 Strengthen the (comp sci) student club

190. 191
DAREDARE
TO SHARETO SHARE

191. Credits
➢
Photo Linus Torvalds: GFDL. Permission of Martin Streicher, Editor-in-Chief,
LINUXMAG.com
➢ Picture (open source business strategies) from IT Manager's Journal, may 2004,
with personal permission from John Koenig
➢ Screenshot http://www.openhandsetalliance.com/
➢
Cartoon Open Source Fish by openssoft
➢ T-Shirt “Best things are life are free” by http://zazzle.com
➢ Drupalcon DC 2009 copyright by “Chris” (Flickr)
➢ Screenshot Acquia
➢
Internet map by The Opte Project, CC-by
➢ Open arrow, CC-by-nd by ChuckCoker
➢ Share matches CC-by-nc-nd by Josh Harper
➢ Question mark CC-by by Stefan Baudy
➢ Social Icons by Iconshock http://www.iconshock.com/social-icons/

192. This presentation was made with 100% Free Software
No animals were harmed
Questier.com
Frederik AT Questier.com
www.linkedin.com/in/fquestie
www.diigo.com/user/frederikquestier
www.slideshare.net/Frederik_Questier
Q
uestions?
A
m
eseginalehu!