[Wikitech-l] Full name in Gerrit

2013-01-03 Thread Juliusz Gonera
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://lists.wikimedia.org/mailman/listinfo/wikitech-l


Re: [Wikitech-l] Full name in Gerrit

2013-01-03 Thread Matma Rex

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 
took any action since September last year.)

___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l


Re: [Wikitech-l] Full name in Gerrit

2013-01-03 Thread Chad
On Thu, Jan 3, 2013 at 2:30 PM, Matma Rex  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
> took any action since September last year.)
>

We're still not on 2.5.

-Chad

___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l


Re: [Wikitech-l] Full name in Gerrit

2013-01-03 Thread Juliusz Gonera

On 01/03/2013 11:52 AM, Chad wrote:

On Thu, Jan 3, 2013 at 2:30 PM, Matma Rex  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
took any action since September last year.)


We're still not on 2.5.


Thanks, it's not that important. I was just wondering if there's an easy 
way to fix it.


Juliusz

___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l


Re: [Wikitech-l] ganglia temporarily private

2013-01-03 Thread Tomasz Finc
What credentials can i use to get access ?

--tomasz


On Fri, Dec 21, 2012 at 10:47 AM, Daniel Zahn  wrote:

> re-enabled the password protection on ganglia per request
>
> ___
> Wikitech-l mailing list
> Wikitech-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l
>
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l


Re: [Wikitech-l] Full name in Gerrit

2013-01-03 Thread Željko Filipin
On Thu, Jan 3, 2013 at 8:27 PM, Juliusz Gonera wrote:

> 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".


If for some reason name is not set, "git review -d (number)" does not
work[1]:

$ git review -d 37771
Traceback (most recent call last):
  File "/usr/local/bin/git-review", line 863, in 
main()
  File "/usr/local/bin/git-review", line 801, in main
print_exit_message(download_review(options.download, branch, remote),
  File "/usr/local/bin/git-review", line 643, in download_review
author = re.sub('\W+', '_', review_info['owner']['name']).lower()
KeyError: 'name'

Željko
--
[1] https://gerrit.wikimedia.org/r/#/c/37771/
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] ganglia temporarily private

2013-01-03 Thread Jeremy Baron
On Thu, Jan 3, 2013 at 9:17 PM, Tomasz Finc  wrote:
> What credentials can i use to get access ?

27 01:59:23 < ori-l> anybody know what the l/p for ganglia is now? (pm
or e-mail)
27 02:15:57 < Reedy> ori-l: /home/wikipedia/docs/ganglia or something there of
27 02:16:32 < Reedy> /home/wikipedia/doc/ganglia.htaccess

(I assume that's a reference to fenari)

___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l


[Wikitech-l] Wikidata change propogation

2013-01-03 Thread Rob Lanphier
Hi folks,

One item that comes up pretty frequently in our regular conversations
with the Wikidata folks is the question of how change propagation
should work.  This email is largely directed at the relevant folks in
WMF's Ops and Platform Eng groups (and obviously, also the Wikidata
team), but I'm erring on the side of distributing too widely rather
than too narrowly.  I originally asked Daniel to send this (earlier
today my time, which was late in his day), but decided that even
though I'm not going to be as good at describing the technical details
(and I'm hoping he chimes in), I know a lot better what I was asking
for, so I should just write it.

The spec is here:
https://meta.wikimedia.org/wiki/Wikidata/Notes/Change_propagation#Dispatching_Changes

The thing that isn't covered here is how it works today, which I'll
try to quickly sum up.  Basically, it's a single cron job, running on
hume[1].  So, that means that when a change is made on wikidata.org,
one has to wait for this job to get around to running before the item.
 It'd be good for someone from the Wikidata team to

We've declared that Good Enough(tm) for now, where "now" is the period
of time where we'll be running the Wikidata client on a small number
of wikis (currently test2, soon Hungarian Wikipedia).

The problem is that we don't have a good plan for a permanent solution
nailed down.  It feels like we should make this work with the job
queue, but the worry is that once Wikidata clients are on every single
wiki, we're going to basically generate hundreds of jobs (one per
wiki) for every change made on the central wikidata.org wiki.

Guidance on what a permanent solution should look like?  If you'd like
to wait for Daniel to clarify some of the tech details before
answering, that's fine.

Rob

[1]  http://wikitech.wikimedia.org/view/Hume

___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l


Re: [Wikitech-l] monitoring / control system for bots

2013-01-03 Thread Lars Aronsson

On 01/02/2013 06:11 PM, Matthew Flaschen wrote:

Every wiki has a different approach to bots.  But for English Wikipedia,
that is not how the approval process
(https://en.wikipedia.org/wiki/Wikipedia:BOTAPPROVAL) works:

"Small changes, for example to fix problems or improve the operation of
a particular task, are unlikely to be an issue, but larger changes
should not be implemented without some discussion. Completely new tasks
usually require a separate approval request. Bot operators may wish to
create a separate bot account for each task."


That is what the rules say, but do you have any science
to back up that this is also how it works in practice?
How many bot accounts are revoked each month
because their owners were naughty and used their bots
in a different manner from what they applied for?
The idea with a bot account, after all, is that nobody
bothers to watch your edits in the Recent Changes.

I think you can go forward if you accept that there are
some bots that run like a machinery, according to the
rules, and other bot accounts that are used like a more
advanced browser for a creative and spontaneous user.


--
  Lars Aronsson (l...@aronsson.se)
  Aronsson Datateknik - http://aronsson.se



___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l


Re: [Wikitech-l] monitoring / control system for bots

2013-01-03 Thread [[w:en:User:Madman]]
On Thu, Jan 3, 2013 at 11:42 PM, Lars Aronsson  wrote:
> That is what the rules say, but do you have any science
> to back up that this is also how it works in practice?
> How many bot accounts are revoked each month
> because their owners were naughty and used their bots
> in a different manner from what they applied for?
> The idea with a bot account, after all, is that nobody
> bothers to watch your edits in the Recent Changes.

That *is* how it works in practice. Bots get blocked for running
unapproved tasks. Most contributors may not watch bots' edits in the
Recent Changes, but they do notice when their articles are edited.
Approved tasks aren't typically revoked, as that usually would be
punitive and unnecessary, but it does happen; for an example of all
approved tasks for a bot being revoked due to inappropriate and
unapproved tasks, please see
http://en.wikipedia.org/wiki/Wikipedia_talk:Bot_Approvals_Group/Archive_8#Kumi-Taskbot.

> I think you can go forward if you accept that there are
> some bots that run like a machinery, according to the
> rules, and other bot accounts that are used like a more
> advanced browser for a creative and spontaneous user.

Bots are *not* advanced browsers and they're not treated as such by
enwiki's bot policy. That's what AWB (hence the name) and gadgets are
for. The BAG has granted some broad approvals in the past, but I think
you'll find that's pretty rare these days.

> --
>   Lars Aronsson (l...@aronsson.se)
>   Aronsson Datateknik - http://aronsson.se

-madman

___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l


Re: [Wikitech-l] Wikidata change propogation

2013-01-03 Thread Rob Lanphier
On Thu, Jan 3, 2013 at 2:57 PM, Rob Lanphier  wrote:
> The thing that isn't covered here is how it works today, which I'll
> try to quickly sum up.  Basically, it's a single cron job, running on
> hume[1].  So, that means that when a change is made on wikidata.org,
> one has to wait for this job to get around to running before the item.
>  It'd be good for someone from the Wikidata team to

*sigh* the dangers of sending email in haste (and being someone who
frequently composes email non-linearly).  What I meant to say was
this:

When a change is made on wikidata.org with the intent of updating an
arbitrary wiki (say, Hungarian Wikipedia), one has to wait for this
single job to get around to running the update on whatever wikis are
in line prior to Hungarian WP before it gets around to updating that
wiki, which could be hundreds of wikis.  That isn't *such* a big deal,
because the alternative is to purge the page, which will also work.

Another problem is that this is running on a specific, named machine.
This will likely get to be a big enough job that one machine won't be
enough, and we'll need to scale this up.

It would be good for Daniel or someone else from the Wikidata team to
chime in to verify I'm characterizing the problem correctly.

Rob

___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l