(Forked from Re: [Wikitech-l] "Not logged in" page)
Is it time to revisit this behaviour? It's come up as being a usability
problem a few times now.
Currently if I log out of a public computer it logs me out of my tablet
device,mobile device and home computer. :(
See bug for reference [1]
[1] https://bugzilla.wikimedia.org/show_bug.cgi?id=49890
On 15 Jul 2014 18:38, "Bryan Davis" <bd808(a)wikimedia.org> wrote:
> On Tue, Jul 15, 2014 at 7:25 PM, Jon Robson <jdlrobson(a)gmail.com> wrote:
> >> regularly. I've found mediawiki logs me out despite the 'keep me
> >> logged in' box, when logging out on a different device, etc.
> > Well that's the bug then no and that should be fixed. Help us work out
> why
> > it is occurring and let's get that dealt with.:)
> >
> > We shouldn't be designing features for edge cases!
>
> Logout was discussed recently on the QA list [0]. The discussion lead
> to Jon Robson pointing out bug 49890 [1] where Chris Steipp stated
> that logout is global.
>
> [0]:https://www.mail-archive.com/[email protected]/msg01559.html
> [1]: https://bugzilla.wikimedia.org/show_bug.cgi?id=49890
> --
> Bryan Davis Wikimedia Foundation <bd808(a)wikimedia.org>
> [[m:User:BDavis_(WMF)]] Sr Software Engineer Boise, ID USA
> irc: bd808 v:415.839.6885 x6855
>
> _______________________________________________
> Wikitech-l mailing list
> Wikitech-l(a)lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l
I'm trying to render an image which uses characters from all of the
languages supported by WP. Is there a single font deployed on production
servers that include all scripts? Any simple font would do, preferably TTF
arial-style.
Thanks!
For the longest time, core skins had a big advantage: they could use the
'skinStyles' parameter of a ResourceLoader module definition, in core's
Resources.php file, to provide different looks for various built-in
functionality. Non-core skin creators could achieve the same by putting
the styles in main skin styles, but this has two big disadvantages: the
styles would be loaded even if not needed on given page, and one often had
to use ugly hacks to "reset" core styles.
With [1] merged, non-core skins can finally do the same, and do it right,
using the new $wgResourceModuleSkinStyles global (akin to
$wgResourceModules):
// Module defined in core or some extension
$wgResourceModules['bar'] = array(
'scripts' => 'resources/bar/bar.js',
'styles' => 'resources/bar/main.css',
);
// Styles defined in the skin
$wgResourceModuleSkinStyles['foo'] = array(
'bar' => 'skins/Foo/bar.css',
);
Documentation is available at
<https://www.mediawiki.org/wiki/Manual:$wgResourceModuleSkinStyles>.
I have already converted Vector to make use of this [2] and I am in the
process of doing the same for Minerva [3][4] (the second patch still
pending, reviews welcome) – MobileFrontend developers were forced to do
some really bad things by the previous limitations ;)
Perhaps someone would be interested in doing this for MonoBook, too? It
currently uses the "everything in main style file" approach.
Have fun!
[1] https://gerrit.wikimedia.org/r/#/c/141259/
[2]
http://git.wikimedia.org/blob/mediawiki%2Fcore.git/1ebad72b0b45209ab0456271…
[3] https://gerrit.wikimedia.org/r/#/c/149780/
[4] https://gerrit.wikimedia.org/r/#/c/150580/
--
Matma Rex
Maybe you can try GNU Unifont.http://en.wikipedia.org/wiki/GNU_Unifont
TTF format:http://www.lgm.cl/trabajos/unifont/index.en.html
Original Message
Sender:Yuri Astrakhanyastrakhan(a)wikimedia.org
Recipient:Wikimedia developerswikitech-l(a)lists.wikimedia.org
Date:Wednesday, Jul 30, 2014 05:33
Subject:[Wikitech-l] Do we have a universal font in production?
I'm trying to render an image which uses characters from all of the languages supported by WP. Is there a single font deployed on production servers that include all scripts? Any simple font would do, preferably TTF arial-style. Thanks! _______________________________________________ Wikitech-l mailing list Wikitech-l(a)lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
The Wikimedia Research Hackathon on August 6 and 7 takes place parallel to
the general Wikimania Hackathon in London.
Wikimania Hackathon information is available at
https://wikimania2014.wikimedia.org/wiki/Hackathon
Research Hackathon information is available at
https://meta.wikimedia.org/wiki/Research:Labs2/Hackathons/August_6-7th,_2014
>From the Research Hackathon info page: this "is an opportunity for anyone
interested in research on wikis, Wikipedia, and other open collaborations
to meet, share ideas, and work together. It's being organized by
researchers in academia and the Wikimedia Foundation, but we want anyone
interested in research to participate. Whether or not you consider yourself
a researcher, or would ever want to be one, come with questions, answers,
data, code, crazy ideas... or just your insatiable curiosity."
Local participation will occur at Wikimania London and in Philadelphia, PA,
US. Remote participation is possible and will include researchers and
community members globally.
Please see the Research Hackathon information page for scheduling and
sign-up details.
Further questions may be directed to Aaron Halfaker (ahalfaker(a)wikimedia.org)
or Leila Zia (leila(a)wikimedia.org).*
Pine
*A $1 fine will be imposed by Oliver Keyes on anyone who misspells Leila's
name or misdirects emails to the WMF Executive Director.
Hi everyone,
I’d like to announce an organizational change at Wikimedia Foundation
in the Platform Engineering group. For those that aren't terribly
interested in how WMF's org chart looks, you can skip the rest of this
email. :-)
Yesterday, we formalized “Release Engineering” as a team, and promoted
Greg Grossmeier to “Release Team Manager” with everyone on the team
reporting to him.
In addition to Greg, the new team comprises:
* Antoine Musso
* Chris McMahon
* Dan Duvall
* Mukunda Modell
* Rummana Yasmeen
* Sam Reed
* Zeljko Filipin
They are broadly responsible for the lifecycle of code from the point
that a developer is ready to check it in through its deployment on our
site, maintaining the processes and tools that reduce negative user
impact of site software changes while simultaneously making software
change deployment efficient and joyful.
On a more detailed level, here’s just a few things the group is responsible for:
* Code and bug report hosting - currently Gerrit and Bugzilla, but in
the glorious future, Phabricator
* Test infrastructure - the team maintains the Beta Cluster, with help
from TechOps
* Test automation - building the Cucumber/RSpec-based infrastructure
for automating browser tests
* Manual testing - actually looking at the product and making sure it
does what all the robots tell us it should be doing
* Test tools - tools that developers can use to test their own code
such as Vagrant
* Deployment tooling - the infrastructure we use to push code out to
production, like scap
More information about the team can be found here:
https://www.mediawiki.org/wiki/Wikimedia_Release_and_QA_Team
You may notice that that page has been around a while (August 2013).
Greg and Chris McMahon have been leading this as a “virtual team” for
the past year, with a shared goal-setting and day-to-day organization.
This has demonstrated that there is a strong case for creating a
formalized team.
Please join me in congratulating Greg and wishing the newly formalized
team continued success!
Rob
This interesting bot showed up on hackernews today:
https://news.ycombinator.com/item?id=8018284
While in this instance the access to anonymous' editors IP addresses is
definitely useful in terms of identifying edits with probable conflict of
interest, it makes me wonder what the history is behind the fact that
anonymous editors are identified by their IP addresses on WMF-hosted wikis.
IP addresses are closely guarded for registered users, why wouldn't
anonymous users be identified by a hash of their IP address in order to
protect their privacy as well? The exact same functionality of being able
to see all edits by a given anonymous IP would still exist, the IP itself
just wouldn't be publicly available, protected with the same access rights
as registered users'.
The "use case" that makes me think of that is someone living in a
totalitarian regime making a sensitive edit and forgetting that they're
logged out. Or just being unaware that being anonymous on the wiki doesn't
mean that their local authorities can figure out who they are based on IP
address and time. Understanding that they're somewhat protected when logged
in and not when logged out requires a certain level of technical
understanding. The easy way out of this argument is to state that these
users should be using Tor or something similar. But I still wonder why we
have this double standard of protecting registered users' privacy in
regards to IP addresses and not applying the same for anonymous users, when
simple hashing would do the job.
Ambassadors (and developers),
I am tremendously happy to announce that the new PDF rendering service is
live for testing on the cluster. At this time, while we shake out
production bugs, it is only available via Special:Book using the 'e-book
(PDF, ocg latex renderer)'. You can also render a specific page by mangling
a 'Download as PDF' sidebar URL as shown in [1]. Specifically, you need to
change the 'writer' GET param to rdf2latex.
Among other things, this service should have significantly better RTL and
non latin language support.
We do have two known large bugs
* We do not yet have table support
* Lots of images fail to render -- this is a recent regression so we should
have a fix quickly.
If you have additional bugs to report; please file a bug in bugzilla under
the Collection MediaWiki extension [2].
For fun plots see ganglia [3] or graphite [4] under the ocg/pdf node.
Note: During the deployment the new renderer was available in the sidebar.
This was reverted fairly quickly, but some pages may still have the link in
cache. It will go away on the next page render / purge.
[1]
https://en.wikipedia.org/w/index.php?title=Special:Book&bookcmd=render_arti…
[2]
https://bugzilla.wikimedia.org/enter_bug.cgi?product=MediaWiki%20extensions…
[3] http://ganglia.wikimedia.org/latest/?c=PDF%20servers%20eqiad
[4] graphite.wikimedia.org
~Matt Walker
Wikimedia Foundation