Introduction to Free Software - SELF | Sharing Knowledge about ...
Introduction to Free Software - SELF | Sharing Knowledge about ...
Introduction to Free Software - SELF | Sharing Knowledge about ...
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
© FUOC • P07/M2101/02709 62 <strong>Free</strong> <strong>Software</strong><br />
Hours per week Percentage<br />
Between 20 and 40 hours 9.2%<br />
More than 40 hours 7.1%<br />
Note<br />
In addition <strong>to</strong> showing the level of professionalisation of free software development teams,<br />
the time spent in hours is a relevant parameter when it comes <strong>to</strong> making cost estimates<br />
and comparisons with private development models in the industry. With free<br />
software, for now, we just have the end products (new software deliveries, synchronisation<br />
of new code in versions systems...) which do not allow us <strong>to</strong> know how much time<br />
the developer has spent on achieving them.<br />
An analysis of these figures tell us that <strong>about</strong> 80% of developers perform the-<br />
se tasks in their free time, whereas only one in five could consider that they<br />
spend as much time on this activity as a professional. Later, in the chapter on<br />
software engineering, we will see how this data matches developers' contribu-<br />
tions, since they both appear <strong>to</strong> follow the Pare<strong>to</strong> law (vid. section 7.6).<br />
4.6. Motivations<br />
There has been speculation and speculation remains as <strong>to</strong> the motivations for<br />
developing free software, especially when it is done in free time (which, as we<br />
have seen, corresponds <strong>to</strong> <strong>about</strong> 80% of developers). As in previous sections,<br />
we only have the survey data, which is why it is important <strong>to</strong> realise that the<br />
answers have been given by the developers themselves, meaning that they<br />
may be more or less coherent with reality. The percentages shown next exceed<br />
the 100% mark because there was an option for participants <strong>to</strong> select several<br />
answers.<br />
In any case, it appears from their answers that most want <strong>to</strong> learn and <strong>to</strong> de-<br />
velop new skills (approximately 80%) and that many do so in order <strong>to</strong> share<br />
knowledge and skills (50%) or <strong>to</strong> participate in a new form of cooperation<br />
(<strong>about</strong> a third). The first data is not surprising, given that a professional with<br />
more knowledge will be in greater demand than one with less. However, it is<br />
not quite so easy <strong>to</strong> explain the second data, and it would even seem <strong>to</strong> con-<br />
tradict Nikolai Bezroukov's opinion in "A second look at the cathedral and the<br />
bazaar" (December, 1998) [91] that the leaders of free software projects are ca-<br />
reful not <strong>to</strong> share all the information in their possession in order <strong>to</strong> perpetuate<br />
their power. Meanwhile, the third most frequent choice is undoubtedly, a true<br />
reflection of developers' enthusiasm <strong>about</strong> the way free software is created in<br />
general; it is difficult <strong>to</strong> find an industry in which a group of lightly organised<br />
volunteers can technologically speaking stand up <strong>to</strong> the sec<strong>to</strong>r's giants.<br />
Although the "classical" theory for explaining why free software developers<br />
spend time contributing <strong>to</strong> this type of projects is reputation and indirect fi-<br />
nancial benefits in the medium and long term, it would appear that developers<br />
themselves disagree with these claims. Just 5% of those surveyed replied that