19:55:37 <GeorgLink> #startmeeting Hangout 2017-11-14
19:55:37 <collabot> Meeting started Tue Nov 14 19:55:37 2017 UTC.  The chair is GeorgLink. Information about MeetBot at http://wiki.debian.org/MeetBot.
19:55:37 <collabot> Useful Commands: #action #agreed #help #info #idea #link #topic.
19:55:37 <collabot> The meeting name has been set to 'hangout_2017_11_14'
19:56:29 <GeorgLink> #idea Maybe we can have the same time for weekly hangout and the monthly call
20:05:41 <LawrenceHecht> http://stackalytics.com/
20:05:57 <GeorgLink> #link http://stackalytics.com/
20:20:45 <GeorgLink> #link http://events.linuxfoundation.org/events/open-source-leadership-summit
20:23:40 <GeorgLink> #info 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.
20:26:06 <GeorgLink> #idea Lawrence proposes that the components of every activity metric should be defined (similar to the asterisks in the Diversity and Participation file)
20:26:33 <GeorgLink> #idea this definitional part might be part of the tooling discussion
20:32:11 <LawrenceHecht> #link https://libraries.io/
20:36:17 <GeorgLink> #info Lawrence pointed out the difference between "metric" and "variable" - a metric is a time series of a variable
20:37:12 <GeorgLink> #info Maybe we can ask Daniel Izquierdo about how to document "components" of activity metrics - that is the implementation specifications - but without being technology dependent
20:37:25 <LawrenceHecht> #info 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) ??
20:41:03 <GeorgLink> #link https://wiki.linuxfoundation.org/chaoss/metrics?rev=1506455252 old wiki page version
20:56:59 <GeorgLink> #info 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.
20:57:04 <GeorgLink> #endmeeting