Re: [Wikitech-l] Login to Wikimedia Phabricator with a GitHub/Google/etc account?

[Martijn Hoekstra]

On May 16, 2014 1:42 AM, "C. Scott Ananian"  wrote:
>
> Ideally you would be able to link your (say) github and WMF account.
> So that if I (as an outsider) start a bug report/patch/etc using my
> existing github account, and then eventually get a WMF account (so
> that I can do labs-related things?) I can manage my bugs/patches
> regardless of which account's cookies happen to be on my machine.
>

Would it be plausible the right thing to do, keeping security and privacy
in mind, to create and attach a SUL right on the first login through an
external identity provider like github?

--Martijn

>
> ___
> 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] Login to Wikimedia Phabricator with a GitHub/Google/etc account?

[Ryan Lane]

On Thu, May 15, 2014 at 7:36 PM, Steven Walling wrote:

> On Thu, May 15, 2014 at 2:20 PM, Quim Gil  wrote:
>
> > However, Phabricator can support authentication using 3rd party providers
> > like GitHub, Google, etc. You can get an idea at
> > https://secure.phabricator.com/auth/start/
> >
>
> I think since this is already built and would require no extra work, we
> should definitely support GitHub and Persona as well.
>
>
Persona is dead. It's no longer being actively developed by Mozilla.

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

Re: [Wikitech-l] [Wikimedia-l] Request for comments: How to deal with open datasets?

[David Cuenca]

On Thu, May 15, 2014 at 11:53 PM, Andrew Gray wrote:

> Definitely agree that we needed something like this. There's a lot of
> confusion about what Wikidata is for, and what is and isn't appropriate for
> it - both from outsiders and from within the Wikimedia community. I've seen
> vague "it's data, it'll go on Wikidata" a few times, which is a bit like
> saying "it's text, it'll go on Wikipedia" ;-)
>

Actually during the Hackathon somebody said: "We need a new project... a
sort of Wiki...Data...Source?" :D And it is great that you make the analogy
of Wikipedia-and-Text because when you think about it, Wikipedia went
through exactly the same process until "Project Sourceberg" was
characterized ;-)

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

[Wikitech-l] Craziness in diff algorithm

[Gryllida]

Hi All,



Please excuse me for sending an HTML attachment to this list. There is
a need to display some part of it with color.



[1]Bug 13462 - Enhance line matching in diffs; An [2]example diff
similar to what I specifically have a problem with on one of Wikimedia
projects for several months: contributors often add and remove line
breaks making paragraph edits hard to analyse.



Effectively I got this (in a table, but tables are hard to read in
emails):



1) -

2) - foobar lin3

1) + foobar line

2)



But I would find this more useful:



1) -

2) - foobar lin3

1)

2) + foobar line





Please participate by providing insight on potential fixes or
workarounds (don't expect me to be able to read the backend codebase of
this software). Thanks.



Gryllida.

References

1. https://bugzilla.wikimedia.org/show_bug.cgi?id=13462
2. https://test.wikipedia.org/w/index.php?diff=199552&oldid=199551
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Login to Wikimedia Phabricator with a GitHub/Google/etc account?

[Chris Steipp]

On May 15, 2014 3:56 PM, "hoo"  wrote:
>
> On Thu, 2014-05-15 at 14:20 -0700, Quim Gil wrote:
> > This is a casual request for comments about the use of 3rd party
> > authentication providers for our future Wikimedia Phabricator instance.
> >
> > Wikimedia Phabricator is expected to replace Bugzilla, Gerrit and many
> > other tools, each of them having their own registration and user
account.
> > The plan is to offer Wikimedia SUL (your Wikimedia credentials) as the
> > default way to login to Phabricator -- details at
http://fab.wmflabs.org/T40
> >
> > However, Phabricator can support authentication using 3rd party
providers
> > like GitHub, Google, etc. You can get an idea at
> > https://secure.phabricator.com/auth/start/
> >
> > There are good reasons to plan for Wikimedia SUL only (consistency with
the
> > rest of Wikimedia projects), and there are good reasons to plan for
other
> > providers as well (the easiest path for most first-time contributors).
> >
> > What do you think? Should we offer alternatives to Wikimedia login? If
so,
> > which ones?
> >
> >
>
> Seeing the mess with user accounts we have on the Wikis these days,
> please make sure we wont run into naming conflicts.
> A wiki user with the global account "foo" should always be able to use
> that account Phabricator, no matter what users from other sources did
> before.

Accounts are kinda namespaced, so github user foo and sul user foo can both
have phabricator accounts.

Since we're using OAuth though, that requires a global wiki account so
local only accounts would not be able to join. So we probably need password
or LDAP auth at minimum.

>
> Cheers,
>
> Marius
>
>
> ___
> 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] Thanks for the New Search and for Flow

[Amir E. Aharoni]

One of these feel-good emails:

Thanks to the people who are working hard on developing the new search:
Nik, Chad, Dan, and everybody who helps, tests, deploys and writes feedback.

A Hebrew Wikipedia user wrote a big and detailed thank you note[1] that
wiki's Village Pump, especially praising the instant indexing of
newly-added content.

The users are not just complaining all the time? :)

[1] http://j.mp/1g8XylW , at least until it's archived. Thanks in advance
to the people who are developing Flow, which should finally make links to
discussions permanent.

--
Amir Elisha Aharoni · אָמִיר אֱלִישָׁע אַהֲרוֹנִי
http://aharoni.wordpress.com
‪“We're living in pieces,
I want to live in peace.” – T. Moore‬
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Login to Wikimedia Phabricator with a GitHub/Google/etc account?

[Petr Bena]

Yes. Support as many providers as possible, google at least, I
basically don't even want to use any more web services with own login
unless I have to. single login FTW

On Fri, May 16, 2014 at 3:51 PM, Chris Steipp  wrote:
> On May 15, 2014 3:56 PM, "hoo"  wrote:
>>
>> On Thu, 2014-05-15 at 14:20 -0700, Quim Gil wrote:
>> > This is a casual request for comments about the use of 3rd party
>> > authentication providers for our future Wikimedia Phabricator instance.
>> >
>> > Wikimedia Phabricator is expected to replace Bugzilla, Gerrit and many
>> > other tools, each of them having their own registration and user
> account.
>> > The plan is to offer Wikimedia SUL (your Wikimedia credentials) as the
>> > default way to login to Phabricator -- details at
> http://fab.wmflabs.org/T40
>> >
>> > However, Phabricator can support authentication using 3rd party
> providers
>> > like GitHub, Google, etc. You can get an idea at
>> > https://secure.phabricator.com/auth/start/
>> >
>> > There are good reasons to plan for Wikimedia SUL only (consistency with
> the
>> > rest of Wikimedia projects), and there are good reasons to plan for
> other
>> > providers as well (the easiest path for most first-time contributors).
>> >
>> > What do you think? Should we offer alternatives to Wikimedia login? If
> so,
>> > which ones?
>> >
>> >
>>
>> Seeing the mess with user accounts we have on the Wikis these days,
>> please make sure we wont run into naming conflicts.
>> A wiki user with the global account "foo" should always be able to use
>> that account Phabricator, no matter what users from other sources did
>> before.
>
> Accounts are kinda namespaced, so github user foo and sul user foo can both
> have phabricator accounts.
>
> Since we're using OAuth though, that requires a global wiki account so
> local only accounts would not be able to join. So we probably need password
> or LDAP auth at minimum.
>
>>
>> Cheers,
>>
>> Marius
>>
>>
>> ___
>> 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] Login to Wikimedia Phabricator with a GitHub/Google/etc account?

[Greg Grossmeier]

On Thu, May 15, 2014 at 4:42 PM, C. Scott Ananian wrote:

> Ideally you would be able to link your (say) github and WMF account.
> So that if I (as an outsider) start a bug report/patch/etc using my
> existing github account, and then eventually get a WMF account (so
> that I can do labs-related things?) I can manage my bugs/patches
> regardless of which account's cookies happen to be on my machine.
>

You can. You can "claim" other accounts in Phab.

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

Re: [Wikitech-l] Transcluding non-text content as HTML on wikitext pages

[Daniel Kinzler]

Hi again!

I have rewritten the patch that enabled HTML based transclusion:

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

I tried to address the concerns raised about my previous attempt, namely, how
HTML based transclusion is handled in expandtemplates, and how page meta data
such as resource modules get passed from the transcluded content to the main
parser output (this should work now).

For expandtemplates, I decided to just keep HTML based transclusions as they are
- including special page transclusions. So, expandtemplates will simply leave
{{Special:Foo}} and {{MediaWiki:Foo.js}} in the expanded text, while in the xml
output, you can still see them as template calls.

Cheers,
Daniel

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

Re: [Wikitech-l] Craziness in diff algorithm

[Gryllida]

Hi All,

To clarify:

This software silently converted the message to plain text, so what I meant is 
clarified below.

On Fri, 16 May 2014, at 21:22, Gryllida wrote:
> Hi All,
> 
> 
> 
> Please excuse me for sending an HTML attachment to this list. There is
> a need to display some part of it with color.
> 
> 
> 
> [1]Bug 13462 - Enhance line matching in diffs; An [2]example diff
> similar to what I specifically have a problem with on one of Wikimedia
> projects for several months: contributors often add and remove line
> breaks making paragraph edits hard to analyse.
> 
> 
> 
> Effectively I got this (in a table, but tables are hard to read in
> emails):
> 
> 
> 
> 1) -

(this line is red)

> 
> 2) - foobar lin3

(this line is red)

> 
> 1) + foobar line

(this line is green)


> 
> 2)
> 
> 
> 
> But I would find this more useful:
> 
> 
> 
> 1) -

(this line is red)

> 
> 2) - foobar lin3

(in this line, the '3' is highlighted in red)

> 
> 1)
> 
> 2) + foobar line

(in this line, the 'e' is highlighted in green)

> 
> 
> 
> 
> 
> Please participate by providing insight on potential fixes or
> workarounds (don't expect me to be able to read the backend codebase of
> this software). Thanks.
> 
> 
> 
> Gryllida.
> 
> References
> 
> 1. https://bugzilla.wikimedia.org/show_bug.cgi?id=13462
> 2. https://test.wikipedia.org/w/index.php?diff=199552&oldid=199551


Gryllida.

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

[Wikitech-l] Login to Wikimedia Phabricator with a GitHub/Google/etc account?

[Quim Gil]

On Thursday, May 15, 2014, Ryan Lane
>
wrote:

>
> Will Labs no longer have the same authentication as the rest of the
> tooling? Is this something that will be solved before the switch?
>

Wikitech-LDAP-Labs-Gerrit remains untouched in the first switch to
Phabricator (what we call Day 1), which aims to task/bug management tools:
Bugzilla, RT, Trello, Mingle.

Still, we need to have a good plan in mind, latest for the code review
migration. I just created a related task at http://fab.wmflabs.org/T338

So far, it seems that the only solid 3rd party candidate to be considered
is GitHub. Task created at http://fab.wmflabs.org/T337


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

Re: [Wikitech-l] Login to Wikimedia Phabricator with a GitHub/Google/etc account?

[Quim Gil]

On Friday, May 16, 2014, Petr Bena  wrote:

> Yes. Support as many providers as possible, google at least, I
> basically don't even want to use any more web services with own login
> unless I have to. single login FTW


I wonder why a user without a Wikimedia account or a GitHub account would
need to login to Wikimedia Phabricator.


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

Re: [Wikitech-l] Login to Wikimedia Phabricator with a GitHub/Google/etc account?

[C. Scott Ananian]

On Fri, May 16, 2014 at 9:23 AM, Quim Gil  wrote:
> On Friday, May 16, 2014, Petr Bena  wrote:
>
>> Yes. Support as many providers as possible, google at least, I
>> basically don't even want to use any more web services with own login
>> unless I have to. single login FTW
>
> I wonder why a user without a Wikimedia account or a GitHub account would
> need to login to Wikimedia Phabricator.

To report or comment on a bug?

To anonymously report an issue?
 --scott

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

Re: [Wikitech-l] Transcluding non-text content as HTML on wikitext pages

[Gabriel Wicke]

On 05/15/2014 04:42 PM, Daniel Kinzler wrote:
> The one thing that will not work on wikis with
> $wgRawHtml disabled is parsing the output of expandtemplates.

Yes, which means that it won't work with Parsoid, Flow, VE and other users.

I do think that we can do better, and I pointed out possible ways to do so
in my earlier mail:

> My preference
> would be to let the consumer directly ask for pre-expanded wikitext *or*
> HTML, without overloading action=expandtemplates. Even indicating the
> content type explicitly in the API response (rather than inline with an HTML
> tag) would be a better stop-gap as it would avoid some of the security and
> compatibility issues described above.

Gabriel

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

[Wikitech-l] enwiki display issues

[John]

Looks like Javascript/CSS is intermittently failing.
http://en.wikipedia.org/wiki/Wikipedia:Village_pump_%28technical%29#Something_is_broken
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] MW-Vagrant improvements at the Zürich Hackathon

[Arthur Richards]

Just wanted to send out an update on the progress we made around MW-Vagrant
improvements at the Zürich Hackathon. Our primary goal was to make some key
production services available in MW-Vagrant in order to make local
development/testing easier/more reliable. We made some excellent headway,
focussing on a few key services: SSL, Varnish, CentralAuth/Multiwiki.

SSL:
I spent a majority of my time focussing on this and received a lot of
support/help from Ori. There is now an 'https' role in mw-vagrant which
when enabled, will allow you to access your devwiki on port 4430 (forwarded
to 443 in Vagrant). There is one outstanding patchset which will make it
possible to use $wgSecureLogin in MW-Vagrant:
https://gerrit.wikimedia.org/r/#/c/132799/

Varnish:
This is proving to be much more difficult than anticipated, however some
progress was made and work is ongoing, spearheaded by Andrew Otto. The plan
is to set up varnish VCLs for mw-vagrant similar to what is set up for text
varnishes in production, with a frontend and backend instance running in
vagrant. Andrew is in the midst of refactoring the production varnish
module, to make it usable in Vagrant.

CentralAuth/Multiwiki:
Bryan Davis, Chris Steipp, and Reedy spent a lot of time hacking on this,
and we now have support for multiwiki/CentralAuth in Vagrant! There is
still some cleanup work being done for the role to remove kludge/hacks/etc
(see https://gerrit.wikimedia.org/r/#/c/132691/).

Also of significant note, Matt Flaschen created a mw-vagrant iso which can
be packaged on USB thumb drives, making it possible to set up mw-vagrant
without a network connection. There is still some work to be done here to
create a one-click installer as well as updating documentation. Matt got
this done before the hackathon, and we brought a bunch of USB sticks imaged
with the iso, which was instrumental in getting a bunch of folks new to
mw-vagrant up and running at the hackathon. This was particularly useful
during Bryan Davis's vagrant bootcamp sessions.

I believe Katie Filbert from Wikidata did some mw-vagrant work at the
hackathon as well, although I'm not clear on the current status. Katie, can
you let us know where things were at with what you were working on?

All in all it felt like a very fruitful hack session, and we're closer than
ever to having a ready-to-go developer instance that mimics our production
environment. Big thanks to everyone involved in making our work successful.

-- 
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] Login to Wikimedia Phabricator with a GitHub/Google/etc account?

[Tyler Romeo]

I feel like the ideal situation would be to:

1) Only allow Phabricator login with a Wikimedia account; and
2) When logging into Wikimedia, allow login with Google, GitHub, etc.

Unfortunately, fulfilling that situation means deploying the OpenID
extension, which is definitely not ready yet.


*-- *
*Tyler Romeo*
Stevens Institute of Technology, Class of 2016
Major in Computer Science


On Fri, May 16, 2014 at 1:47 PM, C. Scott Ananian wrote:

> On Fri, May 16, 2014 at 9:23 AM, Quim Gil  wrote:
> > On Friday, May 16, 2014, Petr Bena  wrote:
> >
> >> Yes. Support as many providers as possible, google at least, I
> >> basically don't even want to use any more web services with own login
> >> unless I have to. single login FTW
> >
> > I wonder why a user without a Wikimedia account or a GitHub account would
> > need to login to Wikimedia Phabricator.
>
> To report or comment on a bug?
>
> To anonymously report an issue?
>  --scott
>
> ___
> 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] MW-Vagrant improvements at the Zürich Hackathon

[Arthur Richards]

PS One thing I forgot to mention - mega thanks to WMF's Office IT for
helping with ordering and imaging the USB sticks!!!


On Fri, May 16, 2014 at 1:40 PM, Arthur Richards wrote:

> Just wanted to send out an update on the progress we made around
> MW-Vagrant improvements at the Zürich Hackathon. Our primary goal was to
> make some key production services available in MW-Vagrant in order to make
> local development/testing easier/more reliable. We made some excellent
> headway, focussing on a few key services: SSL, Varnish,
> CentralAuth/Multiwiki.
>
> SSL:
> I spent a majority of my time focussing on this and received a lot of
> support/help from Ori. There is now an 'https' role in mw-vagrant which
> when enabled, will allow you to access your devwiki on port 4430 (forwarded
> to 443 in Vagrant). There is one outstanding patchset which will make it
> possible to use $wgSecureLogin in MW-Vagrant:
> https://gerrit.wikimedia.org/r/#/c/132799/
>
> Varnish:
> This is proving to be much more difficult than anticipated, however some
> progress was made and work is ongoing, spearheaded by Andrew Otto. The plan
> is to set up varnish VCLs for mw-vagrant similar to what is set up for text
> varnishes in production, with a frontend and backend instance running in
> vagrant. Andrew is in the midst of refactoring the production varnish
> module, to make it usable in Vagrant.
>
> CentralAuth/Multiwiki:
> Bryan Davis, Chris Steipp, and Reedy spent a lot of time hacking on this,
> and we now have support for multiwiki/CentralAuth in Vagrant! There is
> still some cleanup work being done for the role to remove kludge/hacks/etc
> (see https://gerrit.wikimedia.org/r/#/c/132691/).
>
> Also of significant note, Matt Flaschen created a mw-vagrant iso which can
> be packaged on USB thumb drives, making it possible to set up mw-vagrant
> without a network connection. There is still some work to be done here to
> create a one-click installer as well as updating documentation. Matt got
> this done before the hackathon, and we brought a bunch of USB sticks imaged
> with the iso, which was instrumental in getting a bunch of folks new to
> mw-vagrant up and running at the hackathon. This was particularly useful
> during Bryan Davis's vagrant bootcamp sessions.
>
> I believe Katie Filbert from Wikidata did some mw-vagrant work at the
> hackathon as well, although I'm not clear on the current status. Katie, can
> you let us know where things were at with what you were working on?
>
> All in all it felt like a very fruitful hack session, and we're closer
> than ever to having a ready-to-go developer instance that mimics our
> production environment. Big thanks to everyone involved in making our work
> successful.
>
> --
> Arthur Richards
> Software Engineer, Mobile
> [[User:Awjrichards]]
> IRC: awjr
> +1-415-839-6885 x6687
>



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

[Wikitech-l] Roadmap and deployment highlights - week of May 19th

[Greg Grossmeier]

Hello and welcome to the latest edition of the WMF Engineering Roadmap
and Deployment update.

The full log of planned deployments next week can be found at:


A quick list of notable items...


== Monday ==

* Enable CirrusSearch as primary search backend on zh-yue wikipedia.
** 

* Enable anonymous editor acquisition experiment in GettingStarted on
enwiki, dewiki, frwiki, itwiki and test wikis.


== Tuesday ==

* MediaWiki deploy
** group1 to 1.24wmf5: All non-Wikipedia sites (Wiktionary, Wikisource,
   Wikinews, Wikibooks, Wikiquote, Wikiversity, and a few other sites)
** 


* Enable Flow at mw:Talk:Wikibase/Beta Features/Other projects sidebar,
mw:Talk:Design, and mw:Talk:Phabricator/Help
** 

== Wednesday ==

* Swapping GeoData to use Elasticsearch as its backend everywhere.
** 

== Thursday ==

* MediaWiki deploy
** group2 to 1.24wmf4 (all Wikipedias)
** group0 to 1.24wmf5 (test/test2/testwikidata/mediawiki)

* MediaViewer
** English, German, Italian and Russian Wikipedias, and all Wikisources, in
stages.
** <
https://www.mediawiki.org/wiki/Multimedia/Media_Viewer/Release_Plan#Timeline
>


Thanks and as always, questions and comments welcome,

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

Re: [Wikitech-l] MW-Vagrant improvements at the Zürich Hackathon

[Bryan Davis]

On Fri, May 16, 2014 at 3:11 PM, Arthur Richards
 wrote:
> PS One thing I forgot to mention - mega thanks to WMF's Office IT for
> helping with ordering and imaging the USB sticks!!!
>
>
> On Fri, May 16, 2014 at 1:40 PM, Arthur Richards 
> wrote:
>
>> Just wanted to send out an update on the progress we made around
>> MW-Vagrant improvements at the Zürich Hackathon. Our primary goal was to
>> make some key production services available in MW-Vagrant in order to make
>> local development/testing easier/more reliable. We made some excellent
>> headway, focussing on a few key services: SSL, Varnish,
>> CentralAuth/Multiwiki.
>>
>> SSL:
>> I spent a majority of my time focussing on this and received a lot of
>> support/help from Ori. There is now an 'https' role in mw-vagrant which
>> when enabled, will allow you to access your devwiki on port 4430 (forwarded
>> to 443 in Vagrant). There is one outstanding patchset which will make it
>> possible to use $wgSecureLogin in MW-Vagrant:
>> https://gerrit.wikimedia.org/r/#/c/132799/
>>
>> Varnish:
>> This is proving to be much more difficult than anticipated, however some
>> progress was made and work is ongoing, spearheaded by Andrew Otto. The plan
>> is to set up varnish VCLs for mw-vagrant similar to what is set up for text
>> varnishes in production, with a frontend and backend instance running in
>> vagrant. Andrew is in the midst of refactoring the production varnish
>> module, to make it usable in Vagrant.
>>
>> CentralAuth/Multiwiki:
>> Bryan Davis, Chris Steipp, and Reedy spent a lot of time hacking on this,
>> and we now have support for multiwiki/CentralAuth in Vagrant! There is
>> still some cleanup work being done for the role to remove kludge/hacks/etc
>> (see https://gerrit.wikimedia.org/r/#/c/132691/).
>>
>> Also of significant note, Matt Flaschen created a mw-vagrant iso which can
>> be packaged on USB thumb drives, making it possible to set up mw-vagrant
>> without a network connection. There is still some work to be done here to
>> create a one-click installer as well as updating documentation. Matt got
>> this done before the hackathon, and we brought a bunch of USB sticks imaged
>> with the iso, which was instrumental in getting a bunch of folks new to
>> mw-vagrant up and running at the hackathon. This was particularly useful
>> during Bryan Davis's vagrant bootcamp sessions.
>>
>> I believe Katie Filbert from Wikidata did some mw-vagrant work at the
>> hackathon as well, although I'm not clear on the current status. Katie, can
>> you let us know where things were at with what you were working on?
>>
>> All in all it felt like a very fruitful hack session, and we're closer
>> than ever to having a ready-to-go developer instance that mimics our
>> production environment. Big thanks to everyone involved in making our work
>> successful.

I'd like to follow on with a big thanks to Arthur for bringing the
topic up and coordinating all of the meetings that led up to the
event. Never underestimate the power of having a good organizer on
your project!

Bryan
-- 
Bryan Davis  Wikimedia Foundation
[[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

Re: [Wikitech-l] enwiki display issues

[Andre Klapper]

Hi John,

thanks for bringing this up.

On Fri, 2014-05-16 at 16:07 -0400, John wrote:
> Looks like Javascript/CSS is intermittently failing.
> http://en.wikipedia.org/wiki/Wikipedia:Village_pump_%28technical%29#Something_is_broken

This was discussed also in #wikimedia-tech on IRC and as a first step.
If I got it correctly it's not clear yet what the culprit is, but trying
to first bypass your browser cache is recommended to check if the
problem(s) still happen: 
https://en.wikipedia.org/wiki/Wikipedia:BYPASS

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

Re: [Wikitech-l] Login to Wikimedia Phabricator with a GitHub/Google/etc account?

[Daniel Friesen]

On 2014-05-16, 1:57 PM, Tyler Romeo wrote:
> 2) When logging into Wikimedia, allow login with Google, GitHub, etc.
>
> Unfortunately, fulfilling that situation means deploying the OpenID
> extension, which is definitely not ready yet.
GitHub doesn't support OpenID.

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


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

[Wikitech-l] Performance guidelines chat Monday (for Asia/Australia)

[Sumana Harihareswara]

http://www.worldtimebuddy.com/?qm=1&lid=1816670,2147714,1277333,5128581&h=1816670&date=2014-5-19&sln=19-20

I will be in #wikimedia-dev on Monday for an hour to talk about the
performance guidelines
https://www.mediawiki.org/wiki/Performance_guidelines as well as
upcoming security and architecture guidelines:

New York: 7am
Bangalore: 4:30pm
Beijing: 7pm
Sydney: 9pm

This isn't one of the RfC meetings. :)

-- 
Sumana Harihareswara
Senior Technical Writer
Wikimedia Foundation

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

[Wikitech-l] Performance guidelines - aim to make official 23 May

[Sumana Harihareswara]

I've addressed the feedback I got in Zurich.

https://www.mediawiki.org/wiki/Performance_guidelines

I think this page is ready to have the {{draft}} tag removed. I believe
it now represents our consensus on what MediaWiki core, extensions, and
gadgets developers should do to preserve high performance. On May 23,
I'd like to move forward with making a tutorial and a poster based on
this. So, please edit, speak up, and so on, within the next week.

-- 
Sumana Harihareswara
Senior Technical Writer
Wikimedia Foundation

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

[Wikitech-l] Performance guidelines - aim to make official 23 May

[Sumana Harihareswara]

I've addressed the feedback I got in Zurich.

https://www.mediawiki.org/wiki/Performance_guidelines

I think this page is ready to have the {{draft}} tag removed. I believe
it now represents our consensus on what MediaWiki core, extensions, and
gadgets developers should do to preserve high performance. On May 23,
I'd like to move forward with making a tutorial and a poster based on
this. So, please edit, speak up, and so on, within the next week.
-- 
Sumana Harihareswara
Senior Technical Writer
Wikimedia Foundation

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

Re: [Wikitech-l] Login to Wikimedia Phabricator with a GitHub/Google/etc account?

[MZMcBride]

Chris Steipp wrote:
>Accounts are kinda namespaced, so github user foo and sul user foo can
>both have phabricator accounts.
>
>Since we're using OAuth though, that requires a global wiki account so
>local only accounts would not be able to join. So we probably need
>password or LDAP auth at minimum.

I suppose you could rely only on global (in the CentralAuth extension
sense) accounts, but it really would make sense for Wikimedia to get its
own house in order first: we should finish fully unifying login across
Wikimedia wikis before delving into concurrent authentication systems.

I think this mailing list thread suffers from an analysis of what the
potential negative consequences of allowing third-party login are. The
positive to users (one less username and password to remember) is clearer
to see. What are the drawbacks of doing this? I'd like to see the pros and
cons outlined on mediawiki.org or meta.wikimedia.org.

Greg Grossmeier wrote:
>You can. You can "claim" other accounts in Phab.

What's Phab?

MZMcBride



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

Re: [Wikitech-l] enwiki display issues

[Bartosz Dziewoński]

https://bugzilla.wikimedia.org/show_bug.cgi?id=65424

--
Matma Rex

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

Re: [Wikitech-l] enwiki display issues

[Dan Garry]

Thanks so much for working on this, guys!

Dan


On 16 May 2014 19:59, Bartosz Dziewoński  wrote:

> https://bugzilla.wikimedia.org/show_bug.cgi?id=65424
>
> --
> Matma Rex
>
>
> ___
> Wikitech-l mailing list
> Wikitech-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l
>



-- 
Dan Garry
Associate Product Manager for Platform and Mobile Apps
Wikimedia Foundation
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Login to Wikimedia Phabricator with a GitHub/Google/etc account?

[Chad]

On Fri, May 16, 2014 at 4:38 PM, MZMcBride  wrote:

> Chris Steipp wrote:
> >Accounts are kinda namespaced, so github user foo and sul user foo can
> >both have phabricator accounts.
> >
> >Since we're using OAuth though, that requires a global wiki account so
> >local only accounts would not be able to join. So we probably need
> >password or LDAP auth at minimum.
>
> I suppose you could rely only on global (in the CentralAuth extension
> sense) accounts, but it really would make sense for Wikimedia to get its
> own house in order first: we should finish fully unifying login across
> Wikimedia wikis before delving into concurrent authentication systems.
>
>
Yes, let's please. But that's another thread.

I'm less concerned about non-unified accounts than I am about the other
(much more obvious) problem of "how do we use Phabricator if the cluster
is down." Ryan suggested Labs LDAP and I agree, it's a very sane fallback.
It's very unlikely for the cluster *and* LDAP to be down at the same time,
and if they are it's probably network-related and we'll be screwed on using
Phabricator anyway.


> I think this mailing list thread suffers from an analysis of what the
> potential negative consequences of allowing third-party login are. The
> positive to users (one less username and password to remember) is clearer
> to see. What are the drawbacks of doing this? I'd like to see the pros and
> cons outlined on mediawiki.org or meta.wikimedia.org.
>
>
The positive side of "I can use one less login" is nice, don't get me wrong.

I'm mostly worried about security issues in 3rd party implementations of
oAuth
that we can't control. I asked Chris S. about this earlier today and I hope
he'll
expand on this some more--especially concerning to me was the concrete
example he gave with Facebook's own oAuth. Also he mentioned that Twitter's
oAuth is known to be insecure in its implementation.

Depending on how Github's oAuth is implemented that's the one I could see
the strongest case being made for.

Enabling all of them seems like it'll just make the login page cluttered
with
options used by about 1-2 people each but I could be wrong.

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

[Wikitech-l] Fwd: Abigail Ripstra joins the the User Experience team

[Jared Zimmerman]

-- Forwarded message --
From: Jared Zimmerman 
Date: Mon, May 12, 2014 at 1:05 AM
Subject: Abigail Ripstra joins the the User Experience team
To: wmf...@lists.wikimedia.org
Cc: Abbey Ripstra 


Everyone,

Its my great pleasure to welcome *Abigail Ripstra* to the User Experience
team. Most recently she was working as a Design & Usability Research
Analyst at Salesforce. She is excited to be part of the Wikimedia
Foundation’s mission and ongoing task of sharing knowledge and enabling our
users to more easily do so.

*Abigail joins Wikimedia Foundation as User Researcher Lead*, and will be
working with all product teams to help build and extend our ability to do
impactful qualitative research as part of our product development cycle.
She will not only grow the research team but help train all of us to do
research in a way that is consistent, useful, neutral, and most
importantly, effective in enabling decision making. In time we'll look to
Abigail to extend the team not only through hires but also through the
creation of a research internship program in collaboration with the
Grantmaking & Analytics teams modeled after the success of the legal
internship program. Our goals for qualitative research is that it can begin
to help shape our product roadmaps as well as validate and inform our
decision making processes.

Abigail has worked as a design researcher at Cisco Systems and Salesforce
collaboratively defining, testing, and iterating software functionality for
communication and collaboration. She worked at Steelcase to understand the
context, goals and needs of remote, distributed team mates. She has also
worked with a few design consultancies on various projects. For the past 11
years, she has been studying observing, researching and defining products
for people to collaborate and communicate. In a previous life, Abigail ran
her own business as a muralist, sign painter and decorative artist in
Chicago, and had several apprenticeships in graphic printmaking.

 When not at work she travels the world to satisfy her curiosity about how
people communicate and collaborate in and among various political,
technological, geographic, cultural and social contexts around the world.
She is an artist and continues to paint canvases and make drawings and
prints (with ink and paint).  She’s also into cooking, yoga, running on the
beach, riding a bike to get around and having adventures with friends and
family.



Abigail will be sitting with my team in the Northwest corner of the 3rd
floor, please come and introduce yourself.


Jared Zimmerman

Director of User Experience

*Jared Zimmerman * \\  Director of User Experience \\ Wikimedia Foundation

M : +1 415 609 4043 |   :  @JaredZimmerman
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] Status of fully unified login across Wikimedia wikis

[MZMcBride]

Chad wrote:
>On Fri, May 16, 2014 at 4:38 PM, MZMcBride wrote:
>> I suppose you could rely only on global (in the CentralAuth extension
>> sense) accounts, but it really would make sense for Wikimedia to get its
>> own house in order first: we should finish fully unifying login across
>> Wikimedia wikis before delving into concurrent authentication systems.
>
>Yes, let's please. But that's another thread.

All right. What's the status of fully unified login across Wikimedia wikis?

https://meta.wikimedia.org/wiki/SUL_finalisation was marked historical in
January, but that's probably not right.

As far as I'm concerned, the ability to easily rename global wiki accounts
(or accounts across all Wikimedia wikis) and a long warning window prior
to forcible account renames both seem like hard prerequisites, but the
former is still in development and the latter hasn't been started. I
imagine this can't be done in 2014, so possibly 2015?

MZMcBride



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

Re: [Wikitech-l] Status of fully unified login across Wikimedia wikis

[Dan Garry]

Legoktm will be working on this with me, but part of the condition of him
being released from his Flow work to do this was that he finish what he's
doing with Flow first.

Once he's done, we'll be working on it. I really have no way of guessing
when that'll be or how much work we've got ahead of us, so at this stage I
have no way of offering a timeline that isn't just a wild guess.

Dan


On 16 May 2014 20:46, MZMcBride  wrote:

> Chad wrote:
> >On Fri, May 16, 2014 at 4:38 PM, MZMcBride wrote:
> >> I suppose you could rely only on global (in the CentralAuth extension
> >> sense) accounts, but it really would make sense for Wikimedia to get its
> >> own house in order first: we should finish fully unifying login across
> >> Wikimedia wikis before delving into concurrent authentication systems.
> >
> >Yes, let's please. But that's another thread.
>
> All right. What's the status of fully unified login across Wikimedia wikis?
>
> https://meta.wikimedia.org/wiki/SUL_finalisation was marked historical in
> January, but that's probably not right.
>
> As far as I'm concerned, the ability to easily rename global wiki accounts
> (or accounts across all Wikimedia wikis) and a long warning window prior
> to forcible account renames both seem like hard prerequisites, but the
> former is still in development and the latter hasn't been started. I
> imagine this can't be done in 2014, so possibly 2015?
>
> MZMcBride
>
>
>
> ___
> Wikitech-l mailing list
> Wikitech-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l




-- 
Dan Garry
Associate Product Manager for Platform and Mobile Apps
Wikimedia Foundation
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Login to Wikimedia Phabricator with a GitHub/Google/etc account?

[Chris Steipp]

On May 16, 2014 5:20 PM, "Chad"  wrote:
>
> On Fri, May 16, 2014 at 4:38 PM, MZMcBride  wrote:
>
> > Chris Steipp wrote:
> > >Accounts are kinda namespaced, so github user foo and sul user foo can
> > >both have phabricator accounts.
> > >
> > >Since we're using OAuth though, that requires a global wiki account so
> > >local only accounts would not be able to join. So we probably need
> > >password or LDAP auth at minimum.
> >
> > I suppose you could rely only on global (in the CentralAuth extension
> > sense) accounts, but it really would make sense for Wikimedia to get its
> > own house in order first: we should finish fully unifying login across
> > Wikimedia wikis before delving into concurrent authentication systems.
> >
> >
> Yes, let's please. But that's another thread.
>
> I'm less concerned about non-unified accounts than I am about the other
> (much more obvious) problem of "how do we use Phabricator if the cluster
> is down." Ryan suggested Labs LDAP and I agree, it's a very sane fallback.
> It's very unlikely for the cluster *and* LDAP to be down at the same time,
> and if they are it's probably network-related and we'll be screwed on
using
> Phabricator anyway.
>
>
> > I think this mailing list thread suffers from an analysis of what the
> > potential negative consequences of allowing third-party login are. The
> > positive to users (one less username and password to remember) is
clearer
> > to see. What are the drawbacks of doing this? I'd like to see the pros
and
> > cons outlined on mediawiki.org or meta.wikimedia.org.
> >
> >
> The positive side of "I can use one less login" is nice, don't get me
wrong.
>
> I'm mostly worried about security issues in 3rd party implementations of
> oAuth
> that we can't control. I asked Chris S. about this earlier today and I
hope
> he'll
> expand on this some more--especially concerning to me was the concrete
> example he gave with Facebook's own oAuth. Also he mentioned that
Twitter's
> oAuth is known to be insecure in its implementation.

I don't want to start a rumor that using Twitter's OAuth for authentication
is insecure, but OAuth 1 (which phabricator is using for the login) isn't
made for authentication... Insert broken record track of me taking about
this ;)

More authentication systems means a bigger attack surface we have to
secure. If you look at the vulnerabilities fixed in phabricator via their
bounty program [1], 3 are login with OAuth bugs. This makes me nervous (but
kudos to them for running the program and fixing these).

Although it wasn't possible in any of these reported bugs yet, the big risk
is that an attack will allow adding a login account to an existing
phabricator account via csrf, allowing the attacker to add their 3rd party
account to my phabricator account and then they can login as me using their
Facebook, etc account. This famously happened to stack exchange via the
Facebook login last year.

So I'll do an audit on the methods we decide to go with, but I'd like to
keep that number fairly small. Turning them on isn't totally "free".

[1] https://hackerone.com/phabricator
>
> Depending on how Github's oAuth is implemented that's the one I could see
> the strongest case being made for.
>
> Enabling all of them seems like it'll just make the login page cluttered
> with
> options used by about 1-2 people each but I could be wrong.
>
> -Chad
> ___
> 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] Login to Wikimedia Phabricator with a GitHub/Google/etc account?

[Greg Grossmeier]

On May 16, 2014 4:39 PM, "MZMcBride"  wrote:
> Greg Grossmeier wrote:
> >You can. You can "claim" other accounts in Phab.
>
> What's Phab?

Short for Phabricator.

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

Re: [Wikitech-l] Thanks for the New Search and for Flow

[Chad]

On Fri, May 16, 2014 at 8:20 AM, Amir E. Aharoni <
amir.ahar...@mail.huji.ac.il> wrote:

> One of these feel-good emails:
>
> Thanks to the people who are working hard on developing the new search:
> Nik, Chad, Dan, and everybody who helps, tests, deploys and writes
> feedback.
>
> A Hebrew Wikipedia user wrote a big and detailed thank you note[1] that
> wiki's Village Pump, especially praising the instant indexing of
> newly-added content.
>
> The users are not just complaining all the time? :)
>
> [1] http://j.mp/1g8XylW , at least until it's archived. Thanks in advance
> to the people who are developing Flow, which should finally make links to
> discussions permanent.
>
>
Thanks for the kind words Amir :)

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

Re: [Wikitech-l] MW-Vagrant improvements at the Zürich Hackathon

[Ori Livneh]

On Fri, May 16, 2014 at 2:18 PM, Bryan Davis  wrote:
>
>  >> All in all it felt like a very fruitful hack session, and we're closer
> >> than ever to having a ready-to-go developer instance that mimics our
> >> production environment. Big thanks to everyone involved in making our
> work
> >> successful.
>
> I'd like to follow on with a big thanks to Arthur for bringing the
> topic up and coordinating all of the meetings that led up to the
> event. Never underestimate the power of having a good organizer on
> your project!
>

Yes, definitely agree. Thanks very much, Arthur.
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l