Hi,
A Hebrew Wikipedia user complained that the mobile diff colors changed to
dark green and dark pink, which she finds very inconvenient.
What would be the right way to report that? Bugzilla? Some talk page about
Mobile Feedback? [[mw:Talk:Mobile_design]] is empty, but it can be started.
I presume that some serious design work went into that, and I don't have a
strong opinion of my own, but hey - I'm quite pleasantly surprised that
somebody cares about mobile diff colors, so I guess that it should be
considered.
--
Amir Elisha Aharoni · אָמִיר אֱלִישָׁע אַהֲרוֹנִי
http://aharoni.wordpress.com
“We're living in pieces,
I want to live in peace.” – T. Moore
I was on a phone when I looked at this - the videos don't work there so I
was only looking at the screenshot. Yes looking at the video it does make
more sense.
The bit that _doesn't_ make sense is where the 5 seconds come from.
The rule says this:
page.spinner_loading_element.when_not_present
page.submit_button_element.when_present.click
Nothing about 5 seconds.. Waiting 5 seconds for the spinner to disappear is
way too optimistic. VisualEditor can take much much longer than this
especially on beta labs. I'd suggest 10 seconds maybe even 15 seconds -
where does this number 5 come from?
On a side note. I'm really concerned no one else other than me is paying
notice to these mails as they are very noisy....
I'm keen to see less of these e-mails and only see them when they actually
show something is broken. Is there a possibility to only send the mails
when it has been broken for 2 test runs to avoid issues due to the server?
On Fri, Feb 7, 2014 at 11:29 AM, Chris McMahon <cmcmahon(a)wikimedia.org>wrote:
>
>
>
>
> On Fri, Feb 7, 2014 at 12:20 PM, Jon Robson <jrobson(a)wikimedia.org> wrote:
>
>> Note sure why this failed. It works fine for me locally.... It's strange
>> as the screenshot shows it got to the preview screen. Maybe the loader
>> disappeared too fast?!
>>
>
> It tells you exactly why it failed. The message "timed out after 5
> seconds, waiting for {:class=>"spinner loading", :tag_name=>"div"} to
> disappear" seems perfectly clear to me, I hope it is to you also. If you
> click the "Screencast" tab of the SauceLabs display, you see the spinner on
> the last step is present until the video ends.
>
> -Chris
>
>
> On 6 Feb 2014 23:00, <jenkins-no-reply(a)cloudbees.com> wrote:
>>
>>> * FAILURE:
>>> MobileFrontend-en.m.wikipedia.beta.wmflabs.org-linux-firefox Build #336
>>> <https://wmf.ci.cloudbees.com/job/MobileFrontend-en.m.wikipedia.beta.wmflabs…>
>>> (Fri, 07 Feb 2014 06:28:34 +0000)*
>>> *Test Result*<https://wmf.ci.cloudbees.com/job/MobileFrontend-en.m.wikipedia.beta.wmflabs…>
>>> 1 failed, 7 skipped
>>> Failed Tests *Test Name**Duration**Age* Encourage new users to Keep
>>> Going.I see a KeepGoing message after completing my VisualEditor edit<https://wmf.ci.cloudbees.com/job/MobileFrontend-en.m.wikipedia.beta.wmflabs…> 1
>>> min 41 sec6<https://wmf.ci.cloudbees.com/job/MobileFrontend-en.m.wikipedia.beta.wmflabs…> All
>>> Tests *Package**Duration**Fail**Skip**Total* (root)<https://wmf.ci.cloudbees.com/job/MobileFrontend-en.m.wikipedia.beta.wmflabs…>25
>>> min1761
>>>
>>
>
This schema has been around since the dawn of time. It collects data
around the watch star activity.
Currently we don't use it for anything.
I think we should do something about this.
1) Create an automation script using SQL [A] that generates regular
reports showing the top ten watch articles on mobile on wikis for each
month and publish that somewhere. See Graph [C] to get an idea of what
this looks like for January.
2) We may want to do the above but in addition to this stop logging
clicks on the watchstar when logged out. The graph generated for
January [D] from this data is very different, quicker to run and much
more work safe.
3) Kill the schema altogether
I would suggest options 2 or 3. Interested in the wider communities opinion.
(Note 2/3 could take the form of mails to the mobile-l mailing list or
outputted to some server on the labs)
[A] SQL query:
select page_namespace, page_title, count from (
select count(*) as count, page_namespace, page_title
from MobileBetaWatchlist_5281061 as Watchstar
JOIN enwiki.page
ON page_id = event_articleID
where
event_username != 'Selenium user' and
timestamp >= '2014010100000' and
timestamp <= '2014013100000' and
wiki = 'enwiki'
group by page_title )
as MostActive
order by MostActive.count desc
limit 10
[B] Only include logged in users
select page_namespace, page_title, count from (
select count(*) as count, page_namespace, page_title
from MobileBetaWatchlist_5281061 as Watchstar
JOIN enwiki.page
ON page_id = event_articleID
where
event_anon = 0 and
timestamp >= '2014010100000' and
timestamp <= '2014013100000' and
wiki = 'enwiki'
group by page_title )
as MostActive
order by MostActive.count desc
limit 10
[C] List of most watched articles for January including anon clicks
0 Main_Page 47619
12 Searching 3827
0 XXX 2205
6 Xxx_movie.jpg 2054
0 Pornography 1973
0 Facebook 1906
6 Facebook_(login,_signup_page).jpg 1619
6 Elf_Yourself_screenshot.jpg 1566
0 XXX_(film) 1498
0 Android_rooting 1368
[D] List of most watched articles for January excluding anon clicks
0 Main_Page 4079
0 The_Fosters_(2013_TV_series) 186
0 Editor_&_Publisher 99
0 Juan_Mata 85
12 Searching 63
0 Bailee_Madison 55
6 Elf_Yourself_screenshot.jpg 49
0 Android_rooting 48
100 Current_events 47
0 Psychopath_(disambiguation) 44
On Thu, Jan 30, 2014 at 11:38 AM, James Alexander
<jalexander(a)wikimedia.org>wrote:
>
>
> I'm not sure what to suggest.. IANAL either and no one else seems to
> be engaging in this conversation :-S
> Kenan / Juliusz (I think you follow this list) - might be worth you
> following up with legal and raising a bug if necessary? Or maybe Amir,
> you should raise a bug and we could get someone from legals' opinion/
>
[Was not previously a list subscriber; have done that now. Thanks to James
Alexander for bringing this to my attention.]
Kenan and I (along with other members of product and design) have been
looking at this language for a while to try to improve it. #1 on my list is
definitely to say "agree to irrevocably release" instead of "irrevocably
agree to release". :) The legal meaning is essentially the same but the new
wording would be clearer.
That said, we're thinking about rewriting a lot of the copyright language
stuff to make it more clear (and hopefully shorter to boot!) so it don't
think it is a high priority to rewrite/revise this - it may be completely
revised/reorganized in the next few months anyway.
Hope that helps-
Luis
--
Luis Villa
Deputy General Counsel
Wikimedia Foundation
415.839.6885 ext. 6810
NOTICE: *This message may be confidential or legally privileged. If you
have received it by accident, please delete it and let us know about the
mistake. As an attorney for the Wikimedia Foundation, for legal/ethical
reasons I cannot give legal advice to, or serve as a lawyer for, community
members, volunteers, or staff members in their personal capacity.*