[Wikitech-l] Let's discuss Growing the MediaWiki Technical Community (Dev Summit)

[Matthew Flaschen]

At the Dev Summit, Birgit Müller and I will run a session on Growing the 
MediaWiki Technical Community.  If you're attending, we hope you will 
consider joining us.


Everyone (attending the Dev Summit or not) is welcome and encouraged to 
participate at https://phabricator.wikimedia.org/T183318 (please comment 
there, rather than by email).


We are discussing the following questions:

* What would allow you to develop and plan your software more efficiently?
* What would make software development more fun for you?
* What other Open Source communities do we share interests with?
* How can we change our processes to take technical debt more seriously?

"Develop" means any kind of work on a software system, including design, 
documentation, etc.


Our topics are:

* Better processes and project management practices, integrating all 
developers and allowing them to work more efficiently
* Building partnerships with other Open Source communities on shared 
interests (e.g. translation, audio, video)

* Reducing technical debt

Matt Flaschen

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

Re: [Wikitech-l] Can we drop revision hashes (rev_sha1)?

[Matthew Flaschen]

On 09/15/2017 06:51 AM, Daniel Kinzler wrote:

Also, I believe Roan is currently looking for a better mechanism for tracking
all kinds of reverts directly.


Let's see if we want to use rev_sha1 for that better solution (a way to 
track reverts within MW itself) before we drop it.


I know Roan is planning to write an RFC on reverts.

Matt

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

Re: [Wikitech-l] Wikidata properties for a fresh Wikibase

[Matthew Flaschen]

On 06/20/2017 09:32 AM, Susanna Ånäs wrote:

Can you advice how to create equivalent properties to a fresh Wikibase as
exist in Wikidata? Everything cannot be replicated, but having equivalent
IDs would be positive, and as much related information as possible.


After you set:

$wgWBRepoSettings['allowEntityImport'] = true;

you can just import specific (or all) properties from an XML dump (e.g. 
from https://www.wikidata.org/wiki/Special:Export or the dumps).


That will preserve the ID.

Matt

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

Re: [Wikitech-l] "must be of type int, int given"

[Matthew Flaschen]

On 04/17/2017 10:50 PM, Chad wrote:

On Mon, Apr 17, 2017 at 2:07 PM Gergo Tisza  wrote:


On Mon, Apr 17, 2017 at 8:35 PM, Denny Vrandečić 
wrote:


Value returned from function f() must be of type int, int given



Have you enabled PHP7 mode
?



I'm curious if we should enable this in Vagrant and our Jenkins testing so
we can avoid weird failures that spawned this thread.


That sounds like a good idea.  We would want to make sure there is still 
a gate without PHP 7 too, as long as we support PHP 5.5.9 (as core does).


Matt Flaschen

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

Re: [Wikitech-l] Security fix for Flow Nuke integration

[Matthew Flaschen]

On 04/17/2017 12:37 AM, Matthew Flaschen wrote:

This affects your wiki if you are using both Flow and Nuke.

We recently fixed https://phabricator.wikimedia.org/T162621 , an issue
with Flow's Nuke integration.

This has now been merged to master as well as the two supported Flow
release branches (1.27 and 1.28):

master - https://gerrit.wikimedia.org/r/#/c/348407/ (merged)
1.27 - https://gerrit.wikimedia.org/r/#/c/348408/1
1.28 - https://gerrit.wikimedia.org/r/#/c/348409/1


They are now all merged, so you can (and should) update normally.

Thanks,

Matt Flaschen

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

[Wikitech-l] Security fix for Flow Nuke integration

[Matthew Flaschen]

This affects your wiki if you are using both Flow and Nuke.

We recently fixed https://phabricator.wikimedia.org/T162621 , an issue 
with Flow's Nuke integration.


This has now been merged to master as well as the two supported Flow 
release branches (1.27 and 1.28):


master - https://gerrit.wikimedia.org/r/#/c/348407/ (merged)
1.27 - https://gerrit.wikimedia.org/r/#/c/348408/1
1.28 - https://gerrit.wikimedia.org/r/#/c/348409/1

This has already been deployed to WMF production.

There is an unrelated Jenkins issue with 1.27 and 1.28.  Until those are 
merged, you can download the patches using Download->Checkout in the 
top-right of Gerrit.  Sorry for the inconvenience.


Matt Flaschen

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

Re: [Wikitech-l] SECURITY: Flow security fix to make sure EnableFlow is always attributed

[Matthew Flaschen]

On 01/20/2017 05:02 PM, Matthew Flaschen wrote:

There is a security fix to ensure that EnableFlow is always properly
attributed.


Backports have been merged for 1.26, 1.27, and 1.28.

However, please note that MW 1.26 is end-of-life, and we are not 
supporting either MW 1.26 or Flow 1.26.


Matt Flaschen

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

[Wikitech-l] Weigh in on whether to finalize "Amendments" section of Code of Conduct

[Matthew Flaschen]

Please comment on whether to approve the "Amendments" section of the 
draft Code of conduct for technical spaces.


The draft text is at
https://www.mediawiki.org/w/index.php?title=Code_of_Conduct/Draft=2389930#Page:_Code_of_Conduct.2FAmendments
.

You can comment at
https://www.mediawiki.org/wiki/Talk:Code_of_Conduct/Draft#Finalize_.22Amendments.22_section.3F
. A position and brief comment is fine.

You can also send private feedback to conduct-discuss...@wikimedia.org .

Thanks again,

Matt Flaschen

* The "Creation and renewal of the Committee" section has been approved. 
 Thanks to everyone who helped discuss, edit, and approve this section.


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

[Wikitech-l] Please review "Amendments" section of the Code of Conduct

[Matthew Flaschen]

Please take this as a final opportunity to do review/suggest 
changes/etc. to the Amendments section of the draft Code of Conduct. 
This text has been up for a while, but I recently put in a small 
proposed change to make it harder for the Committee to veto amendments.


This is the last section.  After it's approved, the Code of Conduct will 
become policy, and the Amendments section will specify how future 
changes to the policy work.


* Current text: 
https://www.mediawiki.org/w/index.php?title=Code_of_Conduct/Draft=2389930#Page:_Code_of_Conduct.2FAmendments 
(under "Page: Code of Conduct/Amendments")
* Discussion: 
https://www.mediawiki.org/wiki/Talk:Code_of_Conduct/Draft#New_proposal_for_amendments


The approval discussion hasn't started yet.  It will be next and I will 
send out a separate email.


Thanks,

Matt Flaschen

P.S. You can still participate in deciding whether to approve "Creation 
and renewal of the Committee" at 
https://www.mediawiki.org/wiki/Talk:Code_of_Conduct/Draft#Finalize_.22Creation_and_renewal_of_the_Committee.22_section.3F 
.


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

Re: [Wikitech-l] Weigh in on whether to finalize "Creation and renewal of the Committee" section of Code of Conduct

[Matthew Flaschen]

To clarify, this discussion is specifically about "Creation and renewal 
of the Committee". which is the last section of "Page: Code of 
Conduct/Committee".  I've clarified the subject line accordingly.


I appreciate your participation.

Thanks,

Matt Flaschen

On 01/31/2017 08:33 PM, Matthew Flaschen wrote:

Please comment on whether to approve the "Creation and renewal of the
Committee" section of the draft Code of conduct for technical spaces.

The draft text is at
https://www.mediawiki.org/w/index.php?title=Code_of_Conduct/Draft=2374387#Creation_and_renewal_of_the_Committee
.

You can comment at
https://www.mediawiki.org/wiki/Talk:Code_of_Conduct/Draft#Finalize_.22Creation_and_renewal_of_the_Committee.22_section.3F
. A position and brief comment is fine.

You can also send private feedback to conduct-discuss...@wikimedia.org .

Thanks again,

Matt Flaschen

* The "Conflict of Interest" section has been approved.  Thanks to
everyone who helped discuss and edit these sections.


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

[Wikitech-l] Weigh in on whether to finalize "Committee" section of Code of Conduct

[Matthew Flaschen]

Please comment on whether to approve the "Creation and renewal of the 
Committee" section of the draft Code of conduct for technical spaces.


The draft text is at 
https://www.mediawiki.org/w/index.php?title=Code_of_Conduct/Draft=2374387#Creation_and_renewal_of_the_Committee 
.


You can comment at 
https://www.mediawiki.org/wiki/Talk:Code_of_Conduct/Draft#Finalize_.22Creation_and_renewal_of_the_Committee.22_section.3F 
. A position and brief comment is fine.


You can also send private feedback to conduct-discuss...@wikimedia.org .

Thanks again,

Matt Flaschen

* The "Conflict of Interest" section has been approved.  Thanks to 
everyone who helped discuss and edit these sections.


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

[Wikitech-l] Code of Conduct "‎Creation and renewal of the Committee" text

[Matthew Flaschen]

Please participate in the discussion about the "‎Creation and renewal of 
the Committee" section.  This is not to approve it yet, just a discussion:


https://www.mediawiki.org/wiki/Talk:Code_of_Conduct/Draft#.22Creation_and_renewal_of_the_Committee.22_section

Most of this text has been around for a while, but I made a few changes 
to the draft last week, so I wanted to give people an opportunity to 
comment, suggest changes, etc.


I'll give it a few more days, then start the formal approval discussion.

Thanks,

Matt Flaschen

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

Re: [Wikitech-l] SECURITY: Flow security fix to make sure EnableFlow is always attributed

[Matthew Flaschen]

On 01/20/2017 05:02 PM, Matthew Flaschen wrote:

There is a security fix to ensure that EnableFlow is always properly
attributed.

This may be an issue if you see users maliciously using
Special:EnableFlow on pages that already exist.


To clarify, the page already existing is fine.  It's just that users 
were sometimes converting to Flow when it was not appropriate to do so.


Matt

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

[Wikitech-l] SECURITY: Flow security fix to make sure EnableFlow is always attributed

[Matthew Flaschen]

There is a security fix to ensure that EnableFlow is always properly 
attributed.


This may be an issue if you see users maliciously using 
Special:EnableFlow on pages that already exist.


It should be merged shortly, but in the meantime, you can download it 
from Gerrit (https://gerrit.wikimedia.org/r/#/c/01/):


git fetch ssh://gerrit.wikimedia.org:29418/mediawiki/extensions/Flow 
refs/changes/01/01/1 && git checkout FETCH_HEAD


Matt Flaschen

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

[Wikitech-l] Weigh in on whether to finalize "Conflict of interest" sections of Code of Conduct

[Matthew Flaschen]

Please comment on whether to approve the "Conflict of interest" section 
of the draft Code of conduct for technical spaces.  This section did not 
reach not reach consensus earlier, but changes were made seeking to 
address the previous concerns.


You can find the section at 
https://www.mediawiki.org/w/index.php?title=Code_of_Conduct/Draft=2293195#Conflict_of_interest


You can comment at 
https://www.mediawiki.org/wiki/Talk:Code_of_Conduct/Draft#Finalize_new_version_of_.22Conflict_of_interest.22_section.3F 
.


A position and brief comment is fine.

You can also send private feedback to conduct-discuss...@wikimedia.org .

I really appreciate your participation.

Thanks again,

Matt Flaschen

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

[Wikitech-l] CentralAuth MediaWiki-Vagrant

[Matthew Flaschen]

If you use MediaWiki-Vagrant with CentralAuth, you may have noticed it 
stopped working.


There was a recent schema change, and since CA does not use update.php, 
you have to do it manually (or destroy your box, but that will take a 
lot longer).


If it's broken (huge red box and "Unknown column 'lu_local_id' in 'field 
list'")


$ vagrant ssh
$ mysql centralauth < 
/vagrant/mediawiki/extensions/CentralAuth/db_patches/patch-lu_local_id.sql


(This could be done via Puppet, but that would require writing that and 
then checking at runtime whether these columns exist forever.)


I hope that helps,

Matt

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

Re: [Wikitech-l] Code of Conduct

[Matthew Flaschen]

On 09/29/2016 11:23 AM, Steinsplitter Wiki wrote:

Positing it at the village pumpes of the local project (similar to the tech 
news notifications), for example :-)
Or using limited CN banners (similar to the community survey banners).


The local projects in this case are MediaWiki.org, 
wikitech.wikimedia.org, Phabricator, Gerrit, the technical mailing 
lists, the technical IRC channels, and Etherpad.


Activity in village pumps or elsewhere on other projects is not in scope.

I think most people active on these projects have already heard about 
it.  In addition to notifying people on the mailing lists (probably the 
primary way people heard about this) and Phabricator, we've also had 
in-person events.


The sitenotice is something we started looking into 
(https://www.mediawiki.org/wiki/Topic:T53wjhp29sgu6jms), and should 
finish following up on.


Matt

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

Re: [Wikitech-l] Code of Conduct

[Matthew Flaschen]

On 09/28/2016 07:07 AM, Steinsplitter Wiki wrote:

Last but not least: I am not happy at all that me comment has been
strike from
https://www.mediawiki.org/w/index.php?title=Talk:Code_of_Conduct/Draft=2247995=2247822
by Matt Flaschen (WMF). Looks like it is no longer allowed to comment
over there, thus i write here.


It had nothing to do with who made the comment, or your views on the 
section.


Rather, the issue is that you were taking a position in a discussion 
that was closed two weeks ago.  That could confuse people reviewing the 
discussion.


Matt Flaschen

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

Re: [Wikitech-l] Intro to "Committee" and "Diversity" section approved, "Conflict of interest" needs more work

[Matthew Flaschen]

On 09/06/2016 05:42 PM, Matthew Flaschen wrote:

The community approved the introduction to the Committee section
(https://www.mediawiki.org/wiki/Code_of_Conduct/Draft#Page:_Code_of_Conduct.2FCommittee)
(the part after "Committee" and before the "Diversity" section), as well
as the "Diversity" section
(https://www.mediawiki.org/wiki/Code_of_Conduct/Draft#Diversity).

There was not consensus to approve the "Conflict of interest"
(https://www.mediawiki.org/wiki/Code_of_Conduct/Draft#Conflict_of_interest)
section.  Work will continue on this section.  See the top of
https://www.mediawiki.org/wiki/Talk:Code_of_Conduct/Draft#Finalize_.22Conflict_of_interest.22_section.3F
(including the sections linked from those bullet points).


There has been further discussion on it, aiming to solve those issues. 
Please participate in the sub-sections of 
https://www.mediawiki.org/wiki/Talk:Code_of_Conduct/Draft#Finalize_.22Conflict_of_interest.22_section.3F 
and make sure your concerns are being addressed.


Thanks.

Matt Flaschen

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

[Wikitech-l] Intro to "Committee" and "Diversity" section approved, "Conflict of interest" needs more work

[Matthew Flaschen]

The community approved the introduction to the Committee section 
(https://www.mediawiki.org/wiki/Code_of_Conduct/Draft#Page:_Code_of_Conduct.2FCommittee) 
(the part after "Committee" and before the "Diversity" section), as well 
as the "Diversity" section 
(https://www.mediawiki.org/wiki/Code_of_Conduct/Draft#Diversity).


There was not consensus to approve the "Conflict of interest" 
(https://www.mediawiki.org/wiki/Code_of_Conduct/Draft#Conflict_of_interest) 
section.  Work will continue on this section.  See the top of 
https://www.mediawiki.org/wiki/Talk:Code_of_Conduct/Draft#Finalize_.22Conflict_of_interest.22_section.3F 
(including the sections linked from those bullet points).


Thanks,

Matt Flaschen

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

Re: [Wikitech-l] Opening up MediaWiki dev summit in January?

[Matthew Flaschen]

On 09/01/2016 03:35 PM, C. Scott Ananian wrote:
> However, no one was present at the

dev summit who used LanguageConverter on their home wiki, and few folks who
rely on Content Translation routinely.  (Maybe one or two were present, but
not enough to have a reasonable discussion about the future of these
features.)  For better or worse, previous dev summits have had weak
representation from those who are not American users of
projects-other-than-enwiki.


I think this general problem is partly inevitable.

I'm not saying that all Dev Summit attendees are enwiki users, or will 
be in the future.  But I think that even with scholarships and outreach, 
it will inevitably be skewed in a few ways:


1. Almost no one will show up, when compared to our broad user base. 
The people who do come will mostly be a subset of the most enthusiastic 
power users.


Power users are one of the groups we're building software for, but not 
the only one.


This can be mitigated with hard work at outreach to representative users 
who don't typically come to this kind of thing.


But this is also why we need to use other outreach and measurement 
efforts, like EventLogging, to reach and measure the people that don't 
attend summits (and may not answer surveys regularly).


2. The people that do come will be skewed towards being native speakers 
of English.


3. They will be heavily skewed towards being either WMF employees, San 
Francisco, or able to afford to fly.  Scholarships can help with this, 
but only partly.


So I would be careful about seeing this as a great opportunity to meet 
an accurate cross-section of our user base.  We need to be a little more 
strategic when thinking about what to build and who we're building for.


I agree with C. Scott there might be a role for specifically inviting 
key groups of users (e.g. shared hosting) to work with them in person 
and understand their needs.  Though this could be at the Dev Summit, it 
doesn't necessarily have to be.  It could be at Wikimania, or in SF but 
another time, etc.


Matt

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

[Wikitech-l] Weigh in on whether to finalize intro to "Committee" section of Code of Conduct

[Matthew Flaschen]

Please comment on whether to approve the introduction to the "Committee" 
section of the draft Code of conduct for technical spaces.


The draft text is at 
https://www.mediawiki.org/w/index.php?title=Code_of_Conduct/Draft=2208560#Page:_Code_of_Conduct.2FCommittee 
.  This is the part after the "Page: Code of Conduct/Committee" heading 
and before the "Diversity" heading.


You can comment at 
https://www.mediawiki.org/wiki/Talk:Code_of_Conduct/Draft#Finalize_introduction_to_.22Committee.22_section.3F 
. A position and brief comment is fine.


You can also send private feedback to conduct-discuss...@wikimedia.org .

Thanks again,

Matt Flaschen

P.S. Sorry, I should have combined this into my previous email.

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

[Wikitech-l] Weigh in on whether to finalize "Diversity" and “Conflict of interest” sections of Code of Conduct

[Matthew Flaschen]

Please comment on whether to approve the "Diversity" and "Conflict of 
interest" section of the draft Code of conduct for technical spaces:


* Diversity - https://www.mediawiki.org/wiki/Code_of_Conduct/Draft#Diversity
* Conflict of interest - 
https://www.mediawiki.org/wiki/Code_of_Conduct/Draft#Conflict_of_interest


You can comment at 
https://www.mediawiki.org/wiki/Talk:Code_of_Conduct/Draft#Finalize_.22Diversity.22_and_.22Conflict_of_interest.22_sections.3F 
.  A position and brief comment is fine.


You can also send private feedback to conduct-discuss...@wikimedia.org .

Thanks again,

Matt Flaschen

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

Re: [Wikitech-l] [Engineering] Ladies That FOSS in Germany in looking for MediaWiki mentors!

[Matthew Flaschen]

On 08/15/2016 03:34 PM, Rachel Farrand wrote:

Ladies That FOSS is WMDE's first Open Source Hack Event aimed primarily
at women who want to join a Free and Open Source Software (FOSS) project
but don’t know where to start. This is a unique opportunity for
nonbinary and woman coders to test out uncharted waters and code FOSS by
meeting some people who already got the FOSS flu and are deeply involved
in projects.


The event home page is at https://www.wikimedia.de/wiki/LadiesthatFOSS . 
 It is on October 29th, 2016, at Wikimedia Germany's headquarters in 
Berlin.


Matt

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

[Wikitech-l] "Cases" section approved, finishing "Committee" section of Code of Conduct

[Matthew Flaschen]

The community has approved the "Cases" 
(https://www.mediawiki.org/wiki/Code_of_Conduct/Draft#Page:_Code_of_Conduct.2FCases) 
section of the draft Code of Conduct.


The next section is "Committee".

* Section:
https://www.mediawiki.org/wiki/Code_of_Conduct/Draft#Page:_Code_of_Conduct.2FCommittee

* Talk:
https://www.mediawiki.org/wiki/Talk:Code_of_Conduct/Draft

* Alternatively, you can provide anonymous feedback to
conduct-discussion at wikimedia.org .

This is the best time to make any final necessary changes to the 
Committee section (and explain why, in edit summaries and/or talk) and 
discuss it on the talk page.


After this last call, I will send out emails seeking approval of this 
section, organized by sub-section.


Thanks,

Matt Flaschen


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

Re: [Wikitech-l] ACTION NEEDED: Security issues fixed in Flow

[Matthew Flaschen]

On 07/19/2016 05:30 PM, Matthew Flaschen wrote:

Two security issues related to topic title visibility and log entry
hiding were fixed in Flow:

* https://gerrit.wikimedia.org/r/299863
* https://gerrit.wikimedia.org/r/299864

If you are using master, please pull.

Patches are coming for release branches (see follow ups to this thread).


Patches for both supported release branches (REL1_26 and REL1_27) are 
merged as well, so you should pull for them too:

* https://gerrit.wikimedia.org/r/#/c/299882/
* https://gerrit.wikimedia.org/r/#/c/299883/
* https://gerrit.wikimedia.org/r/#/c/299884/
* https://gerrit.wikimedia.org/r/#/c/299885/

Note that these are the only supported release branches for Flow (other 
than current WMF deployment release branches).


Flow was previously marked as supporting 1.24+.  We no longer support 
1.24 or 1.25 (Core also does not; see 
https://www.mediawiki.org/wiki/Version_lifecycle#Versions_and_their_end-of-life).


If you are using 1.24 or 1.25, you should upgrade as soon as possible.

Matt

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

[Wikitech-l] Security issues fixed in Flow

[Matthew Flaschen]

Two security issues related to topic title visibility and log entry 
hiding were fixed in Flow:


* https://gerrit.wikimedia.org/r/299863
* https://gerrit.wikimedia.org/r/299864

If you are using master, please pull.

Patches are coming for release branches (see follow ups to this thread).

Matt

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

Re: [Wikitech-l] What's the "correct" content model when rev_content_model is NULL?

[Matthew Flaschen]

On 07/11/2016 10:10 AM, Brad Jorsch (Anomie) wrote:

On Mon, Jul 11, 2016 at 8:07 AM, Daniel Kinzler 

Re: [Wikitech-l] [Engineering] The train will resume tomorrow (was Re: All wikis reverted to wmf.8 last night due to T119736)

[Matthew Flaschen]

On 07/12/2016 11:35 PM, Legoktm wrote:

We should not be blocking login anymore. The patch[1] I deployed last
night catches the exceptions so users are able to login, but still
continues to log them.


Does that still apply if they're logging in *to* the wiki where their 
user row is missing?


I know it fixes the issue "I can't log into English Wikipedia because my 
account on randomwiki is messed up".


Matt

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

Re: [Wikitech-l] [Engineering] The train will resume tomorrow (was Re: All wikis reverted to wmf.8 last night due to T119736)

[Matthew Flaschen]

On 07/12/2016 09:25 PM, Matthew Flaschen wrote:

I am already writing an incident report, and I welcome a discussion.


Incident report for the Echo part of this: 
https://wikitech.wikimedia.org/wiki/Incident_documentation/20160712-EchoCentralAuth 
.  Please edit and improve.


Thanks,

Matt

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

Re: [Wikitech-l] [Engineering] The train will resume tomorrow (was Re: All wikis reverted to wmf.8 last night due to T119736)

[Matthew Flaschen]

On 07/12/2016 07:07 PM, Greg Grossmeier wrote:

Thanks to Matt Flaschen and Brad Jorsch (and others like Ori Livneh and
Bryan Davis) for their help.


Also Roan Kattouw, Kunal Mehta, and Stephane Bisson.

Matt


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

Re: [Wikitech-l] [Engineering] The train will resume tomorrow (was Re: All wikis reverted to wmf.8 last night due to T119736)

[Matthew Flaschen]

On 07/12/2016 07:56 PM, Ori Livneh wrote:

Is it actually fixed? It doesn't look like it, from the logs.


It's beyond unhelpful that you would send this email without pointing to 
the logs you are referring to.  With a statement like that, a paste is 
called for. 	


If you mean the existing inconsistent state that already exists, there 
is a script running as Greg explicitly noted.



It represents failure of process at multiple levels
and a lack of accountability.


"Lack of accountability" is a serious charge, and one that I disagree 
with.  That would imply people did not take responsibility for their 
code's failures, or did not this seriously, and that is not what I see. 
 The Collaboration team and other people, such as Bryan Davis, worked 
on this promptly as soon as they were made aware, and I take full 
responsibility for causing this issue.


The severity level may not have been evident until last night (thanks to 
Legoktm for helping show this).  Could the severity have been realized 
sooner?  Yes, but I'm not sure this is the way to make that happen.



I think we need to have a serious discussion about what happened, and
think very hard about the changes we would need to make to our processes
and organizational structure to prevent a recurrence.


I am already writing an incident report, and I welcome a discussion.

However, I strongly disagree with the attitude that /there was a serious 
bug; therefore no one cared/ .


I don't dispute it's a very serious and unfortunate bug, and I agree we 
should work to prevent bugs, and ensure they're remediated more promptly.


But I take my work and the extensions my team is responsible for 
seriously, and I worked on this urgently as soon as I knew about it.


Matt Flaschen

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

Re: [Wikitech-l] [Ops] [Engineering] The train will resume tomorrow (was Re: All wikis reverted to wmf.8 last night due to T119736)

[Matthew Flaschen]

On 07/12/2016 08:15 PM, aude wrote:

This (unbreak now) bug has been open since November.  I wonder how this
has been allowed to remain open and not addressed for this long?


This has not all been caused by Echo, and it really isn't one bug, just 
one symptom.


There are clearly multiple causes.  The Echo one has been addressed, and 
there are multiple fixes and mitigation on the CentralAuth/core auth 
side, some merged (e.g. https://gerrit.wikimedia.org/r/#/c/298531/ , 
https://gerrit.wikimedia.org/r/#/c/298416/ ), some still being worked 
on/discussed ( https://gerrit.wikimedia.org/r/#/c/297946/ , 
https://gerrit.wikimedia.org/r/#/c/297936/ ), but work is not done.


Matt

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

[Wikitech-l] Revert to 1.28.0-wmf.8

[Matthew Flaschen]

All wikis were rolled back to 1.28.0-wmf.8 last night due to an increase 
in https://phabricator.wikimedia.org/T119736 .  We're working on it, and 
will either go back to 1.28.0-wmf.9, or to 1.28.0-wmf.10 (at normal 
train pace) when it's resolved.


Matt

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

[Wikitech-l] Weigh in on whether to finalize "Cases" section of CoC

[Matthew Flaschen]

Please comment on whether to approve the "Cases" section of the draft 
Code of conduct for technical spaces 
(https://www.mediawiki.org/wiki/Code_of_Conduct/Draft#Page:_Code_of_Conduct.2FCases).


You can comment at 
https://www.mediawiki.org/wiki/Talk:Code_of_Conduct/Draft#Finalize_.22Cases.22_section.3F 
.  A position and brief comment is fine.


You can also send private feedback to conduct-discuss...@wikimedia.org .

Thanks again,

Matt Flaschen

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

[Wikitech-l] BREAKING CHANGE, ACTION NEEDED: Flow Vagrant role split into 2

[Matthew Flaschen]

I've split the Flow MediaWiki-Vagrant role into two, to make things 
simpler for casual Flow users.


If you don't have the Flow role enabled, you can stop reading now.

The basic 'flow' role will no longer depend on External Store and other 
optional dependencies.


You now need to do one of these things:

---
TLDR: If you use Flow on Vagrant regularly, enable wikimediaflow. 
Otherwise, enable externalstore or destroy your Vagrant.

---

* Enable 'wikimediaflow' (if you care about existing Flow content). 
This will bring in the optional dependencies again, and leave your 
content as-is.


* Enable 'externalstore' (if you care about existing non-Flow content
that is using External Store already).  Avoids the other optional 
dependencies, but brings in External Store, so existing External Store 
content can be read.


* Manually tweak configuration

* Just ignore the problems with old content

* Destroy and re-create your Vagrant (this will destroy the invalid 
content that points to no-longer-existing External Store, and leave you 
with a simpler config).


Matt

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

[Wikitech-l] Proposal to reopen the "Unacceptable behavior" section

[Matthew Flaschen]

Yaron Koren has proposed to reopen the "Unacceptable behavior" section 
(https://www.mediawiki.org/wiki/Talk:Code_of_Conduct/Draft#Suggested_change_to_.22discrimination.22_item).


His perspective and mine are given on the talk page.

In brief:
* He disagrees with how "marginalized and otherwise underrepresented 
groups" and "encouraged" are handled in the original text.
* I support the current text and process, and have explained why on the 
talk page.


Thanks,

Matt Flaschen

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

[Wikitech-l] Finishing "Cases" part of Code of Conduct

[Matthew Flaschen]

People are now working to conclude the "Code of Conduct/Cases" part of 
the draft Code of Conduct:


* Section:
https://www.mediawiki.org/wiki/Code_of_Conduct/Draft#Page:_Code_of_Conduct.2FCases

* Talk:
https://www.mediawiki.org/wiki/Talk:Code_of_Conduct/Draft

* Alternatively, you can provide anonymous feedback to
conduct-discussion at wikimedia.org .

This is the best time to make any final necessary changes to this 
section (and explain why, in edit summaries and/or talk) and discuss it 
on the talk page.


After this last call, I will send out another email seeking approval, 
like before.


Thanks,

Matt Flaschen


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

[Wikitech-l] Code of Conduct amendments text

[Matthew Flaschen]

Please participate in the discussion about how the Code of Conduct 
should be amended:


https://www.mediawiki.org/wiki/Talk:Code_of_Conduct/Draft#Changing_the_Code_once_enacted

Thanks,

Matt Flaschen

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

[Wikitech-l] Collaboration team scrum of scrums update

[Matthew Flaschen]

Collaboration
* Blocking
** External Store work on Beta is back in our court. We'll resume soon.
* Blocked
** We've asked for a schema change for new Echo functionality.  Ops has
started looking at this.
* Updates
** Echo MVC refactoring merged
** Some deletion fixes to core and Flow
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] update: wikipedia.org portal

[Matthew Flaschen]

On 05/21/2016 12:01 PM, rupert THURNER wrote:

quim, i would not be angry if you would show a little bit more empathy
towards a client, a volunteer. if mzmcbride is right and there is a
well established procedure to change this page which was not followed,
the person not following might read the "expected behaviour" page.
putting the blame on the person harrassed/frustrated (mzmcbride), not
on the harrasser (whoever changed the page) seems not a nice move in
that case.


If MZMcBride disagrees with a product decision or how the code is 
maintained, that does not mean he has been harassed.


Rather, it is MZMcBride's response that was hostile and unconstructive.

Matt

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

Re: [Wikitech-l] Automatic image colorization

[Matthew Flaschen]

On 05/03/2016 03:21 PM, Ori Livneh wrote:

In this thread, let's discuss how this technology could be integrated with
the projects. Should we have a bot that can perform colorization on demand,
the way Rotatebot  can
rotate images?


A couple notes:

* This could go in https://www.mediawiki.org/wiki/Extension:ImageTweaks 
when that's ready.


* This should go to a separate destination file (which it appears 
ImageTweaks already supports), since unlike rotation (which can be 
lossless and doesn't fundamentally change the essence of the image), 
colorization is a complete transformation, and it's worth preserving 
both old and new in some cases (e.g. historical images from archives).


Matt Flaschen

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

Re: [Wikitech-l] Automatic image colorization

[Matthew Flaschen]

On 05/03/2016 06:31 PM, Rob Lanphier wrote:

Matt, I agree that they probably picked an inappropriate license.
However, we shouldn't assume that the people picking the license
have a very sophisticated understanding of licenses.  It might be
worthwhile to ask the authors why they chose CC BY-NC-SA 4.0 instead
of a free license (like MIT, Apache, GPL or AGPL).


You're right.  This is a good point and I'm glad Ori contacted them.


Ori, this is a fantastic find!  I haven't created this wiki page
yet, but I think it should exist:


It'd be really awesome if
 contained a pointer
back to this discussion.

That is, of course, that people reading this list agree is
interesting.  Anyone here against colors?  ;-)


Not at all.  I sent my previous message a bit too hastily since I was 
about to go into a meeting, so I neglected to mention:


This is a really cool idea and a neat project (with very impressive 
results if the example images on GitHub are representative).  I hope the 
authors are willing to release their work under an open source license.


Matt

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

Re: [Wikitech-l] Automatic image colorization

[Matthew Flaschen]

On 05/03/2016 03:21 PM, Ori Livneh wrote:

A forthcoming paper
 from
researchers at Waseda University of Japan have developed a method for
automatic image colorization using deep learning neural network. The
results are both impressive and easy to reproduce, as the authors have
published
their code  to
GitHub with a permissive license.


Unfortunately, this is not an open source license, and thus we should 
not use it.  It uses Creative Commons 
Attribution-NonCommercial-ShareAlike 4.0.


Creative Commons consistently recommends against any use of CC licenses 
for software, and this one in particular is not libre or open source 
because it has a non-commercial restriction.


Matt Flaschen

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

Re: [Wikitech-l] MOOC Extension

[Matthew Flaschen]

On 04/13/2016 09:21 AM, Marko Obrovac wrote:

Right. Not everything needs a Vagrant role. However, having one definitely
increases the chance of people using your extension :) As Baha suggested,
you can file a new task in Phabricator and tag it with the
MediaWiki-Vagrant project.


Yes.  A good example of a very simple role is role::doublewiki (but 
please put a better description than that).  If your extension needs 
update.php, grep for needs_update.  role::cite is almost as simple, but 
shows how config settings work.


And you can feel free to ask on Phabricator or here for help.

Matt

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

Re: [Wikitech-l] Problems with building OOjs UI locally and exporting it to MW

[Matthew Flaschen]

On 04/14/2016 02:27 PM, Bartosz Dziewoński wrote:

Yeah, the current state is pretty silly… I think we just got used to it
and no longer question how horrible it is.


Scripted up: https://gerrit.wikimedia.org/r/#/c/283565/ :)

Matt

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

[Wikitech-l] Problems with building OOjs UI locally and exporting it to MW

[Matthew Flaschen]

What's the best way to build OOjs UI locally into the MW lib directory 
while developing?


I'm having two issues:

1. The README.md says:

"Install dev dependencies and build the distribution files:`$ npm 
install`"


This does not actually build to dist for me.

I then tried:

npm run-script publish-build

That partly works but has many errors:

https://phabricator.wikimedia.org/P2903

However, it apparently creates the key files.

2. I see update-oojs-ui.sh, but it looks like it's only intended for 
when the OOjs UI change is already published.


I had to hack it up with:

npm install '/home/matthew/Code/Wikimedia/oojs/oojs-ui/'

which seems to basically work.

If there is not yet a proper way to do this, I'll probably add this as 
an option.


This should be documented, probably at 
https://www.mediawiki.org/wiki/Using_OOjs_UI_in_MediaWiki .


Matt

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

Re: [Wikitech-l] Feelings

[Matthew Flaschen]

On 04/02/2016 09:37 PM, Ori Livneh wrote:

Why am I going on about this? I guess I'm a bit bummed out that the idea of
designing user interfaces that seek to improve the emotional environment by
making it easier to be warm and personal to one another is a joke.


For what it's worth, as someone who wasn't involved in that April 
Fools's "feature", but joke-reviewed it, I did not intend to to 
discourage any serious efforts to encourage a warm and productive editor 
community.


Matt

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

[Wikitech-l] Sections of Code of Conduct resolved and Code of Conduct approval process

[Matthew Flaschen]

We’ve gotten good participation as we’ve worked on sections of the Code 
of Conduct over the past few months, and have made considerable 
improvements to the draft based on your feedback.


Given that, and the community approval through the discussions on each 
section, the best approach is to proceed by approving section-by-section 
until the last section is done.


So, please continue to improve the Code of Conduct by participating now 
and as future sections are discussed.  When the last section is 
completed and approved on the talk page, the Code of Conduct will become 
policy and no longer be marked as a draft.


Also, two more discussions regarding the Code of Conduct have been 
resolved and incorporated into the draft.


* "Enforcement issues" addressed the reporting process and clarified 
that Committee decisions could not be circumvented

* "Marginalized and underrepresented groups" forbids discrimination

Thanks,

Matt Flaschen

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

[Wikitech-l] Please provide feedback on new discrimination and enforcement sections of Code of Conduct

[Matthew Flaschen]

Thanks for your participation in the recent Code of Conduct discussions.

The "Marginalized and underrepresented groups" discussion had a lot of 
feedback.  There was not consensus to use the exact original wording, 
but many people expressed willingness to support a modified text.


I've proposed such a new text, based on Neil P. Quinn's text, with a 
small modification to account for discrimination required by law (e.g. 
age of people who can sign certain contracts).


Please participate at 
https://www.mediawiki.org/wiki/Talk:Code_of_Conduct/Draft#New_proposed_wording 
.


The "Enforcement issues" section received general support, but some of 
that was conditional, or expressed preference for wording that developed 
during the discussion.  The original wording also did not address the 
appeals body, which was raised in the discussion.


Please participate at 
https://www.mediawiki.org/wiki/Talk:Code_of_Conduct/Draft#Circumvention_text_new_wording


Update regarding completed discussions:

The "Clarification of legitimate reasons for publication of private 
communications and identity protection" and "Definitions - trolling, 
bad-faith reports" discussions have been closed.


They both had support, and I've incorporated the text into the draft.

Thanks,

Matt

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

Re: [Wikitech-l] [Analytics] Please provide feedback on suggested improvements to the Code of Conduct

[Matthew Flaschen]

See discussion at 
https://www.mediawiki.org/wiki/Talk:Code_of_Conduct/Draft#Seems_to_be_a_lot_of_unanswered_questions_and_gray_areas 
.


Matt

On 02/23/2016 09:37 PM, regu...@gmail.com wrote:

I notice you mention in a lot of places that people should contact an
administrator. What if the person they are complaining about is an
admin? Because I have seen admins violate several of these rules of
conduct and it's rare for anything to be donecabout it.


Reguyla


Sent from my T-Mobile 4G LTE device


-- Original message--

*From: *Matthew Flaschen

*Date: *Tue, Feb 23, 2016 8:45 PM

*To: *Wikitech List;Engineering List;Design List;Wiki Research
List;Analytics Public List;hackathonorganiz...@lists.wikimedia.org
<mailto:;hackathonorganiz...@lists.wikimedia.org>;

*Subject:*[Analytics] Please provide feedback on suggested improvements
to the Code of Conduct


Thanks to everyone who’s helped work on the Code of Conduct sofar.Pe  <http://far.Pe>ople have brought up issues 
they feel were missed when working on "Unacceptable behavior" 
(https://www.mediawiki.org/wiki/Code_of_Conduct/Draft#Unacceptable_behavior  ) and "Report a problem" 
(https://www.mediawiki.org/wiki/Code_of_Conduct/Draft#Report_a_problem  ).   Consultants have also suggested changes in 
these samesections.Th  <http://sections.Th>ese are important sections, so please take a look at the proposed 
changes (https://www.mediawiki.org/wiki/Talk:Code_of_Conduct/Draft#Suggested_changes).I apologize that this feedback 
arrived later than planned, but I think this will create a better document.If you prefer to give your opinion privately, 
feedback via e-mail is welcome at  conduct-discuss...@wikimedia.org.Thanks  ,Matt Flaschen___Analytics 
mailing  listAnalytics@lists.wikimedia.orghtt  
lto: 
listAnalytics@lists.wikimedia.orghtt>ps://lists.wikimedia.org/mailman/listinfo/analytics
  <http://lists.wikimedia.org/mailman/listinfo/analytics>




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

[Wikitech-l] Please provide feedback on suggested improvements to the Code of Conduct

[Matthew Flaschen]

Thanks to everyone who’s helped work on the Code of Conduct so far.

People have brought up issues they feel were missed when working on 
"Unacceptable behavior" ( 
https://www.mediawiki.org/wiki/Code_of_Conduct/Draft#Unacceptable_behavior 
) and "Report a problem" ( 
https://www.mediawiki.org/wiki/Code_of_Conduct/Draft#Report_a_problem ). 
 Consultants have also suggested changes in these same sections.


These are important sections, so please take a look at the proposed 
changes ( 
https://www.mediawiki.org/wiki/Talk:Code_of_Conduct/Draft#Suggested_changes). 
 I apologize that this feedback arrived later than planned, but I think 
this will create a better document.


If you prefer to give your opinion privately, feedback via e-mail is 
welcome at conduct-discuss...@wikimedia.org.


Thanks,

Matt Flaschen

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

Re: [Wikitech-l] FOSDEM presentation (Converting LQT to Flow)

[Matthew Flaschen]

On 02/08/2016 06:27 PM, Ricordisamoa wrote:

Il 08/02/2016 18:42, Marius Hoch ha scritto:

For the sake of completeness, there also were two presentations held
by WMDE employees:

The presentations held by Lucie about the ArticlePlaceholder can be
found at
http://www.slideshare.net/frimelle/increasing-access-to-free-and-open-knowledge-for-speakers-of-underserved-languages-on-wikipedia



Slideshare is not download friendly. Ouch.


It is possible to download.  Just login.

It would be good to have it on Wikimedia Commons too, if possible.

Matt Flaschen

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

Re: [Wikitech-l] FOSDEM presentation (Converting LQT to Flow)

[Matthew Flaschen]

On 02/08/2016 12:42 PM, Marius Hoch wrote:

The presentations held by Lucie about the ArticlePlaceholder can be
found at
http://www.slideshare.net/frimelle/increasing-access-to-free-and-open-knowledge-for-speakers-of-underserved-languages-on-wikipedia


This was a cool talk about an interesting project.


The presentation Julia and Jens held about the Game Jam can be found at
https://commons.wikimedia.org/wiki/File:Free_Knowledge_Game_Jam_-_Presentation_at_FOSDEM_2016.pdf


I look forward to learning more about this project.

Best,

Matt Flaschen

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

[Wikitech-l] FOSDEM presentation (Converting LQT to Flow)

[Matthew Flaschen]

I've uploaded my slides for my FOSDEM 2016 presentation (Converting 
LiquidThreads to Flow: Or, how I learned to stop worrying and love the 
batch) to Commons:


https://commons.wikimedia.org/wiki/File:Converting_LQT_to_Flow_FOSDEM_2016.pdf

Matt Flaschen

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

Re: [Wikitech-l] Scope of ArchCom

[Matthew Flaschen]

On 01/25/2016 03:16 PM, Rob Lanphier wrote:

In the short-term, I believe a non-Wikimedia focused subgroup of ArchCom
may make sense.  The declining MediaWiki use outside of Wikimedia has been
a longstanding problem for us, but not the biggest problem.


Are there stats that show a decline?  Just curious.


ArchCom's focus is (and should continue to be) the needs of Wikimedia.


Disagree, though if that is what ArchCom sees its role as, then we 
should make a separate committee that considers the overall roadmap of MW.



Yes, I used the word "fork".  I believe Wikimedia Foundation would love it
if MediaWiki forked, and we were "forced" to switch to the fork.  There are
other projects (e.g. gcc, KHTML/WebKit, Inkscape) that were helped by a
fork.


This is very true, and these are good examples.

I'm a huge supporter of the right to fork, and if someone thinks that's 
the best solution, they should do it.


However, there are other examples where governance has successfully 
changed without a fork, such as Apache Cassandra.


There are also other examples of where there's a major user of the 
software (e.g. Wordpress.com) with downstream customizations, but 
powered by open source software also used by others (Wordpress proper).



As it stands, Wikimedia Foundation is the only trusted upstream for the
MediaWiki codebase.  I believe WMF should jealously guard the "MediaWiki"
trademark, if for no other reason than to force someone to come up with a
different name.  "MediaWiki" and "Wikimedia" are too similar, and there are
not good reasons for us to license that trademark to anyone else.


I disagree.  There are a lot of kinds of knowledge, and a lot of ways to 
"freely share in the sum of all knowledge".  Some of those ways are 
consistent with being part of a Wikimedia project (Wikipedia, 
Wiktionary, etc.).


Some other kinds of knowledge sharing could make good use of MediaWiki 
but *don't* belong on a Wikimedia project.


Licensing the MediaWiki trademark (maybe for a limited time at first, to 
make sure the other organization didn't mess it up) is consistent with 
the vision.



- Trusted architects with clear vision and leadership


Yes, and obviously this would include WMF employees, but not exclusively 
(in fact ArchCom already isn't only WMF).



- A governance structure that allows WMF to operate as a worthy peer


+1


So: forks welcome!  Any takers?


None of this requires a fork.

(It also might turn out that we try this, it doesn't work, and it leads 
to a fork.  But maybe that would mean it's the right solution after all. 
 I think we should try it without a fork first, though.)


Matt Flaschen

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

Re: [Wikitech-l] Scope of ArchCom

[Matthew Flaschen]

On 01/25/2016 05:58 PM, Alex Monk wrote:

  On 25 January 2016 at 20:16, Rob Lanphier  wrote:


So: forks welcome!  Any takers?


At this point I'm not sure any non-Wikimedia MediaWiki contributors have
the resources to do so. I think WMF employs most of the main MW developers,
and probably does >50% of the development.


I don't know if anyone has the resources for a fork, and as stated, I 
think the non-fork route should be tried first.


*However*, I have heard (in the source of these discussions) there are 
some resources that could be donated to MW development if there were an 
organization focused on the product itself and able to accept those 
donations (for WMF, that would not be accepted, as a restricted donation).


Matt Flaschen

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

Re: [Wikitech-l] Scope of ArchCom

[Matthew Flaschen]

On 01/22/2016 05:03 PM, Rob Lanphier wrote:

Hi everyone,

Those with a keen eye will notice that I filed T124255
, which calls for renaming
#MediaWIki-RfCs in Phab to "#ArchCom-RfC".  This would be a boring Phab
administrivia email if it was simply that.

The reason I want the rename:  ArchCom is the mechanism we hope to ensure
we build and deploy increasingly excellent software on the Wikimedia
production cluster in a consensus-oriented manner.  MediaWiki is at the
center of this, but ArchCom's responsibility doesn't end with MediaWiki.


In my opinion, there needs to be a group leading development of 
MediaWiki itself, focusing on the product and the product roadmap 
(influenced by who uses it).  WMF is a critically important user of MW, 
but not the only one.


There should also be a group employed by WMF responsible for keeping 
track of what ends up on the WMF cluster.  Obviously, the WMF cluster 
group would have a heavy influence on the MW roadmap, and they should 
not be surprised by anything happening in MW.


Nevertheless, they are separate focuses, and I would suggest we might 
want them to be separate groups.  The group in charge of MW's roadmap 
would not have to care about things like major operations/puppet 
restructuring, while the WMF cluster group would.


(Note, this is related to the discussions about MediaWiki Foundation, 
but doesn't need to wait on that).


Matt Flaschen

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

[Wikitech-l] Fwd: Your speaking schedule at FOSDEM

[Matthew Flaschen]

I will be presenting at FOSDEM on the LiquidThreads to Flow conversion, 
at 2016-01-30, 16:00 Belgium time:


http://www.timeanddate.com/worldclock/fixedtime.html?msg=FOSDEM+LiquidThreads+to+Flow+talk+by+Matt+Flaschen%2C+Livestreamed=20160130T15

It will be live-streamed at 
https://live.fosdem.org/watch.php?room=H.2215%20(Ferrer) (from what I 
can tell in advance).


Thanks,

Matt Flaschen

 Forwarded Message 
Subject: Your speaking schedule at FOSDEM
Date: Fri, 15 Jan 2016 22:13:33 +0100 (CET)
From: FOSDEM Programme Team 
Reply-To: speak...@fosdem.org
Organization: FOSDEM - https://fosdem.org/
To: Matt Flaschen 
CC: speak...@fosdem.org

Dear speaker,

Thank you for agreeing to speak at FOSDEM!

Our programme is now complete:
  https://fosdem.org/2016/schedule/

This is your schedule:

..
| day| time | room| title 
 |

++--+-+--+
| 2016-01-30 | 16:00:00 | H.2215 (Ferrer) | Converting LiquidThreads to 
Flow |

'+--+-+--'

.-.
| links   |
+-+
| https://fosdem.org/2016/schedule/event/flow |
'-'

Please check these links carefully.  If you already created an account at:
  https://fosdem.org/submit
you can login and update the information if need be.

In particular, please upload a photograph if you have not already done
so and enter or update your biography.

Changes take a few minutes to reach the website - the time it was last
updated appears at the bottom of this page:
  https://fosdem.org/2016/schedule/events/

If you find yourself unable to attend, please let your room's organiser
know this as soon as possible.

FOSDEM intends to record and stream the entire conference live - that's
over 300 hours of content!  The recordings will be published under the
same licence as all FOSDEM content (CC-BY).  You are agreeing to this by
taking part in the event.

Any slide decks you present should be uploaded by about half-an-hour
before the start of your talk so that people watching the live stream
can follow them locally if their video resolution leaves slide content
indistinct.  (Our system does not hold back publication, so if you don't
want people to see them too far in advance, don't upload them yet.)

Projectors work at 1024x768 but expect slides (and any demonstrations)
to be scaled down to 720x576 for the video, so try to make them
readable at this lower resolution if you can.

Please don't forget to bring a VGA adaptor if you hope to present from a
laptop that only has a different type of output connector!  We also
recommend bringing a spare copy of any slides on a USB stick.

As usual, we aim to provide free high-quality wireless network
connectivity throughout the event.

Best wishes,

The FOSDEM Programme Team



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

[Wikitech-l] Code of Conduct session at Wikimedia Developer Summit 2016

[Matthew Flaschen]

The Wikimedia Developer Summit starts this Monday, Jan. 4!

There will be an information and discussion session about the 
in-progress Code of Conduct for technical spaces 
(https://www.mediawiki.org/wiki/Code_of_Conduct/Draft) on Monday.


Thanks,

Matt Flaschen

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

Re: [Wikitech-l] Which hook to use and how for pre-save-modifications of wikitext?

[Matthew Flaschen]

On 11/14/2015 05:36 PM, Purodha Blissenbach wrote:

Hi,

I want to implement something similar to  expansion or the pipe-trick
in internal links in an extension.

That is, I need to execute code
- on save and preview only,
- on wikitext ony,
- on page content only,
- before the pre-save-parser treats links in the wikitext,
- altering the wikitext of the page.

I tried several hooks and ideas, but was unable to make it specific enough.


Did you try 
https://www.mediawiki.org/wiki/Manual:Hooks/ArticlePrepareTextForEdit ?


Matt Flaschen

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

Re: [Wikitech-l] IRC office hour this Thursday: reconnecting with the shared hosting community

[Matthew Flaschen]

On 11/16/2015 02:59 PM, Gilles Dubuc wrote:

As part of T113210 [1], which is a broader discussion on track for the
developer summit, I am hosting an IRC office hour [2] this Thursday at
19:00 UTC.


You might also want to send these messages to 
mediawik...@lists.wikimedia.org .  It seems likely that some shared 
hosting users are only signed up for that.  Maybe even 
mediawiki-annou...@lists.wikimedia.org , but the latter risks being spammy.


Matt Flaschen

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

[Wikitech-l] Fwd: Your stand proposal for FOSDEM 2016 has been accepted

[Matthew Flaschen]

The MediaWiki/Wikimedia stand has been accepted for FOSDEM.  The main 
coordination point prior to the event will be 
https://phabricator.wikimedia.org/T106560 .


Thanks,

Matt Flaschen

 Forwarded Message 
Subject: Your stand proposal for FOSDEM 2016 has been accepted
Date: Mon, 14 Dec 2015 20:54:55 +0100 (CET)
From: FOSDEM Stands Team 
To: Matthew 

Hi Matthew,

The FOSDEM stands team is glad to be able to inform you that your request
for a stand for 'MediaWiki' has been accepted.
There will be one table reserved for you.

Like most years, we received roughly twice as many requests for stands
as we have tables available. We have aimed to grant as many requests as
feasible and to increase the diversity of the accepted stands. Because
of this, we have unfortunately had to reduce the space available for a
number of regular attendees, as well as reject some projects that have
been present in previous years years.

You will receive further information about what's expected of you closer
to the event date.

Looking forward to seeing you at FOSDEM 2016!


Kind regards,

Wynke Stulemeijer
FOSDEM stands team



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

[Wikitech-l] Please help finish "Cases" page of CoC (+updates)

[Matthew Flaschen]

We are now working on the "Cases" page of the draft Code of conduct. 
This will become a separate page (for readability of the final CoC), but 
is being drafted on the same page with the rest.


This includes both the intro section, and all the sub-sections, which 
means everything that starts with "2." in the ToC.  Currently this is 
"Handling reports", "Responses and resolutions", and "Appealing a 
resolution".  However, the sections within "Cases" may change:


* Section: 
https://www.mediawiki.org/wiki/Code_of_Conduct/Draft#Page:_Code_of_conduct_for_technical_spaces.2FCases


* Talk: 
https://www.mediawiki.org/wiki/Talk:Code_of_Conduct/Draft#Finishing_the_Cases_page


* Alternatively, you can provide anonymous feedback to 
conduct-discuss...@wikimedia.org .


This is the best time to make any necessary changes to this page (and 
explain why, in edit summaries and/or talk) and discuss it on the talk page.


Other updates:

* The text of the "Report a problem" section has been frozen.  Thanks to 
everyone who helped discuss and edit these sections.  Participation 
(including both named and anonymous) helped us improve the 
confidentiality line.


Thanks,

Matt Flaschen

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

Re: [Wikitech-l] Contributing to Wikimedia Foundation

[Matthew Flaschen]

On 11/19/2015 08:32 AM, Bill Morrisson wrote:

Thanks Brian for the info. I'm realising that it has already been done but
the task was not closed


Actually, it has not been done.  The last change 
(https://phabricator.wikimedia.org/diffusion/MW/history/master/maintenance/oracle/tables.sql) 
to oracle/tables.sql is 	5f8edb2c0a24 , which is the change that caused 
the problem.


You can also see that change did not touch the dummy page.

Thanks,

Matt Flaschen

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

Re: [Wikitech-l] XML dumps

[Matthew Flaschen]

On 05/28/2015 07:52 PM, Lars Aronsson wrote:
> With proper release management, it

should be possible to run the old version of the process
until the new version has been tested, first on some smaller
wikis, and gradually on the larger ones.


I understand your frustration; however release management was not the 
issue in this case.  According to Ariel Glenn on the task 
(https://phabricator.wikimedia.org/T98585#1284441), "It's not a new 
leak, it's just that the largest single stubs file in our dumps runs is 
now produced by wikidata!".


I.E. it was caused by changes to the input data (i.e. our projects), not 
by changes to the code.


Matt Flaschen

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

Re: [Wikitech-l] Security patch for Flow merged

[Matthew Flaschen]

On 11/17/2015 05:12 PM, Matthew Flaschen wrote:

Nick Wilson discovered a security issue that affects Flow when used with
caching proxies such as Varnish:
https://phabricator.wikimedia.org/T116095 (this task will be opened soon).

In such a setup, topics in cache would remain accessible after the board
was deleted.

We have deployed the fix to the cluster and merged it to the Flow
repository.


Sorry, I didn't link the fix.  It's 
https://gerrit.wikimedia.org/r/#/c/253760/ .


Thanks,

Matt Flaschen

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

[Wikitech-l] Security patch for Flow merged

[Matthew Flaschen]

Nick Wilson discovered a security issue that affects Flow when used with 
caching proxies such as Varnish: 
https://phabricator.wikimedia.org/T116095 (this task will be opened soon).


In such a setup, topics in cache would remain accessible after the board 
was deleted.


We have deployed the fix to the cluster and merged it to the Flow 
repository.


Let us know if you are using REL1_24 or REL1_25 of Flow and this issue 
affects you.


Thanks,

Matt Flaschen

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

[Wikitech-l] Weigh in on whether to finalize "Report a problem" section of CoC

[Matthew Flaschen]

Please comment on whether to approve the "Report a problem" section of 
the draft Code of conduct for technical spaces 
(https://www.mediawiki.org/wiki/Code_of_Conduct/Draft#Report_a_problem).


You can comment at 
https://www.mediawiki.org/wiki/Talk:Code_of_Conduct/Draft#Finalize_.22Report_a_problem.22_section.3F 
.  A position and brief comment is fine.


You can also send private feedback to conduct-discuss...@wikimedia.org .

Thanks again,

Matt Flaschen

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

Re: [Wikitech-l] Please help finish "Report a problem" section of CoC (+updates)

[Matthew Flaschen]

On 10/22/2015 12:02 AM, Matthew Flaschen wrote:

We are now working on the "Report a problem" section of the draft Code
of conduct:

* Section:
https://www.mediawiki.org/wiki/Code_of_Conduct/Draft#Report_a_problem

* Talk:
https://www.mediawiki.org/wiki/Talk:Code_of_Conduct/Draft#Finishing_the_.22Report_a_problem.22_section


* Alternatively, you can provide anonymous feedback to
conduct-discuss...@wikimedia.org .


Let's spend another day wrapping this section up, then move to the 
consensus phase.


Thanks as always,

Matt Flaschen

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

[Wikitech-l] Please help finish "Report a problem" section of CoC (+updates)

[Matthew Flaschen]

We are now working on the "Report a problem" section of the draft Code 
of conduct:


* Section: 
https://www.mediawiki.org/wiki/Code_of_Conduct/Draft#Report_a_problem


* Talk: 
https://www.mediawiki.org/wiki/Talk:Code_of_Conduct/Draft#Finishing_the_.22Report_a_problem.22_section


* Alternatively, you can provide anonymous feedback to 
conduct-discuss...@wikimedia.org .


This is the best time to make any necessary changes to this section (and 
explain why, in edit summaries and/or talk) and discuss it on the talk page.


Your participation is also encouraged re the "Project administrators and 
maintainers have the right" line.  See 
https://www.mediawiki.org/wiki/Talk:Code_of_Conduct/Draft#Rewording_proposal.


Other updates:

* The text of the intro, "Principles" and "Unacceptable behavior" 
sections has been frozen.  Thanks to everyone who helped discuss and 
edit these sections.  See 
https://www.mediawiki.org/wiki/Talk:Code_of_Conduct/Draft#Fine_tuning_the_next_steps 
for details.


* The "Expected behavior" section has been moved, to 
https://www.mediawiki.org/wiki/Expected_behavior (a guideline) and (for 
one sentence) to the "Report a problem" section.  See 
https://www.mediawiki.org/wiki/Talk:Code_of_Conduct/Draft#Move_.22Expected_behavior.22_out_to_a_separate_guidelines_page.3F 
and 
https://www.mediawiki.org/wiki/Talk:Code_of_Conduct/Draft#New_proposal.2C_welcomes_feedback_2


* The text at the end of the "Unacceptable behavior" section has been 
rewritten: 
https://www.mediawiki.org/wiki/Talk:Code_of_Conduct/Draft#Move_.22Our_open_source_community_acknowledges22_out_of_the_CoC.3F 
.


Thanks,

Matt Flaschen

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

[Wikitech-l] Code of Conduct and publication of private non-harassing communication

[Matthew Flaschen]

Quim has proposed an alternative wording for the text about 
republication of private communication.


You can comment at 
https://www.mediawiki.org/wiki/Talk:Code_of_Conduct/Draft#New_proposal.2C_welcomes_feedback 
or to conduct-discuss...@wikimedia.org .


Thanks as always,

Matt Flaschen

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

[Wikitech-l] Code of conduct consensus discussions update

[Matthew Flaschen]

Full consensus was not reached on "Follow-up consensus discussion on 
intro, "Principles", "Expected behavior" and "Unacceptable behavior" 
sections" 
(https://www.mediawiki.org/wiki/Talk:Code_of_conduct_for_technical_spaces/Draft#Follow-up_consensus_discussion_on_intro.2C_.22Principles.22.2C_.22Expected_behavior.22_and_.22Unacceptable_behavior.22_sections).


Instead, there are a few discussions about how to move forward (I 
already sent the first two to the list, so consider those a reminder):


* Whether to consider most of the text from the last discussion done, 
but improve the controversial text (certain sentences/paragraphs drew 
the vast majority of the objections): 
https://www.mediawiki.org/wiki/Talk:Code_of_conduct_for_technical_spaces/Draft#Fine_tuning_the_next_steps


* Whether to move out the "Expected behavior" to a separate non-binding 
guidelines page: 
https://www.mediawiki.org/wiki/Talk:Code_of_conduct_for_technical_spaces/Draft#Move_.22Expected_behavior.22_out_to_a_separate_guidelines_page.3F 



* Whether to rearrange the pages used in the discussion process: 
https://www.mediawiki.org/wiki/Talk:Code_of_conduct_for_technical_spaces/Draft#Process_suggestion


* Whether to replace the end of the "Unacceptable behavior" section 
("Our open source community acknowledges" etc.") with two sentences 
(https://www.mediawiki.org/wiki/Talk:Code_of_conduct_for_technical_spaces/Draft#Move_.22Our_open_source_community_acknowledges22_out_of_the_CoC.3F).


Thanks,

Matt Flaschen

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

[Wikitech-l] Code of conduct consensus discussions

[Matthew Flaschen]

The code of conduct 
(https://www.mediawiki.org/wiki/Code_of_conduct_for_technical_spaces/Draft) 
is still actively being worked on.


There are two new consensus discussions:

* Whether to consider most of the text from the last discussion done, 
but improve the controversial text (certain sentences/paragraphs drew 
the vast majority of the objections): 
https://www.mediawiki.org/wiki/Talk:Code_of_conduct_for_technical_spaces/Draft#Fine_tuning_the_next_steps


* Whether to move out the "Expected behavior" to a separate non-binding 
guidelines page: 
https://www.mediawiki.org/wiki/Talk:Code_of_conduct_for_technical_spaces/Draft#Move_.22Expected_behavior.22_out_to_a_separate_guidelines_page.3F


Feel free to state your position with a brief rationale.

Thanks,

Matt Flaschen

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

Re: [Wikitech-l] [Engineering] Feedback needed on intro, "Principles", "Expected behavior" and "Unacceptable behavior" sections of COde of Conduct

[Matthew Flaschen]

On 10/03/2015 10:59 AM, Quim Gil wrote:

2. At
https://www.mediawiki.org/wiki/Talk:Code_of_conduct_for_technical_spaces/Draft#Follow-up_consensus_discussion_on_intro.2C_.22Principles.22.2C_.22Expected_behavior.22_and_.22Unacceptable_behavior.22_sections,
leave your possitioning: {{accept}}, {{neutral}}, or {{oppose}}, and
your signature. Additional comments are welcomed but not required.


Correction: {{support}}, {{neutral}}, or {{oppose}}

Matt Flaschen

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

Re: [Wikitech-l] Announcing Danny Horn's move to Community Tech

[Matthew Flaschen]

On 10/01/2015 07:05 PM, Ryan Kaldari wrote:

Howdy (my apologies for cross-posting),

I'm pleased to announce that the Community Tech team has a new Product
Manager – Danny Horn, who will be moving from the Collaboration team to
join this new initiative. The Community Tech team is focused on building
improved curation and moderation tools for experienced Wikimedia
editors.[1]


Danny, we're going to miss you a lot on the Collaboration team.

But I'm also excited about the work that the Community Tech team is 
doing.  These are important areas that WMF hasn't always spent enough 
resources on.


Matt Flaschen

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

[Wikitech-l] Feedback needed on intro, "Principles", "Expected behavior" and "Unacceptable behavior" sections of COde of Conduct

[Matthew Flaschen]

Consensus was reached in the first discussion regarding the intro, 
"Principles", and "Unacceptable behavior" sections.  See 
https://www.mediawiki.org/wiki/Talk:Code_of_conduct_for_technical_spaces/Draft#Consensus_discussion_on_intro.2C_.22Principles.22.2C_and_.22Unacceptable_behavior.22_sections 
.


However, while that was being discussed, several of us made changes to 
these sections.  In the future, we need to avoid this (to avoid endless 
discussion).


Thus, in the future I'll send out two separate announcements, one for 
"last call to work on these sections" and one for "consensus discussion 
for these sections".


However, this time, that wasn't done.  So I want to give people a chance 
to weigh in on whether we should accept the changes that were made 
during the first discussion.


Thus, there is a new discussion at 
https://www.mediawiki.org/wiki/Talk:Code_of_conduct_for_technical_spaces/Draft#Follow-up_consensus_discussion_on_intro.2C_.22Principles.22.2C_.22Expected_behavior.22_and_.22Unacceptable_behavior.22_sections 
.


This will only last a week.  I expect to close it October 6th.

Thanks,

Matt Flaschen

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

Re: [Wikitech-l] Announcing the launch of Maps

[Matthew Flaschen]

On 09/17/2015 03:26 PM, Tomasz Finc wrote:

The Discovery Department has launched an experimental tile and static maps
service available at https://maps.wikimedia.org.


Congratulations to the whole team.  This is a huge deal, and will open 
up our projects to whole new kinds of media, editing, and interactivity.


Matt Flaschen


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

[Wikitech-l] Consensus discussion on Code of Conduct intro, "Principles", and "Unacceptable behavior" sections

[Matthew Flaschen]

Please weigh in at 
https://www.mediawiki.org/wiki/Talk:Code_of_conduct_for_technical_spaces/Draft#Consensus_discussion_on_intro.2C_.22Principles.22.2C_and_.22Unacceptable_behavior.22_sections 
on whether to consider the text of the intro (section before 
"Principles"), "Principles", and "Unacceptable behavior" sections done.


See link for details on what this means.

Matt Flaschen

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

Re: [Wikitech-l] Code of Conduct: Intro, Principles, and Unacceptable behavior sections

[Matthew Flaschen]

On 09/05/2015 07:11 PM, MZMcBride wrote:

I think there are people who sympathize with and even support efforts to have 
codes of
conduct in technical spaces, but who don't want to feel demonized for
being male.


Then those people should be glad to participate in finalizing this CoC.


There's a dark irony in sites such as Geek Feminism Wiki
feeling the need to prominently answer "Are men welcome here?" in their
FAQ ().


Since I felt welcome on that wiki before reading that FAQ, I don't 
really find it ironic.  Perhaps they went farther than they needed to be 
welcoming, but *that's not a bad thing*.



This isn't to say that there aren't good ideas and good people behind some
of this content, but I can see a lot potential allies to the code of
conduct cause being put off by the militant feminist language and
overeager citations of feminist theory.


There is no such language or citation on the draft.

Matt Flaschen


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

Re: [Wikitech-l] Code of Conduct: Intro, Principles, and Unacceptable behavior sections

[Matthew Flaschen]

On 09/05/2015 05:32 PM, rupert THURNER wrote:

lol, consensus among whom, to what?


"There is consensus at" - Consensus among people discussing at that talk 
page.


"that the best way to finalize the CoC draft is to focus on a few 
sections at once" - Consensus about that.


Matt Flaschen

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

Re: [Wikitech-l] "Try the free Wikipedia app" banners

[Matthew Flaschen]

On 09/04/2015 03:12 PM, Brandon Harris wrote:



On Sep 2, 2015, at 3:53 PM, Toby Negrin 
wrote:



1. We're moving people from an open platform to a closed platform:
I think this is an oversimplification of the situation -- as has
been noted before, the android app is 100% open source and while
the data is not, in my opinion, comprehensive, it's inarguable that
a large percentage of mobile traffic on the internet is from apps.
It's not possible to fulfill our mission[4] if Wikipedia and sister
project content is not available in widely used channels.


I'm not sure this makes a lot of sense.  The widest, most-open
content channel that the projects have is through the web interfaces:
all phones, all devices, all computers can access the same content in
the same manner.  That is to say: 100% of our readers have the
ability to use the web versions (either desktop or mobile web) where
as only a subset can use the Android app, which is a different subset
that can use iOS.  (They also end up having fragmented experiences,
which is sub-optimal.)


Some fraction of our users have the ability to go a library and read
Wikipedia there.  That doesn't mean publishing Wikipedia in library 
kiosk form would fulfill their needs.  A lot of them don't *actually* go 
to libraries, even though they could.  Analogously, a lot of people 
prefer apps to web.


We need to share content in ways our readers and editors want, not in
the ways we prefer they do it.

(There is also a huge role for reusers sharing our content in other
interesting ways, but that's another matter).


So it seems to me that the apps are not required to fulfill the
mission.  They feel like distractions, and - quite possibly -
negatives to the mission (in that we can't convert Readers into
Editors through the app).


Why not?  The app already supports editing.  True, you can't do every 
possible kind of edit/operation, but people don't do all of those as 
early editors anyway.  It certainly provides a way to become an editor, 
and get editing work done.


Matt Flaschen

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

[Wikitech-l] Code of Conduct: Intro, Principles, and Unacceptable behavior sections

[Matthew Flaschen]

There is consensus at
https://www.mediawiki.org/wiki/Talk:Code_of_conduct_for_technical_spaces/Draft#Next_steps
that the best way to finalize the CoC draft is to focus on a few
sections at once (while still allowing people to comment on other
ones).  This allows progress without requiring people to monitor all
sections at once and lets us separate the questions of “what are our
goals here?” and “how should this work?”.  After these sections are
finalized, I recommend minimizing or avoiding later substantive
changes to them.

The first sections being finalized are the intro (text before the
Principles section), Principles, and Unacceptable behavior.  These
have been discussed on the talk page for the last two weeks, and
appear to have stabilized.

However, there may still be points that need to be refined. Please
participate in building consensus on final versions of these sections:

* https://www.mediawiki.org/wiki/Talk:Code_of_conduct_for_technical_spaces/Draft

* https://www.mediawiki.org/wiki/Code_of_conduct_for_technical_spaces/Draft

If you are not comfortable contributing to this discussion under your
name or a pseudonym, you can email your feedback or suggestions to
conduct-discuss...@wikimedia.org .  Quim Gil, Frances Hocutt, and
Kalliope Tsouroupidou will be monitoring this address and will
anonymously bring the points raised into the discussion at your
request.

Thanks,

Matt Flaschen

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

Re: [Wikitech-l] QA: Holding our code to better standards.

[Matthew Flaschen]

On 09/03/2015 02:45 PM, Jon Robson wrote:

The future!:
Given this success:
1) I would like to see us run @integration tests on core, but I
understand given the number of bugs this might not be feasible so far.
2) We should run @integration tests prior to deployments to the
cluster via the train and communicate out when we have failures (and
make a decision to push broken code)
3) I'd like to see other extensions adopt browser test voting on their
extensions. Please feel free to reach out to me if you need help with
that. The more coverage across our extensions we have, the better.


+100%  I assume #2 should be "make a decision whether to push broken code".

Matt Flaschen


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

Re: [Wikitech-l] Collaboration team reprioritization

[Matthew Flaschen]

On 09/03/2015 03:54 AM, Federico Leva (Nemo) wrote:

 > that only non-Wikimedia developers have maintained LQT
 > is false, as a brief review of the commit log will show.

I said "non-Wikimedia users". Not sure what log you've been looking to,
but I did `git log --no-merges -- . ':(exclude)i18n'` and I confirm what
I said. The only exception I found so far is T104421 where you fixed a
fatal (thanks!). Other than that the only bug fixes I see are some in
Flow migration.


Bug fixes are only one form of maintenance.  Performance improvements 
are also important (speed is a feature), as are changes coordinated with 
other repositories (this prevents bit rot).


I got to over ten of these before I stopped counting.

That doesn't even count maintenance changes that are partly for 
LQT->Flow, but also useful in their own right.


And the bug fix you gave is not the only recent one.

Matt Flaschen

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

Re: [Wikitech-l] New RFC: better JS minification

[Matthew Flaschen]

On 09/01/2015 07:53 PM, MZMcBride wrote:

I'd personally prefer that we move in the other direction, removing the
minification. I think it's harmful to the open Web to minify, or worse,
obfuscate our code.


I don't agree with this.  However, I do think source maps (which allow 
you to serve minified code but see the original source code as soon as 
you open the script inspector/debugger) are important.  UglifyJS 
apparently has support for this already 
(https://github.com/mishoo/UglifyJS2), so this would actually probably 
make it more likely to get implemented.



As expected, we've encountered a number of bugs that
disappear when the debug=true URL parameter is specified.


Not all of those are related to minification.  In fact, I think most are 
not.



And given other performance optimization work and existing optimizations such 
as gzip
compression, I don't see the benefits outweighing the costs.


unminified + gzip is still noticeably bigger than minified + gzip.

All of our software is free and open source.  There is no reason we have 
to use more bandwidth than needed.


Matt Flaschen

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

Re: [Wikitech-l] Collaboration team reprioritization

[Matthew Flaschen]

On 09/02/2015 12:35 PM, David Gerard wrote:

On 2 September 2015 at 14:51, Risker  wrote:


I want to thank the Collaboration team for taking this brave step - and
yes, it's a brave step. The natural trajectory of large projects that don't
quite seem to meet their promise is to keep going and going until everyone
is burnt out, and it is courageous to say "this isn't going where we wanted
it to" and break that cycle.  Most of the people who are currently involved
in Flow and the Collaboration team were not there when it started, and they
joined a project that had very mixed levels of support that had very
challenging and broad objectives.  We as a community can learn a lot from
their experience, and we really should make an effort to examine this
project and use this experience to re-examine and improve the process of
developing new software.




+1 - it's far better to kill it now than later.


Flow is not being killed.

In addition to maintaining and supporting it, we'll soon be working on 
rolling out a Beta feature to allow people to enable Flow on their user 
talk pages.


After that, we'll start work on workflows, as noted in the original 
email.  Workflows were *always* planned to be the next stage of Flow. 
That's the whole reason it's called Flow.


Matt

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

Re: [Wikitech-l] Collaboration team reprioritization

[Matthew Flaschen]

On 09/02/2015 02:21 AM, Federico Leva (Nemo) wrote:

Thanks. So now we'll have two unmaintained extensions, LQT and Flow.


As noted, Flow is not unmaintained.


Can we reverse the Flow conversion on mediawiki.org now, so that the wiki
stays on the luckiest side i.e. the extension which has most users and
is most likely to survive in the future?


Extensions are not maintained by 'luck'.  They are maintained by hard 
work.  We've done much of that work, to make sure LQT pages are not 
abandoned.



(LQT is maintained by its non-Wikimedia users, otherwise it would have
broken down years ago on all Wikimedia wikis as well.)


The implication that only non-Wikimedia developers have maintained LQT 
is false, as a brief review of the commit log will show.


Matt Flaschen

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

Re: [Wikitech-l] "Try the free Wikipedia app" banners

[Matthew Flaschen]

On 09/02/2015 03:55 PM, Ryan Lane wrote:

Even ignoring the "is it right and ethical" debate, there's a pretty large
amount of research over the past 6 or so months that show this is a bad
idea.


[citation needed]

Matt Flaschen


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

Re: [Wikitech-l] Collaboration team reprioritization

[Matthew Flaschen]

On 09/02/2015 09:21 AM, David Gerard wrote:

On 2 September 2015 at 07:27, Dan Garry  wrote:

On 1 September 2015 at 23:21, Federico Leva (Nemo) 
wrote:



Thanks. So now we'll have two unmaintained extensions, LQT and Flow.



To quote Danny's email directly, "Flow will be maintained and supported".
Your supposition that the extension will be unmaintained is not correct.



As a third-party MediaWiki tarball user, I'm slightly annoyed because
RationalWIki took on LQT originally because WMF made it sound like it
was definitely the future yep no worries. As the current sysadmin I
desperately would love to set LQT on fire and put it in a bin and was
hoping Flow would be the supported option. Bah, how annoying ...


Flow *is* the supported option, as stated in Danny's original email.


Did the stuff to port LQT threads/pages to Flow ever make it to
production quality?


Yes.  We've done a lot of work to ensure that neither LQT users nor LQT 
talk pages have been left behind.



OTOH, the problems outlined in this message are pretty much exactly
what experienced Wikipedia users said when Flow was started - you need
to be able to cut'n'paste slabs of wikitext (or parsoid HTML5 or
whatever VE actually copies to the clipboard) from the article to the
talk page, which means something VEish on talk too.


Flow has VE support.  However, simply having a free-form area is not the 
full solution. We need to actually make these workflows easier for users 
(not require them to copy and paste templates around), which is the next 
step.


Matt

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

Re: [Wikitech-l] "Try the free Wikipedia app" banners

[Matthew Flaschen]

On 09/01/2015 11:30 AM, Ori Livneh wrote:

We appear to be running a banner campaign on the mobile web site, driving
people to download the mobile app:

https://en.m.wikipedia.org/wiki/?banner=Aug2015_app_banner_2
https://en.m.wikipedia.org/wiki/?banner=Aug2015_app_banner_1

Campaign definition:
https://meta.wikimedia.org/w/index.php?title=Special:CentralNotice=noticeDetail=Android_app

This isn't cool. This isn't us. We don't drive people from an open platform
to a closed one.


I don't necessarily think it's a great idea to push people from web to 
apps either, especially when we also have people working on mobile web.


I also do most of my mobile Wikipedia browsing on mobile web.

That said, I think that assessment is overly critical.

* The Android mobile app is fully free and open source (obvious, since 
all of our stuff is, but worth re-iterating).


* They've done a great job on the app.  In particular, they've 
implemented features that are easier on app (or only feasible there), 
like a user-friendly saved pages list and a nice UI in general.


* I don't know this for sure, but I would guess the app works on 
fully-FOSS versions of Android (e.g. Replicant), since an updated 
version is in the fully-free app store 
(https://f-droid.org/wiki/page/org.wikipedia).  If it doesn't work on 
Replicant (or some similar fully-FOSS Android), that does seem like 
something important to address.


* No one is going to install proprietary software as a result of this 
ad.  It only shows to people who are *already* running Android and asks 
them to install free and open source software.


It's no different then recommending to a Windows user that they install 
Inkscape because it's a great piece of free and open source software.


Finally, this is indeed only configured for Finland.

Matt Flaschen

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

Re: [Wikitech-l] [Engineering] Code of conduct

[Matthew Flaschen]

On 08/22/2015 10:52 PM, Risker wrote:

Perhaps more importantlywho were the local contacts at Hackathon 2015?
I can't even dig that one up in the event documentation.

A policy that exists but has no clear or visible support isn't worth the
bytes it's written with.


This is a good point.  The Friendly space policy needs to be enforced 
(in addition to the code of conduct being drafted now).


I'll be on the look out, to ensure our in-person events properly cite 
the Friendly space policy and list these contacts.  I hope other people 
do the same.


Thanks,

Matt Flaschen


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

Re: [Wikitech-l] [Engineering] Code of conduct

[Matthew Flaschen]

On 08/24/2015 02:44 PM, Brian Wolff wrote:

The I remembered having my butt pinched, my breasts 'accidentally
touched' part would seem to fall under the proposed policy.


As is unwanted attention, even if verbal, and sustained disruption, 
interruption, which would be applicable if people are continually 
interrupting your talk on purpose (similar to the background 
conversation note, though not the same thing).


Matt Flaschen


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

Re: [Wikitech-l] Code of conduct committee

[Matthew Flaschen]

On 08/21/2015 06:43 AM, Quim Gil wrote:

I also would like to see more edits from volunteers and other affiliations.
Please jump in! Most WMF employees drafting and discussing there are doing
so out of their personal interest, with no WMF directive and most likely on
their own time. I'm basically the only exception.


It's important to remember that we're building this CoC because it is 
relevant to both our community and our work.


I know that's why I'm participating, and I believe it's also why the 
volunteers are.


Matt Flaschen


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

Re: [Wikitech-l] Improving CAPTCHA friendliness for humans, and increasing CAPTCHA difficulty for bots

[Matthew Flaschen]

On 08/19/2015 10:17 PM, Jamison Lofthouse wrote:

The subject sounds exactly like the reCAPTCHA 
https://www.google.com/recaptcha/intro/index.html tagline. Not sure how
beneficial the project would be but I have seen it used. Maybe worth
looking into.


Unfortunately, we can not use reCAPTCHA because it is proprietary software.

I agree this is an important issue.  It just isn't resourced right now 
by the WMF, as far as I know.


Matt Flaschen


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

[Wikitech-l] Code of conduct committee

[Matthew Flaschen]

There is some discussion now about how the Code of Conduct Committee 
should be formed.  See:



* 
https://www.mediawiki.org/wiki/Talk:Code_of_conduct_for_technical_spaces/Draft#Membership_of_the_committee_and_ECT.27s_role


and

* 
https://www.mediawiki.org/wiki/Talk:Code_of_conduct_for_technical_spaces/Draft#Another_membership_proposal 
.


Thanks,

Matt Flaschen

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

Re: [Wikitech-l] Tools for dealing with citations of withdrawn academic journal articles

[Matthew Flaschen]

On 08/18/2015 05:42 AM, Pine W wrote:

Is there any easy way to find all of citations of specified academic
articles on Wikipedias in all languages, and the text that is supported by
those references, so that the citations of questionable articles can be
removed and the article texts can be quickly reviewed for possible changes
or removal?


LinkSearch is a start for this, in the meantime:

E.g.:

* A DOI that uses dx.doi.org (such as cite doi): 
https://en.wikipedia.org/w/index.php?target=dx.doi.org%2F10.1000%252F182title=Special%3ALinkSearch


* Another URL: 
https://en.wikipedia.org/w/index.php?target=example.com%2Fwithdrawnpapertitle=Special%3ALinkSearch


The underlying data for this (externallinks) is most likely replicated 
to Labs, so a tool there could do a cross-wiki search.


Matt Flaschen


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

Re: [Wikitech-l] Code of conduct

[Matthew Flaschen]

On 08/17/2015 08:28 PM, Frances Hocutt wrote:

On Mon, Aug 17, 2015 at 5:22 PM, Alex Monk kren...@gmail.com wrote:


It looks like Communicate about technology in public where possible.
Private means of communication do exist, but prefer to use public places
unless an exception is appropriate. has been removed and Publication of
non-harassing private communication. has been added as a form of
harassment...



Correct. I removed the first per the discussion here[1] and brought in some
of the Grants Friendly Space Expectations[2], since those seem to have been
working well.


Yaron actually removed it on Wednesday 
(https://www.mediawiki.org/w/index.php?title=Code_of_conduct_for_technical_spaces/Draftdiff=1836917oldid=1836907) 
on the grounds that it's more of a guideline kind of thing.


Matt Flaschen


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

Re: [Wikitech-l] Code of conduct

[Matthew Flaschen]

On 08/06/2015 08:17 PM, Matthew Flaschen wrote:

Please participate at
https://www.mediawiki.org/wiki/Code_of_conduct_for_technical_spaces/Draft .


The draft has now been rebased onto Contributor Covenant (a widely used 
Code of Conduct), per a discussion on our talk page.


Now is a good time to help refine the draft to make sure previously 
discussed issues are still addressed, and Wikimedia-specific questions 
are answered.


Thanks,

Matt Flaschen


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

Re: [Wikitech-l] [Engineering] Code of conduct

[Matthew Flaschen]

On 08/12/2015 06:41 PM, David Gerard wrote:

On 12 August 2015 at 23:00, Matthew Flaschen mflasc...@wikimedia.org wrote:


Enforcement is still to-be-determined.



This does need to be sorted out ahead of time.


See my proposal at 
https://www.mediawiki.org/wiki/Talk:Code_of_conduct_for_technical_spaces/Draft#First_line_of_enforcement 
.  There are some details to be refined, but I like having a single 
initial point of contact.


Matt Flaschen


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