Last modified: 2014-04-10 17:40:47 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T55595, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 53595 - License shouldn't be hardcoded in MobileFrontend
License shouldn't be hardcoded in MobileFrontend
Status: RESOLVED FIXED
Product: MobileFrontend
Classification: Unclassified
stable (Other open bugs)
unspecified
All All
: Highest major
: ---
Assigned To: Luis Villa (WMF Legal)
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-08-30 15:52 UTC by Quim Gil
Modified: 2014-04-10 17:40 UTC (History)
12 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Quim Gil 2013-08-30 15:52:35 UTC
MobileFrontent shows always 

"Content available under CC BY-SA 3.0"

regardless of the actual license of the site. This is a problem in itself, but it is a major bug now that mobile editing is possible. It introduces a risk of getting contributions from users thinking that they are working under one license, when it is actually another one.

Habeas corpus:

http://espiral.org/wk/Happiness_for_everyone (CC0, as configured)

vs 

http://espiral.org/wk/Happiness_for_everyone?useformat=mobile (CC-BY-SA, hardcoded)
Comment 1 Jon 2013-09-05 19:08:50 UTC
Is there any reason you can't overwrite the message mobile-frontend-footer-license ?
Comment 2 Quim Gil 2013-09-05 19:57:25 UTC
Yes, the expectation that MobileFrontend will just show the same value that $wgRightsText has.  :)

The license of the content will be always the same in desktop and mobile.
Comment 3 Max Semenik 2013-09-05 22:22:07 UTC
(In reply to comment #1)
> Is there any reason you can't overwrite the message
> mobile-frontend-footer-license ?

Because you need to override it in every language possible, compare https://en.m.wikinews.org/wiki/Main_Page vs. https://en.m.wikinews.org/wiki/Main_Page?uselang=fr
Comment 4 Ryan Kaldari 2013-09-06 17:18:27 UTC
Max mentioned that he had a fix for this, but I don't know the details.
Comment 5 Max Semenik 2013-09-07 00:01:10 UTC
(In reply to comment #4)
> Max mentioned that he had a fix for this, but I don't know the details.

https://gerrit.wikimedia.org/r/83104 but it's just a part of a solution - ideally we might want to use the same text. What's preventing us? Desktop links are less of a concern now that we have mobile redirection on wikimediafoundation.org, however for example http://m.wikimediafoundation.org/wiki/Privacy_policy still looks ugly. If we fixed all these technical concerns I think product can work with legal on a solution that we programmers can implement.
Comment 6 Gerrit Notification Bot 2013-09-16 23:49:42 UTC
Change 84465 had a related patch set uploaded by Kaldari:
Un-hardcode footer license message

https://gerrit.wikimedia.org/r/84465
Comment 7 Gerrit Notification Bot 2013-09-16 23:55:45 UTC
Change 84465 merged by jenkins-bot:
Un-hardcode footer license message

https://gerrit.wikimedia.org/r/84465
Comment 8 jeremyb 2013-09-18 03:07:12 UTC
Reopening.

Apparently MobileFrontend and [[Special:allmessages]] both do not follow redirects and use the content from MW core which was written at least 7 years ago. (hard to follow the blame because there were reformattings and moves from one file name to another)

Vector and MonoBook both follow redirects and so they use the custom WMF message.

Compare http://web.archive.org/web/20130907214711/http://en.m.wikipedia.org/wiki/Main_Page vs. http://en.m.wikipedia.org/wiki/Main_Page

Bumping priority because I think legal would object to the current wording. ("Content" vs. "Text". but I guess it can wait until morning.)
Comment 9 Luis Villa (WMF Legal) 2013-09-18 03:48:31 UTC
Someone pinged me this afternoon and I'm looking at it, but I had a few questions. The links to the archive help answer one of those, so thanks!

For the record in the bug, old format:

Text is available under CC BY-SA 3.0; additional terms may apply.

New format:

Content is available under Creative Commons Attribution-Share Alike 3.0 Unported.
Comment 10 Luis Villa (WMF Legal) 2013-09-18 03:49:27 UTC
And I'll take assignment, but who should I reassign to when I'm done? Max?
Comment 11 Tomasz Finc 2013-09-18 06:17:00 UTC
(In reply to comment #10)
> And I'll take assignment, but who should I reassign to when I'm done? Max?

Assign it to Kennan and he can schedule it in an upcoming sprint.
Comment 12 jeremyb 2013-09-18 06:35:00 UTC
(In reply to comment #8)
to clarify, that's mostly not from reading the code but just what I saw when looking at the 3 different interfaces (Vector/MonoBook/Mobile) and [[Special:AllMessages]]. (so maybe it's some other component doing the redirect resolution instead of the skin)
Comment 13 Ryan Kaldari 2013-09-18 19:23:32 UTC
The "redirect" is actually a hook that we don't currently support on the mobile side. It's actually not supported on purpose sine we don't want the paragraph-long notice that currently shows up on en.wiki desktop being shown on mobile. Once I hear back from Luis on the legal requirements for the notice, we can decide how to move forward on improving things further.
Comment 14 Jon 2013-09-23 22:53:02 UTC
Did Change-Id: I0440ecd33e253fdaf77179b855db6cdd4f355935 fix this?
Comment 15 Ryan Kaldari 2013-09-23 23:00:17 UTC
No, that fix wasn't related. But the following are:

https://gerrit.wikimedia.org/r/#/c/84558/
https://gerrit.wikimedia.org/r/#/c/85391/

Should be fixed now and deployed tomorrow.
Comment 16 Quim Gil 2013-11-02 18:56:13 UTC
I just realized that the hardcoded license still shows up in the mobile edit preview page. See what http://espiral.org footer still says (1.22wmf22 - CC0 license):

[CC-by-sa logo]] By clicking "Save", you agree to our Terms of Use and agree to release your text under the CC BY-SA 3.0 License and GFDL.
Comment 17 Juliusz Gonera 2013-11-05 23:10:41 UTC
Also see bug 56639.
Comment 18 Jon 2013-11-12 17:29:17 UTC
This bug was about footer so I believe it should remain closed. Let's work on the other bug 56639 to avoid bug confusion.
Comment 19 Gerrit Notification Bot 2014-04-10 14:47:03 UTC
Change 125192 had a related patch set uploaded by Tarrow:
Don't merge references with same hash into claims

https://gerrit.wikimedia.org/r/125192
Comment 20 Gerrit Notification Bot 2014-04-10 14:57:38 UTC
Change 125192 merged by Addshore:
Don't merge references with same hash into claims

https://gerrit.wikimedia.org/r/125192
Comment 21 Arthur Richards 2014-04-10 17:40:47 UTC
The recent associated patchset seems to not actually have anything even remotely to do with this issue; I've commented on the patchset to change the commit message and am reclosing.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links