On 27-10-2013 02:19, Brandon Harris wrote:
rgree++
While I see the value in specifying font stacks that are arguably “prettier”
I also don’t think it’s worth giving up our principles for it.
sarcasm If that principle means that we try to avoid anything
non-free, then we should simply block
On 27 October 2013 10:14, Erwin Dokter er...@darcoury.nl wrote:
The last thing I want to see is a message box stating To see this site as
intended, DOWNLOAD THIS FREE FONT FIRST. Even though I already have a
truckload of free fonts installed, I prefer to use the system's fonts simply
because
On Sat, Oct 26, 2013 at 9:43 AM, Brad Jorsch (Anomie) bjor...@wikimedia.org
wrote:
I came across Gerrit change 79948[1] today, which makes VectorBeta
use a pile of non-free fonts (with one free font thrown in at the end
as a sop). Is this really the direction we want to go, considering
that
On 27 October 2013 19:37, Steven Walling steven.wall...@gmail.com wrote:
We have never and will never ship a proprietary font to users who do not
have one installed, and I think we should maybe make that an official
policy if it isn't already. However, specifying better font families for
On Sun, Oct 27, 2013 at 3:37 PM, Steven Walling steven.wall...@gmail.comwrote:
1. The 'VectorBeta' change is to create an _opt-in_ beta for typography
changes, as part of the release of BetaFeatures extension. We'd only be
providing something to users who want to try this font stack.
On 2013-10-27 12:37 PM, Steven Walling wrote:
Many FOSS communities have dealt with the trade off between
great-looking fonts and freedom by commissioning foundries to get
their own free fonts. See also: Ubuntu, Android, and more. I've talked
to the design team about this idea, including
On 27 October 2013 19:47, Steven Walling steven.wall...@gmail.com wrote:
On Sun, Oct 27, 2013 at 12:44 PM, David Gerard dger...@gmail.com wrote:
OK ... and the tradeoff of the designer assuming the non-free font,
and it just happening to look like garbage with any free font?
David, you
Hi,
given that there are some extensions which perform edits/actions
automatically (not directly as a result of user request),
I was wondering, was anyone attempting or successful at subclassing
User?
There are some places where name of this class is hardcoded.
//Saper
Saying that the people who picked the font stack should be able to defend
their selection of font stack and their ability to design for all customers
with it isn't avoiding the question; it's sending the question to the ONLY
people who can sensibly answer it.
Keep in mind that a) the design team
Generally I would not recommend subclassing User; while you can certainly
create such a subclass it will have limited utility as you can't really
control how they get created easily.
Like the rest of MediaWiki, the User class is intended to be customized
through extension hooks... What sort of
Agreed with Brion here. The User class has a large mixture of functionality
and is hardcoded all over the place. There are very few use cases I can
think of where it would work, and even then there's no guarantee the
solution will continue to work in future versions.
--
Tyler Romeo
On Oct 27,
Brion Vibber bvib...@wikimedia.org wrote:
Generally I would not recommend subclassing User; while you can certainly
create such a subclass it will have limited utility as you can't really
control how they get created easily.
Like the rest of MediaWiki, the User class is intended to be
On 27-10-2013 20:37, Steven Walling wrote:
Many FOSS communities have dealt with the trade off between great-looking
fonts and freedom by commissioning foundries to get their own free fonts.
See also: Ubuntu, Android, and more. I've talked to the design team about
this idea, including perhaps
On 2013-10-27 2:45 PM, Marcin Cieslak wrote:
Some example:
https://gerrit.wikimedia.org/r/#/c/92252/
needs https://gerrit.wikimedia.org/r/#/c/92179/ in core,
that gives some method to override.
Surprisinly, it even works (rc_ip will be set to on
AbuseFilter blocks).
//Saper
Could you
Steven Walling wrote:
You're leaving out two key facts here:
1. The 'VectorBeta' change is to create an _opt-in_ beta for typography
changes, as part of the release of BetaFeatures extension. We'd only be
providing something to users who want to try this font stack. It's a
choice they
Daniel Friesen dan...@nadir-seen-fire.com wrote:
On 2013-10-27 2:45 PM, Marcin Cieslak wrote:
Some example:
https://gerrit.wikimedia.org/r/#/c/92252/
needs https://gerrit.wikimedia.org/r/#/c/92179/ in core,
that gives some method to override.
Surprisinly, it even works (rc_ip will be set
On Sun, Oct 27, 2013 at 4:23 PM, MZMcBride z...@mzmcbride.com wrote:
Steven Walling wrote:
You're leaving out two key facts here:
1. The 'VectorBeta' change is to create an _opt-in_ beta for typography
changes, as part of the release of BetaFeatures extension. We'd only be
Sorry if you don't like MobileFrontend's design, but it's clearly not an
opinion universally shared among readers and editors on the mobile version
of Wikimedia projects. It's nearing 20% of our overall traffic every
month,
and growing like weeds.[1] Thousands of people a month are editing
On 27/10/13 03:43, Brad Jorsch (Anomie) wrote:
I came across Gerrit change 79948[1] today, which makes VectorBeta
use a pile of non-free fonts (with one free font thrown in at the end
as a sop). Is this really the direction we want to go, considering
that in many other areas we prefer to use
I think a better way to go is to add a hook point in
RecentChange::checkIPaddress()... I don't like mixing more session-related
stuff into User like a getUserIP method.
-- brion
On Oct 27, 2013 2:46 PM, Marcin Cieslak sa...@saper.info wrote:
Brion Vibber bvib...@wikimedia.org wrote:
MediaWiki Bugzilla Report for October 21, 2013 - October 28, 2013
Status changes this week
Reports changed/set to UNCONFIRMED: 7
Reports changed/set to NEW: 17
Reports changed/set to ASSIGNED : 20
On 28/10/13 02:32, Tim Starling wrote:
There is the separate issue that on my Linux laptop, Nimbus Sans L
looks worse than the font my browser will choose for sans-serif. That
is because I have customised Firefox to use the Ubuntu font for
sans-serif, which is very readable. I find all the Arial
The 1.22 release adds a new configuration variable,
$wgRedactedFunctionArguments, that allows administrators of MediaWiki
installations to designate function arguments that should be redacted
from stack traces. For example:
$wgRedactedFunctionArguments[] = array('User::comparePasswords' =
array(
23 matches
Mail list logo
