On Thu, Apr 10, 2014 at 4:26 PM, Brian Wolff bawo...@gmail.com wrote:
I would add as an issue, that there are major variance in the font
selection based on platform and configuration. For some platforms, the
typo refresh chooses a font that is significantly lower quality than
the browser
Dear all,
as you all know the next Wikimedia Hackathon takes place in Zürich,
Switzerland. Registration is already open for a while and we already
passed the deadlines for scholarships and visa assistance. Thanks to the
WMF and several chapters we could assign 29 scholarships to participants
and
On 11-04-2014 04:35, Steven Walling wrote:
How are these specific, replicable bugs? DJ is saying things the current
solution is not working and we cannot do better but there is no
evidence about why this is the case for such a large number of users that
it requires a revert back to plain
Hi,
TL;DR: Gerrit would allow to keep Code-Review votes across
* rebases and
* commit message modifications
of patch sets.
Thereby dropping need to re-review “trivial” changes on patch sets.
Shall we turn that feature on?
Longer version.
Currently,
On Friday, April 11, 2014, Manuel Schneider manuel.schnei...@wikimedia.ch
wrote:
We have 15 beds left until the Youth Hostel is fully booked, 144
participants have registered so far.
This is great news!
Please also those who have already registered review the suggested
sessions and
On Friday, April 11, 2014, Christian Aistleitner christ...@quelltextlich.at
wrote:
Hi,
TL;DR: Gerrit would allow to keep Code-Review votes across
* rebases and
* commit message modifications
of patch sets.
Thereby dropping need to re-review “trivial” changes on patch sets.
Shall we turn
On Fri, Mar 14, 2014 at 4:07 PM, Bryan Davis bd...@wikimedia.org wrote:
The structured logging RFC [0] will be up for discussion again next
Wednesday [1]. There is a strawman implementation in gerrit [2] that
is likely to be the focus of discussion unless there are other issues
that the
What if someone -1's due to something in the summary? It's odd that fixing it
with a new commit would still show -1 on the reviewer's dashboard. I'm fine
with it for automatic rebases though.
--
View this message in context:
Amending a commit message really shouldn't remove existing votes. I
personally would like this on the MobileFrontend repository. I'm not
sure if this can be done on a per project basis if necessary but I
want this.
On Fri, Apr 11, 2014 at 9:29 AM, Aaron Schulz aschulz4...@gmail.com wrote:
What
I keep hearing about ALLL THE BUGS but I've not seen anything on
Bugzilla. This leads me to believe I've not been cc'ed on them or they
haven't been raised (which would be bad). Please can someone raise
these on Bugzilla - if these are being raised on wikis they are not
getting in front of people.
On 11-04-2014 13:11, Erwin Dokter wrote:
[1] shows half the world complaining about the typography refresh.
I forgot to include the URL:
[1]
https://www.mediawiki.org/wiki/Talk:Typography_refresh#Languages_problems
Regards,
--
Erwin Dokter
___
On 11-04-2014 18:42, Jon Robson wrote:
I keep hearing about ALLL THE BUGS but I've not seen anything on
Bugzilla.
That's because you don't *want* to see... Most of the reports on [1] are
from readers who don't know anything about Bugzilla. That doesn't make
that anything less valid.
Since
On Fri, Apr 11, 2014 at 9:44 AM, Erwin Dokter er...@darcoury.nl wrote:
I forgot to include the URL:
[1] https://www.mediawiki.org/wiki/Talk:Typography_refresh#
Languages_problems
Out of all of these, the most clear is that serifs are not great for the
headings in CJK (Chinese, Japanese,
On Fri, Apr 11, 2014 at 10:01 AM, Erwin Dokter er...@darcoury.nl wrote:
There is also a tracking bug [2] with plenty bugs attached, among the [3],
[4] and [5]; *all* language related. Buth the bug reports and Typography
talk page have plenty of screenshots.
[1]
On 11 April 2014 09:29, Aaron Schulz aschulz4...@gmail.com wrote:
What if someone -1's due to something in the summary? It's odd that fixing
it
with a new commit would still show -1 on the reviewer's dashboard.
Sure, but those are relatively rare for simple changes (normally you just
fix
Hey all,
Over the last 2 days, various packages have been upgraded in our Jenkins
environment.
There shouldn't be any noticeable changes (other than bug fixes and minor
improvements).
Let me know if you observe build failures that seem to be unrelated to the
change being tested (e.g. master
Op 11 apr. 2014 om 15:57 heeft Christian Aistleitner
christ...@quelltextlich.at het volgende geschreven:
Hi,
TL;DR: Gerrit would allow to keep Code-Review votes across
* rebases and
* commit message modifications
of patch sets.
Thereby dropping need to re-review “trivial” changes
Since that page was linked as the primary feedback page when the refresh
was
announced, it should be the first place to check for error reports.
Claiming
non-existence of Bugzilla reports is just plain selective ignorance.
I disagree. Bugzilla is where we report bugs. If no one raises bugs as
On Fri, Apr 11, 2014 at 11:17 AM, Brian Cox
nativeforeignerw...@gmail.comwrote:
Perhaps all the user reported bugs should be added to Bugzilla for tracking
purposes. But it's not reasonable to expect the average user to report them
there.
Brian/NF
Yes I think we definitely need to track
I have merged the Gerrit change (https://gerrit.wikimedia.org/r/#/c/124475/),
restoring the body font to sans-serif. The heading font is unchanged for now.
I've read the entire wikitech-l thread (89 emails as of writing) and
pondered this carefully. My summary of the situation is:
* This font
On Fri, 2014-04-11 at 09:42 -0700, Jon Robson wrote:
I keep hearing about ALLL THE BUGS but I've not seen anything on
Bugzilla.
https://bugzilla.wikimedia.org/show_bug.cgi?id=63549 dependency list
plus likely stuff on
https://www.mediawiki.org/wiki/Talk:Typography_refresh that I'd expect
the
On 11-04-2014 20:00, Jon Robson wrote:
Please don't accuse me of things that are not true. I do want to see
these things, but I have to manage 1) mailing lists 2) bugzilla 3)
wiki pages (which i have to know exist). I am only human. Thanks for
the links to bugs I've cc'ed myself on all of
On Fri, Apr 11, 2014 at 11:42 AM, Bartosz Dziewoński matma@gmail.comwrote:
I have merged the Gerrit change (https://gerrit.wikimedia.org/
r/#/c/124475/),
restoring the body font to sans-serif. The heading font is unchanged for
now.
I've read the entire wikitech-l thread (89 emails as of
It looks like Nemo has been doing this (thanks a bunch Nemo) but I
wasn't cc'ed on any of these reports so I was getting just as
frustrated as you thinking we were inside a black hole :)
I don't expect the average user to raise bugs.
This would be a great thing to discuss in the retrospective -
Since we're considering
https://www.mediawiki.org/wiki/Requests_for_comment/Services_and_narrow_interfaces
and asking for discussion on
https://www.mediawiki.org/wiki/Requests_for_comment/Content_API , I put
some time into understanding what a Service-Oriented Architecture and
Representational
On Fri, 11 Apr 2014 18:29:06 +0200, Aaron Schulz aschulz4...@gmail.com wrote:
What if someone -1's due to something in the summary? It's odd that fixing it
with a new commit would still show -1 on the reviewer's dashboard. I'm fine
with it for automatic rebases though.
I think cases of the -1
First, I like to aplologize to anyone who I may have come over too
passionate at some times. Frustration is known to get the better of me,
even though I should control that. (I also quit smoking.)
Not sure where a new font stack should be discussed, so I'm just
throwing it in here. Also, note
3
Thank you Erwin for always moving things forward. Much appreciated. :)
Erik
--
Erik Möller
VP of Engineering and Product Development, Wikimedia Foundation
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
On Friday, April 11, 2014, Erwin Dokter er...@darcoury.nl wrote:
First, I like to aplologize to anyone who I may have come over too
passionate at some times. Frustration is known to get the better of me,
even though I should control that. (I also quit smoking.)
Much harder to quit than to
+1
I never liked this, over and over I point out a fatal issue with a
commit sometimes fundamental to the idea itself and impossible to fix,
so I -1 it, then when a new patchset comes out, completely ignores the
concerns I've pointed out, my -1 with the idea suddenly disappears as if
the
On 11-04-2014 21:49, Steven Walling wrote:
This is the part I want to confirm and test. I want to be 100% sure that we
are not gonna run in to the same ClearType rendering issues. (I have a
Windows 7 laptop at my disposal that I can test with, as well as XP virtual
machines.)
I aksed on the
On Fri, Apr 11, 2014 at 3:06 PM, Sumana Harihareswara suma...@wikimedia.org
wrote:
The way we do stuff now: within your code, you write your core or
extension code so that it interacts with various objects, subclasses
this and event-handles that and hooks into the other thing. And there
are
On 2014-04-11, 12:30 PM, Erwin Dokter wrote:
Nimbus Sans L - for Linux. This is the defacto helv font on Linux
systems which result in an look similair to Mac/Windows. Windows will
not match this font, as the Windows versions of the Nimbus font
packages have different font family names (ie.
On Friday, April 11, 2014, Christian Aistleitner christ...@quelltextlich.at
wrote:
Hi,
TL;DR: Gerrit would allow to keep Code-Review votes across
* rebases and
* commit message modifications
of patch sets.
Thereby dropping need to re-review trivial changes on patch sets.
Shall we turn
On 11-04-2014 22:43, Daniel Friesen wrote:
* However I wonder if 'Helvetica' will ever actually be matched. Even
Arial is crappier than Helvetica in most places (aside from those
Windows installed Helvetica fonts) I can't really think of any
situation where a device would have
Our calendar of activities is filling up.
Tech Talk: Unit testing for MediaWiki projects
https://plus.google.com/events/cae6ng1m9o4mhdbpo10u5v05bvg
April 29, 19:00 UTC
http://www.timeanddate.com/worldclock/fixedtime.html?iso=20140429T12p1=224am=30
If you want to schedule an event,
On 11 April 2014 20:30, Erwin Dokter er...@darcoury.nl wrote:
...
Thank you for your work on this!
Next up I may think about the headers font stack; While Georgia is a good
serif; I detest its use of text figures.
I previously suggested a solution to this that should work for most users
Hello and welcome to the latest edition of the WMF Engineering Roadmap
and Deployment update.
The full log of planned deployments next week can be found at:
https://wikitech.wikimedia.org/wiki/Deployments#Week_of_April_14th
First, please read this blog post regarding the WMF's response to the
On 12-04-2014 00:47, Peter Coombe wrote:
I previously suggested a solution to this that should work for most users (
https://www.mediawiki.org/wiki/Talk:Typography_refresh/Archive_2#Numbers_looks_weird_in_article_title
)
Steven: was this tried?
Using the font-feature-settings CSS. I've had
On Fri, Apr 11, 2014 at 4:15 PM, Greg Grossmeier g...@wikimedia.org wrote:
* Revert font stack change in Typography Refresh to be just sans-serif
** https://gerrit.wikimedia.org/r/#/c/125447/
To be clear per the amended commit message: this is just for the body font
stack. All other aspects
On 12-04-2014 01:29, Erwin Dokter wrote:
Using the font-feature-settings CSS. I've had some trouble using this
with Georgia, but that was regarding tabular numbers. Works just fine
for lining though.
Thinking further... Browser support is pretty recent, doesn't work in
old Opera (Presto) and
On Fri, Apr 11, 2014 at 4:15 PM, Greg Grossmeier g...@wikimedia.org wrote:
* VisualEditor fixes:
** Adding a reference adds an empty one; editing a reference inserts a
new one
** fix JS error on opening redirect pages
+Enable VisualEditor on French Wikinews per community request
42 matches
Mail list logo
