Ugh, that was meant to go to wikitech-l too...
On 09/20/2013 03:38 PM, Juliusz Gonera wrote:
Hi,
A bit of background: Not long ago we launched mobile editing. Soon
after that we discovered that the mobile editor fails on many wikis
because we hadn't thought think about AbuseFilter support
On 09/23/2013 06:48 PM, Andrew Garrett wrote:
You should know about this change[1], which corrects the error
messages to be more in line with the general case, as well as adding
some metadata. It's not been approved yet, so I'm nudging a few reviewers.
You can also determine which mobile
On 09/25/2013 02:38 AM, Andrew Garrett wrote:
On 09/23/2013 06:48 PM, Andrew Garrett wrote:
You should know about this change[1], which corrects the error
messages to be more in line with the general case, as well as adding
some metadata. It's not been approved yet, so I'm nudging a few
On 09/25/2013 12:17 PM, Juliusz Gonera wrote:
I've just checked on my local instance and it seems that this patch
does not change much for the MobileFrontend. As I stated in the first
message, we need to distinguish between warnings and disallowed edits
because they require different UI
I haven't read the paper itself, but just in case someone has a moment
and is interested:
http://www.technologyreview.com/view/520946/can-automated-editorial-tools-help-wikipedias-declining-volunteer-workforce/
--
Juliusz
___
Wikitech-l mailing list
Hi,
Sumana pinged me about this RFC but considering other things I am
working on that have a high priority, I'm unlikely to work on this in
the near future. If anyone is interested in picking it up, feel free to
do so.
https://www.mediawiki.org/wiki/Requests_for_comment/Scoping_site_CSS
--
There are three important bugs that need to be fixed in VE before we can
move it to stable for tablets (specifically iPads). The first two were
added by me just today. The third was reported in May by Rummana and for
some odd reason had Jon assigned to it, although he has never worked on it
(I
One more important bug to add to the list:
https://bugzilla.wikimedia.org/show_bug.cgi?id=64575
(input becomes unresponsive in mobile link inspector on iOS Safari)
On Mon, Jun 23, 2014 at 3:17 PM, Juliusz Gonera jgon...@wikimedia.org
wrote:
There are three important bugs that need to be fixed
Someone in one of our meetings mentioned that Twig is a PHP
implementation of Mustache. This doesn't seem to be the case though.
We need a templating solution that works both on the server and the
client.
On Tue, Aug 26, 2014 at 5:21 PM, Trevor Parscal tpars...@wikimedia.org wrote:
Thanks for
Reposting to wikitech-l, in case someone is interested:
http://www.cloudbees.com/webinars/getting-most-out-selenium-and-jenkins-cloudbees-sauce.cb
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
Hi,
I'm a bit confused when it comes to various options I have in gerrit and
it seems the docs are not up to date on that.
* What is the difference between Verified and Code Review? When would I
put +1 in one of them but -1 in the other?
* What is the difference between +1 and +2,
On 12/27/2012 10:31 AM, Matthew Flaschen wrote:
* What is the difference between +1 and +2, especially in Verified?
I think just how certain you are.
I still don't get it. I either think the code is good and should be
merged or it's not good enough and shouldn't be merged. I don't see any
On 12/27/2012 10:36 AM, Alex Monk wrote:
Only some people (project owners, gerrit admins, some WMF staff, etc.) can
give CodeReview+2 (approved), whereas everyone can give CodeReview+1. Only
people able to approve can mess with Verified I think...
But should we mess with Verified? Or should we
/show_bug.cgi?id=36437).
On 12/31/2012 10:39 AM, Krinkle wrote:
On Dec 27, 2012, at 7:18 PM, Juliusz Gonera jgon...@wikimedia.org wrote:
Hi,
I'm a bit confused when it comes to various options I have in gerrit and it
seems the docs are not up to date on that.
* What is the difference between
Can I change the full name in Gerrit somehow? I don't like the fact that
when I merge something in gerrit my commits have JGonera as an author
instead of Juliusz Gonera.
Juliusz
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https
On 01/03/2013 11:52 AM, Chad wrote:
On Thu, Jan 3, 2013 at 2:30 PM, Matma Rex matma@gmail.com wrote:
There's a bug for everything, and they're all waiting...
https://bugzilla.wikimedia.org/show_bug.cgi?id=40061
(It should only take half a day to make this happen, but apparently nobody
Reposting from mobile-tech:
I wrote a short Ruby script to show what versions of MediaWiki different
projects are running on:
https://gist.github.com/b5a97d4dc34f5fc56304
Shows number of languages running on a given project/version.
Might make easier figuring out if a patch in core we need is
I liked the post, but I'm not sure what exactly we should change in our
code reviews. Could you explain?
On 01/21/2013 01:40 PM, Ori Livneh wrote:
There's a useful blog post on code review at Mozilla by Mozilla developer David
Humphrey on his blog: http://vocamus.net/dave/?p=1569.
I like
Sorry for digging up an old thread, but today I also started wondering
if there's a way of making our deployments simpler and faster.
I'm not a big fan of special highly orchestrated events when the whole
team gathers and waits and then looks for regressions after deploying
dozens of commits
On 02/20/2013 12:04 PM, Luke Welling WMF wrote:
I am strongly of the opinion that within broad ranges deployment frequency
does not matter. It really does not matter if you deploy twice an hour or
every second day.
What teams deploy every second day?
But, having the machinery to make it so
On 02/20/2013 12:15 PM, Mark A. Hershberger wrote:
I think there is a lot of ground to cover before we get more
continuous deployments, but what were you thinking we needed?
A simpler and faster deployment process. The part of the process when
supervision is needed shouldn't, in my opinion,
Hi,
Yesterday we released photo uploads in mobile (actually moved it from
beta to stable). We're logging errors we get when people try to upload
photos and it seems the most common one is that they're not logged in to
Commons even though they logged in to Wikipedia. It seems to be
happening
On 02/27/2013 06:36 PM, Chris Steipp wrote:
I'm not able to reproduce the error (auto login is working for me) in
Chrome 25 or Firefox.
If someone is still able to reproduce this, can you let me know if:
* The images from various Special:AutoLogin pages are loading when you login
* You do (or
On 02/27/2013 05:13 PM, Paul Selitskas wrote:
Do you use the same protocol in Wikipedia and other projects? When I
first log in via HTTPS and then somehow get to HTTP, I need to log in.
We use the same protocol. We enforce HTTPS after login, and later use
protocol agnostic URLs.
--
Juliusz
On 03/09/2013 01:06 PM, Tyler Romeo wrote:
I strongly disagree that Gerrit is harder to learn than Github. The only
difficult thing to understand is the web UI, which takes only a few minutes
to really get used to. Let's look at the biggest complaints:
Let's not forget about this one:
On 03/08/2013 10:20 AM, Bartosz Dziewoński wrote:
On Fri, 08 Mar 2013 17:07:18 +0100, Antoine Musso hashar+...@free.fr
wrote:
I guess the whole idea of using GitHub is for public relation and to
attract new people. Then, if a developer is not willing to learn
Gerrit, its code is probably not
On 03/08/2013 08:55 AM, Andrew Otto wrote:
I've been hosting my puppet-cdh4 (Hadoop) repository on Github for a while now.
I am planning on moving this into Gerrit.
I've been getting pretty high quality pull requests for the last month or so
from a couple of different users. (Including
On 03/14/2013 07:19 PM, Tyler Romeo wrote:
Like I said before, if you know how to use Git, you know how to use Gerrit
(and the contra-positive is true as well). The primary thing holding people
back is that it's confusing and not user friendly enough to make an account
and get working. Imagine
On 03/14/2013 08:36 PM, Erik Moeller wrote:
And I wouldn't be too quick to celebrate the increased vendor lock-in
of a large percentage of the open source community into an ecosystem
of partially proprietary tools and services (the GitHub engine itself,
the official GitHub applications, etc.).
We've been having a hard time making photo uploads work in
MobileFrontend because of CentralAuth's third party cookies problem (we
upload them from Wikipedia web site to Commons API). Apart from the
newest Firefox [1,2], mobile Safari also doesn't accept third party
cookies unless the domain has
Thanks, but I'm afraid they won't help in solving our cookie problems. We
need a subdomain of wikipedia.org (and other projects' domains).
On Fri, Mar 22, 2013 at 9:30 PM, Daniel Zahn dz...@wikimedia.org wrote:
fyi, we have all these:
DNS:
root@sockpuppet:~/pdns-templates# ls -l | grep
On Fri, Mar 22, 2013 at 9:22 PM, MZMcBride z...@mzmcbride.com wrote:
Please draft an RFC at https://www.mediawiki.org/wiki/RFC. :-)
http://www.mediawiki.org/wiki/Requests_for_comment/Alternative_Commons_Domains
Please share your comments.
commons.wikipedia.org already redirects to
On Thu, Mar 28, 2013 at 8:45 AM, Petr Bena benap...@gmail.com wrote:
I don't know if that is actually good for anything :) but it would
surely allow you to bypass cookie restrictions everywhere (for api's
only). On the other way, I think we could just think of using some
different technology
On Thu, Mar 28, 2013 at 9:59 AM, Seb35 seb35wikipe...@gmail.com wrote:
A small issue in this proposition: sub-subdomains are not currently
covered by the https certificate.
That would make only commons.api.wikipedia.org not work, but not
commons.wikipedia.org, right?
--
Juliusz
A friend of mine is co-organizing a conference about APIs. She asked me
if there is someone from Wikimedia or the community who would be
interested in participating. It will take place in Parc 55 Hotel in San
Francisco on October 23, 24, 25. A bit of information about the conference:
APIStrat
One thing I forgot to mention: the organizers of APIStrat would like to
know if we participate or not at the beginning of next week. Please send
a short draft of a proposal to Vanessa (she is one of the organizers) if
you are interested.
On 05/07/2013 02:33 PM, Juliusz Gonera wrote:
A friend
Thank you!
On 05/31/2013 03:14 PM, Ori Livneh wrote:
Hey,
The new version of git-review released today (1.22) includes a patch I
wrote that makes it possible to work against a single 'origin' remote. This
amounts to a workaround for git-review's tendency to frighten you into
thinking you're
I wrote an RFC about scoping Common.css and Mobile.css:
https://www.mediawiki.org/wiki/Requests_for_comment/Scoping_site_CSS
In short: this could help us separate CSS rules added by administrators
from the core UI rules of MediaWiki.
What we would get:
* UI (chrome) CSS more predictable and
Thank you all for a very warm welcome. Hope to meet everyone in person soon!
On Mon, Nov 19, 2012 at 1:59 PM, Tomasz Finc tf...@wikimedia.org wrote:
I am pleased to announce that Juliusz Gonera joins WMF this week as a
Software Developer (Mobile team) today.
Juliusz has worked
39 matches
Mail list logo
