Re: [Wikitech-l] New Feature from Community Tech: Enhanced Password Reset

[Niharika Kohli]

Congratulations CommTech! You rock! :)

On Mon, May 11, 2020 at 6:24 PM Toby Negrin  wrote:

> Congrats Community Tech!
>
> On Mon, May 11, 2020 at 16:26 David Barratt 
> wrote:
>
> > Awesome!!!
> >
> > [image: Wikimedia-logo black.svg] *David Barratt* (he/him)
> > Software Engineer, Anti-Harassment Tools
> > Wikimedia Foundation 
> >
> >
> > On Mon, May 11, 2020 at 6:01 PM Ilana Fried 
> wrote:
> >
> > > Hello everyone,
> > >
> > >
> > > The Community Tech team[1] has released a new feature: Enhanced
> Password
> > > Reset[2]. We developed this feature in response to the #3 wish[3] from
> > the
> > > 2019
> > > Community Wishlist Survey[4]. With this feature, you can prevent
> password
> > > reset emails from being sent unless both your username and email
> address
> > > are provided on Special:PasswordReset. This is an optional feature,
> > > available in the “Email options” section of Preferences. If you enable
> > the
> > > feature, you can reduce harassment through unsolicited password reset
> > > emails. For more information, you can visit the Help:Password Reset
> > page[5]
> > > and the project page[6].
> > >
> > >
> > > Thank you,
> > >
> > >
> > > Ilana Fried
> > >
> > > Product Manager, Community Tech
> > >
> > >
> > > [1]. https://meta.wikimedia.org/wiki/Community_Tech
> > > [2].
> > >
> > >
> >
> https://www.mediawiki.org/wiki/Help:Reset_password#I%E2%80%99m_getting_password_reset_emails_that_I_didn%E2%80%99t_request._How_do_I_prevent_this_from_happening
> > > ?
> > > [3].
> > >
> > >
> >
> https://meta.wikimedia.org/wiki/Community_Wishlist_Survey_2019/Anti-harassment/Add_an_option_to_require_email_address_and_username_to_reset_password
> > > [4].
> > > https://meta.wikimedia.org/wiki/Community_Wishlist_Survey_2019/Results
> > > [5] https://www.mediawiki.org/wiki/Help:Reset_password
> > > [6]
> https://meta.wikimedia.org/wiki/Community_Tech/Password_Reset_Update
> > > ___
> > > 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
>
> --
> -Toby
> ___
> Wikitech-l mailing list
> Wikitech-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l



-- 
Niharika
Product Manager
Anti-Harassment Tools team
Wikimedia Foundation
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Being logged out of gerrit

[Niharika Kohli]

I constantly face this too. Would really like for this to be fixed.

On Sat, Oct 12, 2019 at 5:42 AM Amir Sarabadani  wrote:

> Hello,
> I'm being logged out from gerrit basically every other day, I'm pretty sure
> I use "Remember me" and because my passwords are secure, It's cumbersome to
> login (not that much but it piles up the frustration).
>
> Is it just me? My colleagues and some other people I personally know have
> this issue too but I'm not sure if it's universal.
>
> Best
> --
> Amir (he/him)
> ___
> Wikitech-l mailing list
> Wikitech-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l



-- 
Niharika
Product Manager
Anti-Harassment Tools team
Wikimedia Foundation
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] [Engineering] Gerrit now automatically adds reviewers

[Niharika Kohli]

On Tue, Jan 22, 2019 at 6:12 PM Paladox via Wikitech-l <
wikitech-l@lists.wikimedia.org> wrote:

>  What your saying is making me think I’m wasting my time on improving this
> extension.
> Also other users that have spoken to me have thought this extension is
> great but could do with improvements which I am doing. We need to think of
> new users and how to improve there experence. The task was opened for a
> long while yet no one commented on it.
> I agree with legoktm feedback.
> “A process that annoys people based on nothing but the fact that
> theyhappened to be the last one touching a file *is* fundamentally broken.”
> yes hence why I’ve been making improvements by adding a button which is
> better then nothing right?
> As chad mentions it has no idea what is a typo fix compared to other
> things as it’s not A.I.
>

Thanks for working on this, Paladox. I think this can be a really useful
feature for newcomers and experienced developers alike, if implemented
well. I look forward to seeing it in action.


> On Tuesday, 22 January 2019, 12:05:24 GMT, Thiemo Kreuz <
> thiemo.kr...@wikimedia.de> wrote:
>
>  > Fundamentally broken sounds like a bit of a stretch.
>
> A process that annoys people based on nothing but the fact that they
> happened to be the last one touching a file *is* fundamentally broken.
> This is not how anyone should look for reviewers, neither manually nor
> automatically.
>
> Here is a thought experiment: We could send review requests to the
> *least* active users that are still around, but *never* touched a
> file. The positive effects of such an approach include:
> * More people get familiar with the code.
> * Knowledge gets spread more evenly.
> * Bottlenecks and bus factors get reduced.
> * These people probably have more time.
> * Review requests are spread more evenly.
> * Workload is spread more evenly.
>
> Still sounds like a bad idea? Sure, because it is. Now tell me: How is
> it more clever to do the *opposite* and dump review requests on people
> that have to much workload already?
>
> At this point I don't care any more if we are talking about a fully
> automated process or a suggest button. Both are targeting the wrong
> people.
>
> > it was probably working quite well for our less-trafficked repositories.
>
> What is the difference between being the last one fixing a typo in a
> low-traffic vs. high-traffic repository? In both cases it's the wrong
> person.
>
> Thiemo
>
> ___
> 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



-- 
Niharika
Product Manager
Community Tech
Wikimedia Foundation
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Tidy removed on all Wikimedia wikis (final update)

[Niharika Kohli]

Congratulations! This is a huge win for everyone. Great job, Subbu and
team!

On Thu, Aug 16, 2018 at 3:54 PM Bartosz Dziewoński 
wrote:

> I'd like to offer additional thanks to Izno, who appears to be going
> through all of the old Tidy-related tasks, meticulously testing to see if
> they're fixed in Remex, and closing them! :)
>
> --
> Matma Rex
> ___
> Wikitech-l mailing list
> Wikitech-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l



-- 
Niharika
Product Manager
Community Tech
Wikimedia Foundation
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] GlobalPreferences now available on a wiki near you

[Niharika Kohli]

Hello all,

I'm happy to announce that GlobalPreferences
 is now
available on all Wikimedia wikis. This project came out of the Wishlist
Survey in December 2016 (
https://meta.wikimedia.org/wiki/2016_Community_Wishlist_Survey/Results). It
was #4 on the list. The Community Tech team (
https://meta.wikimedia.org/wiki/Community_Tech) has worked for over 14
months, well past the yearly deadline, to deliver on it. This is one of the
most important projects this team has ever undertaken.

You can enable Global Preferences from *Preferences > Set your global
preferences* under your User Profile. You can also set per-wiki exceptions

for
each global preference.

This has been a long-desired feature (with the earliest known ticket dating
back to July 2008 - https://phabricator.wikimedia.org/T16950). I'd like to
give a shout out to Kunal Mehta (Legoktm), Sam Wilson and Max Semenik for
all their hard work that went into this project.

You can read more about the genesis of the project on the project page:
https://meta.wikimedia.org/wiki/Community_Tech/Global_preferences

You can find more information about how to use GlobalPreferences on the
Help page: https://www.mediawiki.org/wiki/Help:Extension:GlobalPreferences

Questions and comments are welcome on the discussion page:
https://www.mediawiki.org/wiki/Help_talk:Extension:GlobalPreferences

If there is a project you deeply care about and would like our team to work
on, please remember to submit a proposal for it during the next Wishlist
survey (https://meta.wikimedia.org/wiki/2018_Community_Wishlist_Survey)
scheduled to take place in November 2018. Make sure to let your friends at
Wikimania know about it too. :)

Thanks!
-- 
Niharika
Product Manager
Community Tech
Wikimedia Foundation
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] [Engineering] Phabricator spam - account approval requirement enabled

[Niharika Kohli]

On Sat, Jun 30, 2018 at 8:53 PM Greg Grossmeier  wrote:

> Hello,
>
> Unfortunately we are experiencing spam in our Phabricator instance
> again and have decided to turn on the requirement for new account
> approval by Phabricator admins as a mitigation step.
>

I'd request that it please be kept on until we have some spam mitigation
tools. At the very least easier revert actions.


>
> I'm sorry for the inconvenience. We are actively working to address this
> issue.
>
> Greg
>
> --
> | Greg GrossmeierGPG: B2FA 27B1 F7EB D327 6B8E |
> | Release Team ManagerA18D 1138 8E47 FAC8 1C7D |
> ___
> Engineering mailing list
> engineer...@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/engineering
>


-- 
Niharika
Product Manager
Community Tech
Wikimedia Foundation
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Gerrit newcomer bot

[Niharika Kohli]

Great work! I'm sure this will be incredibly helpful to a lot of new
developers. :)

On Fri, May 4, 2018 at 11:45 AM Srishti Sethi  wrote:

> *Hello all,A quick update related to Gerrit -- you will notice a small
> change on patches uploaded by new developers. There is a bot now which is
> adding a reviewer (as "Welcome, new contributor!") and a welcome message in
> a comment to a patch submitted by a new developer. You would also be able
> to query patches of new developers by typing in the search term: `ownerin:
> newcomers` (only applicable to new patches).Learn more about the bot, and
> file an issue here: https://github.com/srish/gerrit-newcomer-bot
> OR comment on the related
> Phab task: https://phabricator.wikimedia.org/T192046
> Thanks,Srishti *
>
> --
> Srishti Sethi
> Developer Advocate
> Technical Collaboration team
> Wikimedia Foundation
>
> https://www.mediawiki.org/wiki/User:SSethi_(WMF)
> ___
> Wikitech-l mailing list
> Wikitech-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l



-- 
Niharika
Product Manager
Community Tech
Wikimedia Foundation
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] [Ops] Changes to SWAT deployment policies, effective Monday April 30th

[Niharika Kohli]

On Fri, Apr 27, 2018 at 8:51 AM, Roan Kattouw 
wrote:

> Will multi-file, single-directory syncs still be allowed? In other words,
> can I deploy a change to the Foo extension that touches many files with
> scap sync-dir extension/Foo ?
>

According to the task description, yes.

While the "one command sync" patch system makes sense to us SWAT deployers,
we do get a fair number of volunteer developers contributing patches for
SWAT. They will have a hard time telling when they need to split a patch up
and how. How do we plan to address that?

Also, I think dropping the limit to 4 patches per window is extreme,
especially if we are asking people to start splitting their patches now.
Very often we can +2 multiple patches in one go if they don't affect each
other, or sync out changes together if they happen to the same file. I've
deployed 8 patches in a window often, with people asking if they can add
more yet. Due to timezone limitations, most people can only attend one of
the SWAT windows and if they can't get it out in that window, they have to
wait a whole day or more to get it out.


>
> On Thu, Apr 26, 2018, 15:15 Greg Grossmeier  wrote:
>
>> Hello,
>>
>> I have made two changes to SWAT policies today.
>>
>> First, we now disallow multi-sync patch deployments. See T187761[0].
>> This means that the sync order of files is determined by git commit
>> parent relationships (or Gerrit's "depends-on"). This is to prevent SWAT
>> deployers from accidentally syncing two patches in the wrong order.
>>
>> Second, we are reducing the number of allowed patches from 8 to 4. This
>> is to reduce stress on the SWAT deployer as well as set expectations for
>> requesters on the pace of the windows. See the approximate best case
>> time spent breakdown[1] for how we came to this number.
>>
>> I've updated the on-wiki documentation on wikitech[2][3].
>>
>>
>> Thank you for flying scap,
>>
>> Greg
>>
>>
>> [0] https://phabricator.wikimedia.org/T187761
>> [1]
>> * +2/Wait for Jenkins to merge - 2 min
>> * prepare git on tin - 1 min
>> * Deploy to mwdebug - 1 min
>> * Verify on mwdebug - 3 min
>> * Deploy to production - 1 min
>> * Verify & wait/watch logs - 2 min
>> [2] https://wikitech.wikimedia.org/w/index.php?title=SWAT_
>> deploys=prev=1789212
>> [3] https://wikitech.wikimedia.org/w/index.php?title=SWAT_
>> deploys=next=1789212
>>
>> --
>> | Greg GrossmeierGPG: B2FA 27B1 F7EB D327 6B8E |
>> | Release Team ManagerA18D 1138 8E47 FAC8 1C7D |
>>
>> ___
>> Ops mailing list
>> o...@lists.wikimedia.org
>> https://lists.wikimedia.org/mailman/listinfo/ops
>>
>
> ___
> Ops mailing list
> o...@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/ops
>
>


-- 
Niharika
Product Manager
Community Tech
Wikimedia Foundation
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Announcing MediaWiki code search

[Niharika Kohli]

On Wed, Jan 17, 2018 at 3:16 AM, Stephane Bisson 
wrote:

> This is currently down with "502 Bad Gateway".
>

It's not broken. There was a maintenance reboot earlier today which seems
to have caused this. The instance probably needs a manual restart by Lego.


> It has become such an important part of my workflow... I hope someone can
> fix it.
>
> On Fri, Dec 22, 2017 at 8:15 PM, Mukunda Modell 
> wrote:
>
> > This is something I've been wanting to build for a long time. Really
> really
> > cool stuff Kunal!
> >
> > On Thu, Dec 21, 2017 at 11:55 AM, Erika Bjune 
> > wrote:
> >
> > > Fantastic! Great work, Kunal!
> > >
> > > 
> > > Erika Bjune
> > > Acting Director of Security & Engineering Manager - Search Platform
> > > Wikimedia Foundation
> > >
> > > On Thu, Dec 21, 2017 at 7:08 AM, Volker E. 
> > wrote:
> > >
> > > > Great, thanks Kunal!
> > > > Another time that you've addressed a major pain point with a
> > convincingly
> > > > simple solution.
> > > >
> > > > On Thu, Dec 21, 2017 at 6:46 AM, Derick N. Alangi <
> > > alangider...@gmail.com>
> > > > wrote:
> > > >
> > > > > Hello Kunal,
> > > > >
> > > > > This tool is superb (i've tried some of it's functionalities out)
> and
> > > > it'll
> > > > > go a long way. Thank you very much. We are very much grateful for
> > this
> > > > > solution :)
> > > > >
> > > > > *Kind regards*
> > > > > *Alangi Derick N*
> > > > >
> > > > > *[image: https://twitter.com/AlangiDerick]
> > > > > 
> > > > >   *
> > > > >
> > > > > On Thu, Dec 21, 2017 at 3:32 PM, Andrew Otto 
> > > wrote:
> > > > >
> > > > > > Super cool!
> > > > > >
> > > > > > On Thu, Dec 21, 2017 at 9:31 AM, zppix e <
> > megadev44s.m...@gmail.com>
> > > > > > wrote:
> > > > > >
> > > > > > > Thank you very much Kunal!
> > > > > > >
> > > > > > > --
> > > > > > > Zppix
> > > > > > > Volunteer Wikimedia Developer
> > > > > > > Volunteer Wikimedia GCI2017 Mentor
> > > > > > > enwp.org/User:Zppix
> > > > > > > **Note: I do not work for Wikimedia Foundation, or any of its
> > > > > chapters.**
> > > > > > >
> > > > > > > > On Dec 21, 2017, at 8:25 AM, Bahodir Mansurov <
> > > > > bmansu...@wikimedia.org
> > > > > > >
> > > > > > > wrote:
> > > > > > > >
> > > > > > > > It's very fast!
> > > > > > > >
> > > > > > > > Also, as far as I know, it's not easy to search all
> extensions
> > at
> > > > > > > > once on Github, which makes this tool even more valuable.
> > > > > > > >
> > > > > > > > Thanks for sharing.
> > > > > > > >
> > > > > > > > Amir Ladsgroup  writes:
> > > > > > > >
> > > > > > > >> Kunal, you rock!
> > > > > > > >>
> > > > > > > >> Best
> > > > > > > >>
> > > > > > > >> ‪On Thu, Dec 21, 2017 at 1:50 PM ‫יגאל חיטרון‬‎ <
> > > > > > khit...@post.bgu.ac.il
> > > > > > > >
> > > > > > > >> wrote:‬
> > > > > > > >>
> > > > > > > >>> Wow, thanks a lot!
> > > > > > > >>> Igal (User:IKhitron)
> > > > > > > >>>
> > > > > > > >>>
> > > > > > > >>> 2017-12-21 14:09 GMT+02:00 Florian Schmidt <
> > > > > > > >>> florian.schmidt.wel...@t-online.de>:
> > > > > > > >>>
> > > > > > >  Kunal….. that is simply awesome! Big thanks for this new
> > tool,
> > > > > this
> > > > > > > will
> > > > > > >  make us in finding usages of deprecated methods, we would
> > like
> > > > to
> > > > > > > remove,
> > > > > > >  much more easy!
> > > > > > > 
> > > > > > > 
> > > > > > > 
> > > > > > >  Best,
> > > > > > > 
> > > > > > >  Florian
> > > > > > > 
> > > > > > > 
> > > > > > > 
> > > > > > >  Von: Wikitech-l [mailto:wikitech-l-bounces@
> > > lists.wikimedia.org]
> > > > > Im
> > > > > > >  Auftrag von Kunal Mehta
> > > > > > >  Gesendet: Donnerstag, 21. Dezember 2017 05:15
> > > > > > >  An: wikitech-l 
> > > > > > >  Betreff: [Wikitech-l] Announcing MediaWiki code search
> > > > > > > 
> > > > > > > 
> > > > > > > 
> > > > > > >  Hi,
> > > > > > > 
> > > > > > >  MediaWiki code search is a fully free software tool that
> > lets
> > > > you
> > > > > > >  easily search through all of MediaWiki core, extensions,
> and
> > > > skins
> > > > > > >  that are hosted on Gerrit. You can limit your search to
> > > specific
> > > > > > >  repositories, or types of repositories too. Regular
> > > expressions
> > > > > are
> > > > > > >  supported in both the search string, and when filtering by
> > > path.
> > > > > > > 
> > > > > > >  Try it out: https://codesearch.wmflabs.org/search/
> > > > > > > 
> > > > > > >  I started working on this because the only other options
> to
> > > > > > searching
> > > > > > >  the entire MediaWiki codebase was either cloning
> everything
> > > > > locally
> > > > > > >  (takes up 

[Wikitech-l] Fwd: [Wikimedia-l] Community Wishlist Survey: Top 10 wishes of 2017!

[Niharika Kohli]

Cross-posting.

-- Forwarded message --
From: Danny Horn 
Date: Thu, Dec 14, 2017 at 7:59 AM
Subject: [Wikimedia-l] Community Wishlist Survey: Top 10 wishes of 2017!
To: Wikimedia Mailing List 


Hi everyone,

The Community Tech team is happy to announce the top 10 wishes from the 2017
Community Wishlist Survey!

More than 1,100 people participated in the survey this year -- proposing,
discussing and voting on 214 ideas. There was a two-week period in November
to submit and discuss proposals, followed by two weeks of support voting.
The top 10 proposals with the most support votes now become Community
Tech's backlog of projects to evaluate and address.

And here's the new top 10:

#1. Maps improvements (154 support votes)
#2. Ping users from the edit summary (127)
#3. Programs and events dashboard (111)
#4. Blame tool (110)
#5. Infobox wizard (106)
#6. Article Alerts for more languages (102)
#7. Auto-save edits (96)
#7. Thanks notification for log entries (tie, 96)
#9. SVG translation (94)
#10. Commons deletion notification bot (91)

You can see the whole list here, with links to proposals, project pages and
Phabricator tickets:
https://meta.wikimedia.org/wiki/2017_Community_Wishlist_Survey/Results

So what happens next?

In 2018, the Community Tech team is responsible for investigating and
addressing the top 10 wishes. If there's a wish in the top 10 that we can't
work on, because it's unfeasible or because another group is working on it,
then we'll explain why we can't.

To get updates on our progress:

There are project pages for each of the top 10 wishes, which you can put on
your watchlist. We'll update them as the project progresses. (At time of
writing, these are just skeletons; actual information on each project is
still to come.) Feel free to post questions and suggestions on the project
talk pages: https://meta.wikimedia.org/wiki/Category:Community_Tech_-
_Current_projects

If you're familiar with the Phabricator ticketing system, the main Phab
task for each wish is noted on the Results page. You can also subscribe to
those tickets for updates.

We also publish several status reports through the year, to keep people
updated. You can watch the main Community Tech page for updates:
https://meta.wikimedia.org/wiki/Community_Tech

There are more questions and answers on the Wishlist Survey FAQ:
https://meta.wikimedia.org/wiki/2017_Community_Wishlist_Survey/FAQ

Thanks to everybody who proposed, discussed, debated and voted on ideas in
this year's Wishlist Survey!
___
Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/
wiki/Mailing_lists/Guidelines and https://meta.wikimedia.org/
wiki/Wikimedia-l
New messages to: wikimedi...@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,




-- 
Niharika
Software Engineer
Community Tech
Wikimedia Foundation
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Wikistats gets a facelift - Alpha Launch of Wikistats 2

[Niharika Kohli]

This is awesome. Great job A-team!

On Thu, Dec 14, 2017 at 12:12 PM, Victoria Coleman 
wrote:

> Nuria and team, fabulous work!  Wikistats 2 is such a huge improvement!
> Thank you!
>
>
> Best wishes,
>
> Victoria Coleman
>
> Chief Technology Officer
> Wikimedia Foundation
> 1 Montgomery Street, Suite 1600
> San Francisco, CA 94104
>
> +1-650-703-8112
>
> vcole...@wikimedia.org
>
>
>
>
>
>
>
>
> > On Dec 13, 2017, at 8:26 PM, Nuria Ruiz  wrote:
> >
> > Hello from Analytics Team!
> >
> > We are happy to announce the Alpha release of Wikistats 2. Wikistats has
> > been redesigned for architectural simplicity, faster data processing,
> and a
> > more dynamic and interactive user experience. First goal is to match the
> > numbers of the current system, and to provide the most important reports,
> > as decided by the Wikistats community (see survey) [1].  Over time, we
> will
> > continue to migrate reports and add new ones that you find useful. We can
> > also analyze the data in new and interesting ways, and look forward to
> > hearing your feedback and suggestions. [2]
> >
> > You can go directly to Spanish Wikipedia
> > https://stats.wikimedia.org/v2/#/es.wikipedia.org
> >
> > or browse all projects
> > https://stats.wikimedia.org/v2/#/all-projects
> >
> > The new site comes with a whole new set of APIs, similar to our existing
> > Pageview API but with edit data. You can start using them today, they are
> > documented here:
> >
> > https://wikitech.wikimedia.org/wiki/Analytics/AQS/Wikistats
> >
> >
> > FAQ:
> >
> > Why is this an alpha?
> > There are features that we feel a full-fledged product should have that
> are
> > still missing, such as localization. The data-processing pipeline for the
> > new Wikistats has been rebuilt from scratch (it uses
> distributed-computing
> > tools such as Hadoop) and we want to see how it is used before calling it
> > final. Also while we aim to update data monthly, it will happen a few
> days
> > after the month rolls because of the amount of data to move and compute.
> >
> > How about comparing data between two wikis?
> > You can do it with two tabs but we are aware this UI might not solve all
> > use cases for the most advanced Wikistats users. We aim to tackle those
> in
> > the future.
> >
> > How do I file bugs?
> > Use the handy link in the footer:
> > https://phabricator.wikimedia.org/maniphest/task/edit/?
> title=Wikistats%20Bug=Analytics-Wikistats,Analytics
> >
> > How do I comment on design?
> > The consultation on design already happened but we are still watching the
> > talk page:
> > https://www.mediawiki.org/wiki/Wikistats_2.0_Design_
> Project/RequestforFeedback/Round2
> >
> >
> > [1]
> > https://www.mediawiki.org/wiki/Analytics/Wikistats/
> DumpReports/Future_per_report
> > [2] https://wikitech.wikimedia.org/wiki/Talk:Analytics/Systems/Wikistats
> > ___
> > 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
>



-- 
Niharika
Software Engineer
Community Tech
Wikimedia Foundation
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Proposal for a developer support channel

[Niharika Kohli]

I'd like to add that having Discourse will provide the one thing IRC
channels and mailing lists fail to - search capabilities. If you hangout on
the #mediawiki IRC channel, you have probably noticed that we get a lot of
repeat questions all the time. This would save everyone time and effort.

Not to mention ease of use. Discourse is way more usable than IRC or
mailing lists. Usability is the main reason there are so many questions
about MediaWiki asked on Stackoverflow instead:
https://stackoverflow.com/unanswered/tagged/mediawiki
,
https://stackoverflow.com/questions/tagged/mediawiki-api?sort=newest
,
https://stackoverflow.com/questions/tagged/mediawiki-extensions...

I'd personally hope we can stop asking developers to go to IRC or mailing
lists eventually and use Discourse/something else as a discussion forum for
support.

On Sat, Nov 18, 2017 at 1:31 PM, Quim Gil  wrote:

> Hi, I have expanded
> https://www.mediawiki.org/wiki/Discourse#One_place_to_
> seek_developer_support
>
> https://www.mediawiki.org/wiki/Project:Support_desk is the only channel
> whose main purpose is to provide support. The volunteers maintaining are
> the ones to decide about its future. There is no rush for any decisions
> there. First we need to run a successful pilot.
>
> The rest of channels (like this mailing list) were created for something
> else. If these channels stop receiving questions from new developers, they
> will continue doing whatever they do now.
>
> > I'd like to understand how adding a venue will improve matters.
>
> For new developers arriving to our shores, being able to ask a first
> question about any topic in one place with a familiar UI is a big
> improvement over having to figure out a disseminated landscape of wiki Talk
> pages, mailing lists and IRC channels (especially if they are not used to
> any of these environments). The reason to propose this new space is them,
> not us.
>
> On Sat, Nov 18, 2017 at 5:01 PM, MZMcBride  wrote:
>
> > Brian Wolff wrote:
> > >On Friday, November 17, 2017, Quim Gil  wrote:
> > >> The Technical Collaboration team proposes the creation of a developer
> > >> support channel focusing on newcomers, as part of our Onboarding New
> > >> Developer program. We are proposing to create a site based on
> Discourse
> > >> (starting with a pilot in discourse-mediawiki.wmflabs.org) and to
> point
> > >>the many existing scattered channels there.
> > >
> > >What does point existing channels to discouse mean exactly? Are you
> > >planning to shutdown any existing channels? If so, which ones?
> >
> > Excellent questions. I'd like to know the answers as well.
> >
> > I raised a similar point at
> > . I skimmed
> > , looking for some answers,
> and
> > I didn't find any.
> >
> > Quim, are you involved in MediaWiki support in places such as the
> > #mediawiki IRC channel or the mediawiki-l mailing list? Are you involved
> > in MediaWiki support elsewhere? I'm trying to better understand how it
> > would be appropriate for you to seemingly suggest disrupting or shutting
> > down these established and functioning venues. If this is not your
> > suggestion, I'd like to understand how adding a venue will improve
> matters.
> >
> > MZMcBride
> >
> >
> >
> > ___
> > Wikitech-l mailing list
> > Wikitech-l@lists.wikimedia.org
> > https://lists.wikimedia.org/mailman/listinfo/wikitech-l
> >
>
>
>
> --
> Quim Gil
> Engineering Community Manager @ 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
>



-- 
Niharika
Software Engineer
Community Tech
Wikimedia Foundation
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Previous mediawiki version test wiki

[Niharika Kohli]

>
> When filing a phab task with some new bug,
> you always want to know - is it really new, or I just did not pay attention
> to it before?

What's the purpose of this information? If it's a bug, new or not, a ticket
needs to be filed.

And when I do know it's a new bug, I can open both versions
> in the same time, and compare the behaviour for this bug. And also, compare
> the console results - what exactly changed in html, in css, in js commands
> reactions.

I agree that information will save some developer time but at the same time
this information is not so easy to gather. This is helpful when the users
have some working knowledge of how developer tools work and how to compare
file changes. Usually in each version there are a lot of new changes. Often
it's not easy for developers even to find out what could be causing the
bug.

I can easily imagine such a wiki quickly falling into disuse.


On Thu, Sep 21, 2017 at 7:29 PM, יגאל חיטרון  wrote:

> It can work. But another Monday. I mean, if Tue-Wed-Thu there is a
> deployment of version 5, a day before, Mon there is a deployment of
> version 4, so starting from tomorrow, group 0 will get a way  to see
> both version, exactly from the beginning, but not until the end, for 6
> days, group 1 for 5 days, and group 2 for 4 days. And from Monday to the
> deployment, 1-2-3 days, there will not be use of this. I'll be very glad if
> it will be decided to do this, and if so, it will be a good thing to add to
> the text of how to report a bug in phabricator help, something about, you
> can check if it is a regression, the last version "falt", by comparing with
> this new wiki. I can thing about many dozens of tasks I wrote and read
> where this information could be useful, if added at the first place. Hope
> you decide this indeed. Thank you very much,
> Igal
>
>
> On Sep 22, 2017 05:17, "Chad"  wrote:
>
> > No non-emergency deployments on Fridays, Saturdays or Sundays.
> > Monday could work.
> >
> > -Chad
> >
> > ‪On Thu, Sep 21, 2017 at 7:15 PM ‫יגאל חיטרון‬‎ 
> > wrote:‬
> >
> > > I glad you say so. What about Friday?
> > > Igal
> > >
> > >
> > > On Sep 22, 2017 05:07, "Chad"  wrote:
> > >
> > > > It wouldn't be hard to do at all, technically. I imagine it'd be
> > > something
> > > > like a test3wiki.
> > > >
> > > > Main thing to know is when do we cycle off of the old version? When
> the
> > > > version goes out on Tuesdays? That day's already pretty loaded for
> > > software
> > > > moving about...
> > > >
> > > > -Chad
> > > >
> > > > On Thu, Sep 21, 2017 at 1:25 PM Brian Wolff 
> wrote:
> > > >
> > > > > Making your case here is probably best. The release engineering
> team
> > > are
> > > > > the people you probably have to convince, although of course anyone
> > > could
> > > > > potentially create such a wiki, in an unofficial way.
> > > > >
> > > > > Keep in mind that keeping an older version of the software running
> > does
> > > > > introduce a maintinance burden, so you will probably have to
> convince
> > > > > people that it would be regularly useful and not just useful this
> one
> > > > time.
> > > > >
> > > > > --
> > > > > bawolff
> > > > >
> > > > > On Thursday, September 21, 2017, יגאל חיטרון 
> > > wrote:
> > > > > > Thank you. Sorry to hear this. Is there some place I can suggest
> > this
> > > > and
> > > > > > explain why do I think it can be very helpful?
> > > > > > Igal
> > > > > >
> > > > > > On Sep 21, 2017 22:12, "Brian Wolff"  wrote:
> > > > > >
> > > > > >> On Thursday, September 21, 2017, יגאל חיטרון <
> > > khit...@post.bgu.ac.il>
> > > > > >> wrote:
> > > > > >> > Hi. Sometimes after the week deployment I need to compare the
> > new
> > > > > version
> > > > > >> > with the previous one, in some aspect. Is there a test wiki
> that
> > > > > always
> > > > > >> has
> > > > > >> > one version before the current?
> > > > > >> > Thank you.
> > > > > >> > Igal (User:IKhitron)
> > > > > >> > ___
> > > > > >> > Wikitech-l mailing list
> > > > > >> > Wikitech-l@lists.wikimedia.org
> > > > > >> > https://lists.wikimedia.org/mailman/listinfo/wikitech-l
> > > > > >>
> > > > > >> No there is not. You can of course download old versions of the
> > > > software
> > > > > >> and setup your own wiki but that is a lot of effort.
> > > > > >>
> > > > > >> --
> > > > > >> bawolff
> > > > > >> ___
> > > > > >> 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] Wikimedia Commons Android app update - new feature

[Niharika Kohli]

Hey Josephine,

Looks awesome. :)
Thank you for your continued dedication for the project (way) after
Outreachy ended. Very few people can do that!

Best of luck.


On Sun, Sep 4, 2016 at 5:35 PM, Josephine Lim 
wrote:

> Thanks Binaris, that would be great! :)
>
> Cheers,
> Josephine
>
>
> >
> > --
> >
> > Message: 7
> > Date: Sun, 4 Sep 2016 10:11:45 +0200
> > From: Bináris 
> > To: Wikimedia developers 
> > Subject: Re: [Wikitech-l] Wikimedia Commons Android app update - new
> > feature
> > Message-ID:
> >  > gmail.com>
> > Content-Type: text/plain; charset=UTF-8
> >
> > Nice effort! I post it onto the village pump of huwiki, maybe somebody
> > begins to post pictures today, as it is a nice Sunday here. :-)
> >
> >
> >
> >
>
>
> --
> Regards,
> Josephine
> ___
> Wikitech-l mailing list
> Wikitech-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l
>



-- 
Niharika
Software Engineer (International)
Wikimedia Foundation
[User:NiharikaKohli]
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] Workaround for repetitive OAuth prompts for labs tools

[Niharika Kohli]

Hi everyone,

If you're tired of repetitively prompting your users to approve your tool
(using MediaWiki oauth), here's a trick that might come in handy: you can
hit ".../w/index.php?title=Special:OAuth/authenticate" in the second leg of
the handshake instead of ".../w/index.php?title=Special:OAuth/authorize"
which would cause it to simply jump over to the callback URL if the user
has approved your tool at least once in the past. This works for authonly
or authonlyprivate grants only.

You can read up more about this here:
https://www.mediawiki.org/wiki/OAuth/For_Developers#Avoid_repetitive_login_prompts

Note that the mwoauth library was recently updated to include this change
so you might just want to update it.

Thanks Brad(for writing it), Gergö (for telling Bryan) and Bryan (for
telling me).
-- 
Niharika
Software Engineer (International)
Wikimedia Foundation
[User:NiharikaKohli]
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] [GSoC 2016] Query about the ideas' project time

[Niharika Kohli]

Hi Li,

On Mon, 2016-03-21 at 20:58 +0800, DJAKN wrote:
> > I am interested in the "Accuracy Review" project, but there is a note
> > saying the estimated time for a senior contributor is 3 weeks. Other
> > projects in the idea list have the similar estimated time. So should
> > we complete more than one project during the three-month internship
> > or just one?


A "senior contributor" here refers to someone who's been actively working
with MediaWiki for a quite long time now. Typically, mentors for a project
are the senior contributors. It's a yardstick we use to measure whether a
project is big enough for GSoC.

Niharika
Software Engineer (International)
Wikimedia Foundation
[User:NiharikaKohli]
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] GSoC 2016

[Niharika Kohli]

Hi Mehul,

You can get your local MediaWiki setup for starters.
https://www.mediawiki.org/wiki/MediaWiki-Vagrant#Quick_start


The developer community hangs out on #wikimedia-dev and #mediawiki on IRC,
in case you need help or have any follow-up questions.

Possible GSoC project ideas can be found here:
https://phabricator.wikimedia.org/project/view/1042/

Welcome!

On Tue, Feb 23, 2016 at 9:38 PM, Bahodir Mansurov 
wrote:

> Hi and welcome,
>
> Here are some easy tasks:
> https://phabricator.wikimedia.org/project/view/169/
>
> Baha
>
>
> On Tue, 23 Feb 2016 11:04:28 -0500, Mehul Sawarkar <
> mehulsawar...@gmail.com> wrote:
>
> Hello,
>>
>> I am Mehul Sawarkar, a Computer Science student from India . I want to be
>> part of wikimedia in GSoC 2016.Pplease help me getting started .Is there
>> any small bug that I can fix?
>>
>> Thanks,
>> Mehul Sawarkar.
>> ___
>> Wikitech-l mailing list
>> Wikitech-l@lists.wikimedia.org
>> https://lists.wikimedia.org/mailman/listinfo/wikitech-l
>>
>
>
> --
> Baha
>
>
> ___
> Wikitech-l mailing list
> Wikitech-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l
>



-- 
Niharika
Software Engineer (International)
Wikimedia Foundation
[User:NiharikaKohli]
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] [WikimediaMobile] (no subject)

[Niharika Kohli]

Congratulations, Josephine! :)

On Thu, Feb 18, 2016 at 1:26 AM, Michael Holloway 
wrote:

> Nice work, Josephine!
>
> On Wed, Feb 17, 2016 at 12:43 AM, Josephine Lim 
> wrote:
>
> > Hi all,
> > I've been working on a project to improve the categorization of pictures
> in the Upload to Commons Android app <
> https://phabricator.wikimedia.org/T115101> as part of the Outreachy Dec
> '15 program, which is soon drawing to an end. To summarize, 3 new features
> have been implemented in this app:
> >
> > 1. If a picture with geolocation is uploaded, nearby category
> suggestions are offered (based on the categories of other Commons images
> with similar coordinates)
> >
> > 2. If a picture with no geolocation is uploaded, nearby category
> suggestions are offered based on the user's current location. This is
> optional and only works if enabled in Settings.
> >
> > 3. Category search (when typing in the search field) has been made more
> flexible, whereas previously this was done solely by prefix search. E.g.
> now searching for 'latte' should be able to return 'iced latte'.
> >
> > The latest version of the app is v1.11 and can be downloaded at <
> https://play.google.com/store/apps/details?id=fr.free.nrw.commons>.
> Please feel free to leave feedback or bug reports at <
> https://github.com/nicolas-raoul/apps-android-commons/issues>.
> >
> > I have had an amazing time working on this app as part of the Outreachy
> program, and I greatly appreciate all the support and help that the WMF
> community has given me. :)
> >
> >
> > Cheers!
> >
> >
> > --
> >
> > Regards,
> > Josephine
> >
> > ___
> > 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
>



-- 
Niharika
Software Engineer (International)
Wikimedia Foundation
[User:NiharikaKohli]
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] [Wikitech-ambassadors] Update about on-going work on Notifications, especially cross-wiki notifications

[Niharika Kohli]

Hi Nick,

Thanks for this update. I was wondering if cross-wiki watchlists are also
something on the Collaboration team roadmap (since you mentioned examining
Crosswatch)?

Cheers.

On Sat, Nov 14, 2015 at 6:21 AM, Rachel diCerbo 
wrote:

> Thank you for the update!
>
> On Fri, Nov 13, 2015 at 2:41 PM, Nick Wilson (Quiddity) <
> nwil...@wikimedia.org> wrote:
>
> > Hi, this is an update on the work we in the Collaboration team are
> > doing. Our focus is on cross-wiki notifications and other back-end
> > improvements to that system.
> >
> > Our long-term goals are to make various improvements to the Notification
> > system.
> >
> > Notifications are at the core of many different on-wiki activities.
> > Making notifications easy to find and use can help those processes. We
> > are focusing our immediate plans on supporting cross-wiki
> > notifications. These will help editors stay informed about the changes
> > they care about on every Wikimedia project on which they work. This is
> > especially important for the editors who work on more than one wiki.
> > Examples include if you upload to Commons, curate on Wikidata, or edit
> > in two or more languages.
> >
> > The team has spent the last few weeks researching the existing and
> > proposed features. This has included examining existing tools such as
> > Crosswatch. We've been considering the problems of:
> >
> > * technical performance (scaling the requests across 800+ wikis),
> > * user preferences (both existing and desired),
> > * user interface design possibilities (how it should work),
> > * how to release an initial, user-testable version for feedback and
> > improvement, and
> > * how to measure the impact of the project (reducing the time it takes
> > to process a notification).
> >
> > We are also doing user research via 1-on-1 interviews. In these we ask
> > active editors about their current notification usage and pain-points.
> > Using a prototype we are evolving, we get feedback on directions to
> > take the design.
> >
> > == Details and further reading ==
> > You can read more about the technical details at:
> >
> >
> https://www.mediawiki.org/wiki/Requests_for_comment/Cross-wiki_notifications
> > .
> >
> > Some of the new backend improvements to Echo:
> > https://phabricator.wikimedia.org/T107823 ("Rewrite
> > EchoNotificationFormatter") and linked tasks.
> >
> > User preference options are:
> > * https://phabricator.wikimedia.org/T117670 ("Define Cross-wiki
> > Notifications settings")
> >
> > User interface design possibilities cover several questions. For
> > example, how should cross-wiki notifications look within the pop-up?
> > How and when should we add enhancements to the Special:Notifications
> > page to filter things? We are drafting and discussing these in:
> >
> > * https://phabricator.wikimedia.org/T114357 (Clarifications to the
> > currently confusing "primary/secondary" link, and proposed future
> > enhancements)
> > * https://phabricator.wikimedia.org/T114356 (Bundled notifications)
> > * https://phabricator.wikimedia.org/T115264 (Controlling notification
> > 'volume' based on the type or location)
> > * https://phabricator.wikimedia.org/T115845 (Clearer use of the
> > notification badges (coloured number in personal toolbar))
> > * https://phabricator.wikimedia.org/T115316 (Better organization of
> > the Special:Notifications page)
> >
> > Note: Most of these are not part of the cross-wiki notifications
> > feature. We won't for sure roll all these out together with the main
> > change.
> >
> > We started user research at https://phabricator.wikimedia.org/T114086
> > and it continues at https://phabricator.wikimedia.org/T116741 . (Note:
> > You can sign-up as a volunteer at https://wikimedia.org/research .)
> >
> > A user-testable release is still just in planning. We decided on a
> > Beta Feature on each wiki as the most scalable and least confusing of
> > all the do-able options. Read our plans in
> > https://phabricator.wikimedia.org/T114237 ("Present cross-wiki
> > notifications as a beta feature to users"). This will help users to
> > try the feature anytime, disabling it if it interferes with their work
> > in some context, and easily suggest how the tool could be improved.
> >
> > There is no system for users having or setting cross-wiki preferences.
> > Waiting to building this would take a long time. For now, we plan to
> > let you enable the Beta Feature at each wiki on which you want to test
> > it. This will let you have a small-scale Beta Feature that you can all
> > try out. We will be able to discover bugs, edge-cases, iterate more,
> > and get even more feedback. Later, when we know what features you
> > need, we can build such a cross-wiki preferences system (including the
> > task linked above).
> >
> > Whilst you wait, we would love to hear your feedback on the above.
> > What comments, what design ideas, and what technical concerns do you
> > have? Please tell us on the linked 

Re: [Wikitech-l] Would anyone be interested in a tech talk about how to make a mw skin?

[Niharika Kohli]

I'd be very interested in this! I hope you schedule it keeping in mind
remote remotees such as me (India). :)

On Tue, Sep 29, 2015 at 4:06 AM, Christopher Wilson 
wrote:

> I'd be interested as well. My employer is going to be rolling out a new
> site design soon, and it'd be great to have our Wikis match everything else
> with regard to look and feel.
>
> On Mon, Sep 28, 2015 at 3:20 PM, Stephen Niedzielski <
> sniedziel...@wikimedia.org> wrote:
>
> > I would be interested as well! I tried making a custom theme based off
> > vector a few years ago but it seemed like quite a bit of effort to build
> > something comprehensive that anyone would actually want to replace the
> > default with. I'd love a guided tour!
> >
> >
> > --stephen
> >
> > On Mon, Sep 28, 2015 at 4:15 PM, Jon Robson  wrote:
> >
> > > I'd be interested in the process people go through purely from a how
> can
> > I
> > > make this simpler perspective. Alternatively you might want to consider
> > > doing a skin hack day/afternoon where people build skins and learn for
> > > themselves the horror of that process :)
> > >
> > >
> > >
> > > On Mon, Sep 28, 2015 at 3:08 PM, Bryan Davis 
> > wrote:
> > >
> > > > On Mon, Sep 28, 2015 at 3:00 PM, Isarra Yos 
> > wrote:
> > > > > Jack Phoenix and I were considering doing a tech talk about how to
> > > make a
> > > > > MediaWiki skin. Would there be any interest in this? What would you
> > > folks
> > > > > want to see from such a talk?
> > > >
> > > > I'd love to get an overview on creating a new skin. I would be
> > > > especially interested in the "tales from the real world" aspects of
> > > > working with RL, what is and isn't possible without implementing
> > > > hooks, and lessons learned from past skins the two of you have worked
> > > > on.
> > > >
> > > > Bryan
> > > > --
> > > > Bryan Davis  Wikimedia Foundation<
> bd...@wikimedia.org>
> > > > [[m:User:BDavis_(WMF)]]  Sr Software EngineerBoise, ID
> USA
> > > > irc: bd808v:415.839.6885
> x6855
> > > >
> > > > ___
> > > > Wikitech-l mailing list
> > > > Wikitech-l@lists.wikimedia.org
> > > > https://lists.wikimedia.org/mailman/listinfo/wikitech-l
> > > >
> > >
> > >
> > >
> > > --
> > > Jon Robson
> > > * http://jonrobson.me.uk
> > > * https://www.facebook.com/jonrobson
> > > * @rakugojon
> > > ___
> > > 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
>



-- 
Niharika
Software Engineer (International)
Wikimedia Foundation
[User:NiharikaKohli]
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] GSoC & Outreachy IRC Showcase

[Niharika Kohli]

Hello!

Google Summer of Code 2015 and Outreachy Round 10 ended last month, and I'm
happy to report that 9 of our initial 10 projects passed successfully. As a
result, we have a couple of new features to Pywikibot - support for OAuth
and Flow, two extensions for VisualEditor - language proofread extension
and graph extension, three altogether new extensions for MediaWiki - one
for Newsletters, another for combating spam and yet another for handling
banners on Wikivoyage and, last but not the least, an awesome new search
feature for TranslateWiki.

If you want to know more about any of these projects, come join us on
Thursday, September 24th at 1530 UTC[1] on #wikimedia-office for the
projects showcase. Here's the Phabricator event:
https://phabricator.wikimedia.org/E69
 that you should get subscribed to.

Hope to see you there!

[1]:
http://www.timeanddate.com/worldclock/fixedtime.html?msg=GSoC+and+Outreachy+IRC+Showcase=20150924T1530=1440=1
-- 
Niharika
Software Engineer (International)
Wikimedia Foundation
[User:NiharikaKohli]
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] GSoC and Outreachy results out!

[Niharika Kohli]

Hello everyone!

After a long and intense selection process, Google and GNOME Foundation
have finally announced the list of GSoC and Outreachy selects for the
current round. I'm pleased to announce we have 9 interns for GSoC and 1 for
Outreachy!

Congratulations to everyone selected and to the mentors who have put in
much hard work in selecting worthy candidates. Also thanks to those who put
in hard work but could not be selected. We had limited projects and had to
make some hard decisions. We hope you'll keep contributing to Mediawiki and
try again for the next GSoC/Outreachy round.

We have a general guide to being a successful intern at
https://www.mediawiki.org/wiki/Outreach_programs/Life_of_a_successful_project
It's
still under development and we'll be adding more details to it as we move
forward in the program. The main pages for the respective programs are at
https://www.mediawiki.org/wiki/Google_Summer_of_Code_2015 and
https://www.mediawiki.org/wiki/Outreachy/Round_10

The students selected are:

Outreachy:

1. Dibya Singh (Phenix303) from India
Project: One-stop Translation Search
Mentors: Nemo_bis and Nikerabbit

Google Summer of Code:

2. Frédéric Bolduc (ferdbold) from Quebec
Project: GraphData extension for VE
Mentors: Mooeypoo and Mvolz

3. Ankita Kumari (ankita-ks) from India
Project: Unified language proofing tools integration framework
Mentors: Aharoni and Eranroz

4. Jiarong Wei (VcamX) from Hangzhou, Zhejiang
Project: Implement OAuth support for Pywikibot
Mentors: Jayvdb and Halfak

5. Tina Johnson (tinajohnson) from India
Project: Newsletter Mediawiki Extension
Mentors: Quim Gil and Tony Thomas

6. Vivek Ghaisas (polybuildr) from India
Project: Extension to identify and delete spam pages
Mentors: Yaron Koren and Jan

7. Sumit Asthana (codezee) from India
Project: Wikivoyage Pagebanner Extension
Mentors: Nicolas Raoul and Jdlrobson

8. Alexander Jones (happy5214) from United States
Project: Implement Flow support in Pywikibot
Mentors: Jayvdb and Mattflaschen

9. Jan Lebert (sitic) from Germany
Project: An enhanced cross-wiki watchlist
Mentors: Yuvipanda, Legoktm

10. Sarvesh Gupta (s1991) from India
Project: Allow contributors to update their own details in tech metrics
Mentors: Alvaro, Daniel

Let's all welcome them into the Wikimedia family!

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

Re: [Wikitech-l] BounceHandler deployed 'everywhere' succesfully

[Niharika Kohli]

Wow. That's awesome. Congratulations!

It's so nice to see that you saw your project through to the end. :)

On Mon, Mar 30, 2015 at 10:53 PM, Tony Thomas 01tonytho...@gmail.com
wrote:

 Hello,

 Happy to inform that we could successfully complete the global
 deployment[1] of Extension:BounceHandler and the Wikipiedia's are handling
 bounce emails effectively. The current threshold for the number of allowed
 bounces is 5, and we could test the unsubscribe action live on
 en.wikipedia.org with help of sysops ( I couldnt send more than 2 emails,
 thanks to the Anti-spam checks ).

 As of now, 'bounce_records' have 37338 entries, mainly from group0 and
 group1 wikis ( in ~ 20 days ). We expect an exponential increase in the
 same, as the en-wiki has got amazing bounce rates.

 This would mean the finish ( deployment ) of my GSoC 2014 project[2] with
 Jeff Green and Legoktm. Thanks to everyone who helped in between, it was
 real fun!

 [1] https://phabricator.wikimedia.org/T92877
 [2] mediawiki.org/wiki/VERP

 Thanks,
 Tony Thomas http://tttwrites.wordpress.com/
 FOSS@Amrita http://foss.amrita.ac.in

 *where there is a wifi, there is a 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

[Wikitech-l] GSoC and Outreachy Selection Process

[Niharika Kohli]

Hi there,

The application deadline for GSoC and Outreachy has passed. We have
received:

- 44 GSoC applications from 43 candidates
- 10 Outreachy applications from 10 candidates including 5 who have also
applied for GSoC

Several of the projects have received multiple proposals, making it hard
for out mentors to choose the best from all the applicants. Everyone is
invited to join in the selection process and actively ask the candidates
questions about their proposals.

The GSoC proposals submitted can be found at
https://phabricator.wikimedia.org/tag/google-summer-of-code-2015/

The Outreachy proposals submitted can be found at
https://phabricator.wikimedia.org/tag/outreachy-round-10/

For our students:

If you have not yet created a task for your project proposal on Phabricator
yet, we encourage you to do that as soon as you can. If your proposal is
complete and you have completed one or more relevant microtasks, you can
sit back and relax now. If not, you should complete your application as
soon as possible.

For the mentors:

All mentors must join the GSoC/Outreachy review websites (
http://www.google-melange.com/gsoc/homepage/google/gsoc2015 and
https://outreachy.gnome.org respectively) in order to privately evaluate
the candidates.
I want to take the opportunity to remind all our mentors that under no
circumstances are we allowed to reveal the results of the selection process
before April 27th 1900 UTC when the official list will be out on Melange.
Hence, no hints or resolutions must be given out on the Phabricator tasks
or on Melange.

Some resources for the mentors:

- Guidelines for possible mentors:
https://www.mediawiki.org/wiki/Outreach_programs/Possible_mentors

- Our selection process:
https://www.mediawiki.org/wiki/Outreach_programs/Selection_process

- Lessons learned from the previous rounds:
https://www.mediawiki.org/wiki/Outreach_programs/Lessons_learned

By April 13 we need to decide how many slots we want to request in both
programs. In GSoC we request a number of slots to Google which we might or
might not get. In Outreachy, we fund some slots, we might request more and
then we might or might not get them.

Questions? Just ask.

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

Re: [Wikitech-l] regarding gsoc 2015

[Niharika Kohli]

On Friday, March 20, 2015, Arindam Padhy b113...@iiit-bh.ac.in wrote:

 Sub:regarding timeline
 is it necessary that we have to complete half project before mid term
 evaluation and the other half after it.
 if we could finish it early before the final term evaluation will there be
 any issue...?

 No issues. But I must tell you that if you want to apply for the current
GSoC round, it's high time you start making a proposal and interacting with
the mentors. Deadline isn't far.



 On Thu, Mar 19, 2015 at 12:18 PM, Niharika Kohli 
 niharikakohl...@gmail.com javascript:;
 wrote:

 
   On Mar 19, 2015, at 12:24 AM, Arindam Padhy b113...@iiit-bh.ac.in
 javascript:;
  wrote:
  
   can you mention where exactly are the microtasks present for the
  following
   project.
   Extension to identify and delete spam pages
  
  
  Clicking on that link would show you this:
  https://phabricator.wikimedia.org/T90238 
  https://phabricator.wikimedia.org/T90238 where “Microtasks” are listed
  right at the end of the Description. The crossed out ones have been
  completed. The others are left. You can comment on the task itself to ask
  for further help, if something isn’t clear.
 
   On Wed, Mar 18, 2015 at 11:09 PM, Niharika Kohli 
  niharikakohl...@gmail.com javascript:;
   wrote:
  
   Hello Arindam,
  
   There are 3 different ideas listed under Mediawiki extensions on
   https://www.mediawiki.org/wiki/Outreach_programs/Possible_projects 
   https://www.mediawiki.org/wiki/Outreach_programs/Possible_projects
  
   If you click on these, you’ll see a Phabricator task which explains
 the
   idea and suggests some microtasks that a prospective student should
 work
   on. You can start working on the one(s) you find interesting. Also,
 you
  can
   start writing a proposal for the project you want to work on. How to
  write
   a proposal is explained on the page linked above itself.
  
   Thank you!
   Niharika.
  
   On Mar 18, 2015, at 9:57 PM, Arindam Padhy b113...@iiit-bh.ac.in
 javascript:;
   wrote:
  
   i am interested in the mediawiki extensions idea proposed by the org.
   what should i do next...??
  
   On Wed, Mar 18, 2015 at 5:56 PM, Quim Gil q...@wikimedia.org
 javascript:; wrote:
  
   Hi Arindam,
  
   On Tue, Mar 17, 2015 at 8:58 PM, Arindam Padhy 
 b113...@iiit-bh.ac.in javascript:;
  
   wrote:
  
   hello
   i am a b.tech student pursuing my carrer at iiit bhubaneswar,india.
   i am deeply interested in gsoc 2015 and wanted to do a project
 under
   this
   organization.
   how should i proceed..??
  
  
   Please go to
  https://www.mediawiki.org/wiki/Google_Summer_of_Code_2015
   and
   check the project ideas proposed.
  
  
   do we need to solve any bugs..??
  
  
   Yes, we are requiring candidates to solve microtasks as part of
 their
   evaluation. Every project idea proposed has a list of suggested
   microtasks.
   ___
   Wikitech-l mailing list
   Wikitech-l@lists.wikimedia.org javascript:;
   https://lists.wikimedia.org/mailman/listinfo/wikitech-l
   ___
   Wikitech-l mailing list
   Wikitech-l@lists.wikimedia.org javascript:;
   https://lists.wikimedia.org/mailman/listinfo/wikitech-l
  
   ___
   Wikitech-l mailing list
   Wikitech-l@lists.wikimedia.org javascript:;
   https://lists.wikimedia.org/mailman/listinfo/wikitech-l
  
   ___
   Wikitech-l mailing list
   Wikitech-l@lists.wikimedia.org javascript:;
   https://lists.wikimedia.org/mailman/listinfo/wikitech-l
 
  ___
  Wikitech-l mailing list
  Wikitech-l@lists.wikimedia.org javascript:;
  https://lists.wikimedia.org/mailman/listinfo/wikitech-l
 
 ___
 Wikitech-l mailing list
 Wikitech-l@lists.wikimedia.org javascript:;
 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] regarding gsoc 2015

[Niharika Kohli]

 On Mar 19, 2015, at 12:24 AM, Arindam Padhy b113...@iiit-bh.ac.in wrote:
 
 can you mention where exactly are the microtasks present for the following
 project.
 Extension to identify and delete spam pages
 
 
Clicking on that link would show you this: 
https://phabricator.wikimedia.org/T90238 
https://phabricator.wikimedia.org/T90238 where “Microtasks” are listed right 
at the end of the Description. The crossed out ones have been completed. The 
others are left. You can comment on the task itself to ask for further help, if 
something isn’t clear. 

 On Wed, Mar 18, 2015 at 11:09 PM, Niharika Kohli niharikakohl...@gmail.com
 wrote:
 
 Hello Arindam,
 
 There are 3 different ideas listed under Mediawiki extensions on
 https://www.mediawiki.org/wiki/Outreach_programs/Possible_projects 
 https://www.mediawiki.org/wiki/Outreach_programs/Possible_projects
 
 If you click on these, you’ll see a Phabricator task which explains the
 idea and suggests some microtasks that a prospective student should work
 on. You can start working on the one(s) you find interesting. Also, you can
 start writing a proposal for the project you want to work on. How to write
 a proposal is explained on the page linked above itself.
 
 Thank you!
 Niharika.
 
 On Mar 18, 2015, at 9:57 PM, Arindam Padhy b113...@iiit-bh.ac.in
 wrote:
 
 i am interested in the mediawiki extensions idea proposed by the org.
 what should i do next...??
 
 On Wed, Mar 18, 2015 at 5:56 PM, Quim Gil q...@wikimedia.org wrote:
 
 Hi Arindam,
 
 On Tue, Mar 17, 2015 at 8:58 PM, Arindam Padhy b113...@iiit-bh.ac.in
 wrote:
 
 hello
 i am a b.tech student pursuing my carrer at iiit bhubaneswar,india.
 i am deeply interested in gsoc 2015 and wanted to do a project under
 this
 organization.
 how should i proceed..??
 
 
 Please go to https://www.mediawiki.org/wiki/Google_Summer_of_Code_2015
 and
 check the project ideas proposed.
 
 
 do we need to solve any bugs..??
 
 
 Yes, we are requiring candidates to solve microtasks as part of their
 evaluation. Every project idea proposed has a list of suggested
 microtasks.
 ___
 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 mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] regarding gsoc 2015

[Niharika Kohli]

Hello Arindam,

There are 3 different ideas listed under Mediawiki extensions on 
https://www.mediawiki.org/wiki/Outreach_programs/Possible_projects 
https://www.mediawiki.org/wiki/Outreach_programs/Possible_projects 

If you click on these, you’ll see a Phabricator task which explains the idea 
and suggests some microtasks that a prospective student should work on. You can 
start working on the one(s) you find interesting. Also, you can start writing a 
proposal for the project you want to work on. How to write a proposal is 
explained on the page linked above itself. 

Thank you!
Niharika. 

 On Mar 18, 2015, at 9:57 PM, Arindam Padhy b113...@iiit-bh.ac.in wrote:
 
 i am interested in the mediawiki extensions idea proposed by the org.
 what should i do next...??
 
 On Wed, Mar 18, 2015 at 5:56 PM, Quim Gil q...@wikimedia.org wrote:
 
 Hi Arindam,
 
 On Tue, Mar 17, 2015 at 8:58 PM, Arindam Padhy b113...@iiit-bh.ac.in
 wrote:
 
 hello
 i am a b.tech student pursuing my carrer at iiit bhubaneswar,india.
 i am deeply interested in gsoc 2015 and wanted to do a project under this
 organization.
 how should i proceed..??
 
 
 Please go to https://www.mediawiki.org/wiki/Google_Summer_of_Code_2015 and
 check the project ideas proposed.
 
 
 do we need to solve any bugs..??
 
 
 Yes, we are requiring candidates to solve microtasks as part of their
 evaluation. Every project idea proposed has a list of suggested microtasks.
 ___
 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] Application period for GSoC and Outreachy now open!

[Niharika Kohli]

Google Summer of Code 2015 and Outreachy Round 10 have kicked off. We have
already received a few proposals and a lot of projects have received
tremendous interest. But some of these projects still lack mentors and
we're hoping you might be interested in being one.

1. Cross-wiki watchlists[1]: A standalone cross-wiki watchlist web app has
been proposed by Sitic. A prototype can be found at [2]. Missing mentors.

2. One stop translation[3]: Proposal by Phoneix303 for improving search for
translation messages.

3. Show edits made on Commons on Watchlist[4]: Needs mentors.

4. Adding new datatypes in Wikidata[5]: Needs mentors and discussion.

5. Automatic analysis of Commons images for color-blind[6]: Needs
discussion and mentors.

6. Adding user preference to deactivate/delete account[7]: Needs discussion
and mentors.

Your feedback on these is would be very helpful in pushing them forward.
All projects in the pipeline can be found at [8].

[1]: https://phabricator.wikimedia.org/T92955
[2]: https://tools.wmflabs.org/watchr/
[3]: https://phabricator.wikimedia.org/T92929
[4]: https://phabricator.wikimedia.org/T91192
[5]: https://phabricator.wikimedia.org/T91505
[6]: https://phabricator.wikimedia.org/T59806
[7]: https://phabricator.wikimedia.org/T34815
[8]: https://phabricator.wikimedia.org/project/board/1042/

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

[Wikitech-l] Fwd: Upcoming GSoC and Outreachy rounds

[Niharika Kohli]

Hello!

I am pleased to announce that Wikimedia has been selected as a mentoring
organization for the upcoming Google Summer of Code (out of only 137
organizations selected for this round) and Outreachy rounds.
Congratulations!

We have a phabricator board for possible projects[1] students can work on.
Currently, only 7 projects are in the Featured column with well-defined
project scope and mentors assigned.

A lot more are sitting in the Needs Discussion and Missing Mentors
columns, looking forward to your input.

Enlisting some of the more discussed projects here:

- Gadget Usage Statistics [2]
- Out-of-date fact and statistics identification and review [3]
- Cross-wiki watchlists [4]
- Newsletter Mediawiki Extension [5]

Your comments would be greatly appreciated in shaping these ideas into
featured projects for the students.

If you know of other projects which could be a good fit for a 3 month
GSoC/Outreachy round, please feel free to add them to the board.
If you think you can mentor one of these projects, please do comment on the
ticket indicating so.

[1] https://phabricator.wikimedia.org/tag/possible-tech-projects/
[2] https://phabricator.wikimedia.org/T21288
[3] https://phabricator.wikimedia.org/T89416
[4] https://phabricator.wikimedia.org/T5525
[5] https://phabricator.wikimedia.org/T76199

Thank you!
Niharika.

PS: I am a co-organizer for the upcoming GSoC  Outreachy rounds for
Wikimedia, along with Quim. Nice to meet you!
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Announcement: Yuvi Panda joins Ops

[Niharika Kohli]

Awesome Yuvi. Congratulations! :D 

 On Nov 6, 2014, at 10:47 PM, Danese Cooper dan...@gmail.com wrote:
 
 Woot!  Way to go, Yuvi!
 
 D
 
 On Thu, Nov 6, 2014 at 4:55 PM, Mark Bergsma m...@wikimedia.org wrote:
 
 Hi all,
 
 I'm very pleased to announce that as of this week, Yuvi Panda is part of
 the Wikimedia Technical Operations team, to work on our Wikimedia Labs
 infrastructure. Yuvi originally joined the Wikimedia Foundation Mobile team
 in December 2011, where he has been lead development for the original
 Wikipedia App and its rewrite, amongst many other projects.
 
 Besides his work in Mobile, Yuvi has been volunteering for Ops work in
 Wikimedia Labs for a long time now. One of the notable examples of his work
 is a seamlessly integrated Web proxy system that allows public web requests
 from the Internet to be proxied to Labs instances on private IPs without
 requiring public IP addresses for each instance. This very user friendly
 system, which he built on top of NGINX, LUA, redis, sqlite and the
 OpenStack API, sees a lot of usage and has dramatically reduced the need
 for Labs users to request (scarce) public IP address resources via a manual
 approval process.
 
 Another example of his work that has made a big difference is the
 initiation of the Labs-Vagrant project; bringing the virtues of the
 Mediawiki:Vagrant project to Wikimedia Labs, and allowing anyone to bring a
 MediaWiki development environment up in Labs with great ease. More recently
 Yuvi has been working on our much needed infrastructure in Labs for
 monitoring metrics (Graphite) and service availability (Shinken). We expect
 this will give us a lot more insight into the internals and availability of
 software and services running in Wikimedia Labs and its many projects, and
 we should be able to deploy it in Production as well.
 
 Of course all of this work didn't go unnoticed, and about half a year ago
 we've asked Yuvi if he was interested to move to Ops. With his extensive
 development experience and his demonstrated ability to join this with solid
 Ops work to create stable and highly useful solutions, we think he's a
 great fit for this role.
 
 Yuvi recently had his VISA application accepted, and is planning to move to
 San Francisco in March 2015. Until then he will be working with us remotely
 from India.
 
 Please join me in congratulating Yuvi!
 
 --
 Lead Operations Architect
 Director of Technical Operations
 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


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