Re: [Wikitech-l] MathJax opt-in for all visitors

[Niklas Laxström]

On 3 May 2013 08:13, Peter Krautzberger  wrote:
> Hi,
>
> Here's an idea somebody suggested to me.
>
> I would like to propose a way for any visitor to opt-in to MathJax on the
> fly. (Oh, maybe I should add a disclaimer: I work for MathJax.)
>
> This would be simply a button on pages with math that would switch MathJax
> on (and possibly off via a cookie).

What is the state of MathJax i18n currently? Before we show it to lots
of users it should be translatable.

  -Niklas


--
Niklas Laxström

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

Re: [Wikitech-l] MathJax opt-in for all visitors

[Matthew Flaschen]

On 05/03/2013 03:29 AM, Niklas Laxström wrote:
> On 3 May 2013 08:13, Peter Krautzberger  
> wrote:
>> Hi,
>>
>> Here's an idea somebody suggested to me.
>>
>> I would like to propose a way for any visitor to opt-in to MathJax on the
>> fly. (Oh, maybe I should add a disclaimer: I work for MathJax.)
>>
>> This would be simply a button on pages with math that would switch MathJax
>> on (and possibly off via a cookie).
> 
> What is the state of MathJax i18n currently? Before we show it to lots
> of users it should be translatable.

Hard-coded into minified JavaScript (not using ResourceLoader),
unfortunately (https://bugzilla.wikimedia.org/show_bug.cgi?id=35038)

I think this is an interesting idea (it's a middle ground towards
possibly changing the default), worth exploring, but it definitely needs
some work.  Filed at https://bugzilla.wikimedia.org/show_bug.cgi?id=48036

Note, there is already a bug about enabling it by default
(https://bugzilla.wikimedia.org/show_bug.cgi?id=36496), which is a
bigger change.

See also https://bugzilla.wikimedia.org/show_bug.cgi?id=35480 (a
proposal to send down PNG and then immediately transform it to MathJax
in supported browsers).

Matt Flaschen

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

[Wikitech-l] Issue with: en.m.wikipedia.org

[Martin Butler]

Hi

I'm not sure I'm posting this in the right place, but I (and I expect lots of 
others!) can't use en.m.wikipedia.org via Opera Mini.
This is because the GO button next to the search box has disappeared.


This email and any attachments to it may contain information which is 
confidential, legally privileged, subject to the Official Secrets Act, or 
otherwise not disclosable by law, and is protected by copyright. It is intended 
only for the addressee named above. If you are not the intended recipient you 
must delete this email immediately and not use, distribute, copy, disclose or 
take any action in reliance on this email or its contents. If you have received 
this email in error please notify us by return email immediately. 
Airwave Solutions Limited is a company registered in England and Wales having 
company number 03985643. 
Registered Office: Airwave Solutions Ltd, Charter Court, 50 Windsor Road, 
Slough, Berkshire, SL1 2EJ.
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] [GSoc2013] Interested in developing Entity Suggester

[aude]

On Fri, May 3, 2013 at 5:39 AM, Nilesh Chakraborty wrote:

> Hi Lydia,
>
> I am currently drafting my proposal, I shall submit within a few hours once
> the initial version is complete.
>
> I installed mediawiki-vagrant on my PC and it went quite smoothly. I could
> do all the usual things through the browser; I logged into the mysql server
> to examine the database schema.
>
> I also began to clone the
> wikidata-vagrant repo.
> But it seems that the 'git submodule update --init' part would take a long
> time - if I'm not mistaken, it's a huge download (excluding the vagrant up
> command, which alone takes around 1.25 hours to download everything). I
> wanted to clarify something before downloading it all.
>
> Since the entity suggester will be working with wikidata, it'll obviously
> need to access the whole live dataset from the database (not the xml dump)
> to make the recommendations. I tried searching for database access APIs or
> high-level REST APIs for wikidata, but couldn't figure out how I to do
> that. Could you point me to the proper documentation?
>

One of the best examples of a MediaWiki extension interacting with a Java
service is how Solr is used.  Solr is still pretty new at Wikimedia,
though.  It is used with the GeoData extension and then Solr is used by
geodata api modules.

I think Solr gets updated via a cronjob (solrupdate.php) which creates jobs
in the job queue.  Not 100% sure of the exact details.

I do not think direct access to the live database is very practical. I
think anyway the data (json blobs) would need indexing in some particular
way to support what the entity selector needs to do.

http://www.mediawiki.org/wiki/Extension:GeoData

The Translate extension also uses Solr in some way, though I am not very
familiar with the details.

On the operations side, puppet is used to configure everything.  The puppet
git repo is available to see how things are done.

https://gerrit.wikimedia.org/r/gitweb?p=operations/puppet.git;a=tree;f=modules/solr;hb=HEAD


>
> And also, what is the best way to add a few .jar files to wikidata and
> execute them with custom commands (nohup java blah.jar --blah blah -->
> running as daemons)? I can of course set it up on my development box inside
> virtualbox - I want to know how to "integrate" it into the system so that
> any other user can download vagrant and wikidata and have the jars all
> ready and running? What is the proper development workflow for this?
>

wikidata-vagrant is maintained in github, though I think might not work
perfectly right now.  We need to update it and it's on our to-do, and
perhaps could be moved to gerrit.  I do not know about integrating the
jars, but should be possible.

Cheers,
Katie Filbert

[answering from this email, as I am not subscribed to wikitech-l on my
wikimedia.de email]


>
> Thanks,
> Nilesh
>
>
>
> On Sun, Apr 28, 2013 at 3:01 AM, Nilesh Chakraborty  >wrote:
>
> > Awesome. Got it.
> >
> > I see what you mean, great, thank you. :)
> >
> > Cheers,
> > Nilesh
> > On Apr 28, 2013 2:56 AM, "Lydia Pintscher"  >
> > wrote:
> >
> >> On Sat, Apr 27, 2013 at 11:14 PM, Nilesh Chakraborty <
> nil...@nileshc.com>
> >> wrote:
> >> > Hi Lydia,
> >> >
> >> > That helps a lot, and makes it way more interesting. Rather than
> being a
> >> > one-size-fits-all solution, as it seems to me, each property or each
> >> type
> >> > of property (eg. different relationships) will need individual
> attention
> >> > and different methods/metrics for recommendation.
> >> >
> >> > The examples you gave, like continents, sex, relations like
> father/son,
> >> > uncle/aunt/spouse, or place-oriented properties like place of birth,
> >> > country of citizenship, ethnic group etc. - each type has a certain
> >> pattern
> >> > to it (if a person was born in the US, US should be one of the
> >> countries he
> >> > was a citizen of; US census/ethnicity statistics may be used to
> predict
> >> > ethnic group etc.) I'm already starting to chalk out a few patterns
> and
> >> how
> >> > they can be used for recommendation. In my proposal, should I go into
> >> > details regarding these? Or should I just give a few examples and
> >> explain
> >> > how the algorithms would work, to explain the idea?
> >>
> >> Give some examples and how you'd handle them. You definitely don't
> >> need to have it for all properties. What's important is giving an idea
> >> about how you'd tackle the problem. Give the reader the impression
> >> that you know what you are talking about and can handle the larger
> >> problem.
> >>
> >> Also: Don't make the system too intelligent like it knowing about US
> >> census data for example. Keep it simple and stupid for now. Things
> >> like "property A is usually used with value X, Y or Z" should cover a
> >> lot already and are likely enough for most cases.
> >>
> >>
> >> Cheers
> >> Lydia
> >>
> >> --
> >> Lydia Pintscher - http://about.me/lydia.pintscher
> >> Community C

Re: [Wikitech-l] Issue with: en.m.wikipedia.org

[Andre Klapper]

Hi,

On Fri, 2013-05-03 at 09:39 +, Martin Butler wrote:
> I'm not sure I'm posting this in the right place, but I (and I expect
> lots of others!) can't use en.m.wikipedia.org via Opera Mini.
> This is because the GO button next to the search box has disappeared.

This is covered in
https://bugzilla.wikimedia.org/show_bug.cgi?id=47567

andre
-- 
Andre Klapper | Wikimedia Bugwrangler
http://blogs.gnome.org/aklapper/


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

[Wikitech-l] GSoC Proposal - Incremental Data Dumps

[Jeremy Coffman]

Hello,

My name is Jeremy Coffman. I am a second year student studying Computer Science 
at Brandeis University, with a possible focus on natural language processing. I 
have decided to apply to work on the Incremental Data Dumps project. My 
proposal can be found here:
http://www.mediawiki.org/wiki/User:J.a.coffman/GSoc_2013_Proposal

I know I'm rather close to the deadline, but I welcome any feedback you may 
have.

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

Re: [Wikitech-l] MathJax opt-in for all visitors

[Derk-Jan Hartman]

I think it's a nice idea if to trigger such a suggestion. I would add
something to it though. I'd add a timer that checks how long it takes to
markup the page, and that when it detects that pages take extremely long to
finish rendering with MathJax, automatically proposes to the user to
'switch back'.

That makes the whole experience a bit safer for people.

DJ



On Fri, May 3, 2013 at 11:17 AM, Matthew Flaschen
wrote:

> On 05/03/2013 03:29 AM, Niklas Laxström wrote:
> > On 3 May 2013 08:13, Peter Krautzberger 
> wrote:
> >> Hi,
> >>
> >> Here's an idea somebody suggested to me.
> >>
> >> I would like to propose a way for any visitor to opt-in to MathJax on
> the
> >> fly. (Oh, maybe I should add a disclaimer: I work for MathJax.)
> >>
> >> This would be simply a button on pages with math that would switch
> MathJax
> >> on (and possibly off via a cookie).
> >
> > What is the state of MathJax i18n currently? Before we show it to lots
> > of users it should be translatable.
>
> Hard-coded into minified JavaScript (not using ResourceLoader),
> unfortunately (https://bugzilla.wikimedia.org/show_bug.cgi?id=35038)
>
> I think this is an interesting idea (it's a middle ground towards
> possibly changing the default), worth exploring, but it definitely needs
> some work.  Filed at https://bugzilla.wikimedia.org/show_bug.cgi?id=48036
>
> Note, there is already a bug about enabling it by default
> (https://bugzilla.wikimedia.org/show_bug.cgi?id=36496), which is a
> bigger change.
>
> See also https://bugzilla.wikimedia.org/show_bug.cgi?id=35480 (a
> proposal to send down PNG and then immediately transform it to MathJax
> in supported browsers).
>
> Matt Flaschen
>
> ___
> 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 Proposal - Incremental Data Dumps

[Rahul Maliakkal]

Hello

I hope you have added the proposal of yours to
http://www.google-melange.com/gsoc/homepage/google/gsoc201
3

If you have done that then add yourself to
http://www.mediawiki.org/wiki/Summer_of_Code_2013.

Thanks
Rahul


On Fri, May 3, 2013 at 7:48 PM, Jeremy Coffman  wrote:

> Hello,
>
> My name is Jeremy Coffman. I am a second year student studying Computer
> Science at Brandeis University, with a possible focus on natural language
> processing. I have decided to apply to work on the Incremental Data Dumps
> project. My proposal can be found here:
> http://www.mediawiki.org/wiki/User:J.a.coffman/GSoc_2013_Proposal
>
> I know I'm rather close to the deadline, but I welcome any feedback you
> may have.
>
> Thank you,
> Jeremy Coffman
> ___
> 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] Next bugday: May 03rd, 15:00-16:30UTC on MediaWiki Installer issues

[Andre Klapper]

Reminder: Bugday starts soon.

andre

On Tue, 2013-04-30 at 14:08 +0200, Andre Klapper wrote:
> Friday, May 03rd, 15:00-16:30 UTC [1]
> in #wikimedia-office on Freenode IRC [2]
> 
> We are going to take a look at recent MediaWiki installer reports,
-- 
Andre Klapper | Wikimedia Bugwrangler
http://blogs.gnome.org/aklapper/


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

Re: [Wikitech-l] MathJax opt-in for all visitors

[praveenp]

I would like to see Server rendered png issues fixed before this. Simple 
images are better for various devices and browsers. But it will be 
better to allow users to force technology, if no other simple solutions 
possible.


On Friday 03 May 2013 12:59 PM, Niklas Laxström wrote:


What is the state of MathJax i18n currently? Before we show it to lots
of users it should be translatable.


MathJax available in Math extension is not completely capable to handle 
non-latin scripts. ( See this bug we filed yesterday: 
https://bugzilla.wikimedia.org/show_bug.cgi?id=48032 )



   -Niklas


--
Niklas Laxström

___
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] GSoC 2013 Proposal for Entity Suggester

[Nilesh Chakraborty]

Hello,

I have drafted my proposal under my user page here:
https://www.mediawiki.org/wiki/User:Nilesh.c/Entity_Suggester

Please have a look at it and let me know if I can make any changes to make
it better in any way. :-)

Cheers,
Nilesh

-- 
A quest eternal, a life so small! So don't just play the guitar, build one.
You can also email me at cont...@nileshc.com or visit my
website
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] GSoC 2013 Proposal for Entity Suggester

[Lydia Pintscher]

On Fri, May 3, 2013 at 5:43 PM, Nilesh Chakraborty  wrote:
> Hello,
>
> I have drafted my proposal under my user page here:
> https://www.mediawiki.org/wiki/User:Nilesh.c/Entity_Suggester
>
> Please have a look at it and let me know if I can make any changes to make
> it better in any way. :-)

Please don't forget to also submit it on google-melange.com before the
deadline in a few hours. Otherwise we can not accept it.


Cheers
Lydia

--
Lydia Pintscher - http://about.me/lydia.pintscher
Community Communications for Technical Projects

Wikimedia Deutschland e.V.
Obentrautstr. 72
10963 Berlin
www.wikimedia.de

Wikimedia Deutschland - Gesellschaft zur Förderung Freien Wissens e. V.

Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg
unter der Nummer 23855 Nz. Als gemeinnützig anerkannt durch das
Finanzamt für Körperschaften I Berlin, Steuernummer 27/681/51985.

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

Re: [Wikitech-l] GSoC 2013 Proposal for Entity Suggester

[Rahul Maliakkal]

Hello

1-Upload your proposal on google-melange.
2-After uploading it, please add your name to the
http://www.mediawiki.org/wiki/Summer_of_Code_2013#Students list.

Thanks
Rahul


On Fri, May 3, 2013 at 9:18 PM, Lydia Pintscher <
lydia.pintsc...@wikimedia.de> wrote:

> On Fri, May 3, 2013 at 5:43 PM, Nilesh Chakraborty 
> wrote:
> > Hello,
> >
> > I have drafted my proposal under my user page here:
> > https://www.mediawiki.org/wiki/User:Nilesh.c/Entity_Suggester
> >
> > Please have a look at it and let me know if I can make any changes to
> make
> > it better in any way. :-)
>
> Please don't forget to also submit it on google-melange.com before the
> deadline in a few hours. Otherwise we can not accept it.
>
>
> Cheers
> Lydia
>
> --
> Lydia Pintscher - http://about.me/lydia.pintscher
> Community Communications for Technical Projects
>
> Wikimedia Deutschland e.V.
> Obentrautstr. 72
> 10963 Berlin
> www.wikimedia.de
>
> Wikimedia Deutschland - Gesellschaft zur Förderung Freien Wissens e. V.
>
> Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg
> unter der Nummer 23855 Nz. Als gemeinnützig anerkannt durch das
> Finanzamt für Körperschaften I Berlin, Steuernummer 27/681/51985.
>
> ___
> 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 Proposal for Entity Suggester

[Rahul Maliakkal]

ctrl + F "mediawiki" in your proposal. It is "MediaWiki" and not
"mediawiki".

Thanks


On Fri, May 3, 2013 at 9:13 PM, Nilesh Chakraborty wrote:

> Hello,
>
> I have drafted my proposal under my user page here:
> https://www.mediawiki.org/wiki/User:Nilesh.c/Entity_Suggester
>
> Please have a look at it and let me know if I can make any changes to make
> it better in any way. :-)
>
> Cheers,
> Nilesh
>
> --
> A quest eternal, a life so small! So don't just play the guitar, build one.
> You can also email me at cont...@nileshc.com or visit my
> website
> ___
> 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] [GSOC Proposal] Incremental data dumps - Shaohong

[Shao Hong]

Hi all,

I have just updated my proposal for "Incremental data dumps" and you can
view it at https://www.mediawiki.org/wiki/User:Shaohong and please feel
free to give me comments or suggestion! Thanks!


Shao Hong
shaohon...@gmail.com

"Respect needs to be earned, but honour is an attitude of the heart. Not
everyone will earn your respect, but everyone deserves to be shown honour."
- Anonymous
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] GSoC 2013 Proposal for Entity Suggester

[Nilesh Chakraborty]

Hi Lydia,

I've submitted the proposal via google-melange.com too.

Thanks Rahul, I added my details on the
http://www.mediawiki.org/wiki/Summer_of_Code_2013#Students list.

Could you tell me whom I should list as my mentor?

Cheers,
Nilesh


On Fri, May 3, 2013 at 9:29 PM, Rahul Maliakkal wrote:

> ctrl + F "mediawiki" in your proposal. It is "MediaWiki" and not
> "mediawiki".
>
> Thanks
>
>
> On Fri, May 3, 2013 at 9:13 PM, Nilesh Chakraborty  >wrote:
>
> > Hello,
> >
> > I have drafted my proposal under my user page here:
> > https://www.mediawiki.org/wiki/User:Nilesh.c/Entity_Suggester
> >
> > Please have a look at it and let me know if I can make any changes to
> make
> > it better in any way. :-)
> >
> > Cheers,
> > Nilesh
> >
> > --
> > A quest eternal, a life so small! So don't just play the guitar, build
> one.
> > You can also email me at cont...@nileshc.com or visit my
> > website
> > ___
> > 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
>



-- 
A quest eternal, a life so small! So don't just play the guitar, build one.
You can also email me at cont...@nileshc.com or visit my
website
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] RFC: New approach to release notes

[Krinkle]

On May 2, 2013, at 7:41 PM, Brad Jorsch  wrote:

> I like the idea of not having to mess with RELEASE-NOTES-#.## merge
> conflicts. But I'm not entirely sure about everything in the proposal.
> 
> On Thu, May 2, 2013 at 12:30 PM, Krinkle  wrote:
>> For more details see Proposal 2 on this page:
>> 
>> https://www.mediawiki.org/wiki/Requests_for_comment/Release_notes_automation#Proposal_2:_Proper_commit_message
> 
>>> To avoid wrong entries for bugs that were merely mentioned in the commit
>>> message but not fixed in that commit, it becomes more important that we
>>> enforce a consistent format. "bug 123" is a mention. "Bug: 123" in footer
>>> meta-data indicates the bug was fixed.
> 
> So we're changing the semantics of that "Bug" footer already? Instead
> of being used for searching changesets related to a bug, now it's only
> for searching changesets actually fixing a bug? And what about
> changesets that only partially fix a bug? Or bugs where changes to
> both core and extensions are needed to fix a bug?
> 

Fair point. We could use some other detectable way instead. However
I'd prefer to keep things simple where "bug 123" is a mention and
"Bug: 123" a resolution. Both are linkified by Gerrit, so that's not
an issue.

We could introduce something like "Bug-Fixed: 123". But I'm not sure
if more syntax is the answer here. Note we also have people using
"(bug 123)" in the subject still, and even people copying BugZilla's
format of "Bug 123: title".

Or we could simply omit this detection altogether and build the list
from Bugzillla instead (resolved bugs marked as fixed for the
appropriate milestone). Then we'd only have to make sure periodically
that recently closed bugs without a milestone set get a milestone set.
I believe several people perform such query already and fill in the
missing milestones.

>>> We can't use the commit message subject because they aren't always the same
>>> as what you want to write in the release notes.
> 
> So are we getting rid of the recommended less-than-50-character limit
> on commit subjects? Or are we assuming that whoever volunteers to
> clean up the subject-dump will expand on it as necessary?
> 

No, the commit subject character limit is there for a good reason. We
shouldn't change that for this.

First of all, I think a lot of our commit subjects are poorly written,
even for a commit message. Having said that, a good commit subject is
also a good release note (that is, if the change itself is notable for
release notes). I don't think that these extensive paragraphs of text
we are known for in release notes are a good habit.

We already have a 62-char limit for the commit subject. That seems to
be going well. Assuming that we properly summarise changes that way
already, why would one need more room in the release notes? It is the
same event.

There are cases where it is important to write more elaborate notes
for maintenance for extension developers and migration/upgrading for
site administrators.

And yes when the release notes are processed on the wiki page, things
that need further documentation can be freely written in (for example)
an "Upgrade" or "To extension maintainers" section – instead of
scattered through the bullet point lists.

For example:

> == Changes ==
> * foo: Upgrade to version 1.20
> * bar: Don't silently ignore invalid values in event handler
> * ..
> 
> == To extension maintainers ==
>
> Various bar plugins are known to call the event handler with an object instead
> of an array containing the object. This was previously silently skipped.
> This failure is now explicit by throwing an invalid arguments exception.
> 


>>> Mark entries with the relevant labels ("New", "Removed", "Breaking" etc.)
> 
> I worry that whoever is doing this for API changes (if it doesn't wind
> up being me) won't know how we determine "Breaking" for API changes.
> I.e. "anything that's not backwards-compatible for API users".
> 

"If you don't know what you're doing, don't do it?"

I think we can reasonably assume good faith that people won't go and
mislabel things on the wiki page as "breaking" for a component they
are not knowledgeable in.

Plus, it is a wiki page, so it'll be a lot easier to keep track of and
fix for everyone involved.

This will make that easier since this would basically turn to doing a
"post-merge" review of activities to some degree.

-- Krinkle






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

[Wikitech-l] [GSoC 2013] Mobilize Wikidata project proposal

[Pragun Bhutani]

Hello,

I've completed my proposal for my project aimed at Mobilizing Wikidata. I'd
really appreciate any and all feedback from the community. Nitpicking is
welcome. :)

http://www.mediawiki.org/wiki/User:Pragunbhutani/GSoC_2013_Proposal

Best regards,
Pragun Bhutani
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] GSoC/OPW Proposal Updates: VisualEditor Mathematical Equation Plugin

[praveenp]

On Thursday 02 May 2013 11:26 PM, Jiabao Wu wrote:

Hi praveenp,

Is the language Malayalam...? It looks pretty cute, but I can't understand
it (as google translate can't translate it) :P What non-Latin codes you
would actually like the mathematical equation plugin to support?
Yes it is Malayalam. Also I found various other languages with strong 
mathematical history (Hindi, Tamil, Arabic etc) also not supported by 
Math extension. Details available in the bug.



On Fri, May 3, 2013 at 3:47 AM, Jiabao Wu  wrote:


Thanks a lot for your advices and encouragements. :D


On Fri, May 3, 2013 at 3:11 AM, Peter Krautzberger <
peter.krautzber...@mathjax.org> wrote:


Looks good. I left a comment.


On Thu, May 2, 2013 at 10:04 AM, Jiabao Wu  wrote:


Hey all,

I have made a big change to my proposal in accordance to community's
responses.
I'd like to invite feedback on this new proposal,

http://www.mediawiki.org/wiki/User:Jiabao_wu/GSoC_2013_Application

I know the VisualEditor team and everyone else are all very busy as its
almost
closing in to the final submission date, but comments still would be

great,

either before or after that deadline.

A short summary of my approach to VisualEditor Mathematical Equation

Plugin

step 1: make a node handler in visual editor to allow user to type in

LaTex

code in a box and display it underneath in real time, which is

similar to

Aloha Editor suggested by Peter.
step 2: update the GUI to have symbols and function buttons, which

allow

user

to click the buttons and insert the latex code of the symbol or

function

in

the editing box
step 3: allow users with latex experience to edit math in VisualEditor

like

in Google Docs (this has been moved to optional currently, but still

very

likely to be able to make it.)

Those changes are applied to my synopsis, deliverables, and timeline.

Thanks!

jiabao
___
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



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

[Wikitech-l] Project proposal for GSOC

[siddharth patel]

Hi,

I understand that it seems that i'm bit late to apply for a project,
however i want to assure you that i'm very interested and motivated to
build it.

In my application i gave a brief report about building a
knowledge/educational website.

what do you think about it?
is it a cool idea?

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

[Wikitech-l] Proposal for Inline commenting , summer of code project.

[Sastry aditya]

Name and contact information

*Name: AV Aditya Sastry*
*Email:ganeshadit...@gmail.com*
*IRC or IM networks/handle(s): **ganeshadit...@gmail.com*
*Location:Vishakhapatanam, Andhra Pradesh*
*Typical working hours: 2:00 PM to 12:30AM*
Synopsis

Every MediaWiki article has a talk page. But the discussions here are very
generic in nature and are concerned with the whole article rather than a
part of it.


With Inline commenting, user could select a line of an article and write a
comment for it, which could be viewed by other users and they can respond
to the comment as well.



This greatly helps engage the readers as well the editors in discussions
about the articles and thus help make them better and accurate.


The project itself can be divided into two parts.

1) User Interface.

2) Database classes.



Every article being displayed will have a tab in the top right corner
linking it to this extension. Here the user can view the comments for the
article as well as make comments.



When the user clicks on the tab, the name of the article is communicated to
the extension which is used to retrieve the comments from the database.



Each comment is indexed with three entities the page name, starting and
ending index and these are used to retrieve the associated comments from
the database and display them. Displaying them is done using AJAX and
JQuery. In the mockup I have provided I haven't used these two technologies
as I was constrained by time.
Deliverables

1) Special page to view comments as well as make them

2) Database classes.

3) Sanitizer classes needed to sanitize the comments posted.

4) Parser functions(A special magic word will be created as {{Page title,
Start index, ending index}} which will be converted to a link by this
parsing function.)

5) AJAX, JQuery and any necessary JS functions to implement this
functionality.

Time frame:

   1. pre 16th: Learning about JQuery specifically this functionality
   http://www.w3schools.com/jquery/tryit.asp?filename=tryjquery_slide_down and
   about the database classes helper functions(will be consulting my mentor
   for the databases part).
   2. 16th to 23rd june: Developing the Database classes and unit testing.
   3. 23rd june to 30th june: Working with the sanitizer classes to
   implement any additional functionalities needed to secure Database access
   and unit testing it.
   4. 30th june to 7th july: Developing the parser functions and unit
   testing.
   5. 7th july to 20th july:  Smoke testing with these three components put
   together.
   6. 20th july to 31st july: Developing the User interface using JQuery,
   AJAX and JS as well as writting the necessary CSS.
   7. 31st july to 10th august: putting everything together and smoke
   testing it.
   8. 10th august to 20th august: Beta testing and using the feedback to
   make modifications
   9. 20th august to 16th September: Documenting the whole extension.

About you



I have been using Wikipedia since my 10th class. I owe my life to Wikipedia
cause anything I have accomplished academically its owing to Wikipedia. I
have only contributed to my university's Wikipage once. But mostly I have
been a consumer.


How ever I feel ashamed in confessing that until I started working on
MediaWiki I didn't know about the talk page and even when I came to know
about it, I noticed that the talk pages of few articles that I frequently
read are congested with discussions about the whole article rather than a
sub part of it that I am concerned with. Hence I had to read the whole
discussion to comprehend the context to be able to contribute to these
discussions. I am sure other Wikipedia readers might have felt the same
about it to.

Participation

I am a workaholic. I can't focus on anything else when I have some work
pending. So I will be spending all my free time on this project and it is
my first priority.



I will be communicating my progress on weekly basis and I plan on putting
my extension in a github and I would be committing to it regularly on daily
basis so that my mentor could track my progress.



Till the end of this month I wouldn't be available on IRC as am changing my
ISP(My current ISP strangely blocks IRC, SSH, FTP and it is because of him
that my bugfixes were so horrible initially). However I am still accessible
on email, gmail, facebook and on phone if deemed necessary. Once I finish
switching my ISP I will be available in Freenode.
Past open source experience

I have fixed three bugs in MediaWiki. Here's my github account
https://github.com/ganeshaditya1. Here I am posting the gerrit links as
they are shorter than the bug links in buzilla, these three have been
merged, the insert http links is not working.

   - https://gerrit.wikimedia.org/r/#/c/59822/
   - https://gerrit.wikimedia.org/r/#/c/59395/ (This was my first bugfix to
   an opensource project and my first time with git and I had a pathetically
   slow (3kbps 2G internet connection), so I made a lot of mistakes and
   occasio

Re: [Wikitech-l] Project proposal for GSOC

[Sumana Harihareswara]

On 05/03/2013 01:53 PM, siddharth patel wrote:
> Hi,
> 
> I understand that it seems that i'm bit late to apply for a project,
> however i want to assure you that i'm very interested and motivated to
> build it.
> 
> In my application i gave a brief report about building a
> knowledge/educational website.
> 
> what do you think about it?
> is it a cool idea?
> 
> Regards
> Siddharth Patel

Hi, Siddharth.  Thanks for your note.

In case you don't get into GSoC: you are always welcome to contribute to
MediaWiki as a volunteer.  Guide:
https://www.mediawiki.org/wiki/How_to_contribute

If you want feedback from the community in the next hour, you will need
to make your proposal public in Melange, or put a draft on mediawiki.org
(perhaps in a subpage of your user page).  Then link to it in a reply to
this mailing list thread.

I building an educational website that helps people gain knowledge.
That is a reason I work on MediaWiki for Wikimedia. :-)

-- 
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] Proposal for Inline commenting , summer of code project.

[Jeremy Baron]

On Fri, May 3, 2013 at 5:53 PM, Sastry aditya  wrote:
> *Typical working hours: 2:00 PM to 12:30AM*

That's essentially useless data without a timezone...

-Jeremy

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

Re: [Wikitech-l] GSoC 2013 Proposal for Entity Suggester

[Lydia Pintscher]

On Fri, May 3, 2013 at 7:02 PM, Nilesh Chakraborty  wrote:
> Hi Lydia,
>
> I've submitted the proposal via google-melange.com too.
>
> Thanks Rahul, I added my details on the
> http://www.mediawiki.org/wiki/Summer_of_Code_2013#Students list.
>
> Could you tell me whom I should list as my mentor?

Please list Denny and Daniel Kinzler for now. (This might change still.)


Cheers
Lydia

--
Lydia Pintscher - http://about.me/lydia.pintscher
Community Communications for Technical Projects

Wikimedia Deutschland e.V.
Obentrautstr. 72
10963 Berlin
www.wikimedia.de

Wikimedia Deutschland - Gesellschaft zur Förderung Freien Wissens e. V.

Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg
unter der Nummer 23855 Nz. Als gemeinnützig anerkannt durch das
Finanzamt für Körperschaften I Berlin, Steuernummer 27/681/51985.

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

[Wikitech-l] Google Summer of Code 2013 applications are closed

[Sumana Harihareswara]

We are no longer accepting applications for Google Summer of Code (GSoC)
2013.  We are always accepting new volunteer contributors:
https://www.mediawiki.org/wiki/How_to_contribute
-- 
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] RFC: New approach to release notes

[Brad Jorsch]

On Fri, May 3, 2013 at 1:02 PM, Krinkle  wrote:
> First of all, I think a lot of our commit subjects are poorly written,
> even for a commit message. Having said that, a good commit subject is
> also a good release note (that is, if the change itself is notable for
> release notes). I don't think that these extensive paragraphs of text
> we are known for in release notes are a good habit.

In my opinion, a good commit summary and a good release note are not
necessarily the same thing at all, otherwise we could just dump the
git log as the release notes and be done with it. Release notes
*should* go into sufficient detail to tell the reader what it is they
should be noting.

> We already have a 62-char limit for the commit subject. That seems to
> be going well. Assuming that we properly summarise changes that way
> already, why would one need more room in the release notes? It is the
> same event.

Taking a recent example,[1] please tell me how to compress the
following into 62 characters:

(in the New features section)

* (bug 45535) introduced the new 'LanguageLinks' hook for manipulating the
  language links associated with a page before display.

(in the API section)

* BREAKING CHANGE: action=parse no longer returns all langlinks for the page
  with prop=langlinks by default. The new effectivelanglinks parameter will
  request that the LanguageLinks hook be called to determine the effective
  language links.
* BREAKING CHANGE: list=allpages, list=langbacklinks, and prop=langlinks do not
  apply the new LanguageLinks hook, and thus only consider language links
  stored in the database.

I don't think "Add LanguageLinks hook with breaking changes to 4 API
modules" is detailed enough for release notes. And before you try to
cheat and split it into multiple commits, note that the new hook and
what it means for how langlinks are stored in the database is what is
the breaking change in those API modules; the actual changes to the
API modules are just mitigating or noting it.

The summary actually used for that revision, BTW, was "(bug 45535)
Hook for changing language links".

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

> "If you don't know what you're doing, don't do it?"

But do you know that you don't know?


-- 
Brad Jorsch
Software Engineer
Wikimedia Foundation

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

[Wikitech-l] Wikidata Features

[Puneet Kaur]

Hi all ,

I know its late but still.

I wished to let you all know that I have applied for the Wikidata Features
Project Idea in GSOC 2013.

I have a bit of experience in website development and designing, but I am
not sure whether all of my present knowledge would be sufficient for the
project.

I shall be exploring my hands on wikidata, the online knowledge base for
the rest of days.

Do let me know if I am expected of anything else than that mentioned above.


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

[Wikitech-l] Prototyping Wiki Inline Comments

[Anthony]

Dear all,

I have applied for the Prototyping Inline Comments for the Google Summer of
Code.

Essentially, the project is an extension that allows any wiki user to
select text and then make an inline comment or a reply to an existing
inline comment. Imagine: a user lands in a Wikipedia article, selects one
sentence and leaves an inline comment that others can optionally read and
reply to.

Users can make useful comments regarding specific part of articles, which
will be a part of collaborative work. The key benefit is to users to
collaborate easily - because this actually allows you to point to something
and comment in direct reference to it. It's like pointing your finger to a
piece of paper and telling your friend sitting next to you, which can only
be done in person and is currently impossible over the Internet. So it's a
really powerful feature for collaborations since it makes one of the
Internet-impossibles into a possible action.

That was for the insertion of a new comment. For the replying part, it will
be a format will likely be similar to how threads are like in a forum, for
the prototype.

As I go along the project, I will be posting more technical details and
updates. From now til the end of the project, I do hope to get everyone's
feedback along the way :)
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Prototyping Wiki Inline Comments

[Daniel Mietchen]

Hi Anthony,

interesting feature. How would the system handle cases in which the
content originally pointed at when making the initial inline comment
has been changed?

Daniel


On Fri, May 3, 2013 at 10:09 PM, Anthony  wrote:
> Dear all,
>
> I have applied for the Prototyping Inline Comments for the Google Summer of
> Code.
>
> Essentially, the project is an extension that allows any wiki user to
> select text and then make an inline comment or a reply to an existing
> inline comment. Imagine: a user lands in a Wikipedia article, selects one
> sentence and leaves an inline comment that others can optionally read and
> reply to.
>
> Users can make useful comments regarding specific part of articles, which
> will be a part of collaborative work. The key benefit is to users to
> collaborate easily - because this actually allows you to point to something
> and comment in direct reference to it. It's like pointing your finger to a
> piece of paper and telling your friend sitting next to you, which can only
> be done in person and is currently impossible over the Internet. So it's a
> really powerful feature for collaborations since it makes one of the
> Internet-impossibles into a possible action.
>
> That was for the insertion of a new comment. For the replying part, it will
> be a format will likely be similar to how threads are like in a forum, for
> the prototype.
>
> As I go along the project, I will be posting more technical details and
> updates. From now til the end of the project, I do hope to get everyone's
> feedback along the way :)
> ___
> 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] MathJax opt-in for all visitors

[Peter Krautzberger]

Thanks for all the feedback!

Matthew -- yes, the CAPTCHA bug is what I had in mind. IIRC navigating to
the MathJax option as a registered user was also complicated. Thanks for
creating the bug to track this proposal.

MZMcBride -- yes, I'm aware of it. This idea is specifically for
unregistered users

Niklas -- our upcoming release will have a full localization. Our beta came
out today, see http://www.mathjax.org/mathjax-v2-2-beta-now-available/.
We're hoping we get hosted on TranslateWiki team. Alternatively, we'll put
something up on Transifex.

Derk-Jan -- good point. I think an on/off button would be very useful. But
I'm not sure it's necessary to stop the rendering since the code I
suggested will replace the images only by the rendered equation. So from a
reader's perspective, there's no interruption. (Try the code as a
bookmarklet to see what I mean.)

Praveenp -- not sure how the two issues are related. I've commented on the
bug thread for some background on MathJax.


On Fri, May 3, 2013 at 8:13 AM, praveenp  wrote:

> I would like to see Server rendered png issues fixed before this. Simple
> images are better for various devices and browsers. But it will be better
> to allow users to force technology, if no other simple solutions possible.
>
>
> On Friday 03 May 2013 12:59 PM, Niklas Laxström wrote:
>
>>
>> What is the state of MathJax i18n currently? Before we show it to lots
>> of users it should be translatable.
>>
>
> MathJax available in Math extension is not completely capable to handle
> non-latin scripts. ( See this bug we filed yesterday:
> https://bugzilla.wikimedia.**org/show_bug.cgi?id=48032)
>
>
> -Niklas
>>
>>
>> --
>> Niklas Laxström
>>
>> __**_
>> 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

[Wikitech-l] Deployment Highlights - Week of May 6th

[Greg Grossmeier]

Hello and welcome to the latest installment of the Deployment Highlights
email.

The full calendar for next week lives at:
https://wikitech.wikimedia.org/wiki/Deployments#Week_of_May_6th

For the week of May 6th we have the following interesting deployments:

== Monday ==

* MediaWiki 1.22wmf3 to English Wikipedia
* Wikidata updates to English Wikipedia

https://www.mediawiki.org/wiki/MediaWiki_1.22/Roadmap#Schedule_for_the_deployments


== Tuesday ==

* Internationalization team:
** Run refresh-translatable-pages.php for remaining WMF wikis using
   Translate extension (mediawiki and meta were done last week).
** Enable ULS for anonymous users without language selection. This
   brings web fonts and input methods to anonymous users on wikis which
   have ULS (meta, mediawiki, wikidata and couple of others). Tehnically:
   $wgULSEnableAnon is replaced with $wgULSAnonCanChangeLanguage. 


== Wednesday ==

* MediaWiki 1.22wmf3 to the rest of the 'pedias.

== Thursday ==

* Normal Editor Engagement and Editor Engagement Experiments deploy
  windows.


== Friday ==

* NO DEPLOYS! ;-)


== All week ==

* Lightning Deploys!
** https://wikitech.wikimedia.org/wiki/Lightning_deployments


Best,

Greg

-- 
| Greg GrossmeierGPG: B2FA 27B1 F7EB D327 6B8E |
| identi.ca: @gregA18D 1138 8E47 FAC8 1C7D |

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

Re: [Wikitech-l] [WikimediaMobile] Caching Problem with Mobile Main Page?

[Arthur Richards]

+wikitech-l

I've confirmed the issue on my end; ?action=purge seems to have no effect
and the 'last modified' notification on the mobile main page looks correct
(though the content itself is out of date and not in sync with the 'last
modified' notification). What's doubly weird to me is the 'Last modified'
HTTP response headers says:

Last-Modified: Tue, 30 Apr 2013 00:17:32 GMT

Which appears to be newer than when the content I'm seeing on the main page
was updated... Anyone from ops have an idea what might be going on?


On Thu, May 2, 2013 at 10:01 PM, Yuvi Panda  wrote:
>
> Encountered
https://en.wikipedia.org/wiki/Wikipedia:Village_pump_(technical)#Issue_with_Main_Page_on_mobile.2C_viz._it_hasn.27t_changed_since_Tuesday
>
> Some people seem to be having problems with the mobile main page being
> cached too much. Can someone look into it?
>
>
> --
> Yuvi Panda T
> http://yuvi.in/blog
>
> ___
> Mobile-l mailing list
> mobil...@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/mobile-l




--
Arthur Richards
Software Engineer, Mobile
[[User:Awjrichards]]
IRC: awjr
+1-415-839-6885 x6687
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Issue with: en.m.wikipedia.org

[Arthur Richards]

The mobile web team is planning to deploy a fix for Opera Mini-related
issues this coming Tuesday afternoon, which we expect will resolve this
particular issue.


On Fri, May 3, 2013 at 3:33 AM, Andre Klapper wrote:

> Hi,
>
> On Fri, 2013-05-03 at 09:39 +, Martin Butler wrote:
> > I'm not sure I'm posting this in the right place, but I (and I expect
> > lots of others!) can't use en.m.wikipedia.org via Opera Mini.
> > This is because the GO button next to the search box has disappeared.
>
> This is covered in
> https://bugzilla.wikimedia.org/show_bug.cgi?id=47567
>
> andre
> --
> Andre Klapper | Wikimedia Bugwrangler
> http://blogs.gnome.org/aklapper/
>
>
> ___
> Wikitech-l mailing list
> Wikitech-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l
>



-- 
Arthur Richards
Software Engineer, Mobile
[[User:Awjrichards]]
IRC: awjr
+1-415-839-6885 x6687
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] [WikimediaMobile] Caching Problem with Mobile Main Page?

[Asher Feldman]

The problem is due to recent changes that were made to how mobile caching
works.  I just flushed cache on all of the frontend varnish instances which
indeed appears to have fixed the problem but it isn't actually fixed.
Note, the frontend instances just have 1GB of cache, so only very popular
objects (like the enwiki front page) avoid getting LRU'd.  The backend
varnish instances utilize the ssd's and perform the heavy caching work.

When I originally built this, I had the frontends force a short (300s) ttl
on all cacheable objects, while the backends honored the times specified by
mediawiki.

I chose to only send purges to the backend instances (via wikia's old
varnishhtcpd) and let the frontend instances catch up with their short
ttls.  My reasoning was:

1) Our multicast purge stream is very busy and isn't split up by cache
type, so it includes lots of purge requests for images on
upload.wikimedia.org.  Processing the purges is somewhat cpu intensive, and
I saw doing so once per varnish server as preferable to twice.

2) Purges are for url's such as "en.wikipedia.org/wiki/Main_Page".  The
frontend varnish instance strips the m subdomain before sending the request
onwards, but still caches content based on the request url.  Purges are
never sent for "en.m.wikipedia.org/wiki/Main_Page" - every purge would need
to be rewritten to apply to the frontend varnishes.  Doing this blindly
would be more expensive than it should be, since a significant percentage
of purge statements aren't applicable.

I don't think my original approach had any fans.  Purges are now sent to
both varnish instances per host, and more recently, the 300s ttl override
was removed from the frontends.  But all of the purges are no-ops.

There are multiple ways to approach making the purges sent to the frontends
actually work such as rewriting the purges in varnish, rewriting them
before they're sent to varnish depending on where they're being sent, or
perhaps changing how cached objects are stored in the frontend.  I
personally think it's all an unnecessary waste of resources and prefer my
original approach.

-Asher

On Fri, May 3, 2013 at 2:23 PM, Arthur Richards wrote:

> +wikitech-l
>
> I've confirmed the issue on my end; ?action=purge seems to have no effect
> and the 'last modified' notification on the mobile main page looks correct
> (though the content itself is out of date and not in sync with the 'last
> modified' notification). What's doubly weird to me is the 'Last modified'
> HTTP response headers says:
>
> Last-Modified: Tue, 30 Apr 2013 00:17:32 GMT
>
> Which appears to be newer than when the content I'm seeing on the main
> page was updated... Anyone from ops have an idea what might be going on?
>
>
>
> On Thu, May 2, 2013 at 10:01 PM, Yuvi Panda  wrote:
> >
> > Encountered
> https://en.wikipedia.org/wiki/Wikipedia:Village_pump_(technical)#Issue_with_Main_Page_on_mobile.2C_viz._it_hasn.27t_changed_since_Tuesday
> >
> > Some people seem to be having problems with the mobile main page being
> > cached too much. Can someone look into it?
> >
> >
> > --
> > Yuvi Panda T
> > http://yuvi.in/blog
> >
> > ___
> > Mobile-l mailing list
> > mobil...@lists.wikimedia.org
> > https://lists.wikimedia.org/mailman/listinfo/mobile-l
>
>
>
>
> --
> Arthur Richards
> Software Engineer, Mobile
> [[User:Awjrichards]]
> IRC: awjr
> +1-415-839-6885 x6687
>
> ___
> Mobile-l mailing list
> mobil...@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/mobile-l
>
>
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] GSoC / OPW mentors README

[Matthew Flaschen]

On 04/27/2013 07:58 PM, Quim Gil wrote:
> SELECTING CANDIDATES
> 
> After the deadline we will meet to prioritize GSoC and OPW candidates.

When is this meeting?

Thanks,

Matt Flaschen

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

[Wikitech-l] GSoC: next steps

[Quim Gil]

Hi,

The Google Summer of Code student application phase is closed.

We have got a total of 69 applications from 60 students. The numbers so 
far are:


* 52 valid applications from 51 students. We are still triaging some of 
the last submissions. This number might decrease over the weekend.


* 11 ignored from 10 students: out of scope, clearly incomplete or 
duplicate.


* 6 withdrawn by the students.

The table at https://www.mediawiki.org/wiki/Summer_of_Code_2013 should 
match the list in the GSoC site.



Next milestone: May 6
Telling Google the min/max number of slots we want before May 6. Last 
year we got 9 slots and by all measurements we need a lot more this 
time. Both students and mentors need to work hard to convince Google 
that we deserve them!



EVERYBODY

Remember that all community members can provide feedback about features 
and proposals: 
http://lists.wikimedia.org/pipermail/wikitech-l/2013-May/069040.html



STUDENTS

Complete your data in the public Students table. Get feedback and 
improve your proposal in your wiki page. Contribute! 
https://www.mediawiki.org/wiki/How_to_contribute



MENTORS

* Fight for your slot! Remember that Google is the first who needs to be 
convinced. Wish-to-mentor ALL candidates for the features you volunteer 
to mentor. Don't worry yet about selecting candidates.


* Specify in the private comments whether you consider the projects you 
mentor ESSENTIAL or DESIRABLE. We will use this input to ask Google 
min/max slots. (Language, VisualEditor and Wikidata teams have already 
sent their team decisions on max/min slots).


* Be aware of the selection process: 
https://www.mediawiki.org/wiki/Mentorship_programs/Selection_process#Selecting_the_right_ones 
-  http://lists.wikimedia.org/pipermail/wikitech-l/2013-April/068913.html


I will submit the min/max numbers for Google by Sunday night PDT.

Questions? Just ask.

Enjoy your weekend!


PS: I won't chase students or mentors during the selection process. The 
principle is: if I have to do it now then I'll have to do it even more 
during the program.  B)


--
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] Wikitech-l Digest, Vol 118, Issue 13

[KAUSHAL SINGH]

Hello Sir,

I've submitted the proposal via google-melange.com
https://google-melange.appspot.com/gsoc/proposal/review/google/gsoc2013/kaushalsingh11/1

Also the project details are there on
http://www.mediawiki.org/wiki/User:Kaushalsingh11/Summer_of_Code_2013

-- 
With Kind Regards,
Kaushal Kumar Singh
B.tech Part III
Electronics Engineering
Indian Institute of Technology, B.H.U, Varanasi
INDIA  PIN-221005
Mo: +91 - 9839203380
E-Mail :  kaushal.ksingh.ec...@itbhu.ac.in
 kaushal.sing...@gmail.com
Skype : kaushal.singh07
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] I didn't withdraw. Dashboard says I have...

[Quim Gil]

Hi,

On 05/03/2013 08:58 PM, hungers.to.nurt...@gmail.com wrote:

I submitted my proposal to Wikimedia yesterday via GSoC. Now in my
dashboard of GSoC it's showing that I have withdrawn my proposal. But,*I
didn't *do that. So, please help me.


Mentors and org admins can't withdraw proposals, only their authors. 
Anyway, let's try to solve this:


"ALERT: The student has withdrawn this proposal. He/She can resubmit 
this proposal by clicking the Resubmit button that is accessible to them 
against the text "Withdraw proposal" on this page."


I have allowed you to edit your proposal only to see if you can 
re-enable it. Please don't edit it further. You can keep editing your 
wiki page.


If this doesn't work then please contact me personally. No need to 
involve wikitech-l.


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