The document discusses assessing the health of open source software communities using concepts from service-oriented computing. It proposes monitoring key health indicators of communities by treating monitoring tools as services that can obtain and apply metrics. This would allow analyzing community data to inform strategies for proactively adapting communities and selecting appropriate open source software. Monitoring could be done actively through embedded sensors or passively through data retrieved from tools.

1. Assessing Open Source Communities’ Health
using Service Oriented Computing concepts
Marc Oriol, Oscar Franco-Bedoya, Xavier Franch, Jordi Marco

2. 2
85%Commercial software
will include
Open Source components
2015

3. 3
Quality
MATTERS

4. 4
Communities

5. 5
Our goal is
assess the health
of OSS communities

6. 6
Key health
indicators
metrics

7. 7
How can we monitor
these metrics ?

8. 8
Service Oriented
Computing

9. 9
The current state of the art in Service Oriented
Computing (SOC) related to quality assessment can
be ported into OSS community health analysis
“
”
Service Oriented
Computing

10. 10
SLA1
SLO1.1
SLO1.2
...
SLA1
SLO1.1
SLO1.2
...
Service
Service
Service Provider
Service
provides
Monitor
measures
obtains
appliesto
Service Client
+
Analyzer
informs
SLA
SLO1.1
SLO1.2
...
QoS
+
negotiate
checks checks
ServiceOriented Computing
Proactiveadaptation ...
Additional techniqueson top
triggers
SLA1
SLO1.1
SLO1.2
...
SLA1
SLO1.1
SLO1.2
...
OSScomp.
OSScomp
OSSCommunity
OSScomp.
distributes
Monitor
measures
obtains
appliesto
+
Analyzer
CLA
CLO1.1
CLO1.2
...
Comm.
indicators
+
negotiate
checks checks
Open SourceSoftware
OSSadopter
informs
OSSselection ...
Additional techniqueson top
triggers

11. 11
Monitoring services
with SALMon

12. 12
Monitoring comunitties
with SALMonOSS

13. 13
Where can we
obtain the
data
?

14. 14

15. 15
Monitoring
Software
management
tool
Service

16. 16
What are
the
strategies
?

17. 17
Monitoring
Software
management
tool
Service
Monitoring
Software
management
tool
Service
Active
Passive

18. 18
Conclusions
 Monitor: active or passive strategies
 Aligment with Service Oriented Computing concepts.
Wrapping tools into services
 KHIs  Metrics
 Apply techniques on top (e.g. OSS selection)

19. 19
Thank you!
moriol@essi.upc.edu
http://twitter.com/marc_oriol
ohernan@essi.upc.edu
https://twitter.com/ohfrancob
franch@essi.upc.edu jmarco@lsi.upc.edu
contact information
@gessi_upc
www.essi.upc.edu/~gessi