Re: [Wikitech-l] Fwd: No more Architecture Committee?

2015-01-22 Thread Brian Wolff

 I would also suggest that an effort be made to find community members
 who are not WMF employees to participate in the ArchCom and then to have
 their voices heard during in quarterly planning.

I dont know if this is practical. As Chad noted earlier, WMF hires the best
and the brightest. Even if the entire arch comitte was hit by a bus, the
people who i think would logically be next in line are still employed by
wmf. Even if those people got hit by a bus, i still think their logical
replacements would largely be wmf employees.

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

Re: [Wikitech-l] New feature in development: collections

2015-01-22 Thread Federico Leva (Nemo)
From 
https://tools.wmflabs.org/meetbot/wikimedia-office/2015/wikimedia-office.2015-01-14-21.00.log.html 
:
21:15:49 Emufarmers Is this collections thing the same as 
https://www.mediawiki.org/wiki/Mobile_web_projects/Collections_Backend 
(just came up during the research showcase)?


They look related, so I commented on the talk page there. It seems there 
are parallel discussions in other unknown mailing lists, so it's useful 
to centralise on the wiki.


Nemo

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

Re: [Wikitech-l] wfRunHooks deprecation

2015-01-22 Thread Legoktm


On 01/21/2015 09:39 AM, Jeroen De Dauw wrote:
 Hey,
 
 Does the new syntax offer any advantage over the old one?

It's a little bit faster by cutting down one function call which adds up
when a lot of hooks are called.

-- Legoktm

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

Re: [Wikitech-l] Fwd: No more Architecture Committee?

2015-01-22 Thread MZMcBride
Mark A. Hershberger wrote:
I am not qualified for the ArchCom, but I am familiar with several
engineers working in government or running private wiki farms or their
own businesses who I think would be qualified.

Another qualification I'd look for is substantial Wikimedia community
involvement. Architecting requires a very thorough understanding of who
you're building for. (I recently raised this same issue on the design
mailing list related to editing Wikipedia... I think it's very difficult
to build great tools for a community that you're not a part of.)

Thankfully, we have lots of good candidates who are both brilliant and
understand Wikimedia (Domas, Magnus, and Platonides come to mind off-hand).

The trickier part of having non-employees on a committee like this is that
other people won't be getting paid to participate and may not have as much
time to commit as a result. It's still a bit unclear to me how much work
is involved on a weekly basis. If it's just an hour-long IRC session,
that's a lot different than needing ten hours or more every week.

MZMcBride



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

Re: [Wikitech-l] Fwd: No more Architecture Committee?

2015-01-22 Thread Brian Wolff
On Jan 22, 2015 6:43 PM, Brian Wolff bawo...@gmail.com wrote:


 On Jan 22, 2015 2:08 PM, Tyler Romeo tylerro...@gmail.com wrote:
 
  I think that’s kind of insulting to those of us who don’t work at the
WMF. Just because they hire the “best and the brightest” does not mean
there are not people out there who are just as intelligent, if not more,
but do not or cannot work for the WMF for whatever reason. Restricting
Archcom to WMF employees is just about the stupidest thing you could do for
an open source software project. It defeats the entire purpose of MediaWiki
being open-source.
 

I apologize, i didnt mean to imply non wmf employees are any less bright
than wmf employees.

What i more meant to say (which i didnt express very well) is that the arch
comitte (essentially bdfl by comittee in my understanding. Not just about
architecture but also vision for mediawiki) should be composed of leaders
of the community who have been in the mediawiki community a long time, and
have fairly universal respect due to demonstrating wisdom over the long
term.

I dont think arch comitte should be composed solely of wmf'ers, i think
selection should be made entirely independent of affiliation (so working
for wmf should not disqualify someone). It just happens that the people who
i think are likely candidates all happen to currently work for the
wmf/wm-de.

This assumes of course that wmf wont force its employees to have certain
opinions. I dont think they have any intention of doing so.

After all, look at the current dev summit attendence list. How many people
on that list:
*has been fairly regularly active devs for at least 5 years
*has demonstrated wisdom (however you define that)
*does not currently work for wmf

Otoh perhaps other people have a different conception of what the arch
comitte should be or what the criteria for membership should be.

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

Re: [Wikitech-l] Fwd: No more Architecture Committee?

2015-01-22 Thread Federico Leva (Nemo)
Bawolff, I don't think the list of attendees of the current SF meeting 
is indicative of anything other than of the difficulty we have in 
talking with non-Wikimedia people; and even within Wikimedia, between 
WMF and non-WMF. Cf. 
https://www.mediawiki.org/wiki/Talk:MediaWiki_Developer_Summit_2015#Name .


As for «fairly regularly active devs for at least 5 years», we simply 
have no idea how many such persons there are outside our fishbowl. If, 
before even starting, we already exclude the iceberg of invisible people 
and use cases, no wonder we stay where we are. You don't need a 
committee to reinforce and calcify existing trends and structures.


If there is a need to expand/strengthen/diversify the committee, I'd 
rather look for members able to enlarge the MediaWiki contributor base 
in new directions. Mark mentioned some examples. Again, all this in the 
assumption we suffer from disunity, see my previous message.


Nemo

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

Re: [Wikitech-l] Fwd: No more Architecture Committee?

2015-01-22 Thread Tyler Romeo
Ah, I see. Yeah then it was just a misunderstanding. I completely agree with 
you on that point. I would be fine with an entirely-WMF ArchCom as long as 
being in the WMF was not one of the criteria they were selected because of.

-- 
Tyler Romeo
0x405D34A7C86B42DF

On January 22, 2015 at 17:51:59, Brian Wolff (bawo...@gmail.com) wrote:

I apologize, i didnt mean to imply non wmf employees are any less bright
than wmf employees.

What i more meant to say (which i didnt express very well) is that the arch
comitte (essentially bdfl by comittee in my understanding. Not just about
architecture but also vision for mediawiki) should be composed of leaders
of the community who have been in the mediawiki community a long time, and
have fairly universal respect due to demonstrating wisdom over the long
term.

signature.asc
Description: Message signed with OpenPGP using AMPGpg
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] Wikidata search provider for GNOME Shell

2015-01-22 Thread Bahodir Mansurov
I’ve created a GNOME Shell extension that allows the user to search for 
Wikidata items directly from the shell. Currently you can search for simple 
things such as “Obama”, “Book”, etc. I plan on adding support for complex 
queries such as “the population of the earth” which would show the current 
population of the earth. In the future I also see this extension handle the 
submission of new entries or editing existing ones. Check it out here [1] if 
you’re interested. Pull requests are also welcome ;)

[1] https://github.com/6ahodir/wikidata-search-provider
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Wikidata betalabs

2015-01-22 Thread Jon Robson
I managed to login after clearing some cookies and trying again.

So I had a few issues (not sure if these are reported anywhere):
* http://en.m.wikidata.beta.wmflabs.org/ is showing the desktop site.
* When I login via that url I somehow get stuck in https mode
* When I login from http://en.m.wikidata.beta.wmflabs.org/ I get taken to
https://login.wikimedia.beta.wmflabs.org/wiki/Special:CentralLogin/start
which is a broken page.

Is it possible to get all properties imported from wikidata.org into
the beta labs instance?
I do not have permissions on
http://en.wikidata.beta.wmflabs.org/wiki/Special:NewProperty and there
must be a faster way then manual entry?


On Thu, Jan 22, 2015 at 10:05 AM, Ryan Kaldari rkald...@wikimedia.org wrote:
 I can log in as well.

 On Jan 22, 2015, at 9:38 AM, Jon Robson jdlrob...@gmail.com wrote:

 Are we using http://wikidata.beta.wmflabs.org/ ?
 I can't seem to login

 ___
 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



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

Re: [Wikitech-l] Wikidata betalabs

2015-01-22 Thread Ryan Kaldari
I can log in as well.

On Jan 22, 2015, at 9:38 AM, Jon Robson jdlrob...@gmail.com wrote:

 Are we using http://wikidata.beta.wmflabs.org/ ?
 I can't seem to login
 
 ___
 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] Fwd: No more Architecture Committee?

2015-01-22 Thread Tyler Romeo
I think that’s kind of insulting to those of us who don’t work at the WMF. Just 
because they hire the “best and the brightest” does not mean there are not 
people out there who are just as intelligent, if not more, but do not or cannot 
work for the WMF for whatever reason. Restricting Archcom to WMF employees is 
just about the stupidest thing you could do for an open source software 
project. It defeats the entire purpose of MediaWiki being open-source.

-- 
Tyler Romeo
0x405D34A7C86B42DF

On January 22, 2015 at 06:31:29, Brian Wolff (bawo...@gmail.com) wrote:

I dont know if this is practical. As Chad noted earlier, WMF hires the best
and the brightest. Even if the entire arch comitte was hit by a bus, the
people who i think would logically be next in line are still employed by
wmf. Even if those people got hit by a bus, i still think their logical
replacements would largely be wmf employees.

signature.asc
Description: Message signed with OpenPGP using AMPGpg
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Wikidata betalabs

2015-01-22 Thread Alex Monk
Looks like you can use
http://m.wikidata.beta.wmflabs.org/wiki/Wikidata:Main_Page - but some
things are broken (e.g. remove '/wiki/' and get a broken redirect back)
Not sure why it accepts 'en.wikidata.beta.wmflabs.org' either

On 22 January 2015 at 19:51, Jon Robson jdlrob...@gmail.com wrote:

 I managed to login after clearing some cookies and trying again.

 So I had a few issues (not sure if these are reported anywhere):
 * http://en.m.wikidata.beta.wmflabs.org/ is showing the desktop site.
 * When I login via that url I somehow get stuck in https mode
 * When I login from http://en.m.wikidata.beta.wmflabs.org/ I get taken to
 https://login.wikimedia.beta.wmflabs.org/wiki/Special:CentralLogin/start
 which is a broken page.

 Is it possible to get all properties imported from wikidata.org into
 the beta labs instance?
 I do not have permissions on
 http://en.wikidata.beta.wmflabs.org/wiki/Special:NewProperty and there
 must be a faster way then manual entry?


 On Thu, Jan 22, 2015 at 10:05 AM, Ryan Kaldari rkald...@wikimedia.org
 wrote:
  I can log in as well.
 
  On Jan 22, 2015, at 9:38 AM, Jon Robson jdlrob...@gmail.com wrote:
 
  Are we using http://wikidata.beta.wmflabs.org/ ?
  I can't seem to login
 
  ___
  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



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

Re: [Wikitech-l] Fwd: No more Architecture Committee?

2015-01-22 Thread Mark A. Hershberger
Tyler Romeo tylerro...@gmail.com writes:

 Just because they hire the “best and the brightest” does not mean
 there are not people out there who are just as intelligent, if not
 more, but do not or cannot work for the WMF for whatever
 reason. Restricting Archcom to WMF employees is just about the
 stupidest thing you could do for an open source software project.

Exactly.  It ensures that those of us using or supporting MediaWiki
outside of the WMF have no voice in the direction of MW.

I am not qualified for the ArchCom, but I am familiar with several
engineers working in government or running private wiki farms or their
own businesses who I think would be qualified.

I think the WMF has hired the people it can hire, but that doesn't mean
all ArchCom-level knowledge is found only in Foundation employees.

Thinking that only the WMF has high-level MW knowledge and ability is a
myopic view that threatens the future of MediaWiki as software that is
useful outside of the WMF.

Mark.

-- 
Mark A. Hershberger
NicheWork LLC
717-271-1084

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

[Wikitech-l] Wikidata betalabs

2015-01-22 Thread Jon Robson
Are we using http://wikidata.beta.wmflabs.org/ ?
I can't seem to login

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

Re: [Wikitech-l] Wikidata betalabs

2015-01-22 Thread Jon Robson
oops pressed submit accidentally :-)
So yeh.. I can't seem to login and I am keen to test some things on
beta labs between this and the wikipedia beta labs instead
http://en.m.wikipedia.beta.wmflabs.org/

Is this known to be broken? Are there any bugs open?

Jon

On Thu, Jan 22, 2015 at 9:38 AM, Jon Robson jdlrob...@gmail.com wrote:
 Are we using http://wikidata.beta.wmflabs.org/ ?
 I can't seem to login



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

Re: [Wikitech-l] Wikidata betalabs

2015-01-22 Thread Alex Monk
I managed to log in successfully.

On 22 January 2015 at 17:38, Jon Robson jdlrob...@gmail.com wrote:

 Are we using http://wikidata.beta.wmflabs.org/ ?
 I can't seem to login

 ___
 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] wfRunHooks deprecation

2015-01-22 Thread Mark A. Hershberger
Legoktm legoktm.wikipe...@gmail.com writes:

 On 01/21/2015 09:39 AM, Jeroen De Dauw wrote:
 Hey,
 
 Does the new syntax offer any advantage over the old one?

 It's a little bit faster by cutting down one function call which adds up
 when a lot of hooks are called.

adds up is a poor defense for creating work for end users and
developers.  Has anyone actually measured what the difference is or is
this just an example of premature optimization[1]?

Mark.

Footnotes: 
[1]  http://en.wikipedia.org/wiki/Program_optimization#When_to_optimize

-- 
Mark A. Hershberger
NicheWork LLC
717-271-1084

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

Re: [Wikitech-l] wfRunHooks deprecation

2015-01-22 Thread Bryan Davis
On Thursday, January 22, 2015, Mark A. Hershberger m...@nichework.com
wrote:

 Legoktm legoktm.wikipe...@gmail.com javascript:; writes:

  On 01/21/2015 09:39 AM, Jeroen De Dauw wrote:
  Hey,
 
  Does the new syntax offer any advantage over the old one?
 
  It's a little bit faster by cutting down one function call which adds up
  when a lot of hooks are called.

 adds up is a poor defense for creating work for end users and
 developers.  Has anyone actually measured what the difference is or is
 this just an example of premature optimization[1]?

 Mark.

 Footnotes:
 [1]  http://en.wikipedia.org/wiki/Program_optimization#When_to_optimize

 I don't have before/after measurements but Aaron started changing from
wfRunHooks to direct Hook calls based on data gathered from WMF production
profiling. There was a non-trivial performance impact of the additional
layer of indirection.

Bryan


-- 
Bryan Davis  Wikimedia Foundationbd...@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

Re: [Wikitech-l] wfRunHooks deprecation

2015-01-22 Thread Chad
On Thu Jan 22 2015 at 1:10:27 PM Bryan Davis bd...@wikimedia.org wrote:

 On Thursday, January 22, 2015, Mark A. Hershberger m...@nichework.com
 wrote:

  Legoktm legoktm.wikipe...@gmail.com javascript:; writes:
 
   On 01/21/2015 09:39 AM, Jeroen De Dauw wrote:
   Hey,
  
   Does the new syntax offer any advantage over the old one?
  
   It's a little bit faster by cutting down one function call which adds
 up
   when a lot of hooks are called.
 
  adds up is a poor defense for creating work for end users and
  developers.  Has anyone actually measured what the difference is or is
  this just an example of premature optimization[1]?
 
  Mark.
 
  Footnotes:
  [1]  http://en.wikipedia.org/wiki/Program_optimization#When_to_optimize
 
  I don't have before/after measurements but Aaron started changing from
 wfRunHooks to direct Hook calls based on data gathered from WMF production
 profiling. There was a non-trivial performance impact of the additional
 layer of indirection.


Sure, but obvious performance gains are obvious. The real question to
me is was moving it into a static function inside of Hooks a benefit over
it just being a global function? My guess is no, not really.

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

Re: [Wikitech-l] Changing contentmodel of pages

2015-01-22 Thread Legoktm
Hi,

On 01/09/2015 04:25 PM, Erik Bernhardson wrote:
 However, changing the content model of an existing page is a disruptive
 change. We added the right `editcontentmodel` without which attempts to
 change content model through the API or EditPage.php fail. Currently no
 group (user or bot) has this right. So we think it's OK and safe to enable
 $wgContentHandlerUseDB on WMF wikis.
 https://gerrit.wikimedia.org/r/#/c/170129/ is the patch.

I think this is fine to turn on as well.

 There are issues with granting the editcontentmodel right, see T85847.

I disagree that we need a editcontentmodel user right. I think all
users should be allowed to change the content model of a page (provided
they have the right to edit it, etc.). Changing the content model of a
page is currently disruptive because the only way to do it (and undo it)
is via the API[1], and normal tools like undo don't work[2]. For now I'd
suggest we grant it to syops and then later on grant it to '*' by default.

 Daniel Kinzler proposed that we should not grant the editcontentmodel right
 because any change to content model is a special case that requires smart
 handling via dedicated PHP code. Which is what Flow is doing for both the
 Co-op bot and the future Special:Flowify.

That might make sense for changing the content model of an existing
page, but I don't think it applies for when we want to create a new page
with a content model different from the default. For example, in the
MassMessage extension we let people create pages with the
MassMessageListContent type wherever they want. It's not set as a
default anywhere meaning that you currently need the editcontentmodel
right to just create a list. :/

[1] https://phabricator.wikimedia.org/T72592
[2] https://phabricator.wikimedia.org/T73163

-- Legoktm

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