Is it by any chance possible to run cucumber tests under Safari on
Cloudbees? If not, are there alternative solution to running the Cucumber
tests on Safari automatically?
Hello,
The 1.23 release of MediaWiki deprecates
the ResourceLoaderGetStartupModules hook which TimedMediaHandler /
MwEmbedSupport depend on. See <
https://bugzilla.wikimedia.org/show_bug.cgi?id=63240> for details.
I'd like to accelerate the complete removal of this hook. It was created as
a special kludge for MwEmbedSupport, with the expectation that it would be
used only on pages which require the extension, and only until
MwEmbedSupport could be refactored to be in-line with other MediaWiki
extensions. Instead, MwEmbedSupport uses it to load five modules on every
single page: 'jquery.triggerQueueCallback', 'Spinner',
'jquery.loadingSpinner', 'jquery.mwEmbedUtil', and 'mw.MwEmbedSupport'. (A
sixth module, 'mw.MwEmbedSupport.style', is also added to every page, but
by different means.)
This has been the status quo for just under three years, now:
commit dc5c9fe9efa, which added "TODO look into loading this on-demand
instead of all pages", was merged in June 2011.
Could the multimedia team please make this a priority? I'd recommend using
the opportunity to fold MwEmbedSupport support into TimedMediaHandler.
MwEmbedSupport passes itself as a generic module-loading framework, but
three years in, TimedMediaHandler remains its single application.
The relevant bugs are:
https://bugzilla.wikimedia.org/show_bug.cgi?id=55550https://bugzilla.wikimedia.org/show_bug.cgi?id=58086https://bugzilla.wikimedia.org/show_bug.cgi?id=42928https://bugzilla.wikimedia.org/show_bug.cgi?id=58082
I can't imagine it's too much fun to wade into these problems, but we need
to fix this, finally. I would be happy to help.
Hi,
I was curious what it might take to create a 'click for part2, click for
part 3... etc' feature to .webm video on commons.
I'd like to upload longer video files, and allowing users to easily click
through to scenes or only view the clips they wish would be valuable for me
:)
--
*Victor Grigas*
Storyteller <https://www.youtube.com/watch?v=3Knv6D6Thi0>
Wikimedia Foundation
vgrigas(a)wikimedia.org
https://donate.wikimedia.org/
Hi folks,
We would appreciate your thoughts about a proposed "View Original File” feature for Media Viewer. (1)
1. Goals
In our surveys and discussions, many users have asked for either access to original files — or a zoom feature.
These frequent requests cover a range of use cases:
* view the original file in its full resolution
* edit, crop and/or re-use images
* zoom in to see details
2. Feature
To address these requests, this feature would enable you to access the original file from Media Viewer, so you can examine it in your browser, and easily edit/re-use it. To view that original file, you would simply click on a new "View original file" button next to the image, as shown in this mockup (2). This would open the original full-size image in the same browser window, as happens now when you click images in file description pages on Commons. Your browser’s back button would return you to the Media Viewer.
This proposal would support the use cases above by providing the same core functionality editors are used to on file description pages. It would enable you to operate on files (convert/edit them), and also give you the ability to zoom on common file types in modern browsers.
3. Alternatives
The multimedia team has investigated several other solutions to address these user requests. We developed a Simple Zoom Link (3), which you can test now on Commons: but we’re concerned that this implementation provides a poor user experience that’s more complex than it needs to be. We also considered a Basic Zoom feature (4) and a Full Zoom feature (5). But these implementations require more development time than we have right now. We’re eager to wrap up this version of Media Viewer this month, so we can move on to other important issues, such as upgrading UploadWizard or fixing bugs in our technical debt.
4. What do you think?
We’d be grateful for your feedback about this proposal and some of the short-term options we’re considering, by answering these two questions:
Q1. How important to you is it that we implement “View original file” or a similar feature at this time?
a) very important
b) somewhat important
c) not important
Q2. Which of the following options do you think we should develop at this time?
a) View Original File: (~1 day of work) (1)
b) Simple Zoom Link to original file in a tab: (already on Commons, ~1 day to improve) (3)
c) Basic Zoom to original file in Media Viewer: (~1 week of work) (4)
d) Do Nothing
You can respond to these questions by email, or here on our main discussion page:
https://www.mediawiki.org/wiki/Talk:Multimedia/About_Media_Viewer
Thanks in advance for your guidance about this important issue. With your help, we hope to implement a practical solution that can address your most pressing needs in coming weeks.
Regards as ever,
Fabrice
_____________________________
(1) View Original File (#630): https://wikimedia.mingle.thoughtworks.com/projects/multimedia/cards/630
(2) Design Mockup: https://commons.wikimedia.org/wiki/File:Media_Viewer_-_View_Original_File_-…
(3) Simple Zoom Link (#588): https://wikimedia.mingle.thoughtworks.com/projects/multimedia/cards/588
(4) Basic Zoom feature (#504): https://wikimedia.mingle.thoughtworks.com/projects/multimedia/cards/504
(5) Full Zoom feature (#167): https://wikimedia.mingle.thoughtworks.com/projects/multimedia/cards/167
_______________________________
Fabrice Florin
Product Manager
Wikimedia Foundation
http://en.wikipedia.org/wiki/User:Fabrice_Florin_(WMF)
Hi folks,
Per our meeting earlier today, it sounds like we want to request a delay in
removing jQuery migrate. Timo's mail is included below.
Timo has staged this change here:
https://gerrit.wikimedia.org/r/#/c/134607/
What day do we want to delay to? Who should make the request? Is
TimedMediaHandler the main blocker, or are there others that need fixing up?
Rob
---------- Forwarded message ----------
From: Krinkle <krinklemail(a)gmail.com>
Date: Wed, May 7, 2014 at 9:29 AM
Subject: [Wikitech-l] Upcoming jQuery upgrade (breaking change)
To: Wikimedia developers <wikitech-l(a)lists.wikimedia.org>
Hey all,
TL;DR: jQuery will soon be upgraded from v1.8.3 to v1.11.x (the latest).
This
major release removes deprecated functionality. Please migrate away from
this
deprecated functionality as soon as possible.
It's been a long time coming but we're now finally upgrading the jQuery
package
that ships with MediaWiki.
We used to regularly upgrade jQuery in the past, but got stuck at v1.8 a
couple
of years ago due to lack of time and concern about disruption. Because of
this,
many developers have needed to work around bugs that were already fixed in
later
versions of jQuery. Thankfully, jQuery v1.9 (and its v2 counterpart) has
been
the first release in jQuery history that needed an upgrade guide[1][2].
It's a
major release that cleans up deprecated and dubious functionality.
Migration of existing code in extensions, gadgets, and user & site scripts
should be trivial (swapping one method for another, maybe with a slight
change
to the parameters passed). This is all documented in the upgrade
guide[1][2].
The upgrade guide may look scary (as it lists many of your favourite
methods),
but they are mostly just addressing edge cases.
== Call to action ==
This is a call for you, to:
1) Get familiar with http://jquery.com/upgrade-guide/1.9/.
2) Start migrating your code.
jQuery v1.9 is about removing deprecated functionality. The new
functionality is
already present in jQuery 1.8 or, in some cases, earlier.
3) Look out for deprecation warnings.
Once instrumentation has begun, using "?debug=true" will log jQuery
deprecation
warnings to the console. Look for ones marked "JQMIGRATE" [7]. You might
also
find deprecation notices from mediawiki.js, for more about those see the
mail
from last October [8].
== Plan ==
1) Instrumentation and logging
The first phase is to instrument jQuery to work out all the areas which will
need work. I have started work on loading jQuery Migrate alongside the
current
version of jQuery. I expect that to land in master this week [6], and roll
out on
Wikimedia wikis the week after. This will enable you to detect usage of most
deprecated functionality through your browser console. Don't forget the
upgrade
guide[1], as Migrate cannot detect everything.
2) Upgrade and Migrate
After this, the actual upgrade will take place, whilst Migrate stays. This
should not break anything since Migrate covers almost all functionality that
will be removed. The instrumentation and logging will remain during this
phase;
the only effective change at this point is whatever jQuery didn't think was
worth covering in Migrate or were just one of many bug fixes.
3) Finalise upgrade
Finally, we will remove the migration plugin (both the Migrate compatibility
layer and its instrumentation). This will bring us to a clean version of
latest
jQuery v1.x without compatibility hacks.
A rough timeline:
* 12 May 2014 (1.24wmf4 [9]): Phase 1 – Instrumentation and logging starts.
This
will run for 4 weeks (until June 9).
* 19 May 2014 (1.24wmf5): Phase 2 – "Upgrade and Migrate". This will run
for 3
weeks (upto June 9). The instrumentation continues during this period.
* 1 June 2014 (1.24wmf7) Finalise upgrade.
== FAQ ==
Q: The upgrade guide is for jQuery v1.9, what about jQuery v1.10 and v1.11?
A: Those are regular updates that only fix bugs and/or introduce
non-breaking
enhancements. Like jQuery v1.7 and v1.8, we can upgrade to those without any
hassle. We'll be fast-forwarding straight from v1.8 to v1.11.
Q: What about the jQuery Migrate plugin?
A: jQuery developed a plugin that adds back some of the removed features
(not
all, consult the upgrade guide[2] for details). It also logs usage of these
to
the console.
Q: When will the upgrade happen?
A: In the next few weeks, once we are happy that the impact is reasonably
low.
An update will be sent to wikitech-l just before this is done as a final
reminder.
This will be well before the MediaWiki 1.24 branch point for extension
authors
looking to maintain compatibility.
Q: When are we moving to jQuery v2.x?
A: We are not currently planing to do this. Despite the name, jQuery v2.x
doesn't contain any new features compared to jQuery v1 [3]. The main
difference
is in the reduced support for different browsers and environments; most
noticeably, jQuery 2.x drops support for Internet Explorer 8 and below,
which
MediaWiki is still supporting for now, and is outside the scope of this
work.
Both v1 and v2 continue to enjoy simultaneous releases for bug fixes and new
features. For example, jQuery released v1.11 and v2.1 together[4][5].
-- Krinkle
[1]
http://blog.jquery.com/2013/01/15/jquery-1-9-final-jquery-2-0-beta-migrate-
final-released/
[2] http://jquery.com/upgrade-guide/1.9/
[3] http://blog.jquery.com/2013/04/18/jquery-2-0-released/
[4] http://blog.jquery.com/2014/01/24/jquery-1-11-and-2-1-released/
[5] http://blog.jquery.com/2013/05/24/jquery-1-10-0-and-2-0-1-released/
[6] https://gerrit.wikimedia.org/r/131494
[7] https://github.com/jquery/jquery-migrate/blob/master/warnings.md
[8] http://www.mail-archive.com/wikitech-l@lists.wikimedia.org/msg72198.html
[9] https://www.mediawiki.org/wiki/MediaWiki_1.24/Roadmap
_______________________________________________
Wikitech-l mailing list
Wikitech-l(a)lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
https://integration.wikimedia.org/ci/job/mwext-MultimediaViewer-qunit/1888/…
Can't reproduce locally. This time the server logs were unhelpful, and the
QUnit log doesn't show which test is failing. Usually the list of QUnit
tests is displayed, but not here. The only information we have is that the
failing test is supposed to have 1 assertion...
Hi folks,
Here’s this week's update on our global release of Media Viewer (1).
1. This week’s release
This week, we plan to enable Media Viewer on two more large sites: Italian and Russian Wikipedias — during tomorrow’s platform train, on Thursday, May 22. We're pushing back releases to other sites to coming weeks, so we can address current issues and avoid deploying to our largest sites right before a holiday. :)
2. Next releases
We now plan to release on the English and German Wikipedias on Tuesday, June 3, as part of a special deployment. This will give us more time to address new user feedback, with more focus on these communities. If all goes well with these releases, we then plan to deploy the tool on all wikis the following week, as described in our release plan. (2)
3. Feedback
Feedback from our onwiki discussions is surfacing great suggestions for improvement, which we are reviewing and discussing with community members. Links to these discussions are available in our release plan, and we invite you to post your own impressions on our main discussion page (3).
We also keep getting increasingly favorable feedback from our user surveys, across 8 languages:
* about 69% of 7,766 respondents so far find the tool useful, on average
* approval rates keep growing (French approval grew by 2 points to 72%, Hungarian by 3 points up to 62%)
* approval breakdown by language: French 70%, Spanish 80%, Dutch 61%, Portuguese 72%, Hungarian 62%
Learn more in our survey report (4), to be updated again after the English and German deployments.
4. Metrics
We are now tracking over 4.7 million image views globally, across 23 sites, as shown in our new global view dashboard (5). Overall performance has stabilized, and the longest image loads are now about 2.8 seconds for 90% of our users, 4.6 seconds for the 95th percentile and 16.4 seconds for the 99th percentile. Learn more in our global metrics performance dashboards (6).
5. Next steps
We are now working on a short list of issues from our community, and have added them to our current cycle board (6). We plan to gradually address the most pressing issues in coming weeks, while resuming our work on technical debt and the upload wizard upgrade. We are reaching out to community members to help us prioritize the most critical tasks in coming weeks.
Thanks to everyone who is helping us with this Media Viewer release! Gergo will send a separate update on other projects that our team is working on.
Best regards,
Fabrice
(1) About Media Viewer: https://www.mediawiki.org/wiki/Multimedia/About_Media_Viewer
(2) Large Wiki Releases: https://www.mediawiki.org/wiki/Multimedia/Media_Viewer/Release_Plan#Large_W…
(3) Discussion Page: https://www.mediawiki.org/wiki/Talk:Multimedia/About_Media_Viewer
(4) Survey Report: https://www.mediawiki.org/wiki/Multimedia/Media_Viewer/Survey
(5) Global Image Views Dashboard: http://multimedia-metrics.wmflabs.org/graphs/mmv_image_views_global (to be updated soon)
(6) Global Performance Dashboard: http://multimedia-metrics.wmflabs.org/dashboards/mmv#overall_network_perfor…
(7) Current Cycle Board: http://ur1.ca/h7w5s
_______________________________
Fabrice Florin
Product Manager, Multimedia
Wikimedia Foundation
https://www.mediawiki.org/wiki/User:Fabrice_Florin_(WMF)
