[Wikitech-l] Google Summer of Code 2016 and Outreachy results out, Congrats interns

2016-04-23 Thread Tony Thomas 
Hello all,

Google released the selects for GSoC 2016 yesterday, and Wikimedia is happy
to welcome its 8 interns:

   1. Accuracy Review of Wikipedia
    - Priyanka. Mentors - James
   Salsman, Fabian Flock
   2. Extension for page creating/editing notification
    - Abhinand. Mentors -
   Yaron_Koren, tosfos
   3. Implementing HTML E-Mail support in MediaWiki
    - Galorefitz. Mentors -
   Parent5446, Tony Thomas
   4. Integration of IFTTT support to WikiData
    - D3r1ck01. Mentors -
   Slaporte, Bene, hoo, Lydia_Pintscher
   5. Improving static analysis tools for MediaWiki
    - Lethexie. Mentors. Mentors
   - Addshore, EBernhardson, Legoktm
   6. List Of Contributors  -
   Devirk. Mentors- Addshore, Samtar
   7. Port catimages.py to pywikibot-core
    - AbdealiJK. Mentors -
   DrTrigo, jayvdb
   8. Pywikibot Support for Thanks
    - darthbhyrava. Mentors -
   javydb, legoktm

Your comments and feedback are welcome at the proposal and its parent
tasks. We have couple of projects coming up from the Community Wishlist
survey, and thanks to the Wikidata team too for their help.

We selected three[1] of our Outreachy interns for GSoC, as their mentors
and org admins agreed.

For the selected applicants, the community bonding period will begin
shortly, and you can find out how to make maximum out of it in our *Life of
a successful project* doc[2]. Edits are welcome on that document too, to
make things easy for the interns.

For applicants who came up with a strong proposal, and couldn't make it for
this round, you can plan to work on the same ( if your mentors agree too ).
You can apply with the same for a future round considering consensus and
eligibility.
We have marked rejected proposal tasks as declined, but feel free to
implement, in case the community and mentors seem interested. Consider
notifying your siblings about the upcoming Google Code In ( g.co/gci )
round too, if they are < 18 years of age and do take a look at Wikimedia
PEG[3].

Thanks to Sumit[4] and Niharika for co-organizing this round with me, and
Quim for his time.

You can find the GSoC-16 phab project at
https://phabricator.wikimedia.org/tag/google-summer-of-code-2016/ for a
better view.

[1] https://wiki.gnome.org/Outreachy/2016/MayAugust#Wikimedia
[2]
https://www.mediawiki.org/wiki/Outreach_programs/Life_of_a_successful_project#Community_bonding_period
[3] https://meta.wikimedia.org/wiki/Grants:PEG\
[4] https://www.mediawiki.org/wiki/User:Sumit.iitp

Thanks,
Tony Thomas 
Home  | Blog  |
ThinkFOSS 
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Google Summer of Code 2016 and Outreachy results out, Congrats interns

2016-04-23 Thread Aashaka Shah 
Congratulations to all selected interns!

I had also submitted a GSoC proposal for "Improving static analysis tools
for MediaWiki", but I suppose the better candidate got selected. What I
would like to know, for the next round of GSoC/ Outreachy is, how exactly
was the better candidate decided? The answer would be really helpful to me
and all other future candidates :)

Thank you, and good luck to all the interns!
Regards,
Aashaka Shah


On Sat, Apr 23, 2016 at 12:31 PM, Tony Thomas <01tonytho...@gmail.com>
wrote:

> Hello all,
>
> Google released the selects for GSoC 2016 yesterday, and Wikimedia is happy
> to welcome its 8 interns:
>
>1. Accuracy Review of Wikipedia
> - Priyanka. Mentors - James
>Salsman, Fabian Flock
>2. Extension for page creating/editing notification
> - Abhinand. Mentors -
>Yaron_Koren, tosfos
>3. Implementing HTML E-Mail support in MediaWiki
> - Galorefitz. Mentors -
>Parent5446, Tony Thomas
>4. Integration of IFTTT support to WikiData
> - D3r1ck01. Mentors -
>Slaporte, Bene, hoo, Lydia_Pintscher
>5. Improving static analysis tools for MediaWiki
> - Lethexie. Mentors.
> Mentors
>- Addshore, EBernhardson, Legoktm
>6. List Of Contributors  -
>Devirk. Mentors- Addshore, Samtar
>7. Port catimages.py to pywikibot-core
> - AbdealiJK. Mentors -
>DrTrigo, jayvdb
>8. Pywikibot Support for Thanks
> - darthbhyrava. Mentors -
>javydb, legoktm
>
> Your comments and feedback are welcome at the proposal and its parent
> tasks. We have couple of projects coming up from the Community Wishlist
> survey, and thanks to the Wikidata team too for their help.
>
> We selected three[1] of our Outreachy interns for GSoC, as their mentors
> and org admins agreed.
>
> For the selected applicants, the community bonding period will begin
> shortly, and you can find out how to make maximum out of it in our *Life of
> a successful project* doc[2]. Edits are welcome on that document too, to
> make things easy for the interns.
>
> For applicants who came up with a strong proposal, and couldn't make it for
> this round, you can plan to work on the same ( if your mentors agree too ).
> You can apply with the same for a future round considering consensus and
> eligibility.
> We have marked rejected proposal tasks as declined, but feel free to
> implement, in case the community and mentors seem interested. Consider
> notifying your siblings about the upcoming Google Code In ( g.co/gci )
> round too, if they are < 18 years of age and do take a look at Wikimedia
> PEG[3].
>
> Thanks to Sumit[4] and Niharika for co-organizing this round with me, and
> Quim for his time.
>
> You can find the GSoC-16 phab project at
> https://phabricator.wikimedia.org/tag/google-summer-of-code-2016/ for a
> better view.
>
> [1] https://wiki.gnome.org/Outreachy/2016/MayAugust#Wikimedia
> [2]
>
> https://www.mediawiki.org/wiki/Outreach_programs/Life_of_a_successful_project#Community_bonding_period
> [3] https://meta.wikimedia.org/wiki/Grants:PEG\
> [4] https://www.mediawiki.org/wiki/User:Sumit.iitp
>
> Thanks,
> Tony Thomas 
> Home  | Blog  |
> ThinkFOSS 
> ___
> 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] Google Summer of Code 2016 and Outreachy results out, Congrats interns

2016-04-23 Thread Tony Thomas 
Hello Aashaka,

On Sat, Apr 23, 2016 at 1:26 PM, Aashaka Shah  wrote:

> I had also submitted a GSoC proposal for "Improving static analysis tools
> for MediaWiki", but I suppose the better candidate got selected. What I
> would like to know, for the next round of GSoC/ Outreachy is, how exactly
> was the better candidate decided? The answer would be really helpful to me
> and all other future candidates :)
>

True. The best approach would be to open up a Conpherence with your mentors
( I hope they appreciate it ), and asking the same. If you do not find any
lucky with that, kindly ping or add in the the org-admins too, and we will
get this resolved.

Thanks,
Tony Thomas 
Home  | Blog  |
ThinkFOSS 
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Best practices for read/write vs read-only requests, and our multi-DC future

2016-04-23 Thread Brion Vibber 
I've opened a phab task https://phabricator.wikimedia.org/T133448 about
writing up good intro docs and updating other docs to match it.

Feel free y'all to add to that or hang additional tasks onto it like better
utility classes to help folks transition code to background jobs... And
maybe infrastructure to make sure we're handling those jobs reliably on
small sites without dedicated job runners.

-- brion
On Apr 21, 2016 5:26 PM, "Brion Vibber"  wrote:

> On Thu, Apr 21, 2016 at 4:59 PM, Erik Bernhardson <
> ebernhard...@wikimedia.org> wrote:
>
>> On Apr 20, 2016 10:45 PM, "Brion Vibber"  wrote:
>> > Note that we could fire off a job queue background task to do the actual
>> > removal... But is it also safe to do that on a read-only request?
>> >
>>
>> https://www.mediawiki.org/wiki/Requests_for_comment/Master_%26_slave_datacenter_strategy_for_MediaWiki
>> > seems to indicate job queueing will be safe, but would like to confirm
>> > that. :)
>> >
>>
>> I think this is the preferred method. My understanding is that the jobs
>> will get shipped to the primary DC job queue.
>>
>
> *nod* looks like per spec that should work with few surprises.
>
>
>>
>> > Similarly in https://gerrit.wikimedia.org/r/#/c/284269/ we may wish to
>> > trigger missing transcodes to run on demand, similarly. The actual re
>> > encoding happens in a background job, but we have to fire it off, and we
>> > have to record that we fired it off so we don't duplicate it...
>> [snip]
>> >
>> The job queue can do deduplication, although you would have to check if
>> that is active while the job is running and not only while queued. Might
>> help?
>>
>
> Part of the trick is we want to let the user know that the job has been
> queued; and if the job errors out, we want the user to know that the job
> errored out.
>
> Currently this means we have to update a row in the 'transcode' table
> (TimedMediaHandler-specific info about the transcoded derivative files)
> when we fire off the job, then update its state again when the job actually
> runs.
>
> If that's split into two queues, one lightweight and one heavyweight, then
> this might make sense:
>
> * N web requests hit something using File:Foobar.webm, which has a missing
> transcode
> * they each try to queue up a job to the lightweight queue that says
> "start queueing this to actually transcode!"
> * when the job queue runner on the lightweight queue sees the first such
> job, it records the status update to the database and queues up a
> heavyweight job to run the actual transcoding. The N-1 remaining jobs duped
> on the same title/params either get removed, or never got stored in the
> first place; I forget how it works. :)
> * ... time passes, during which further web requests don't yet see the
> updated database table state, and keep queueing in the lightweight queue.
> * lightweight queue runners see some of those jobs, but they have the
> updated master database state and know they don't need to act.
> * database replication of the updated state hits the remote DC
> * ..time passes, during which further web requests see the updated
> database table state and don't bother queueing the lightweight job
> * eventually, the heavyweight job runs, completes, updates the states at
> start and end.
> * eventually, the database replicates the transcode state completion to
> the remote DC.
> * web requests start seeing the completed state, and their output includes
> the updated transcode information.
>
> It all feels a bit complex, and I wonder if we could build some common
> classes to help with this transaction model. I'm pretty sure we can be
> making more use of background jobs outside of TimedMediaHandler's slow
> video format conversions. :D
>
> -- brion
>
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] ResourceLoader, latency, & progressive enhancement

2016-04-23 Thread Brion Vibber 
Started as quick thoughts, turned into more of an essay, so I've posted the
bulk on mediawiki.org:

https://www.mediawiki.org/wiki/User:Brion_VIBBER/ResourceLoader_and_latency


tl;dr summary:

On slow networks, latency in loading large JS and HTML resources means
things don't always work right when we first see them.

If we take advantage of HTTP 2 we could skip the concatenation of separate
ResourceLoader modules to reduce latency until each module _runs_, without
adding _network_ latency.

And if we're more clever about handling 'progressive enhancement' via JS
_while_ an HTML page loads, we could reduce the time before large pages
become fully interactive.

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

Re: [Wikitech-l] ResourceLoader, latency, & progressive enhancement

2016-04-23 Thread Daniel Friesen 
Tangentially related, Chrome plans to drop support for SPDY and go
HTTP/2 only this year, Edge already dropped support for SPDY, and other
browsers may too.
So before this is actually implemented, Wikimedia might want to upgrade
web server software to support HTTP/2 (currently MediaWiki.org looks to
only be using SPDY).

Though a sad realization is that IE11 only supports HTTP/2 on Windows 10
(other Windows versions will only support SPDY) and same goes for Safari
only doing HTTP/2 on OSX 10.11+.
Which is relevant because some webservers like Nginx intentionally drop
the SPDY implementation in the release they implement HTTP/2.

~Daniel Friesen (Dantman, Nadir-Seen-Fire) [http://danielfriesen.name/]

On 2016-04-23 3:08 PM, Brion Vibber wrote:
> Started as quick thoughts, turned into more of an essay, so I've posted the
> bulk on mediawiki.org:
>
> https://www.mediawiki.org/wiki/User:Brion_VIBBER/ResourceLoader_and_latency
>
>
> tl;dr summary:
>
> On slow networks, latency in loading large JS and HTML resources means
> things don't always work right when we first see them.
>
> If we take advantage of HTTP 2 we could skip the concatenation of separate
> ResourceLoader modules to reduce latency until each module _runs_, without
> adding _network_ latency.
>
> And if we're more clever about handling 'progressive enhancement' via JS
> _while_ an HTML page loads, we could reduce the time before large pages
> become fully interactive.
>
> -- brion
> ___
> 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] My username

2016-04-23 Thread Muhammed Tatlısu 
Hı, I requested to change the user name (Kingbjelica to Müdür)
Now I want to cancel it.
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] My username

2016-04-23 Thread K. Peachey 
On 24 April 2016 at 15:37, Muhammed Tatlısu 
wrote:

> Hı, I requested to change the user name (Kingbjelica to Müdür)
> Now I want to cancel it.
>
> Where?
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] My username

2016-04-23 Thread Keegan Peterzell 
On Sun, Apr 24, 2016 at 12:37 AM, Muhammed Tatlısu <
tatlisumuham...@gmail.com> wrote:

> Hı, I requested to change the user name (Kingbjelica to Müdür)
> Now I want to cancel it.
> ___
> Wikitech-l mailing list
> Wikitech-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l


I have declined the request on your behalf in my volunteer capacity as a
Global Renamer (volunteer account isn't subscribed to these lists).

-- 
Keegan Peterzell
Community Liaison, Product
Wikimedia Foundation
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l