From bug 483987, comment 16: Things I'd like to see added: - a "what's this?" link on the version edit page next to the dev agreements - any tests? And not blocking but something for future reference and consider changing later: - queries in loops are very bad and has killed us before - Need to check the return value of save(). You can use transactions. + put license text in the database
(In reply to comment #0) > From bug 483987, comment 16: I guess you mean "bug 483897, comment 16", right? And what about my proposal (ie. bug 483897, comment 17)?
(In reply to comment #1) > (In reply to comment #0) > > From bug 483987, comment 16: > > I guess you mean "bug 483897, comment 16", right? And what about my proposal > (ie. bug 483897, comment 17)? I think adding the tri-license sounds good. CCing Nick.
I'll check with legal on the tri-license to see if there's any reason not to include it.
To include the tri-license, we have to show three links in the UI to the appropriate licenses when the developer picks a license as well as when users view them. punt to 5.0.8 since this is actually more than just a 1 day job.
Some more context- the reason why we have to do this is that the tri-license isn't actually a license, it's an agreement by the developer to adopt three licenses that don't conflict with each other.
This is basically three things: 1. Add an option to the list of licenses that says Tri-license (MPL 1.1/GPL 2.0/LGPL 2.1) 2. Add links that say (View MPL 1.1, View GPL 2.0, View LGPL 2.1) in place of "View license" 3. Add link to FAQ for what's this explaining licensing
Status: NEW → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → WONTFIX
Product: addons.mozilla.org → addons.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.