More Related Content


More from Roberto Galoppini(20)


Scoring zarafa with sos open source

  1. Scoring the Zarafa Ecosystem on open source maturity, licensing, adoption and leadership Roberto Galoppini & Davide Galletti some rights reserved 2011
  13. EDOS, FLOSSMetrics, FLOSSMole, Mancoosi, QualiPSo, QSOS, Qualoss, SQO-OSS
  46. Ohcount output: 18.9%
  57. Roberto Galoppini Davide Galletti SOS Open Source: email: [email_address]

Editor's Notes

  1. Many oss projects are well known There is a general lack of knowledge about open source software packages, but for few dozen of products, either because of their long history or because created by open source vendors backed by VCs.
  2. But they are so many that it's likely that some names are not known in spite of the fact that they are very well done, reliable, mature Actually many thousands of open source projects, included those that are considered by ISVs, SIs and solution providers “enterprise ready”, are largely unknown among the general public. It is interesting to notice that beyond infrastractural open source programs, open source now is entering the enterprise application arena. Moreover, many open source projects community-led – e.g. Apache, Eclipse, just to name the most famous foundations taking good care of projects falling under their 'umbrellas' – are building blocks used to create commercial products (either proprietary or fully open source) and frameworks for building enterprise software.
  3. Facebook has been developed from the ground up using open source software, not only using open source packages but also contributing to existing projects or even releasing new ones. As formerly observed with Twitter (, also open source projects used at Facebook are almost unknown with very few exceptions. IT Giants stand on the shoulders of dwarfs, let's see how we can do the same.
  4. Twitter recently made public its open source love, disclosing contributions to 29 different projects and making names of all their contributors. Looking at the Twitter open source directory and reading the twitter engineering blog is clear that they invest time and effort to qualify, select and write open source software. As a matter of fact most of those projects are almost unknown with very few exceptions, are not commercially backed by vendors but yet are able to provide great value to Twitter and others.
  5. Looking at top downloads … where we hardly find enterprise software though
  6. So we have a wealth of information, we need metrics so that we can make good use of it Open Source Software Metrics..
  7. The European Union within the fifth and sixth programme has funded projects around open source software quality assessment for 25-30 millions of euros. ALCUNI PROGETTI FINANZIATI PARZIALMENTE QSOS e FLOSSMOLE Despite many of these projects' goals were overlapping ( and a big picture is still missing, some of them elaborated interesting methodologies (e.g. QSOS), and others created useful tools (e.g. FLOSSMetrics) and extracted data from different sources (e.g. OSSMole).
  8. (poco aggiornato); project is closed but Melquiades continues adding some projects; about 3234 projects The FLOSSMetrics project funded by European Commission FLOSSMetrics stands for Free/Libre Open Source Software Metrics. The main objective of FLOSSMETRICS is to construct, publish and analyse a large scale database with information and metrics about libre software development coming from several thousands of software projects, using existing methodologies, and tools already developed. FLOSSMetrics is providing access to dumps of this database (along with charts, tables and other quantitative information about FLOSS development projects) in the Melquiades website
  9. Direct db access, download db Since 2004, FLOSSmole aims to: * freely provide data about free, libre, and open source software (FLOSS) projects in multiple formats for anyone to download; * integrate donated data from other research teams; * provide a community for researchers to discuss public data about FLOSS development. FLOSSmole contains: Nearly 1 TB of data covering the period 2004-now, and growing with data sets from over 275 web spidering operations, and growing each month. This includes data about more than 500,000 different open source projects and their developers. How to Cite FLOSSmole Data Howison, J., Conklin, M., & Crowston, K. (2006). FLOSSmole: A collaborative repository for FLOSS research data and analyses. International Journal of Information Technology and Web Engineering, 1(3), 17–26. (More) All original data is copyright of its owners. 1. If you use the data, please cite the source as shown above. 2. Please be ethical in your use of this data. You may wish to consult the publication Ethical decision-making and Internet research: Recommendations from the AOIR ethics working committee. 3. Please be aware that your use of this data for research may require approval by your company's or institution's IRB (Institutional Review Board).
  10. Ohloh is a directory, a community, and an analytics service Ohloh is a wiki About Ohloh Ohloh is a free public directory of open source software and people. Ohloh is a wiki, and anyone is welcome to join our community and add new projects to our directory, or to make corrections to existing directory pages. This public review makes Ohloh one of the largest, most accurate, and up-to-date software directories available.. Ohloh is not a forge -- we do not host open source projects in the traditional sense. Ohloh is a directory, a community, and an analytics service. We use the data from our directory to create historical reports about the changing demographics of the open source world. Ohloh is owned and operated by Black Duck Software .
  11. We need to get oriented and many sites attempt to lend a hand to us Compass
  12. SOS Opensource is an ongoing effort to take the best from those methodologies and use as much as factual data as it is presently available to support the above evaluations; SOSOSS does not tell anything about functionalities The methodology will be seen in detail applied on Zarafa project
  13. List of tools that have been analized
  14. Non in maniera lineare ma vedendo la sedimentazione del codice; sappiamo da quando esiste; Linux Magazine Febbraio 2008
  15. Normally from scm, here from releases and bug tracking activity; I hear there are plans to open the scm Derivata implicitamente dal sistema di bug tracking vivo e attivo e dalle release; non dedotto dal scm
  16. + popolare in olanda belgio austria germania
  17. Michael Kromer <> The book will be in german language, but the publisher told me it will do everything to release an english version of it as soon as it can see the popular demand on it.
  18. Zarafa is evaluating switching to git to make the repository public Enterprise edition is on the same scm than community Milo: The core team is over 10 people
  19. Correlate: Licenza Leadership Modifiability Tabella: accesso al codice: azienda proprietaria Lo vedi ma non lo tocchi Lo vedi e lo tocchi Vedi tabella in fondo: Zarafa ha un privilegio unico; quindi le aziende non hanno voglia di investirci Eclipse (semi copyleft; mi ridai quello che modifichi) invece le aziende ci investono e poi proprietarizzano il tutto Apache: molto libera; fai quello che vuoi. Mysql nasce in anni in cui “non copyleft” erano poco note; mysql faceva business dicendo che se lo usavi dovevi prendere quella commerciale (non vero legalmente); della comunità non hanno avuto mai troppo rispetto
  20. Maturity (4/4) Maturity (2) over 3 years old Stability (2) Stable and maintained Adoption (4/6) Popularity (1) Small but growing trend References (2) Case studies and implementations available on the net Books (0) None Leadership (3/4) Team size (2) More than 10 Management style (1) Company-led
  21. Partner commerciali che hanno capacità di estendere la piattaforma Voto forse un po' generoso; in realtà per avere una sla ti rivolgi solo a loro; cosa comune tra i progetti open Vedere; tra i prodotti oss supportati e certificati non c'è Zarafa
  22. Gita e trac;
  23. Zarafa è nei repository Canonical Partner; poi è disponibile su Fedora, > Debian Wheezy, CentOS > Global Partner di Novel > > "Zarafa is compatible with SuSE ES 9 and 10. And with Novell E-Directory > over Zarafa’s LDAP Coupling."
  24. > > 2011/5/26 "Oostergo, Milo" <>: >> > > Dear Roberto, >> > > >> > > Thanks for starting the opensource scan. >> > > Hereby some additional information. >> > > >> > > Zarafa offers at the moment not a public source repository, however the > > source code can be found on<version>/<minor > > version>/sourcecode. >> > > As still some enterprise features are in the same source branch and we have > > one base for both community and enterprise editions, we couldn't open our svn > > at the moment, but we >> > > are already evaluating the switch to git where we have more flexibilities to > > make it public.
  25. > > Programming languages: only 1 language, 1 main language, more languages Core systems is all in C++, WebAccess is written in PHP. For the rest all unit tests and many scripts are written in Python. The whole Zarafa API is also available through the Python language. Language Files Code Comment Comment % Blank Total ---------------- ----- --------- --------- --------- --------- --------- cpp 584 237365 56991 19.4% 52067 346423 javascript 280 75301 22738 23.2% 12539 110578 autoconf 6 38277 9 0.0% 4587 42873 php 273 35448 23811 40.2% 7756 67015 make 69 33440 976 2.8% 3819 38235 c 79 22088 5493 19.9% 2623 30204 shell 52 11101 1831 14.2% 1404 14336 xml 3 9775 182 1.8% 1203 11160 html 343 9420 877 8.5% 685 10982 css 54 8479 522 5.8% 1537 10538 python 11 3879 83 2.1% 295 4257 automake 69 1275 22 1.7% 302 1599 perl 9 978 57 5.5% 228 1263 sql 1 14 0 0.0% 0 14 ---------------- ----- --------- --------- --------- --------- --------- Total 1833 486840 113592 18.9% 89045 689477
  26. Services (4/4) Training (2) Available from multiple vendors and in different languages Commercial Support (2) Available from multiple vendors and in different languages Documentation (2/2) Documentation (2) Availablein many languages QA (6/6) Bugs reactivity (2) Formalized and reactive QA Process (2) Supported by tools QA tools (2) Very active use of tools Packaging (6/8) Source (2) Virtual appliance available Red Hat (2) certified Non RHEL commercial Linux distros (e.g. Ubuntu, Suse, Mandriva, etc) (2) Many (more than 3) Windows (0) n/a Maintainability (5/6) Amount of comments (2) Well commented Programming languages (1) One main language Modularity (2) Available tools to create extensions
  27. For the current community members that hasn't been really a bottle neck to contribute, however to make the development process more open indeed the review for migration to GIT was started > > Do people need to write a CLA? Yes, we have a contribution agreement. You can find this also on the developer page on the community hub .
  28. License (0/2) License (0) Copyleft (e.g.: GPL, EUPL) Modifiability (1/2) Modifiability (1) Tools to access and modify code available, but the process is not well defined Roadmap (1/2) Roadmap (1) Not detailed roadmap available Sponsor (0/2) Sponsor (0) Unique sponsor
  29. Zarafa context mitigates the low result on questions related to strategy As there a really strong relationship with partners; many partners, most of them offering value added services and very committed to the platform Zarafa is anyway improving in many areas: The book is going to be published Git is being evaluated as a new scm (rep for code) allowing better access New Community portal Next summercamp Zarafa's score will be even better Many thanks!
  30. To our evaluation Zarafa is a great and well engineered product; There a strong relation with many partners in many countries; Strategy can be made more visible to a wider community and It would benefit Also the fact that this year a book will be published will have an impact on the adoption of the Zarafa Ecosystem New community portal site is an important move in this direction