===================================== #chaoss-community: Hangout 2017-11-14 ===================================== Meeting started by GeorgLink at 19:55:37 UTC. The full logs are available at http://ircbot.wl.linuxfoundation.org/meetings/chaoss-community/2017/chaoss-community.2017-11-14-19.55.log.html . Meeting summary --------------- * IDEA: Maybe we can have the same time for weekly hangout and the monthly call (GeorgLink, 19:56:29) * LINK: http://stackalytics.com/ (LawrenceHecht, 20:05:41) * LINK: http://stackalytics.com/ (GeorgLink, 20:05:57) * LINK: http://events.linuxfoundation.org/events/open-source-leadership-summit (GeorgLink, 20:20:45) * Organizational Diversity can be interpreted in different usecases for different decisions: (1) A giant company that sees its competitors invest in an open source project may decide to monitor the technology; (2) When looking at non-vendor companies, corporate involvement may signal adoption; (3) A blogger may call out that a lack of diversity speaks against the open source spirit. (GeorgLink, 20:23:40) * IDEA: Lawrence proposes that the components of every activity metric should be defined (similar to the asterisks in the Diversity and Participation file) (GeorgLink, 20:26:06) * IDEA: this definitional part might be part of the tooling discussion (GeorgLink, 20:26:33) * LINK: https://libraries.io/ (LawrenceHecht, 20:32:11) * Lawrence pointed out the difference between "metric" and "variable" - a metric is a time series of a variable (GeorgLink, 20:36:17) * Maybe we can ask Daniel Izquierdo about how to document "components" of activity metrics - that is the implementation specifications - but without being technology dependent (GeorgLink, 20:37:12) * metrics for dependencies: 1) how many other repos does its components rely on? 2) what is the risk associated with the third-party component? 3) ?? (LawrenceHecht, 20:37:25) * LINK: https://wiki.linuxfoundation.org/chaoss/metrics?rev=1506455252 old wiki page version (GeorgLink, 20:41:03) * for releasing metrics, maybe we can use a structure like: metric-category-activitymetric-rationale&usecases with each level being a sub-section of the previous. (GeorgLink, 20:56:59) Meeting ended at 20:57:04 UTC. People present (lines said) --------------------------- * GeorgLink (12) * LawrenceHecht (3) * collabot (3) Generated by `MeetBot`_ 0.1.4