Include license information in AMO website CSS files

RESOLVED WONTFIX

Status

addons.mozilla.org Graveyard
Policy
--
trivial
RESOLVED WONTFIX
10 years ago
3 years ago

People

(Reporter: baz, Unassigned)

Tracking

Details

(Reporter)

Description

10 years ago
Right now, we do not include copyright information in the CSS files. For other source files, we include the tri-license info. Legal is supposed to advise us about the right course of action here.

Comment 1

10 years ago
Once and if CSS and JS files are "minified" correctly, all comments will be lost in production anyway. However, in the source code we could add the entire comment block like we do for the PHP source files, as it will not lead to more end-user traffic.
Something else to consider is that oftentimes CSS and JS are copied from other sources or merged into one file, in which case it isn't ours to license.

Comment 3

10 years ago
How does that differ from PHP code?
It doesn't. I just haven't done that with any PHP code for AMO, whereas I have with CSS and JS (for example, putting timeplot CSS in with AMO statistics CSS).
I'd like to WONTFIX this...can someone CC me on bug 444240? thx.
(In reply to comment #5)
> I'd like to WONTFIX this...can someone CC me on bug 444240? thx.

Why is this a WONTFIX?

Oh, and I don't have access to that bug either, can someone CC me as well?
Severity: normal → trivial
(In reply to comment #6)
> (In reply to comment #5)
> > I'd like to WONTFIX this...can someone CC me on bug 444240? thx.
> 
> Why is this a WONTFIX?

The mixing of licenses that are getting stripped out anyway makes it seem unnecessary.  Seems like a LICENSE file in the top level would be easier.

> Oh, and I don't have access to that bug either, can someone CC me as well?

It's wonderfully mysterious.
We should do a top level LICENSE and get rid of in-file licenses.  ->wontfix.
Status: NEW → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → WONTFIX
(Assignee)

Updated

3 years ago
Product: addons.mozilla.org → addons.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.