1538139 - metrics.yaml files in glean should include a license header

Status: RESOLVED FIXED

(Toolkit :: Telemetry, enhancement, P3)

Description

[Michael Droettboom [:mdroettboom]]

See :liuche's suggestion here:

https://github.com/mozilla-mobile/fenix/pull/1067#discussion_r267989975

It doesn't seem like android-components typically put license headers on the build config files (build.gradle, etc.) but I don't feel strongly either way on this.

Comment 1

[Alessio Placitelli [:Dexter]]

It doesn't seem we're putting license notices on Desktop files: https://searchfox.org/mozilla-central/rev/56705678f5fc363be5e0237e1686f619b0d23009/toolkit/components/telemetry/Scalars.yaml

Georg (Product)/chutten (Data steward) any opinion on this?

Comment 2

[Chris H-C :chutten]

From a Data Steward POV I don't have an opinion. The intersection between Data Stewardship and these files are that they serve as public documentation. That means that they must remain public, and they could do that under strict licenses as easily as under the public domain.

That being said, it'd be nice to be clear to anyone who might want to copy the format or contents which license they're free to do so under. It'd also be nice to our contributors to be clear under what license their work on those files would be licensed to others as.

Comment 3

[Georg Fritzsche [:gfritzsche]]

To my knowledge, all code, configuration files, etc. in Firefox and other Mozilla code bases must have our license.
There are only explicit exceptions, like for test files.

As a component owner i say: Let's just put the applicable licenses on it.

Comment 4

[Michael Droettboom [:mdroettboom]]

Attachment: GitHub Pull Request

Comment 5

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/13cd75fcbab9
[components] 1538139: Add MPL license header to metrics.yaml files