Skip to main content

Appropriation of the Eclipse Ecosystem: Local Integration of Global Network Production

  • Conference paper
  • First Online:

Abstract

Eclipse and Mozilla Firefox represent a new type of open software that can be supplemented by manifold extensions, being implemented by independent software vendors and open source projects. Research on such software ecosystems shows that collaboration patterns in the software industry evolve from value chains to value nets. An often ignored side-effect of this development is a vast extent of integration work that needs to be done by users. Taking a user point of view, this paper presents an empirical study on the practices of appropriating the Eclipse ecosystem as an example of radical tailorability, based on new opportunities given by the surrounding ecosystem. We show the practices users have developed to manage the antagonism of maintaining a stable and productive working environment, while simultaneously innovating it. Based on these results, we outline different opportunities to improve flexible software by supporting cooperation among the diverse actors involved, in a network of production and consumption.

This is a preview of subscription content, log in via an institution.

Buying options

Chapter
USD   29.95
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
eBook
USD   129.00
Price excludes VAT (USA)
  • Available as EPUB and PDF
  • Read on any device
  • Instant download
  • Own it forever
Softcover Book
USD   169.99
Price excludes VAT (USA)
  • Compact, lightweight edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info
Hardcover Book
USD   169.99
Price excludes VAT (USA)
  • Durable hardcover edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info

Tax calculation will be finalised at checkout

Purchases are for personal use only

Learn about institutional subscriptions

Notes

  1. 1.

    Eclipse users are typically software developers. Despite the fact that this group does not present ‘the’ typical end user, we decided after discussing the pros and cons, to investigate the appropriation practices of Eclipse. The main reason is similar to a ‘lead user’-approach as we can observe emerging strategies to make use of a widespread, dynamical and complex software ecosystem. It has millions of users, it realized a highly advanced technological concept of ‘everything is a plug-in’ [12] and its complex ecosystem offers one of the most advanced platforms to enable a network economy in the software industry.

  2. 2.

    A feature in Eclipse defines a set of plug-ins and sub features which must be installed when the feature is installed.

  3. 3.

    We calculated the distance of two configurations with the set of features Ci and Cj as follows: ufeature(Ci,Cj) = (|Ci\Cj| + | Cj\Ci|)/(|Ci| + |Cj|). Based on this calculated the average distance: ūfeature(C1,…, Cn) = 1/n*(n-1)*S 0£ i < j £ n Ufeature (Ci,Cj). A value of ū near 0 means that the different Eclipse installations are almost identical; a value near 1 means that the installations are most different.

  4. 4.

    The other way round “Did you ever share plug-ins with colleagues?” and “Which way did you use to share these plug-ins?” provide a nearly identical pictures.

  5. 5.

    This citation also shows how subtle the balance between autonomy and cooperative integration is constructed: The seasoned developer submits an individualized offer, but respecting the autonomy and the tool competence of the other, even if he is a novice. Below, we discuss this topic in more detail.

  6. 6.

    At first glance the expression “the real one” sounds strange. But a fine-grained analysis showed that he applies a conservative release policy (in respect to his colleague) using only major releases. His colleagues also use the innovation-oriented milestone builds, but as they are not that stable, they are “unreal”. We could validate this interpretation by using other interview passages. The case shows that Eclipse is updated quite often, which confirms the quantitative data (although the quantitative data also indicates a more ‘conservative’ or ‘rational’ update behavior, as we found no milestone build configuration in any of the 75 cases).

  7. 7.

    Here, the qualitative data explain what the quantitative study suggested, namely that some participants have more than one Eclipse configuration. Another reason is that developers sometimes working in several projects, where a different set of tools are needed.

References

  1. Bowers, J. The Work to Make a Network Work: Studying CSCW in Action. in Proc. of CSCW ’94. 1994: ACM Press, New York.

    Google Scholar 

  2. Grinter, R., et al. The Work to Make a Home Network Work. in Proc. of the ECSCW’05. 2005.

    Google Scholar 

  3. Henderson, A. and M. Kyng, There’s no place like home: Continuing Design in Use, in J. Greenbaum and M. Kyng (eds.), Design at work. 1991, Erlbaum, Hillsdale, NJ. pp. 219–240.

    Google Scholar 

  4. Lieberman, H., F. Paternò, and V. Wulf, eds. End-User Development, 2006, Springer, Dordrecht.

    Google Scholar 

  5. Mackay, W. Patterns of Sharing Customizable Software. in Proc. of CSCW’90. 1990.

    Google Scholar 

  6. MacLean, A., et al. User-Tailorable Systems: Pressing the Issues with Buttons. in Proc. of CHI 90. 1990: ACM Press, New York.

    Google Scholar 

  7. Messerschmitt, D. and C. Szyperski, Software Ecosystem. MIT Press, Cambridge, MA, 2003.

    Google Scholar 

  8. Vasilis, B., J. Slinger, and B. Sjaak, Formalizing software ecosystem modeling, in Proc. of 1st international workshop on Open component ecosystems. 2009.

    Google Scholar 

  9. McIlroy, M.D. Mass produced software components. in Software Engineering - NATO Science Committee Report. 1968. Garmisch, Germany.

    Google Scholar 

  10. Herbsleb, J.D. and R.E. Grinter. Splitting the organization and integrating the code: Conway’s Law revisited. in Proc. of ICSE’99. 1999.

    Google Scholar 

  11. Schmidt, K. and L. Bannon, Taking CSCW seriously. JCSCW, 1992. 1(1): pp. 7–40.

    Google Scholar 

  12. Beck, K. and E. Gamma, Contributing to Eclipse: Principles, Patterns and Plugins. 2003, Addison-Wesley, Boston, MA.

    Google Scholar 

  13. Muller, M.J., J. Haslwanter, and T. Dayton, Participatory Practices in the Software Lifecycle, in M. Helander, T. Landauer, and P. Prabhu (Ed.), Handbook of HCI. 1997, Elsevier, Amsterdam. pp. 255–313.

    Google Scholar 

  14. Mørch, A., et al., Component-based technologies for end-user development. Communication of the ACM, 2004. 47(9): pp. 59–62.

    Article  Google Scholar 

  15. Mackay, W. and L. Angeles. Patterns of Sharing Customizable Software. in Proc. Of Conference on Computer-Supported Cooperative Work. 1990.

    Google Scholar 

  16. Pipek, V., From tailoring to appropriation support: Negotiating groupware usage. 2005, University of Oulu: Oulu.

    Google Scholar 

  17. Star, S.L. and K. Ruhleder, Steps toward an ecology of infrastructure: Design and access for large information spaces. ISJ, 1996. 7: pp. 111–134.

    Google Scholar 

  18. Balka, E. and I. Wagner. Making Things Work: Dimensions of Configurability as Appropriation Work. in Proc. of CSCW 2006. 2006: ACM Press, New York.

    Google Scholar 

  19. O’Mahony, S., F.C. Diaz, and E. Mamas, IBM and Eclipse 2005. Boston, Harvard Business School Press, pp. 906–1007.

    Google Scholar 

  20. Grinter, R.E., J.D. Herbsleb, and D.E. Perry. The geography of coordination: dealing with distance in R&D work. in Proc. of GROUP ’99. 1999.

    Google Scholar 

  21. Stevens, G. and B. Nett, Business Ethnography as a research method to support evolutionary design. Navigatoren, 2009. 9(2).

    Google Scholar 

  22. Oevermann, U., et al., Structures of meaning and objective Hermeneutics, in Meja, V., Misgeld, D. and Stehr, N. (Eds.), Modern German sociology, 1987, Columbia University Press, New York. pp. 436–447.

    Google Scholar 

  23. Tashakkori, A. and C. Teddle, eds. Handbook of Mixed Methods in Social and Behavioral Research. 2003, Sage Publications, Thousand Oaks, CA.

    Google Scholar 

  24. Strübing, J., Arbeitsstil und Habitus – zur Bedeutung kultureller Phänomene in der Programmierarbeit. 1992, Universität Kassel, Germany.

    Google Scholar 

  25. Day, D., Behavioral and perceptual responses to constraint management in computer-mediated design activities. EJC/REC, 1993. 3(2).

    Google Scholar 

  26. Draxler, S., H. Sander, P. Jain, A. Jung, and G. Stevens, Peerclipse: Tool Awareness in Local Communities. In Supplementary Proceedings of the 11th European Conference on Computer Supported Cooperative Work. Vienna, Austria, 2009. p.19.

    Google Scholar 

  27. Dittrich, Y., S. Vaucouleur, and S. Giff, ERP Customization as Software Engineering. IEEE SOFTWARE, 2009. 26(6): pp. 41–47.

    Article  Google Scholar 

Download references

Acknowledgements

We thank the participants for their time, Volker Wulf and Bernhard Nett for discussing earlier Versions of this paper and Thomas von Rekowski for his help preparing this document. The CoEUD project was funded by the German Ministry for Education and Research.

Author information

Authors and Affiliations

Authors

Corresponding author

Correspondence to Gunnar Stevens .

Editor information

Editors and Affiliations

Rights and permissions

Reprints and permissions

Copyright information

© 2010 Springer London

About this paper

Cite this paper

Stevens, G., Draxler, S. (2010). Appropriation of the Eclipse Ecosystem: Local Integration of Global Network Production. In: Lewkowicz, M., Hassanaly, P., Wulf, V., Rohde, M. (eds) Proceedings of COOP 2010. Springer, London. https://doi.org/10.1007/978-1-84996-211-7_16

Download citation

  • DOI: https://doi.org/10.1007/978-1-84996-211-7_16

  • Published:

  • Publisher Name: Springer, London

  • Print ISBN: 978-1-84996-210-0

  • Online ISBN: 978-1-84996-211-7

  • eBook Packages: Computer ScienceComputer Science (R0)

Publish with us

Policies and ethics