Re: [Wikitech-l] Nagios is dead, long live icinga!

[Matthew Flaschen]

On 02/26/2013 11:55 PM, Leslie Carr wrote:
> Thanks - I'll try to get status.wikimedia updated in the morning.
> 
> Can you try with https now  ? I had forgotten to reload apache when
> pushing out a change to the https config (to allow https without
> login).  You can also use http.

HTTPS works.

Thanks,

Matt Flaschen

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

Re: [Wikitech-l] Nagios is dead, long live icinga!

[Leslie Carr]

Thanks - I'll try to get status.wikimedia updated in the morning.

Can you try with https now  ? I had forgotten to reload apache when
pushing out a change to the https config (to allow https without
login).  You can also use http.

On Tue, Feb 26, 2013 at 8:46 PM, Matthew Flaschen
 wrote:
> On 02/26/2013 11:35 PM, Jeremy Baron wrote:
>> On Feb 26, 2013 11:25 PM, "Matthew Bowker" 
>> wrote:
>>> I hate to be "that guy," but is it supposed to be password protected? Is
>> there somewhere non-ops people can look for server status, or is
>> http://status.wikimedia.org it?
>>
>> try HTTP instead of HTTPS. (I don't know anything about why they're not the
>> same or how long they've been like that.)
>
> Nagios shows as "disruption" on the HTTP (http://status.wikimedia.org/)
>
> Matt Flaschen
>
> ___
> Wikitech-l mailing list
> Wikitech-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l



-- 
Leslie Carr
Wikimedia Foundation
AS 14907, 43821
http://as14907.peeringdb.com/

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

Re: [Wikitech-l] Nagios is dead, long live icinga!

[Matthew Flaschen]

On 02/26/2013 11:35 PM, Jeremy Baron wrote:
> On Feb 26, 2013 11:25 PM, "Matthew Bowker" 
> wrote:
>> I hate to be "that guy," but is it supposed to be password protected? Is
> there somewhere non-ops people can look for server status, or is
> http://status.wikimedia.org it?
> 
> try HTTP instead of HTTPS. (I don't know anything about why they're not the
> same or how long they've been like that.)

Nagios shows as "disruption" on the HTTP (http://status.wikimedia.org/)

Matt Flaschen

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

Re: [Wikitech-l] Nagios is dead, long live icinga!

[Jay Ashworth]

- Original Message -
> From: "Jeremy Baron" 

> On Feb 26, 2013 11:25 PM, "Matthew Bowker"
> 
> wrote:
> > I hate to be "that guy," but is it supposed to be password
> > protected? Is
> there somewhere non-ops people can look for server status, or is
> http://status.wikimedia.org it?
> 
> try HTTP instead of HTTPS. (I don't know anything about why they're
> not the same or how long they've been like that.)

Noted.

Understand that for people who have HTTPS-anywhere installed (which should
be approximately everyone by now), that will be a common question.

Cheers,
- jra
-- 
Jay R. Ashworth  Baylink   j...@baylink.com
Designer The Things I Think   RFC 2100
Ashworth & Associates http://baylink.pitas.com 2000 Land Rover DII
St Petersburg FL USA   #natog  +1 727 647 1274

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

Re: [Wikitech-l] Nagios is dead, long live icinga!

[Jeremy Baron]

On Feb 26, 2013 11:25 PM, "Matthew Bowker" 
wrote:
> I hate to be "that guy," but is it supposed to be password protected? Is
there somewhere non-ops people can look for server status, or is
http://status.wikimedia.org it?

try HTTP instead of HTTPS. (I don't know anything about why they're not the
same or how long they've been like that.)

> On a slightly un-related note, nagios-wm is still in the IRC channels.
 Does that mean Nagios will still be providing the IRC feed?

There's also an icinga-wm. Not sure how long we'll have both. If I had to
guess I'd say having then both is intentional for now.

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

Re: [Wikitech-l] Nagios is dead, long live icinga!

[Jay Ashworth]

- Original Message -
> From: "Leslie Carr" 

> Icinga is public.

It may be, but that URL goes to an HTTPS Auth dialog, with nothing 
behind it if one cancels.  Perhaps something was missed?
-- jra
-- 
Jay R. Ashworth  Baylink   j...@baylink.com
Designer The Things I Think   RFC 2100
Ashworth & Associates http://baylink.pitas.com 2000 Land Rover DII
St Petersburg FL USA   #natog  +1 727 647 1274

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

Re: [Wikitech-l] Nagios is dead, long live icinga!

[Matthew Bowker]

I hate to be "that guy," but is it supposed to be password protected? Is there 
somewhere non-ops people can look for server status, or is 
http://status.wikimedia.org it?  

On a slightly un-related note, nagios-wm is still in the IRC channels.  Does 
that mean Nagios will still be providing the IRC feed?

Matthew Bowker
http://en.wikipedia.org/wiki/User:Matthewrbowker

On Feb 26, 2013, at 8:59 PM, Jay Ashworth  wrote:

> - Original Message -
>> From: "Liangent" 
> 
>>> nagios.wikimedia.org now redirects to icinga.wikimedia.org ! Please
>>> let us know if you notice anything that has broken or is
>>> inconsistent.
>> 
>> So now there's no public view of server monitoring info?
>> 
>> http://status.wikimedia.org/ always shows nagios as disrupted now.
> 
> No, having done this sort of thing before, I would speculate that it
> just slipped off their checklist, and they thank you for reminding them.
> 
> I thank you for reminding *me* that was there in the first place, though
> I see that I once knew, for it is already listed here:
> 
>   http://wiki.outages.org/index.php/Dashboard
> 
> Cheers,
> -- jra
> -- 
> Jay R. Ashworth  Baylink   
> j...@baylink.com
> Designer The Things I Think   RFC 2100
> Ashworth & Associates http://baylink.pitas.com 2000 Land Rover DII
> St Petersburg FL USA   #natog  +1 727 647 1274
> 
> ___
> 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] Nagios is dead, long live icinga!

[Leslie Carr]

Icinga is public.
On Feb 26, 2013 7:49 PM, "Liangent"  wrote:

> On Wed, Feb 27, 2013 at 9:32 AM, Leslie Carr  wrote:
> > As some may have noticed, we are phasing out nagios in favor of icinga
> > ( https://www.icinga.org/ )
> >
> > nagios.wikimedia.org now redirects to icinga.wikimedia.org ! Please
> > let us know if you notice anything that has broken or is inconsistent.
>
> So now there's no public view of server monitoring info?
>
> http://status.wikimedia.org/ always shows nagios as disrupted now.
>
> -Liangent
>
> >
> > Thanks
> > Leslie
> >
> >
> >
> > --
> > Leslie Carr
> > Wikimedia Foundation
> > AS 14907, 43821
> > http://as14907.peeringdb.com/
> >
> > ___
> > 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
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Nagios is dead, long live icinga!

[Jay Ashworth]

- Original Message -
> From: "Liangent" 

> > nagios.wikimedia.org now redirects to icinga.wikimedia.org ! Please
> > let us know if you notice anything that has broken or is
> > inconsistent.
> 
> So now there's no public view of server monitoring info?
> 
> http://status.wikimedia.org/ always shows nagios as disrupted now.

No, having done this sort of thing before, I would speculate that it
just slipped off their checklist, and they thank you for reminding them.

I thank you for reminding *me* that was there in the first place, though
I see that I once knew, for it is already listed here:

   http://wiki.outages.org/index.php/Dashboard

Cheers,
-- jra
-- 
Jay R. Ashworth  Baylink   j...@baylink.com
Designer The Things I Think   RFC 2100
Ashworth & Associates http://baylink.pitas.com 2000 Land Rover DII
St Petersburg FL USA   #natog  +1 727 647 1274

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

Re: [Wikitech-l] Nagios is dead, long live icinga!

[Liangent]

On Wed, Feb 27, 2013 at 9:32 AM, Leslie Carr  wrote:
> As some may have noticed, we are phasing out nagios in favor of icinga
> ( https://www.icinga.org/ )
>
> nagios.wikimedia.org now redirects to icinga.wikimedia.org ! Please
> let us know if you notice anything that has broken or is inconsistent.

So now there's no public view of server monitoring info?

http://status.wikimedia.org/ always shows nagios as disrupted now.

-Liangent

>
> Thanks
> Leslie
>
>
>
> --
> Leslie Carr
> Wikimedia Foundation
> AS 14907, 43821
> http://as14907.peeringdb.com/
>
> ___
> 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] Nagios is dead, long live icinga!

[Jay Ashworth]

- Original Message -
> From: "Ryan Lane" 

> On Tue, Feb 26, 2013 at 5:32 PM, Leslie Carr 
> wrote:
> 
> > As some may have noticed, we are phasing out nagios in favor of
> > icinga ( https://www.icinga.org/ )
> >
> > nagios.wikimedia.org now redirects to icinga.wikimedia.org ! Please
> > let us know if you notice anything that has broken or is
> > inconsistent.

> Awesome work Leslie!

And thanks for the pointer, too; didn't realize the fork had happened.

Cheers,
-- jra
-- 
Jay R. Ashworth  Baylink   j...@baylink.com
Designer The Things I Think   RFC 2100
Ashworth & Associates http://baylink.pitas.com 2000 Land Rover DII
St Petersburg FL USA   #natog  +1 727 647 1274

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

Re: [Wikitech-l] Nagios is dead, long live icinga!

[Damian Zaremba]

In the words of Gerrit +2 looks good to me!

Awesome job :)

- Damian

On 27/02/2013 01:42, Alolita Sharma wrote:

++1 Leslie!

-Alolita

On Tue, Feb 26, 2013 at 5:39 PM, Ryan Lane  wrote:


On Tue, Feb 26, 2013 at 5:32 PM, Leslie Carr  wrote:


As some may have noticed, we are phasing out nagios in favor of icinga
( https://www.icinga.org/ )

nagios.wikimedia.org now redirects to icinga.wikimedia.org ! Please
let us know if you notice anything that has broken or is inconsistent.



Awesome work Leslie!

- Ryan
___
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] Nagios is dead, long live icinga!

[Alolita Sharma]

++1 Leslie!

-Alolita

On Tue, Feb 26, 2013 at 5:39 PM, Ryan Lane  wrote:

> On Tue, Feb 26, 2013 at 5:32 PM, Leslie Carr  wrote:
>
> > As some may have noticed, we are phasing out nagios in favor of icinga
> > ( https://www.icinga.org/ )
> >
> > nagios.wikimedia.org now redirects to icinga.wikimedia.org ! Please
> > let us know if you notice anything that has broken or is inconsistent.
> >
> >
> Awesome work Leslie!
>
> - Ryan
> ___
> Wikitech-l mailing list
> Wikitech-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l
>



-- 
Alolita Sharma
Director of Engineering
Language Engineering
Wikimedia Foundation
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Nagios is dead, long live icinga!

[Ryan Lane]

On Tue, Feb 26, 2013 at 5:32 PM, Leslie Carr  wrote:

> As some may have noticed, we are phasing out nagios in favor of icinga
> ( https://www.icinga.org/ )
>
> nagios.wikimedia.org now redirects to icinga.wikimedia.org ! Please
> let us know if you notice anything that has broken or is inconsistent.
>
>
Awesome work Leslie!

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

[Wikitech-l] Nagios is dead, long live icinga!

[Leslie Carr]

As some may have noticed, we are phasing out nagios in favor of icinga
( https://www.icinga.org/ )

nagios.wikimedia.org now redirects to icinga.wikimedia.org ! Please
let us know if you notice anything that has broken or is inconsistent.

Thanks
Leslie



-- 
Leslie Carr
Wikimedia Foundation
AS 14907, 43821
http://as14907.peeringdb.com/

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

Re: [Wikitech-l] Developer Hub simplification (was Re: Gsoc 2013 guidelines)

[Waldir Pimenta]

Thanks for the pointer.

My main concern with that page and most documentation on mw.org (and the
reason I started a personal list, so I could quickly find the stuff that
matters to me) is that it's too massive, with too many links (as you noted
yourself) and too much stuff highlighted, and I honestly feel a little
overwhelmed reading it, finding myself following links only to find out
that their target doesn't provide the information at the abstraction level
that I expected.

I'll speculate a little, and suggest that the root of this disorientation
happens due to not separating reference docs from tutorial docs, from what
I'll call "guided overviews", and allowing each of these to clearly assume
one of those identities.

The list I've been putting together comprises reference docs, essentially
index-like material that one can look up whenever one needs information on
a specific part of mediawiki; There isn't much done in this regard. Brion
once started a page which he called "Module
registry",
in 2009, which looked promising but it wasn't updated since.

Tutorials should be mostly aimed at absolute newcomers: very short, and
with a rather gentle learning curve; i.e., they should not introduce too
many concepts too fast, nor assume a lot of previous knowledge. modular,
interconnected compoments should be described in separate pages and
hyperlinked so budding developers can RTFM, choose-your-own-adventure
style. Currently very little of the docs fit that goal.

Guided overviews are like Wikipedia articles: long, descriptive and mostly
sequential texts describing an important component of the mediawiki
infrastructure, such as the skinning system, or the messages API. I
actually am not sure about the usefulness of such long guides, since
newcomers will have a hard time following them, and experts will likely
benefit more from index-like reference material. Maybe they should be
broken down into interconnected bite-sized tutorials.

I just came up with these categories, so there are probably many flaws to
this analysis, but at a glance this seems like a good-enough overview of
the state of our docs and what (in my humble opinion) needs to be done.
Maybe my position won't be shared by many, but I'll be content if it causes
some discussion about what overall strategy we need to implement to improve
MW docs (which is undeniably considered important: let's not forget it's
bug #1).

--Waldir

On Tue, Feb 26, 2013 at 10:14 PM, Quim Gil  wrote:

> On 02/26/2013 06:40 AM, Waldir Pimenta wrote:
>
>> I've been collecting a few links at
>> http://www.mediawiki.org/?**oldid=651991#MediaWiki_**reference
>> that might be useful for newcomer developers to get a first overview of
>> various components of the MediaWiki universe.
>>
>
> Your help is welcome aligning your selection with
> http://www.mediawiki.org/wiki/**Developer_hub
>
> By the way, do we really need 23 links under "Key documents",
> after the 23 links contained at the "Overview" section,
> following the first paragraph containing 5 links?
>
> No wonder someone like Atul keeps asking about what to read for a first
> contribution.
>
>  Let me know if those are helpful to you and what you think is missing from
>> that list. Bear in mind that it's a work in progress, though.
>>
>
>
> --
> Quim Gil
> Technical Contributor Coordinator @ Wikimedia Foundation
> http://www.mediawiki.org/wiki/**User:Qgil
>
> __**_
> 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] Nominating Mark Hershberger as core maintainer

[Alolita Sharma]

Great to hear this! Thanks for your efforts Mark!

-Alolita

On Mon, Feb 25, 2013 at 9:41 AM, Sumana Harihareswara
 wrote:
> On 02/21/2013 07:53 AM, Siebrand Mazeland (WMF) wrote:
>> I've nominated Mark Hershberger as MediaWiki core maintainer in Gerrit.
>> Please provide your feedback at the following URL:
>>
>> https://www.mediawiki.org/wiki/Git/Gerrit_project_ownership#hexmode_.2F_Mark_Hershberger_for_MediaWiki_core
>>
>> Cheers!
>
> I believe we have consensus so I have added him to the list of MediaWiki
> core maintainers.  Thank you, Mark, for your work.
>
> --
> Sumana Harihareswara
> Engineering Community Manager
> Wikimedia Foundation
>
> ___
> 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] [Labs-l] Merging wikitech and labsconsole on Thursday at 1 PM PDT

[Ryan Lane]

On Tue, Feb 26, 2013 at 2:46 PM, Petr Bena  wrote:

> the labsconsole will remain operational? or it will redirect?
>
>
labsconsole will redirect.

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

Re: [Wikitech-l] [Engineering] Merging wikitech and labsconsole on Thursday at 1 PM PDT

[Ryan Lane]

On Tue, Feb 26, 2013 at 2:43 PM, MZMcBride  wrote:

> Ryan Lane wrote:
> > At 1 PM I'll do the following:
> >
> > 1. Mark wikitech as read-only
> > 2. Add wikitech-old.wikimedia.org, pointing at the old wiki
> > 3. Change wikitech.wikimedia.org to labsconsole's IP
> > 4. Import all of the content to labsconsole
> > 5. Change labsconsole.wikimedia.org to wikitech.wikimedia.org
> >
> >[...]
>
> labsconsole.wikimedia.org and wikitech.wikimedia.org have different
> article view paths:
>
> * https://labsconsole.wikimedia.org/wiki/Main_Page
> * http://wikitech.wikimedia.org/view/Main_Page
>
> As long as the wikitech.wikimedia.org/view/ URL forms continue to work, I
> don't see any issue here. I suppose there are a few different ways to
> support this.
>
>

I have a rewrite rule on the new server for this, that I pushed in
yesterday:

https://gerrit.wikimedia.org/r/#/c/50856/

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

Re: [Wikitech-l] [Engineering] Merging wikitech and labsconsole on Thursday at 1 PM PDT

[Petr Bena]

I don't really see problems with view -> wiki but problem might be to
redirect labsconsole to wikitech, as there are some bots using
labsconsole api now (these will possibly break) but not a big deal, I
would rather be ready for that

On Tue, Feb 26, 2013 at 11:43 PM, MZMcBride  wrote:
> Ryan Lane wrote:
>> At 1 PM I'll do the following:
>>
>> 1. Mark wikitech as read-only
>> 2. Add wikitech-old.wikimedia.org, pointing at the old wiki
>> 3. Change wikitech.wikimedia.org to labsconsole's IP
>> 4. Import all of the content to labsconsole
>> 5. Change labsconsole.wikimedia.org to wikitech.wikimedia.org
>>
>>[...]
>
> labsconsole.wikimedia.org and wikitech.wikimedia.org have different
> article view paths:
>
> * https://labsconsole.wikimedia.org/wiki/Main_Page
> * http://wikitech.wikimedia.org/view/Main_Page
>
> As long as the wikitech.wikimedia.org/view/ URL forms continue to work, I
> don't see any issue here. I suppose there are a few different ways to
> support this.
>
> MZMcBride
>
>
>
> ___
> 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] [Labs-l] Merging wikitech and labsconsole on Thursday at 1 PM PDT

[Petr Bena]

the labsconsole will remain operational? or it will redirect?

On Tue, Feb 26, 2013 at 11:22 PM, Greg Grossmeier  wrote:
> 
>> If you believe there's a time conflict with this migration let me know and
>> I can reschedule it.
>
> Good from my perspective.
>
> Greg
>
> --
> | Greg GrossmeierGPG: B2FA 27B1 F7EB D327 6B8E |
> | Release Manager A18D 1138 8E47 FAC8 1C7D |
>
> ___
> 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] [Engineering] Merging wikitech and labsconsole on Thursday at 1 PM PDT

[MZMcBride]

Ryan Lane wrote:
> At 1 PM I'll do the following:
>
> 1. Mark wikitech as read-only
> 2. Add wikitech-old.wikimedia.org, pointing at the old wiki
> 3. Change wikitech.wikimedia.org to labsconsole's IP
> 4. Import all of the content to labsconsole
> 5. Change labsconsole.wikimedia.org to wikitech.wikimedia.org
>
>[...]

labsconsole.wikimedia.org and wikitech.wikimedia.org have different
article view paths:

* https://labsconsole.wikimedia.org/wiki/Main_Page
* http://wikitech.wikimedia.org/view/Main_Page

As long as the wikitech.wikimedia.org/view/ URL forms continue to work, I
don't see any issue here. I suppose there are a few different ways to
support this.

MZMcBride



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

Re: [Wikitech-l] [Labs-l] Merging wikitech and labsconsole on Thursday at 1 PM PDT

[Greg Grossmeier]

> If you believe there's a time conflict with this migration let me know and
> I can reschedule it.

Good from my perspective.

Greg

-- 
| Greg GrossmeierGPG: B2FA 27B1 F7EB D327 6B8E |
| Release Manager A18D 1138 8E47 FAC8 1C7D |

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

Re: [Wikitech-l] [Engineering] Merging wikitech and labsconsole on Thursday at 1 PM PDT

[Steven Walling]

May the force be with you.


On Tue, Feb 26, 2013 at 2:08 PM, Ryan Lane  wrote:

> At 1 PM I'll do the following:
>
> 1. Mark wikitech as read-only
> 2. Add wikitech-old.wikimedia.org, pointing at the old wiki
> 3. Change wikitech.wikimedia.org to labsconsole's IP
> 4. Import all of the content to labsconsole
> 5. Change labsconsole.wikimedia.org to wikitech.wikimedia.org
>
> I anticipate the process to take roughly an hour. I'll do an export of
> wikitech prior to setting it read-only, so that we'll have as little
> downtime as possible. I'll do a second export/import to ensure all changes
> are accounted for.
>
> If you believe there's a time conflict with this migration let me know and
> I can reschedule it.
>
> - Ryan
>
> ___
> Engineering mailing list
> engineer...@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/engineering
>
>


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

[Wikitech-l] Developer Hub simplification (was Re: Gsoc 2013 guidelines)

[Quim Gil]

On 02/26/2013 06:40 AM, Waldir Pimenta wrote:

I've been collecting a few links at
http://www.mediawiki.org/?oldid=651991#MediaWiki_reference
that might be useful for newcomer developers to get a first overview of
various components of the MediaWiki universe.


Your help is welcome aligning your selection with 
http://www.mediawiki.org/wiki/Developer_hub


By the way, do we really need 23 links under "Key documents",
after the 23 links contained at the "Overview" section,
following the first paragraph containing 5 links?

No wonder someone like Atul keeps asking about what to read for a first 
contribution.



Let me know if those are helpful to you and what you think is missing from
that list. Bear in mind that it's a work in progress, though.



--
Quim Gil
Technical Contributor Coordinator @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil

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

Re: [Wikitech-l] Gsoc 2013 guidelines

[Quim Gil]

On 02/26/2013 08:29 AM, Yuri Astrakhan wrote:

I am not sure how GSOC supervision functions, but I
will definitely be involved with the implementation.


Everything starts with you (and any other potential mentors) adding 
yourself to https://www.mediawiki.org/wiki/Summer_of_Code_2013#Mentors :)


--
Quim Gil
Technical Contributor Coordinator @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil

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

Re: [Wikitech-l] Gerrit reports

[Matthew Flaschen]

On 02/19/2013 02:36 AM, MZMcBride wrote:
> Hi.
> 
> I wrote  over the weekend.

Cool!  And a creative bot name, as always.

Matt Flaschen

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

Re: [Wikitech-l] Better non-MySQL db support

[Matthew Flaschen]

On 02/26/2013 02:14 PM, Luke Welling WMF wrote:
> Specifically, do we use MySQL specific syntax that is more efficient (but
> breaks elsewhere) or do we attempt to write lowest common denominator SQL
> that will run more places, but not run as efficiently on our primary target?

There's a DB layer for runtime operations (select, update, insert,
etc.), and my understanding is that's supposed to be used for pretty
much everything.

However, part of the optimization is choosing indices, which as you
noted is db-specific (part of tables.sql)

Matt Flaschen

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

Re: [Wikitech-l] Blame maps aka authorship detection

[Matthew Flaschen]

On 02/26/2013 02:29 AM, Luca de Alfaro wrote:
>- We need a way to poll the database for things like what are all
>revision_ids of a given page.  We could use the API instead, but it's less
>efficient.

Yes, as others have said LAbs should allow that either now or shortly.
You should sign up for
https://lists.wikimedia.org/mailman/listinfo/labs-l and feel free to ask
Labs questions there.

>- We need a place where to store the authorship information.  This is
>several terabytes for enwiki.  Basically, we need access to some text
>store.  Is this available on labs?

I don't know if you'll be able to get that or not.  You'll have to make
a special request.

Matt Flaschen

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

Re: [Wikitech-l] Gerrit reports

[Jon Robson]

Thanks MZ. This is really useful!

On Mon, Feb 18, 2013 at 11:36 PM, MZMcBride  wrote:
> Hi.
>
> I wrote  over the weekend.
>
> MZMcBride
>
>
>
> ___
> Wikitech-l mailing list
> Wikitech-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l



-- 
Jon Robson
http://jonrobson.me.uk
@rakugojon

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

Re: [Wikitech-l] Gerrit: fatal: Couldn't find remote ref

[Matthew Walker]

I'm an idiot. I was in a submodule instead of core where that patch
actually was (thanks for that Tim!)

~Matt Walker
Wikimedia Foundation
Fundraising Technology Team


On Tue, Feb 26, 2013 at 11:42 AM, Matthew Walker wrote:

> Chad (or anyone else that might know),
>
> I've a patch [1] that's been hanging out in gerrit for a while, and I was
> going to go back and revise it but for some reason I cannot get git review
> to download it. It gives a fatal: Couldn't find remote ref
> refs/changes/24/44224/10. Manually doing a git ls-remote doesn't show it
> either. Other patch sets in the same repo are not affected, I can git
> review -d all the ones I tested.
>
> I've made sure my machine is fully up to date (ie: ran git fetch); and I
> tried rebasing the patchset via gerrit web to see if that would create the
> ref. No such luck :(
>
> Any idea what's going on? Or how to fix it? (is my machine just crazy?)
>
> [1] https://gerrit.wikimedia.org/r/#/c/44224/
>
> ~Matt Walker
> Wikimedia Foundation
> Fundraising Technology Team
>
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] Gerrit: fatal: Couldn't find remote ref

[Matthew Walker]

Chad (or anyone else that might know),

I've a patch [1] that's been hanging out in gerrit for a while, and I was
going to go back and revise it but for some reason I cannot get git review
to download it. It gives a fatal: Couldn't find remote ref
refs/changes/24/44224/10. Manually doing a git ls-remote doesn't show it
either. Other patch sets in the same repo are not affected, I can git
review -d all the ones I tested.

I've made sure my machine is fully up to date (ie: ran git fetch); and I
tried rebasing the patchset via gerrit web to see if that would create the
ref. No such luck :(

Any idea what's going on? Or how to fix it? (is my machine just crazy?)

[1] https://gerrit.wikimedia.org/r/#/c/44224/

~Matt Walker
Wikimedia Foundation
Fundraising Technology Team
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Better non-MySQL db support

[Marc A. Pelletier]

On 02/26/2013 02:14 PM, Luke Welling WMF wrote:

Do we have an official position on cross database compatibility?


It would be nice if we did.  In my own production environments, I always 
use postgres.  To date, mw has been "good enough" with its support that 
I've never had significant integration problems, but looking forward is 
always a little worrying.


-- Marc


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

Re: [Wikitech-l] DevOps/Continuous Deployment discussion?

[Jay Ashworth]

- Original Message -
> From: "Juliusz Gonera" 

> 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?

The ones who accidentally shipped a brown-paper-bag bug 2 days ago. ;-)

Cheers,
-- jra
-- 
Jay R. Ashworth  Baylink   j...@baylink.com
Designer The Things I Think   RFC 2100
Ashworth & Associates http://baylink.pitas.com 2000 Land Rover DII
St Petersburg FL USA   #natog  +1 727 647 1274

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

Re: [Wikitech-l] Better non-MySQL db support

[Luke Welling WMF]

Do we have an official position on cross database compatibility?

Some of the MediaWiki SQL is in separate files and can be easily directed
at a specific database engine.  A lot of it though is scattered as
fragments though other code and is going to be run on any engine we connect
to.

Specifically, do we use MySQL specific syntax that is more efficient (but
breaks elsewhere) or do we attempt to write lowest common denominator SQL
that will run more places, but not run as efficiently on our primary target?

The only SQL coding standard doc I have seen treats Database and MySQL as
synonyms: http://www.mediawiki.org/wiki/Manual:Coding_conventions/Database

Luke Welling


On Tue, Feb 26, 2013 at 5:37 AM, Dmitriy Sintsov  wrote:

>
>
>  26 Февраль 2013 г. 14:27:06 пользователь Nikola Smolenski (
>> smole...@eunet.rs) написал:
>>
>>
>> On 26/02/13 04:18, Matthew Flaschen wrote:
>> > Sure, for starters. :) Bear in mind, if we want to keep support for all
>> > these dbs, every change to the database schema has to (at some point)
>> > result in a change to separate SQL files for each DB (MySQL and SQLite
>> > use the same ones).For instance, there is a separate active
>> > oracle/tables.sql.
>> I am wondering if it would make sense to give up on SQL, make universal
>> table creation functions in PHP, the same way there are for other queries,
>> and use that. Has anyone tried this before, is there other software that
>> works like this?
>>
>
> http://stackoverflow.com/**questions/108699/good-php-orm-**library
>
> By the way, MySQL 5.6 is out and it supports fulltext search indexation
> for InnoDB tables. They also promise better peformance on large hardware.
> Still cannot find 12.04 ppa for 5.6.10, though and do not want to go
> troubles installing from source (although I installed MySQL from source
> some years ago)..
> Why going another database engines besides MySQL / MariaDB?
> Dmitriy
>
>
> __**_
> 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] Gsoc 2013 guidelines

[Nischay Nahata]

On Tue, Feb 26, 2013 at 9:59 PM, Yuri Astrakhan wrote:

> Atul, one of the fun projects that has been sitting on my backburner is to
> implement errors and warnings localization for the Web API. The project
> would involve some planning, figuring out translation framework, and later
> - converting all API modules and extensions to use it. As a result, all
> clients, including mobile, will be able to report errors to the users in
> their native language. I am not sure how GSOC supervision functions, but I
> will definitely be involved with the implementation.
>
> This is slightly bigger than a bug fix, but should be fairly independent
> from everything and will give you good exposure into internals as well as
> javascript and other  clients.
>
>
>
I think this is a potential 'good' project itself. There are also small
tasks associated that the applicant can learn from, say properly handle
the errors and warnings in an extension that doesn't already do it.


> On Tue, Feb 26, 2013 at 11:20 AM, Atul Agrawal 
> wrote:
>
> > @Waldir:working on the link you sent me.I will notify you if I need any
> > help
> >
> > @Quim:While I will love to work under a project and be guided .It will be
> > great if you can suggest some beginner level project and  I can work with
> > someone or by my own.
> > I will like to solve arithmetic bugs,logical bugs,deadlock situation and
> > teamworking bugs.
> > And one more thing as mediaWiki documentation is so vast, how will I know
> > in which specific area I have to develop my skills so that I will able to
> > get the idea as well as solve it which will be proposed for gsoc 2013?Do
> I
> > need to contact the mentors?
> >
> > Thanks for being so helpful.
> >
> > Atul
> >
> >
> >
> > On Tue, Feb 26, 2013 at 9:13 PM, Quim Gil  wrote:
> >
> > > On 02/26/2013 01:23 AM, Atul Agrawal wrote:
> > >
> > >> Thanks a lot.Will try to fix bugs.But what knowledge should I have to
> > fix
> > >> bugs?knowing php is sufficient?Till now I have read this page(
> > >> Developing_Extensions > >> Developing_extensions<
> > http://www.mediawiki.org/wiki/Manual:Developing_extensions>
> > >> >.If
> > >> you can share the documents one should read before fixing bugs,I will
> be
> > >> highly obliged.
> > >>
> > >
> > > We have many different software projects, and what to read depends pon
> > > what bugs you want to fix.
> > >
> > > Why not choosing first a project or a bug that interests you, and then
> > > learn about the pieces involved as you try to fix it?
> > >
> > > We can help you find a first bug. What is your area of interest?
> > >
> > >
> > > --
> > > Quim Gil
> > > Technical Contributor Coordinator @ Wikimedia Foundation
> > > http://www.mediawiki.org/wiki/**User:Qgil<
> > http://www.mediawiki.org/wiki/User:Qgil>
> > >
> > > __**_
> > > Wikitech-l mailing list
> > > Wikitech-l@lists.wikimedia.org
> > > https://lists.wikimedia.org/**mailman/listinfo/wikitech-l<
> > https://lists.wikimedia.org/mailman/listinfo/wikitech-l>
> > >
> >
> >
> >
> > --
> > Atul Agrawal
> > B.E Mechanical
> > BITS PILANI Goa Campus
> > Mobile:+91-81491-95049
> > ___
> > 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
>



-- 
Cheers,

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

Re: [Wikitech-l] DevOps/Continuous Deployment discussion?

[Juliusz Gonera]

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, take more than 15 
minutes (or less). Later, populating everything to all the machines 
should be fully automatic and not require any kind of human supervision. 
A report should be generated at the end. If something goes wrong, then 
an alert should be sent to someone responsible.


I never deployed on that scale before but I did read a bit how other 
projects deal with this and talked to some people. Definitely, a staging 
environment which mirrors production would help a lot. I hope we'll get 
there soon.


I know that Facebook has something like an internal bleeding edge 
version that is used by their employees. It works with the same database 
as the official Facebook so employees can use it just like they would 
use Facebook any day. This gives them an opportunity to test many things 
manually before they go live for millions of people without actually 
wasting time on boring testing, but just by using the product. I don't 
know the details but I think they sync the production with bleeding edge 
once or twice a week.


--
Juliusz

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

Re: [Wikitech-l] Blame maps aka authorship detection

[Gabriel Wicke]

Hi Luca,

we are working on somewhat related issues in Parsoid [1][2]. The
modified HTML DOM is diffed vs. the original DOM on the way in. Each
modified node is annotated with the base revision. We don't store this
information yet- right now we use it to selectively serialize modified
parts of the page back to wikitext. We will however soon store the HTML
along with wikitext for each revision, which should make it possible to
display a coarse blame map.

There are several limitations:

* We don't preserve blame information on wikitext edits yet. This should
become possible with the incremental re-parsing optimization which is on
our roadmap for this summer.

* Our DOM diff algorithm is extremely simplistic. We are considering to
port XyDiff for better move detection.

* The information is pretty coarse at a node level. Refining this to a
word level would require an efficient encoding for that information,
possibly as length/revision pairs associated with the wrapping element.

* We have not moved metadata from attributes to a metadata section with
efficient encoding yet.

We don't currently plan to work on blame maps ourselves. Maybe there are
opportunities for collaboration?

Gabriel

[1]: http://www.mediawiki.org/wiki/Parsoid
[2]: http://www.mediawiki.org/wiki/Parsoid/Roadmap

-- 
Gabriel Wicke
Senior Software Engineer
Wikimedia Foundation

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

Re: [Wikitech-l] DevOps/Continuous Deployment discussion?

[Matthew Flaschen]

On 02/20/2013 05:56 PM, Arthur Richards wrote:
> Once we have MobileFrontend working properly (in a production-like manner)
> on betalabs, we'll be a big step closer to this - particularly once
> betalabs is continuously updating to head of master for MobileFrontend. I
> believe a majority of the problems we find during MobileFrontend
> deployments would get caught during QA/testing in this environment.

That would be very helpful for E3 too.  It would be a bonus if alternate
branches (e.g. a feature branch could be automatically deployed to a
different wiki (e.g. in labs).

Matt Flaschen

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

Re: [Wikitech-l] Do we need to change the MW release process to better involve the non-WMF community?

[Chris McMahon]

On Fri, Feb 22, 2013 at 7:06 PM, Matthew Flaschen
wrote:

> On 02/22/2013 09:38 PM, Chad wrote:
> > So, I've seen this site tossed around quite a bit recently, and I'm
> curious:
> > is there any plan to start integrating this jenkins and our other
> jenkins?
>

Depends on what you mean by "integrate".   Right now the sweet spot for
browser tests shown at https://wmf.ci.cloudbees.com/ is to track the
deployment schedule over individual code commits and to target integrated
institutional test environments like test2wiki and beta cluster, while
https://integration.mediawiki.org/ci/ mostly targets unit-type tests run on
the Jenkins host itself.  There are a lot of builds there right now already.

In the longer term we want to have browser tests targeting more specialized
test environments and more granular code commits.  There are lots of ways
that Jenkins instances can share data, so when that sort of activity comes
along we'll figure out the details at that time.

> More importantly: is there any chance to get the results of these sorts of
> > tests in Gerrit? I think it's great that we're expanding test coverage,
> but
> > without feedback on people's patches they're usually unaware that they're
> > breaking things.
>

As of today browser test status changes are being reported to
#wikimedia-dev by a bot named "wmf-jenkins-bot", e.g.:

(09:30:18 AM) wmf-jenkins-bot-: Project _debug-irc build #17: SUCCESS in 90
ms: https://wmf.ci.cloudbees.com/job/_debug-irc/17/

Integration with Gerrit as well as Jenkins is certainly feasible, and as
the information provided by these tests becomes more closely tied to the
code itself rather than the environments in which the code is deployed, we
can put that integration in place as it becomes valuable.
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] DevOps/Continuous Deployment discussion?

[Juliusz Gonera]

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 that you could deploy twice an hour
if you wanted to is all kinds of valuable.

Putting time into building:
  * Continuous integration with build-on-commit
  * Tests with good coverage
  * A staging environment that reflects production
  * Managed configuration
  * Scripted deployment to a large number of machines
pays dividends in uptime, ops sanity and developer productivity even if you
only use that machinery every few days.

We have some of that, but heading further down that road would be a good
thing even if we chose to keep organized periodic deployments.


I couldn't agree more. It's not that I feel a need of deploying 
something every single day, I just want the whole process to be easier 
and less scary, so that it doesn't disrupt everyone's work for half a 
day. Also, it shouldn't be a big deal to push a quick fix in between 
deployments.


--
Juliusz

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

Re: [Wikitech-l] cleaning database of spam

[Jay Ashworth]

- Original Message -
> From: "Petr Bena" 

> You meant innodb_file_per_table

Yes; I forgot the exact name, and tried (apparently unsuccessfully) to 
make that look as little like an exact parameter as possible.

Happily, the OP runs that way anyway.

Cheers,
-- jra
-- 
Jay R. Ashworth  Baylink   j...@baylink.com
Designer The Things I Think   RFC 2100
Ashworth & Associates http://baylink.pitas.com 2000 Land Rover DII
St Petersburg FL USA   #natog  +1 727 647 1274

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

Re: [Wikitech-l] Blame maps aka authorship detection

[Petr Bena]

your site doesn't work

http://blamemaps.wmflabs.org/mw/index.php/Main_Page -> the connection timed out

On Tue, Feb 26, 2013 at 5:52 PM, Bartosz Dziewoński  wrote:
> I have briefly toyed with something similar. Unlike yours, it has a (very
> simple and rudimentary) interface, but no sophisticated algorithms inside :)
> – just a standard LCS diff library. It also works in real time (but is
> awfully slow).
>
> It can be seen at http://wikiblame.heroku.com/ (source at
> https://github.com/MatmaRex/wikiblame) – there's some weird bug right now
> that makes it fail for titles with non-ASCII characters that I haven't had
> time to investigate, and due to free platform limitations it'll fail if
> generation of the blame map would takes over 30 seconds (that would be for
> most articles > 3 kB or with more than 50 revisions); I was intending to
> move it to some toolserver or labs or something, but haven't had time for
> this either.
>
> I've also seen some gadget on en.wiki that did something similar, but I
> don't remember the name and can't find it right now.
>
> --
> Matma Rex
>
>
> ___
> 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] Blame maps aka authorship detection

[Bartosz Dziewoński]

I have briefly toyed with something similar. Unlike yours, it has a (very 
simple and rudimentary) interface, but no sophisticated algorithms inside :) – 
just a standard LCS diff library. It also works in real time (but is awfully 
slow).

It can be seen at http://wikiblame.heroku.com/ (source at 
https://github.com/MatmaRex/wikiblame) – there's some weird bug right now that 
makes it fail for titles with non-ASCII characters that I haven't had time to 
investigate, and due to free platform limitations it'll fail if generation of the 
blame map would takes over 30 seconds (that would be for most articles > 3 kB 
or with more than 50 revisions); I was intending to move it to some toolserver or 
labs or something, but haven't had time for this either.

I've also seen some gadget on en.wiki that did something similar, but I don't 
remember the name and can't find it right now.

--
Matma Rex

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

Re: [Wikitech-l] cleaning database of spam

[Petr Bena]

You meant innodb_file_per_table

On Tue, Feb 26, 2013 at 5:39 PM, Petr Bena  wrote:
> yes that's what I do :>
>
> On Tue, Feb 26, 2013 at 4:39 PM, Jay Ashworth  wrote:
>> - Original Message -
>>> From: "Platonides" 
>>
>>> > What is exact procedure of properly removing page from database so
>>> > that it doesn't break anything? What needs to be deleted and in
>>> > which order?
>>>
>>> maintenance/deleteArchivedRevisions.php permanently removes the
>>> content of deleted pages from the db.
>>>
>>> For removing those users, see
>>> http://www.mediawiki.org/wiki/Extension:User_Merge_and_Delete
>>>
>>> Also remember that due to the way mysql works, it may not release
>>> those 20GB back to the filesystem.
>>
>> In particular, to get anything for your trouble, you will probably need
>> to dump the database, drop it, shut down MySQL and switch it to innodb
>> tablespace-per-file, turn it back on, and then reload the dump, as I
>> recently had to.
>>
>> This way, at least, once you clean it up, you can do the same dump and
>> reload procedure on only one table, not the whole shootin' match.
>>
>> Cheers,
>> -- jra
>> --
>> Jay R. Ashworth  Baylink   
>> j...@baylink.com
>> Designer The Things I Think   RFC 
>> 2100
>> Ashworth & Associates http://baylink.pitas.com 2000 Land Rover 
>> DII
>> St Petersburg FL USA   #natog  +1 727 647 
>> 1274
>>
>> ___
>> 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] cleaning database of spam

[Petr Bena]

yes that's what I do :>

On Tue, Feb 26, 2013 at 4:39 PM, Jay Ashworth  wrote:
> - Original Message -
>> From: "Platonides" 
>
>> > What is exact procedure of properly removing page from database so
>> > that it doesn't break anything? What needs to be deleted and in
>> > which order?
>>
>> maintenance/deleteArchivedRevisions.php permanently removes the
>> content of deleted pages from the db.
>>
>> For removing those users, see
>> http://www.mediawiki.org/wiki/Extension:User_Merge_and_Delete
>>
>> Also remember that due to the way mysql works, it may not release
>> those 20GB back to the filesystem.
>
> In particular, to get anything for your trouble, you will probably need
> to dump the database, drop it, shut down MySQL and switch it to innodb
> tablespace-per-file, turn it back on, and then reload the dump, as I
> recently had to.
>
> This way, at least, once you clean it up, you can do the same dump and
> reload procedure on only one table, not the whole shootin' match.
>
> Cheers,
> -- jra
> --
> Jay R. Ashworth  Baylink   
> j...@baylink.com
> Designer The Things I Think   RFC 2100
> Ashworth & Associates http://baylink.pitas.com 2000 Land Rover DII
> St Petersburg FL USA   #natog  +1 727 647 1274
>
> ___
> 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] Blame maps aka authorship detection

[Mark A. Hershberger]

On 02/25/2013 09:21 PM, Luca de Alfaro wrote:
>  The problem is of putting together a bit of effort to get to that first
> running version.

How big are the wikis that you've tried this on?  Would smaller academic
wikis be able to use this code?

I may have a use for your code since one of the wikis I'm working on is
targeted to academics where getting a citation really improves wiki
participation.

-- 
http://hexmode.com/

There is no path to peace. Peace is the path.
   -- Mahatma Gandhi, "Non-Violence in Peace and War"

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

Re: [Wikitech-l] Gsoc 2013 guidelines

[Yuri Astrakhan]

Atul, one of the fun projects that has been sitting on my backburner is to
implement errors and warnings localization for the Web API. The project
would involve some planning, figuring out translation framework, and later
- converting all API modules and extensions to use it. As a result, all
clients, including mobile, will be able to report errors to the users in
their native language. I am not sure how GSOC supervision functions, but I
will definitely be involved with the implementation.

This is slightly bigger than a bug fix, but should be fairly independent
from everything and will give you good exposure into internals as well as
javascript and other  clients.


On Tue, Feb 26, 2013 at 11:20 AM, Atul Agrawal  wrote:

> @Waldir:working on the link you sent me.I will notify you if I need any
> help
>
> @Quim:While I will love to work under a project and be guided .It will be
> great if you can suggest some beginner level project and  I can work with
> someone or by my own.
> I will like to solve arithmetic bugs,logical bugs,deadlock situation and
> teamworking bugs.
> And one more thing as mediaWiki documentation is so vast, how will I know
> in which specific area I have to develop my skills so that I will able to
> get the idea as well as solve it which will be proposed for gsoc 2013?Do I
> need to contact the mentors?
>
> Thanks for being so helpful.
>
> Atul
>
>
>
> On Tue, Feb 26, 2013 at 9:13 PM, Quim Gil  wrote:
>
> > On 02/26/2013 01:23 AM, Atul Agrawal wrote:
> >
> >> Thanks a lot.Will try to fix bugs.But what knowledge should I have to
> fix
> >> bugs?knowing php is sufficient?Till now I have read this page(
> >> Developing_Extensions >> Developing_extensions<
> http://www.mediawiki.org/wiki/Manual:Developing_extensions>
> >> >.If
> >> you can share the documents one should read before fixing bugs,I will be
> >> highly obliged.
> >>
> >
> > We have many different software projects, and what to read depends pon
> > what bugs you want to fix.
> >
> > Why not choosing first a project or a bug that interests you, and then
> > learn about the pieces involved as you try to fix it?
> >
> > We can help you find a first bug. What is your area of interest?
> >
> >
> > --
> > Quim Gil
> > Technical Contributor Coordinator @ Wikimedia Foundation
> > http://www.mediawiki.org/wiki/**User:Qgil<
> http://www.mediawiki.org/wiki/User:Qgil>
> >
> > __**_
> > Wikitech-l mailing list
> > Wikitech-l@lists.wikimedia.org
> > https://lists.wikimedia.org/**mailman/listinfo/wikitech-l<
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l>
> >
>
>
>
> --
> Atul Agrawal
> B.E Mechanical
> BITS PILANI Goa Campus
> Mobile:+91-81491-95049
> ___
> 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] Blame maps aka authorship detection

[Krenair]

It sounds like some of those things should be working in labs soon with 
DB replication. I doubt they'll let you store terabytes though.


Alex Monk

On 26/02/13 07:29, Luca de Alfaro wrote:

What we wrote can work also on labs, but:

- We need a way to poll the database for things like what are all
revision_ids of a given page.  We could use the API instead, but it's less
efficient.
- We need a way to read the text of revisions.  Again, the API can work,
but having better access is better.
- We need a place where to store the authorship information.  This is
several terabytes for enwiki.  Basically, we need access to some text
store.  Is this available on labs?


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

Re: [Wikitech-l] Gsoc 2013 guidelines

[Atul Agrawal]

@Waldir:working on the link you sent me.I will notify you if I need any help

@Quim:While I will love to work under a project and be guided .It will be
great if you can suggest some beginner level project and  I can work with
someone or by my own.
I will like to solve arithmetic bugs,logical bugs,deadlock situation and
teamworking bugs.
And one more thing as mediaWiki documentation is so vast, how will I know
in which specific area I have to develop my skills so that I will able to
get the idea as well as solve it which will be proposed for gsoc 2013?Do I
need to contact the mentors?

Thanks for being so helpful.

Atul



On Tue, Feb 26, 2013 at 9:13 PM, Quim Gil  wrote:

> On 02/26/2013 01:23 AM, Atul Agrawal wrote:
>
>> Thanks a lot.Will try to fix bugs.But what knowledge should I have to fix
>> bugs?knowing php is sufficient?Till now I have read this page(
>> Developing_Extensions> Developing_extensions
>> >.If
>> you can share the documents one should read before fixing bugs,I will be
>> highly obliged.
>>
>
> We have many different software projects, and what to read depends pon
> what bugs you want to fix.
>
> Why not choosing first a project or a bug that interests you, and then
> learn about the pieces involved as you try to fix it?
>
> We can help you find a first bug. What is your area of interest?
>
>
> --
> Quim Gil
> Technical Contributor Coordinator @ Wikimedia Foundation
> http://www.mediawiki.org/wiki/**User:Qgil
>
> __**_
> Wikitech-l mailing list
> Wikitech-l@lists.wikimedia.org
> https://lists.wikimedia.org/**mailman/listinfo/wikitech-l
>



-- 
Atul Agrawal
B.E Mechanical
BITS PILANI Goa Campus
Mobile:+91-81491-95049
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Blame maps aka authorship detection

[Sumana Harihareswara]

On 02/25/2013 06:21 PM, Luca de Alfaro wrote:
> I am writing this message as we hope this might be of interest, and as we
> would be quite happy to find people willing to collaborate.  Is anybody
> interested in developing a GUI for it and talk to us about what API we
> should have for retrieving this authorship information?  Is there anybody
> interested in helping to move the code to production-ready stage?

I'm emphasizing this message.  Thanks for the roundup, Luca!

-- 
Sumana Harihareswara
Engineering Community Manager
Wikimedia Foundation

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

Re: [Wikitech-l] Gsoc 2013 guidelines

[Quim Gil]

On 02/26/2013 01:23 AM, Atul Agrawal wrote:

Thanks a lot.Will try to fix bugs.But what knowledge should I have to fix
bugs?knowing php is sufficient?Till now I have read this page(
Developing_Extensions.If
you can share the documents one should read before fixing bugs,I will be
highly obliged.


We have many different software projects, and what to read depends pon 
what bugs you want to fix.


Why not choosing first a project or a bug that interests you, and then 
learn about the pieces involved as you try to fix it?


We can help you find a first bug. What is your area of interest?

--
Quim Gil
Technical Contributor Coordinator @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil

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

Re: [Wikitech-l] cleaning database of spam

[Jay Ashworth]

- Original Message -
> From: "Platonides" 

> > What is exact procedure of properly removing page from database so
> > that it doesn't break anything? What needs to be deleted and in
> > which order?
> 
> maintenance/deleteArchivedRevisions.php permanently removes the
> content of deleted pages from the db.
> 
> For removing those users, see
> http://www.mediawiki.org/wiki/Extension:User_Merge_and_Delete
> 
> Also remember that due to the way mysql works, it may not release
> those 20GB back to the filesystem.

In particular, to get anything for your trouble, you will probably need
to dump the database, drop it, shut down MySQL and switch it to innodb
tablespace-per-file, turn it back on, and then reload the dump, as I 
recently had to.

This way, at least, once you clean it up, you can do the same dump and 
reload procedure on only one table, not the whole shootin' match.

Cheers,
-- jra
-- 
Jay R. Ashworth  Baylink   j...@baylink.com
Designer The Things I Think   RFC 2100
Ashworth & Associates http://baylink.pitas.com 2000 Land Rover DII
St Petersburg FL USA   #natog  +1 727 647 1274

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

Re: [Wikitech-l] Gsoc 2013 guidelines

[Waldir Pimenta]

On Tue, Feb 26, 2013 at 9:23 AM, Atul Agrawal  wrote:

> Thanks a lot.Will try to fix bugs.But what knowledge should I have to fix
> bugs?knowing php is sufficient?Till now I have read this page(
> Developing_Extensions<
> http://www.mediawiki.org/wiki/Manual:Developing_extensions>.If
> you can share the documents one should read before fixing bugs,I will be
> highly obliged.
>

I've been collecting a few links at
http://www.mediawiki.org/?oldid=651991#MediaWiki_reference
that might be useful for newcomer developers to get a first overview of
various components of the MediaWiki universe.

Let me know if those are helpful to you and what you think is missing from
that list. Bear in mind that it's a work in progress, though.

--Waldir

ps - while you're at that page, if you find some interest in any of some of
the bugs I've listed in the "easy" part of the "Potential bugs for hacking
sessions" section, I'd love to help you go about fixing them.
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] Propose topics for the Amsterdam Hackathon

[Quim Gil]

Please propose topics for the Amsterdam Hackathon here:

https://www.mediawiki.org/wiki/Amsterdam_Hackathon_2013/Topics

This is specially useful when there is various people intending to go to 
Amsterdam to discuss and work around a specific topic.


For instance, I have heard a couple of people mentioning the possibility 
of running a Design workshop. Listing this topic there is useful, as it 
will make the organizers and other potential attendees to consider.


Thank you!

--
Quim Gil
Technical Contributor Coordinator @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil

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

Re: [Wikitech-l] cleaning database of spam

[Petr Bena]

but it will stop incrementing the datafile

On Tue, Feb 26, 2013 at 12:40 PM, Platonides  wrote:
> On 26/02/13 11:57, Petr Bena wrote:
>> Hi, this is more related to mediawiki rather than wikimedia, but this
>> list is being watched a bit more I guess.
>>
>> Is there any extension that allows permanent removal of deleted pages
>> (or eventually selected deleted pages) from database and removal of
>> blocked users from database?
>>
>> Imagine you have a mediawiki wiki that has 20 gb database, where
>> 19.99gb of database is spam and indefinitely blocked users. I think
>> lot of wikis has this problem, making extension to deal with this
>> would be useful for many small wikis.
>>
>> What is exact procedure of properly removing page from database so
>> that it doesn't break anything? What needs to be deleted and in which
>> order?
>
> maintenance/deleteArchivedRevisions.php permanently removes the content
> of deleted pages from the db.
>
> For removing those users, see
> http://www.mediawiki.org/wiki/Extension:User_Merge_and_Delete
>
> Also remember that due to the way mysql works, it may not release those
> 20GB back to the filesystem.
>
>
> ___
> 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

[Wikitech-l] Translate extension design walkthrough

[Pau Giner]

The Language Engineering team is in the process of redesigning the Translate
extension .
The Translate extension turns MediaWiki into a localisation platform, and
it is used in Meta-Wiki, mediawiki.org and a few other Wikimedia wikis, as
well as other opensource projects, to make them available in multiple
languages.

We are planning to do a walkthrough for the latest revision of the designs
tomorrow.
Since the extension is used by many different projects and users, we want
to make this meeting open to get feedback from anyone interested.

So we welcome you to join us in the discussion:

*When.* Wednesday 27 of February at 8:30 PST (San Francisco), 16:30 UTC
(UK), 17:30 CET (most of Europe), and 22:00 IST (India).

*What.* During the meeting we'll discuss information from our design
specification
 and the current implementation available at
translatewiki.net.
Feel free to take a look to the docs or try the new UI before the event.

*How* to participate. The event will be broadcasted using Google Hangouts
On Air, so that it can be seen live or accessed later. We'll share the URL
as the event approaches. The #mediawiki-i18n IRC channel will be used to
get questions from the audience.
If you are interested in entering the hangout for a face-to-face
participation, you can ping me and I'll send an invite as long as there are
free seats remaining.


Pau

-- 
Pau Giner
Interaction Designer
Wikimedia Foundation
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] cleaning database of spam

[Platonides]

On 26/02/13 11:57, Petr Bena wrote:
> Hi, this is more related to mediawiki rather than wikimedia, but this
> list is being watched a bit more I guess.
> 
> Is there any extension that allows permanent removal of deleted pages
> (or eventually selected deleted pages) from database and removal of
> blocked users from database?
> 
> Imagine you have a mediawiki wiki that has 20 gb database, where
> 19.99gb of database is spam and indefinitely blocked users. I think
> lot of wikis has this problem, making extension to deal with this
> would be useful for many small wikis.
> 
> What is exact procedure of properly removing page from database so
> that it doesn't break anything? What needs to be deleted and in which
> order?

maintenance/deleteArchivedRevisions.php permanently removes the content
of deleted pages from the db.

For removing those users, see
http://www.mediawiki.org/wiki/Extension:User_Merge_and_Delete

Also remember that due to the way mysql works, it may not release those
20GB back to the filesystem.


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

[Wikitech-l] cleaning database of spam

[Petr Bena]

Hi, this is more related to mediawiki rather than wikimedia, but this
list is being watched a bit more I guess.

Is there any extension that allows permanent removal of deleted pages
(or eventually selected deleted pages) from database and removal of
blocked users from database?

Imagine you have a mediawiki wiki that has 20 gb database, where
19.99gb of database is spam and indefinitely blocked users. I think
lot of wikis has this problem, making extension to deal with this
would be useful for many small wikis.

What is exact procedure of properly removing page from database so
that it doesn't break anything? What needs to be deleted and in which
order?

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

Re: [Wikitech-l] Better non-MySQL db support

[Dmitriy Sintsov]

26 Февраль 2013 г. 14:27:06 пользователь Nikola Smolenski (smole...@eunet.rs) 
написал:

On 26/02/13 04:18, Matthew Flaschen wrote:
> Sure, for starters. :) Bear in mind, if we want to keep support for all
> these dbs, every change to the database schema has to (at some point)
> result in a change to separate SQL files for each DB (MySQL and SQLite
> use the same ones).    For instance, there is a separate active
> oracle/tables.sql.
I am wondering if it would make sense to give up on SQL, make universal 
table creation functions in PHP, the same way there are for other 
queries, and use that. Has anyone tried this before, is there other 
software that works like this?


http://stackoverflow.com/questions/108699/good-php-orm-library

By the way, MySQL 5.6 is out and it supports fulltext search indexation for 
InnoDB tables. They also promise better peformance on large hardware.
Still cannot find 12.04 ppa for 5.6.10, though and do not want to go troubles 
installing from source (although I installed MySQL from source some years ago)..
Why going another database engines besides MySQL / MariaDB?
Dmitriy

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

Re: [Wikitech-l] Better non-MySQL db support

[Nikola Smolenski]

On 26/02/13 04:18, Matthew Flaschen wrote:

Sure, for starters. :) Bear in mind, if we want to keep support for all
these dbs, every change to the database schema has to (at some point)
result in a change to separate SQL files for each DB (MySQL and SQLite
use the same ones).  For instance, there is a separate active
oracle/tables.sql.


I am wondering if it would make sense to give up on SQL, make universal 
table creation functions in PHP, the same way there are for other 
queries, and use that. Has anyone tried this before, is there other 
software that works like this?


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

Re: [Wikitech-l] Gsoc 2013 guidelines

[Atul Agrawal]

Thanks a lot.Will try to fix bugs.But what knowledge should I have to fix
bugs?knowing php is sufficient?Till now I have read this page(
Developing_Extensions.If
you can share the documents one should read before fixing bugs,I will be
highly obliged.

Thanks for replying



On Tue, Feb 26, 2013 at 1:58 AM, Quim Gil  wrote:

> Hi Atul,
>
>
> On 02/25/2013 12:12 PM, Atul Agrawal wrote:>
>
>> I installed MediaWiki software and I was going through the link "become
>> a MediaWiki hacker".My question is how will the community judge me?Do I
>> have to create a new extension?And whom should I report?
>>
>
> Those are very good questions. GSOC apart, people here (as in most
> communities) will probably judge at the end how helpful / useful you are.
>
> For a programmer, fixing bugs effectively is a way to learn and be helpful
> at the same time. You can start with something small and grow the weight of
> your fixes as your experience grows. Here is a good starting point:
>
> https://www.mediawiki.org/**wiki/Annoying_Little_Bug
>
> PS: Very good start so far!
>
> --
> Quim Gil
> Technical Contributor Coordinator @ Wikimedia Foundation
> http://www.mediawiki.org/wiki/**User:Qgil
>
> __**_
> Wikitech-l mailing list
> Wikitech-l@lists.wikimedia.org
> https://lists.wikimedia.org/**mailman/listinfo/wikitech-l




-- 
Atul Agrawal
B.E Mechanical
BITS PILANI Goa Campus
Mobile:+91-81491-95049
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l