Can we add a section for release date of the extension or skin release. because it would be easer to view the release date in the special version page then go to the extension page and try to look it up.
I asked this on wikimedia-l in the recent discussion with no answer. I
was wondering what the status of this feature was ...
- d.
---------- Forwarded message ----------
From: David Gerard <dgerard(a)gmail.com>
Date: 1 September 2014 18:00
Subject: Re: [Wikimedia-l] Next steps regarding WMF<->community
disputes about deployments
To: Wikimedia Mailing List <wikimedia-l(a)lists.wikimedia.org>
On 1 September 2014 17:57, Martijn Hoekstra <martijnhoekstra(a)gmail.com> wrote:
> The same, by the way, goes for VE, which should have had "bail and give me
> what you have now as wikitext" from the onset, and Flow which needs a "bail
> and convert this thread to ye olde talkpage thread" (which I fear will be
> batted away as reactionary crank talk, and "by the time flow will be done
> unneeded anyway")
By the way:
Is Flow going to support the use case of cut'n'pasting a piece from
the article page to the talk page, as a lump of wikitext or as a piece
of rich text from VE?
'Cos if it doesn't, I predict that will be the sticking point with the
people who actually communicate on talk pages.
- d.
[X-posted announcement]
Hello,
The Language Engineering team of the Wikimedia Foundation has been working
on a tool for easy translation of Wikipedia articles from one language to
another. The Content Translation tool has been in development since early
2014 and in July it was deployed and opened for testing on beta labs. The
tool currently provides an editing interface, limited machine translation
capability, link and reference adaptation and dictionary support. The first
rollout included machine translation support from Spanish to Catalan. Since
then, the tool has been used to create more than 100 new articles for the
Catalan Wikipedia.
On 5 September 2014, the team will be hosting a round-table conversation
with some of the editors from the Catalan Wikipedia who have been using
Content Translation. The online event is scheduled from 1600 UTC to 1700
UTC. We would like to invite everyone to join us (please use the event url
below) and add your questions to know more about this project. The same url
can be used later to view an archived version of the event.
Thank you.
Event Details:
==========
# Event url - https://plus.google.com/u/0/events/ckphmp2shtnc6hadsca95thshp4
# Date: September 5, 2014 (Friday)
# Time: 1600 UTC (check local time:
http://www.timeanddate.com/worldclock/fixedtime.html?iso=20140905T1600)
Project Details:
============
# Project Home: https://www.mediawiki.org/wiki/Content_translation
# Announcements:
##
http://blog.wikimedia.org/2014/07/16/first-look-at-the-content-translation-…
and
##
http://blog.wikimedia.org/2014/08/26/content-translation-100-published-arti…
--
regards,
Runa
Language Engineering - Outreach and QA Coordinator
Wikimedia Foundation
Executive summary:
Wikitech may be a bit different today. Please log any new issues here:
https://bugzilla.wikimedia.org/enter_bug.cgi?product=Wikimedia%20Labs
and select 'wikitech-interface'.
The whole story:
Since the birth of Labs, wikitech.wikimedia.org (formerly known as
'labsconsole') has been managed by hand by Labs operations staff. While
wikitech was in rapid development it made sense to keep its off-the-cuff
design, but now that it's become a (quite) essential and (fairly) stable
part of our infrastructure, it was time to bring it into the fold.
So, as of today, wikitech is running a wiki config that's managed by our
deployment infrastructure -- Internally, this is know as being 'on the
deployment train.' It's a good place to be -- wikitech will receive
more timely updates, and can now be more easily configured by WMF staff
and volunteers. But, be warned: since this entailed in a fresh build
of wikitech from new code, there are bound to be unintended
differences. I haven't found any serious ones, but I bet you will!
Please be on the lookout for new bugs, unexpected changes of behavior,
etc. When you find problems, report them using the bugzilla link
above. If these issues are urgent (in other words, preventing you from
doing stuff that you need to do) feel free to nag one of the involved
people on IRC: coren, bd808, reedy, or me (andrewbogott).
Many thanks to Bryan, Sam, Chad, Coren, and all others who helped with
this endeavor!
-Andrew
For almost three years, Rachel Farrand has been a regular contributor in
the organization of public and internal Wikimedia events since she joined
the Wikimedia Foundation as an Admin Assistant and then Project Coordinator
with the Engineering department. This past year, Rachel has been the lead
coordinator at the WMF for the Architecture Summit in San Francisco, the
Wikimedia Hackathon in Zürich, the Wikimania Hackathon in London, most of
the Tech Talks scheduled, and many on-site and off-site meetings. Those of
us lucky to work with Rachel know that she is a reliable and patient team
worker who excels at organizing activities for others to enjoy.
For all these reasons and more, we have decided to evolve Rachel's role as
Events Coordinator at the Engineering Community team. With this change,
Rachel will be able to dedicate more time and attention to this area, where
we are already playing good tactics but we need a more consistent strategy
movement-wide. Rachel's current goals include merging our Architecture
Summit, WMF Tech Days, and SF Hackathon into a single event this Winter;
document a HowTo for hackathon organizers compiling our many lessons
learned; and keeping a regular stream of online Tech Talks and on-site
Wikimedia Tech meetups in San Francisco.
She will also assist in the organization of our outreach programs (Google
Summer of Code, FOSS Outreach Program for Women, Google Code-in):
time-based activities that share many aspects with our technical events.
It’s been a great process to work with Lynette on Rachel’s transition into
the ECT team, and we are delighted Engineering Community events will have
the dedication and focus Rachel brings to the work!.
Congrats and "Welcome" Rachel!
--
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
I recently found the idea of
* "lazy rendering" (of tables, images, media objects)
Has application of lazy load techniques ever been considered for
MediaWiki pages?
Here are some pointers:
* https://github.com/ressio/lazy-load-xt Lazy load XT (fully featured
version)
* http://www.appelsiini.net/projects/lazyload
Lazy Load is delays loading of images in long web pages. Images outside
of viewport are not loaded until user scrolls to them. This is opposite
of image preloading
<http://www.appelsiini.net/2007/6/sequentially-preloading-images> …
Using Lazy Load on long web pages will make the page load faster. In
some cases it can also help to reduce server load.
* http://www.datatables.net/extensions/scroller/
Scroller is a virtual rendering plug-in for DataTables which allows
large datasets to be drawn on screen every quickly. What the virtual
rendering means is that only the visible portion of the table (and a bit
to either side to make the scrolling smooth) is drawn, while the
scrolling container gives the visual impression that the whole table is
visible…
*
http://www.datatables.net/release-datatables/extensions/Scroller/examples/s…
DataTables' server-side processing mode is a feature that naturally fits
in with Scroller perfectly. Server-side processing can be used to show
large data sets, with the server being used to do the data processing,
and Scroller optimising the display of the data in a scrolling viewport…
Hi,
Users of the future Wikimedia Phabricator will have a very simple and
straightforward interface to create and edit tasks. Bugzilla's UI was one
of the top complaints from new/casual users, and we can fix this in
Phabricator easily. Currently we are testing this setup in fab.wmflabs.org,
where you can see an example:
http://fab.wmflabs.org/maniphest/task/create/ (imagine that the "Points"
field is not there).
Advanced users needing to prioritize tasks, assign them to someone, and
resolve them can join the Triagers team in order to get the additional
permissions:
http://fab.wmflabs.org/project/view/74/
We are still fine tuning this process at http://fab.wmflabs.org/T64 -- your
feedback is welcome.
--
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
Hi all.
I've noticed Echo has a separate special page, Special:Notifications. Would we like to rewrite the extension so that it adds entries to the watchlist instead? (And add 'Edits' tab into echo itself - put the watchlist items there).
There is a lot of Special: pages already and adding new ones doesn't - immediately - appear to help usability.
svetlana