Tools to explore the OPAM Community Amir Chaudhry Christophe Troestler OCaml 2015 Vancouver

Community? Code — libraries, projects, applications Comms — email, social, websites, meetups Orgs — companies, governance

Community? Code — libraries, projects, applications Comms — email, social, websites, meetups Orgs — companies, governance

Scope and Aims Create tools for people/projects to use
 lots of existing libs to build on e.g. opam-lib, ocaml-git, cohttp, etc Qualitative look at the OPAM universe
 constrained to OCaml code, version-controlled in git

Qualitative vs Quantitative

Qualitative Quantitative Holistic
 Understand complex relationships Targeted
 Explanation and control Patterns and themes Non-causal Correlation and validation Cause and effect Evolves with data Subjective ongoing judgement Hypothesis driven Interpret once at the end Continual interpretation Unique to context Summative interpretation Generalise findings Adapted from: http://www.qualitative-researcher.com/focus-group/qualitative-vs-quantitative/

Qualitative Quantitative Holistic
 Understand complex relationships Targeted
 Explanation and control Patterns and themes Non-causal Correlation and validation Cause and effect Evolves with data Subjective ongoing judgement Hypothesis driven Interpret once at the end Continual interpretation Unique to context Summative interpretation Generalise findings Adapted from: http://www.qualitative-researcher.com/focus-group/qualitative-vs-quantitative/

Scope and Aims Create tools for people/projects to use
 lots of existing libs to build on e.g. opam-lib, ocaml-git, cohttp, etc Qualitative look at the OPAM universe
 constrained to OCaml code, version-controlled in git

Starting point OPAM metadata Commits Authors Package relations github.com/ocamllabs/cosmetrics

Scope and Aims Create tools for people/projects to use
 lots of existing libs to build on e.g. opam-lib, ocaml-git, cohttp, etc Qualitative look at the OPAM universe
 constrained to OCaml code, version-controlled in git

Coverage Can reach ~70% of OPAM packages
 Involves guessing the dev-repo field Simple filtering for OCaml code
 Check for presence of .ml files in src/ or lib/ Can actually look at ~60% of packages
 Issues with connections to some repos (bitbucket)

All commits

All commits

Examples

Add more stuff… Pull Requests/Issues! Other VCS’! Project features! Dashboards!

… but remember Qualitative Exploratory Beware Assumptions

Tools matter Existing libraries made this feasible Quick iteration is important Adaptable to different purposes

Feedback?