I'd need internetarchive python package into Labs:
https://pypi.python.org/pypi/internetarchive , a python bot for Internet
Archive. I cant't find how to ask for installing it into Labs. Can you help
me?
It's an interesting package - it can be implemented into a pywikibot and
manage both mediawiki pages and Internet Archive items both reading and
editing metadata and uploading new items/pages. I've been encouraged to go
on by Tpt.
Alex brollo
We bumped the releases back to make them more awesome (and include login &
basic editing features in the first big release). Few more weeks. :)
-- brion
On Sat, Feb 22, 2014 at 10:22 PM, Yuvi Panda <yuvipanda(a)wikimedia.org>wrote:
> On Sat, Feb 22, 2014 at 4:50 AM, Greg Grossmeier <greg(a)wikimedia.org>wrote:
>>
>>
>> == Friday ==
>>
>> New versions of the iOS and Android applications will be submitted to
>> their respective markets.
>>
>>
> I don't think that's happening?
>
>
> _______________________________________________
> Engineering mailing list
> Engineering(a)lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/engineering
>
>
Hi,
I need help with an uploaded file on Commons which is broken:
https://commons.wikimedia.org/wiki/File:Caspary,_Daniel_%28de%29.webm
This file was - among many others - uploaded to Commons using the
Commonist. Now as you see the wikitext is completely missing and there
is no way to add it. The wikitext revision seems to be missing,
rendering the database broken.
* the history is empty
* trying to edit the page results in an edit conflict which is not
resolvable (trying to overwrite just triggers the next edit conflict)
Can someone please have a look at the database and fix this issue?
Thanks,
Manuel
--
Manuel Schneider - Chief Information Officer
Wikimedia CH - Verein zur Förderung Freien Wissens
Lausanne, +41 (21) 340 66 22 - www.wikimedia.ch
Hi,
Does Wikipedia have any exit or click-through stats, like what links
are the visitors following from an article? If yes, are those public?
Thanks,
Strainu
Amazing work. Added bug to integrate into TMH player.
https://bugzilla.wikimedia.org/show_bug.cgi?id=61823
I can’t imagine anyone being against flash to deliver free formats!
—michael
On Feb 23, 2014, at 5:45 PM, Brion Vibber <bvibber(a)wikimedia.org> wrote:
> In case anybody's interested but not on wikitech-l; looking for some feedback on possible directions for fallback in-browser video players.
>
> -- brion
>
> ---------- Forwarded message ----------
> From: Brion Vibber <bvibber(a)wikimedia.org>
> Date: Sun, Feb 23, 2014 at 6:43 AM
> Subject: Re: ogv.js - JavaScript video decoding proof of concept
> To: Wikimedia-tech list <wikitech-l(a)lists.wikimedia.org>
>
>
> Just an update on this weekend project, see the current demo in your browser[1] or watch a video of Theora video playing on an iPhone 5s![2]
>
> [1] https://brionv.com/misc/ogv.js/demo/
> [2] http://www.youtube.com/watch?v=U_qSfHPhGcA
>
> * Got some fixes and testing from one of the old Cortado maintainers -- thanks Maik!
> * Audio/video sync is still flaky, but everything pretty much decodes and plays properly now.
> * IE 10/11 work, using a Flash shim for audio.
> * OS X Safari 6.1+ works, including native audio.
> * iOS 7 Safari works, including native audio.
>
> Audio-only files run great on iOS 7 devices. The 160p video transcodes we experimentally enabled recently run *great* on a shiny 64-bit iPhone 5s, but are still slightly too slow on older models.
>
>
> The Flash audio shim for IE is a very simple ActionScript3 program which accepts audio samples from the host page and outputs them -- no proprietary or patented codecs are in use. It builds to a .swf with the open-source Apache Flex SDK, so no proprietary software is needed to create or update it.
>
> I'm also doing some preliminary research on a fully Flash version, using the Crossbridge compiler[3] for the C codec libraries. Assuming it performs about as well as the JS does on modern browsers, this should give us a fallback for old versions of IE to supplement or replace the Cortado Java player... Before I go too far down that rabbit hole though I'd like to get peoples' opinions on using Flash fallbacks to serve browsers with open formats.
>
> As long as the scripts are open source and we're building them with an open source toolchain, and the entire purpose is to be a shim for missing browser feature support, does anyone have an objection?
>
> [3] https://github.com/adobe-flash/crossbridge
>
> -- brion
>
>
> On Mon, Oct 7, 2013 at 9:01 AM, Brion Vibber <bvibber(a)wikimedia.org> wrote:
> TL;DR SUMMARY: check out this short, silent, black & white video: https://brionv.com/misc/ogv.js/demo/ -- anybody interested in a side project on in-browser audio/video decoding fallback?
>
>
> One of my pet peeves is that we don't have audio/video playback on many systems, including default Windows and Mac desktops and non-Android mobile devices, which don't ship with Theora or WebM video decoding.
>
> The technically simplest way to handle this is to transcode videos into H.264 (.mp4 files) which is well supported by the troublesome browsers. Unfortunately there are concerns about the patent licensing, which has held us up from deploying any H.264 output options though all the software is ready to go...
>
> While I still hope we'll get that resolved eventually, there is an alternative -- client-side software decoding.
>
>
> We have used the 'Cortado' Java applet to do fallback software decoding in the browser for a few years, but Java applets are aggressively being deprecated on today's web:
>
> * no Java applets at all on major mobile browsers
> * Java usually requires a manual install on desktop
> * Java applets disabled by default for security on major desktop browsers
>
> Luckily, JavaScript engines have gotten *really fast* in the last few years, and performance is getting well in line with what Java applets can do.
>
>
> As an experiment, I've built Xiph's ogg, vorbis, and theora C libraries cross-compiled to JavaScript using emscripten and written a wrapper that decodes Theora video from an .ogv stream and draws the frames into a <canvas> element:
>
> * demo: https://brionv.com/misc/ogv.js/demo/
> * code: https://github.com/brion/ogv.js
> * blog & some details: https://brionv.com/log/2013/10/06/ogv-js-proof-of-concept/
>
> It's just a proof of concept -- the colorspace conversion is incomplete so it's grayscale, there's no audio or proper framerate sync, and it doesn't really stream data properly. But I'm pleased it works so far! (Currently it breaks in IE, but I think I can fix that at least for 10/11, possibly for 9. Probably not for 6/7/8.)
>
> Performance on iOS devices isn't great, but is better with lower resolution files :) On desktop it's screaming fast for moderate resolutions, and could probably supplement or replace Cortado with further development.
>
> Is anyone interested in helping out or picking up the project to move it towards proper playback? If not, it'll be one of my weekend "fun" projects I occasionally tinker with off the clock. :)
>
> -- brion
>
>
> _______________________________________________
> Multimedia mailing list
> Multimedia(a)lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/multimedia
<quote name="Yuvi Panda" date="2014-02-23" time="11:52:49 +0530">
> On Sat, Feb 22, 2014 at 4:50 AM, Greg Grossmeier <greg(a)wikimedia.org> wrote:
> >
> >
> > == Friday ==
> >
> > New versions of the iOS and Android applications will be submitted to
> > their respective markets.
> >
> >
> I don't think that's happening?
First I've heard. Do let me know, member of the mobile team :)
Greg
--
| Greg Grossmeier GPG: B2FA 27B1 F7EB D327 6B8E |
| identi.ca: @greg A18D 1138 8E47 FAC8 1C7D |
Hello and welcome to your weekly deployments and roadmap update email.
The full schedule for next week is at:
https://wikitech.wikimedia.org/wiki/Deployments#Week_of_February_24th
Highlights:
== Week of ==
We will be upgrading Varnish (caching servers) instances to a newer
version (previously deployed/tested at ulsfo) slowly over the week.
== Monday ==
We will be fixing doc.wikimedia.org and integration.wikimedia.org
http->https redirects
* https://gerrit.wikimedia.org/r/#/c/111917/
== Tuesday ==
MediaWiki deploy window, currently following the 1.23 schedule
* https://www.mediawiki.org/wiki/MediaWiki_1.23/Roadmap#Schedule_for_the_depl…
* group1 to 1.23wmf15: All non-Wikipedia sites (Wiktionary, Wikisource,
* Wikinews, Wikibooks, Wikiquote, Wikiversity, and a few other sites)
** includes the wikidata extension code updates (which includes a new
Lua interface) to Wikivoyage, Commons, Wikisource.
== Thursday ==
MediaWiki deploy window, currently following the 1.23 schedule)
* group2 to 1.23wmf15 (all Wikipedias)
** includes the wikidata extension code updates (which includes a new
Lua interface) to Wikipedias
* group0 to 1.23wmf16 (test/test2/testwikidata/mediawiki)
== Friday ==
New versions of the iOS and Android applications will be submitted to
their respective markets.
As always, questions welcome,
Greg
--
| Greg Grossmeier GPG: B2FA 27B1 F7EB D327 6B8E |
| identi.ca: @greg A18D 1138 8E47 FAC8 1C7D |
I refactored a standalone script in bingle I wrote a while back called
bingleResolved and integrated it with bingle proper. bingleResolved will
attempt to reconcile bugs marked as 'resolved' (or some configurable
status) with Mingle. That is, if you have bug cards floating around in some
backlog in Mingle but they get marked as resolved in Bugzilla,
bingleResolved will put them where you ask it to (for instance, into the
'accepted' column of your current iteration). This should help keep Mingle
instances tidier and Mingle bug backlogs better in sync with Bugzilla.
If you pull the latest Bingle (b1ff82f46e9d422d016335667556d2a4b23410d4)
and want to use the resolved feature, make sure to update your bingle.ini
(see changes in bingle.ini.example) and run bingle with -r.
Happy Friday!
--
Arthur Richards
Software Engineer, Mobile
[[User:Awjrichards]]
IRC: awjr
+1-415-839-6885 x6687
FYI.
---------- Forwarded message ----------
From: Erik Moeller <erik(a)wikimedia.org>
Date: Fri, Feb 21, 2014 at 2:40 PM
Subject: Update on WMF Director of TechOps
To: All Wikimedia Foundation Staff
Hi folks,
in consultation with Faidon and Mark, we've decided not to immediately
post the Director of TechOps job. Instead, Mark Bergsma will continue
to fill the role indefinitely. This is an exploration - he wants to
see whether he can balance compelling technical work with the
managerial side of the role in a manner that makes him happy and
serves the organization's needs.
It makes a lot of sense to me. Hiring leadership roles is always
high-risk in our complex environment, and with the VPE/ED hires around
the corner, there's already a lot of risk to deal with. So I'm
grateful Mark's willing to continue to step in, and perhaps he will
actually enjoy the hybrid tech/management role in the long run. :)
Given that the team is heavily distributed, it's less of an issue that
he is not based in SF.
To ensure that the responsibilities are manageable and to support the
team going forward, we're preparing a Technical Project Manager role
that will also include some procurement/vendor negotiations
responsibilities. The person will need to have ops/infrastructure
experience to be able to hit the ground running. Internal applicants
will be welcome, of course.
On a side note, Engineering/Product is also hiring an additional admin
staff member to support the department's growing administrative
support needs, which should also help with the overall workload.
Thanks again to Mark and the whole team for making this work. :)
Erik
--
Erik Möller
VP of Engineering and Product Development, Wikimedia Foundation
--
Erik Möller
VP of Engineering and Product Development, Wikimedia Foundation