[Wikitech-l] 2016W43 ArchCom-RFC meeting: Allow HTML in SVG?

Hi everyone, For [this week's ArchCom-RFC meeting][E325], let's talk about SVG. As you probably know, MediaWiki optionally allows for SVG uploads, which is allowed on many Wikimedia wikis (e.g. on Commons). However, in order to make this preference safe to use, we need to validate the SVG. One

[Wikitech-l] 2016W42 ArchCom-RFC meeting: Surveying Cookie/Local Storage Use

Hi all, At this week's ArchCom Office hour, we'd like to help the WMF Legal team ensure our software development practices don't accidentally cause us to enable all sorts of creepy surveillance because a naive developer adds it. The challenge, of course, is when the royal "we" accidentally add

[Wikitech-l] 2016W41 ArchCom-RFC meeting: CREDITS

Hi everyone, This week's ArchCom Office Hour[1] is going to be about a long-neglected item: giving credit where credit's due in the CREDITS file (Jon Robson's T139300 proposal[2]). Jon and I spoke about it earlier today; he's not sure he can be there, and this is a meeting where I would have

[Wikitech-l] Timing of ArchCom meetings

Hi folks, The thing that's been great about having ArchCom meetings at the same time and place has been that we've been able to make a habit out of having them. Because we're a global movement, there's never a good time for anyone, but the time we typically schedule for these was the best

Re: [Wikitech-l] Wikimedia Developer Summit 2017 discussion

ssion about Phabricator vs MediaWiki to handle the call for participation. " That said, I'll provide a more detailed reply, because someone is wrong on the Internet! ;-) More inline On Wed, Sep 28, 2016 at 2:27 AM, Legoktm <legoktm.wikipe...@gmail.com> wrote: > On 09/27/2016 09:55 PM, Ro

Re: [Wikitech-l] Wikimedia Developer Summit 2017 discussion

At the risk of threadjacking about dogfooding On Tue, Sep 27, 2016 at 2:45 PM, Legoktm wrote: > On 09/27/2016 03:57 AM, Quim Gil wrote: >> * Phabricator form to submit Wikimedia developer Summit 2017 proposals >> (urgent because it blocks the opening of the call

[Wikitech-l] Wikimedia Developer Summit 2017 discussion

Hi everyone, Abstract --- This mail doubles as an invitation to come to this week's ArchCom office hour (Phab:E285), and provides an attempt to provide answers to questions about the agenda of the Wikimedia Developer Summit (WikiDev17). I'm hoping we find a way to work with people who

Re: [Wikitech-l] Gerrit screen size

On Sun, Sep 25, 2016 at 5:41 AM, Tim Starling wrote: > On 25/09/16 21:09, Bináris wrote: > > I try to familiarize myself with Gerrit which is not a good example for > > user-friendly interface. > > I noticed a letter B in the upper right corner of the screen, and I > >

Re: [Wikitech-l] Debian and Ubuntu packages for MediaWiki now available

On Wed, Sep 21, 2016 at 11:44 PM, Legoktm wrote: > Instructions, links, and help can all be found at > . Please let me > know if you have any questions or feedback. > > Finally, thanks to Luke Faraone, Faidon

[Wikitech-l] WikiDev17 Collaboration topic (Re: Opening up MediaWiki dev summit in January?)

Scott suggested the following as one of three suggested topic ideas for WikiDev17. The three ideas: 1) Collaboration 2) Wikitext Maintenance 3) Machine Translation More inline about "1) Collaboration" below: On Tue, Sep 20, 2016 at 10:05 AM, C. Scott Ananian wrote: >

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

On Tue, Sep 20, 2016 at 10:05 AM, C. Scott Ananian wrote: > Here are three topic suggestions, cc'ed here in case folks aren't following > the Flow, with an illustrative (but not exhaustive) list of sessions that > could fit under each Thanks for doing that breakdown! I

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

On Thu, Sep 15, 2016 at 1:09 AM, Daniel Kinzler wrote: > Am 15.09.2016 um 01:54 schrieb Chad: >> Bummer. I think paying down tech debt is fun and way more rewarding >> than making shiny new things. >> >> But I'm also weird as hell... > > /me waves to a kindred soul.

[Wikitech-l] No ArchCom IRC office hour planned for this week (2016W37)

Hi folks, Many of us at WMF will be at a Product and Tech meeting here in SF, so we decided not to hold the usual IRC office hour on #wikimedia-office. I've updated "upcoming meetings" part of the status page with some info on *next* week's meeting:

Re: [Wikitech-l] Memento MediaWiki Extension at the W3C

On Mon, Sep 12, 2016 at 10:57 AM, Shawn Jones wrote: > Considering the consensus from the RFC was to start a pilot of Memento on > English Wikipedia, how do we start that process again? Hi Shawn, Thanks for your previous email, with all of the links. Several of us

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

On Thu, Sep 8, 2016 at 7:53 AM, Nuria Ruiz wrote: > > Seems that defining what areas we want to cover in the summit is > a prerequisite to do what Brion was asking for in the initial e-mail, to > open the summit beyond WMF. > > Good point. Let's say that we had to pick only

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

Hi Quim, Thanks for the response, and thanks for responding for my request to talk about this at the upcoming IRC meeting: I've got a lot of thoughts about your response, but I'm going to zero in on the central thing that's confusing me

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

On Mon, Sep 5, 2016 at 11:14 PM, Quim Gil wrote: > Thank you for starting this conversation, Brion! > > Let me share the point where Rachel Farrand (Summit organizer) and I > (Summit budget owner) find ourselves, after some conversations. > > GOALS [...] The Summit and its

[Wikitech-l] 2016W36 ArchCom-RFC meeting: shadow namespaces?

Hi all, What do y'all think of using this week's ArchCom review to talk about T91162: Shadow Namespaces[1]? That's what I just put into the status page[2], and up in the Phab event for this week[3]. This would be at the usual time (Wednesday 21 UTC, 14 PDT, 23 CEST) and place

[Wikitech-l] Dev Summit ideas from 2013

orwarded message ------ From: Rob Lanphier <ro...@wikimedia.org> Date: Fri, Sep 6, 2013 at 5:01 PM Subject: Architecture discussion next week To: Development and Operations Engineers <engineer...@lists.wikimedia.org> Hi everyone, I’d like to bring you up to speed

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

On Thu, Sep 1, 2016 at 1:33 PM, Rob Lanphier <ro...@wikimedia.org> wrote: > I copied your message here: > <https://www.mediawiki.org/wiki/Talk:WikiDev17> Ooops, I meant here: <https://www.mediawiki.org/wiki/Talk:Wikimedia_Develo

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

On Thu, Sep 1, 2016 at 10:12 AM, Brion Vibber wrote: > I think we should change this. I think so too! I have a lot more to say, but I'm thinking that the best place to say it will be on wiki rather than on mailing list. So, I copied your message here:

Re: [Wikitech-l] 2016W35 ArchCom-RFC meeting: Revisiting image/oldimage (T589)

rected version below (highlighted with "***") Rob On Wed, Aug 31, 2016 at 12:20 AM, Rob Lanphier <ro...@wikimedia.org> wrote: > Hi everyone, > > For this week's office hour, we'd like to discuss [T589: ***RfC: image and > oldimage tables***][1] Timo brought this up on

[Wikitech-l] 2016W35 ArchCom-RFC meeting: Revisiting image/oldimage (T589)

Hi everyone, For this week's office hour, we'd like to discuss [T589: schema change for page content language][1] Timo brought this up on the list a couple of weeks ago, and didn't get much of a response. (But thank you Jaime for responding!) We discussed this one fairly recently ([July

[Wikitech-l] Last call on ArchCom-RFC T69223 (Schema change for page content language)

Hi everyone Per During E263, Jaime (@jcrespo) put the following choice to us. Should he: a. Apply this change to all wikis b. Apply this change to a subset of wikis, on request c. Not apply this change We seemed to get consensus around "a"

Re: [Wikitech-l] Introduction for Gsoc 2017

On Wed, Aug 24, 2016 at 10:09 AM, MAYANK JINDAL wrote: > My name is Mayank Jindal. I am third year undergraduate student > currently studying at Indian Institute of Technology, Kharagpur. I want to > take part in Gsoc-2017 from Wikimedia. > I have knowledge of C,

[Wikitech-l] 2016W34 ArchCom-RFC meeting: Schema change for page content language

Hi everyone, For this week's office hour, let's discuss [T69223: schema change for page content language][1] Jaime Crespo has asked that the developers seeking this change get general consensus for the change. A discussion at an ArchCom IRC meeting isn't strictly necessary for this, it can't

Re: [Wikitech-l] T47317: Sections generated by tag extension do not show up in TOC

On Thu, Jul 28, 2016 at 5:46 AM, Lord_Farin wrote: > I would like to draw your attention to ticket > https://phabricator.wikimedia.org/T47317. > This ticket highlights some issues with the way sections, headers and the > TOC are handled in the parser in combination with

[Wikitech-l] 2016W33 ArchCom-RFC meeting: Revisiting Content model storage

Hi everyone, For this week's office hour, we'll be revisiting the 2015 proposal to change content model storage[1] (see also T105652). The RFC describes the problems it is solving: > * The content model and format of a revision is stored as NULL if it >is the default. This makes changing

[Wikitech-l] 2016W32 ArchCom-RFC meeting: Wikitext

Hi everyone, This week's office hour: Wikitext! This discussion is intended to be a continuation of the "Loosing the history of our projects to bitrot." thread. Coren stated the work in front of us very well at the start of it. > You know, this is actually quite troublesome: as the platform

Re: [Wikitech-l] Loosing the history of our projects to bitrot. Was: Acquiring list of templates including external links

On Wed, Aug 3, 2016 at 8:48 PM, Subramanya Sastry <ssas...@wikimedia.org> wrote: > On 08/03/2016 07:17 PM, Rob Lanphier wrote: >> In our planning meeting (E250), we discussed this issue as a >> possibility for next week's ArchCom office hour (E259). We don't >> (yet)

Re: [Wikitech-l] Loosing the history of our projects to bitrot. Was: Acquiring list of templates including external links

On Mon, Aug 1, 2016 at 10:15 PM, Subramanya Sastry wrote: > When [a detailed list of stuff is] done, it become far more feasible to think > of defining > a spec for wikitext parsing that is not tied to the internals of mediawiki > or its extensions. At that point, you

[Wikitech-l] 2016W31 ArchCom-RFC meeting:

Hi everyone We have another ArchCom-RFC IRC office hour coming up tomorrow. This week, we plan to discuss what parts of the notification infrastructure in Echo we can/should move into MediaWiki Core (T128351). Brion is shepherding this RFC, and pointed out on the task that we need "good enough

Re: [Wikitech-l] Loosing the history of our projects to bitrot. Was: Acquiring list of templates including external links

On Mon, Aug 1, 2016 at 1:56 PM, Gergo Tisza <gti...@wikimedia.org> wrote: > On Mon, Aug 1, 2016 at 1:01 PM, Rob Lanphier <ro...@wikimedia.org> wrote: >> On Mon, Aug 1, 2016 at 12:19 PM, Gergo Tisza <gti...@wikimedia.org> wrote: >> > Specifying wikitext-html co

Re: [Wikitech-l] Loosing the history of our projects to bitrot. Was: Acquiring list of templates including external links

On Mon, Aug 1, 2016 at 12:19 PM, Gergo Tisza wrote: > Specifying wikitext-html conversion sounds like a MediaWiki 2.0 type of > project (ie. wouldn't expect it to happen in this decade), and even then it > would not fully solve the problem[...] You seem to be suggesting

Re: [Wikitech-l] Loosing the history of our projects to bitrot. Was: Acquiring list of templates including external links

On Mon, Aug 1, 2016 at 9:51 AM, Subramanya Sastry wrote: > On 08/01/2016 11:37 AM, Marc-Andre wrote: >> Is there something we can do to make the passage of years hurt less? >> Should we be laying groundwork now to prevent issues decades away? > > > One possibility is

Re: [Wikitech-l] BetaFeatures grafana dashboard

On Fri, Jul 29, 2016 at 11:14 AM, James Forrester wrote: > > On 29 July 2016 at 02:54, Addshore wrote: > > > Recently WMDE started rolling out the RevisionSlider beta feature to a > > handful of wikis. > >[...] > >

[Wikitech-l] 2016W30 ArchCom-RFC meeting: authenticated key-value store

Hi everyone In our upcoming ArchCom-RFC IRC office hour meeting, we plan to discuss T128602, which discusses how to implement an authenticated key-value store in MediaWiki. Dmitry Brant wrote the original RFC, and Brad Jorsch refined it, listing out many questions on the Phab task (e.g. Action

Re: [Wikitech-l] How widely is Flow being used?

On Thu, Jul 21, 2016 at 4:19 PM, Pine W wrote: > > I believe that Flow is being used on an opt-in basis on Wikidata and > Catalan Wikipedia, and is used on user talk pages by default on MediaWiki. > > Is that correct? > > Are there any wikis other than MediaWiki where Flow is

[Wikitech-l] 2016W29 ArchCom-RFC meeting: Plan for a cross-wiki watchlist back-end

Hi all, The plan for next week's ArchCom office hour is to discuss T126641: [RFC] Devise plan for a cross-wiki watchlist back-end. There's been a fair amount of discussion already on T126641 which is trying to sort out the following questions: * Is keeping a central table of all recent changes

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

On Tue, Jul 12, 2016 at 8:02 AM, Brad Jorsch (Anomie) wrote: > One simple method: assign the numeric IDs by making the numeric ID column > auto-increment, and insert the model strings into the table as needed. > PageAssessments uses this model for tracking its project

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

On Tue, Jul 12, 2016 at 1:40 AM, Daniel Kinzler wrote: > Do we really want to manage something that is essentially configuration, > namely > the set of available content models and formats, in a database table? How > is it > maintained? > > For context: > * As per

[Wikitech-l] 2016W28 ArchCom-RFC meeting: image and oldimage tables

Hi all, The ArchCom-RFC office hour is coming up soon (Wednesday, 21:00 UTC, 2pm PDT, 23:00 CEST). Our topic: image and oldimage tables (which are an artifact from when we had "cur" and "old" tables). Rumor has it that it was discussed at the 2011 Amsterdam Hackathon Phab task:

[Wikitech-l] 2016W27 ArchCom-RFC meeting: programming languages in MediaWiki

Hi everyone, This week, here's the planned agenda for the ArchCom office hour: ArchCom-RFC office hour 2016W27: 2016-06-29: E226 (E66/42)[1] - T136866: Improve the per-programming-language listings for our tools[2] - Let's figure out how newcomers should identify programming

Re: [Wikitech-l] Crediting the work of our community members

On Tue, Jul 5, 2016 at 10:33 AM, Brion Vibber wrote: > On Mon, Jul 4, 2016 at 9:06 AM, Jon Robson wrote: >> I've created the following 2 actionable tasks: >> https://phabricator.wikimedia.org/T139300 >> https://phabricator.wikimedia.org/T139301 >> >> I

Re: [Wikitech-l] μRfC: Requiring 'curl' PHP extension for MediaWiki

On Wed, Jun 15, 2016 at 1:51 PM, James Forrester wrote: > Right now we have some features that require curl (it's probably the #2 > issue third parties have with installing VisualEditor, for instance, after > mis-matched versions). We discussed [the proposal to start

[Wikitech-l] Plan for 2016W26 ArchCom-RFC meeting: curl? programming languages?

Hi everyone, With Wikimania and associated summer travel, this is going to be a rough week to get everyone together at our usual time for the weekly ArchCom-RFC IRC office hour: There are a couple of RFCs that might make good short-term choices: -

[Wikitech-l] Plan for 2016W25 ArchCom RFC meeting: talk about Markdown support

Hi folks I've made some updates to the [ArchCom status][1] page. In particular, I linked to [the very rough RFC I filed about Markdown][2], where I'm suggesting we develop a strategy around Markdown. The plan we agreed to in [2016W24 ArchCom Planning meeting][3] was to discuss Markdown at [next

[Wikitech-l] 2016W24 ArchCom RFC meeting (2016-06-15)

Hi everyone, We're holding another ArchCom-RFC meeting this week to follow up on the thread Yuri started about T120452. The ArchCom status page is finally up-to-date with last week's info: (and it's quoted below) Links!: This week's

Re: [Wikitech-l] Enabling shared tabular data pages

Let's revive this thread for this week's ArchCom RFC meeting. I'll doll up a more formal announcement as I finish cleaning up some of our notes documents, but for now, the short version: URL: Time: 2016-06-15, Wednesday 21:00 UTC (2pm PDT, 23:00 CEST)

Re: [Wikitech-l] Crediting the work of our community members

On Tue, Jun 7, 2016 at 9:19 AM, Andre Klapper wrote: > Is there a Phabricator task [associated with MediaWiki CREDITS file > membership] so this topic does not get forgotten? Not that I'm aware of. It's easy to get lost looking through the various attempts to

[Wikitech-l] 2016W23 ArchCom RFC meeting (2016-06-08)

Hi everyone, This week's ArchCom-RFC meeting is about T89331 ("Replace Tidy in MW parser with HTML 5 parse/reserialize"). Information about the goings-on of ArchCom continues to exist on the ArchCom Status page: ...and also copied below

Re: [Wikitech-l] Enabling shared tabular data pages

On Mon, Jun 6, 2016 at 6:40 AM, Yuri Astrakhan wrote: > Daniel, I agree about the data/api versioning. I was mostly talking about > features and capabilities. For example, we could spend the next year > developing a visual table editor, implement support for unlimited

[Wikitech-l] 2016W22 ArchCom RFC meeting (2016-06-01)

Hi everyone, We're planning to have our regular ArchCom-RFC IRC meeting in a couple of hours. Phab event: Location: #wikimedia-office IRC channel Meeting type: Problem definition Time: 2016-06-01 Wednesday 21:00 UTC (2pm PDT, 23:00 CEST) The experiment

Re: [Wikitech-l] RFC: Add Content-Security-Policy header to MediaWiki

On Sun, May 22, 2016 at 6:17 PM, Brian Wolff wrote: > Content-Security-Policy (CSP) header is a header that disables certain > javascript features that are commonly used to exploit XSS attacks, in > order to mitigate the risks of XSS. I think we could massively benefit > from

[Wikitech-l] ArchCom-RFC triage meeting later today (22:00 UTC/2pm PDT)

Hi everyone, We're planning on making today's RFC office hour[1] a triage meeting (at my request). The agenda I'm planning to use is to (reasonably) quickly step through the list of RFCs in the backlog column of the ArchCom-RFC board. A wiki copy of this is posted on mediawiki.org[3], which I

[Wikitech-l] ArchCom-RFC status update: 2016-W20

Hi everyone, Here's the ArchCom RFC status update for 2016-W20 [1], which is also available via mw:Architecture_committee/Status [2] = Recent RFC meetings = * ArchCom Planning meeting 2016W20: 2016-05-18: [[Phab:E183]] (E156/7) ** Notes: [[Architecture committee/2016-05-18]] *

Re: [Wikitech-l] Proposal to invest in Phabricator Calendar

> If we're going to be investing money into improving Phabricator upstream... It's really good that we're having a healthy debate about the usability of Phabricator. I've enjoyed working with Phab a lot more than the tools that it has replaced, but it is by no means perfect. We have a role to

[Wikitech-l] ArchCom-RFC status update: 2016-05-11

Hi everyone, The ArchCom-RFC status update from our previous Wednesday's ArchCom meeting is in the mail below. The dedicated wiki page was updated in a far more timely manner than this mailing list: - # Recent RFC meetings

Re: [Wikitech-l] [Mediawiki-i18n] Providing the effective language of messages

Hi everyone, Niklas brought this message[1] to my attention as something that probably deserves more attention than it has gotten, and I trust he's correct. What he said back in April: "I added wikitech-l to CC in hopes that people who have worked on localisation cache more recently would

[Wikitech-l] ArchCom-RFC status update: 2016-05-04

Hi everyone, I've included the ArchCom-RFC status update in this mail below, which now has a dedicated wiki page: Assuming we build the habit, this should be updated weekly. Rob Recent RFC office hours - 2016-05-04:

[Wikitech-l] Last call: on the idea of "last call"

Hi folks, One thing we've implicitly adopted is "last calls" for ArchCom-RFCs. I filed it as an RFC to get it on our workboard: https://phabricator.wikimedia.org/T120164 However, what that means is that we need to have a last call on the "last call" RFC. Obligatory xkcd reference:

Re: [Wikitech-l] Automatic image colorization

On Tue, May 3, 2016 at 2:59 PM, Matthew Flaschen wrote: > 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 >>

[Wikitech-l] ArchCom-RFC status update: 2016-04-27

Hi everyone, Below is the ArchCom-RFC status update for this week. This is copied from the notes for the ArchCom Planning Meeting, available at [[mw:Architecture_committee/2016-04-27]] . One update while I have your attention: on

Re: [Wikitech-l] Rob Lanphier appointed to the Architecture Committee

On Mon, Apr 25, 2016 at 10:32 PM, Tim Starling <tstarl...@wikimedia.org> wrote: > At the previous meeting of the MediaWiki Architecture Committee > (April 20), the members present approved the appointment of Rob Lanphier > to the committee. > Thank you, Tim and the rest

[Wikitech-l] ArchCom RFC update #6

Hi everyone, Here is the RFC status update from last week's ArchCom meeting (E165). This is pretty much what is posted on-wiki [1], where everything has links. Rob Today's IRC session ** April 20 [[Phab:E66/31]] *** T91162: RFC: Shadow namespaces Queue for future RfC

Re: [Wikitech-l] Improving Wikimedia's Code Review process

On Wed, Mar 16, 2016 at 3:47 PM, Jon Robson wrote: > We have two swat windows every day. It's magical... I post a request for a > deploy on a Wiki page and someone deploys it. > > Could we try a similar thing with code review. Code review window (maximum > 1 patch per

[Wikitech-l] RFC meeting (E147): Notifications in core & define an official thumb API

Hi everyone, We plan to discuss two RFCs at the 2016-03-09 RFC Meeting (22:00 UTC on Wednesday): - T128351 RfC: Notifications in core - @brion is shepherding, and would like to confirm

[Wikitech-l] ArchCom RFC triage on Wednesday 2016-03-02?

Hi folks, An ArchCom RFC triage (per ) was penciled in for this past RFC meeting (), but I was out for jury duty and wasn't able to make the push for this or facilitate it if we stuck with my hasty plan. I'm done

Re: [Wikitech-l] Using assignees for RFC shepherd

On Thu, Feb 4, 2016 at 7:08 AM, MZMcBride wrote: > > I'm still not really sure what [the "shepherd" definition in the > Governance RFC > ] means. > The biggest focus seems to be on speed and throughput for the RFC

[Wikitech-l] Using assignees for RFC shepherd

Hi folks, In the ArchCom meeting earlier today, Daniel, Timo, Tim and I discussed the way we handle RFC assignments in Phabricator. Previously, the RFC would frequently be assigned to person writing the RFC. As we try out the Rust model (per T123606 ),

Re: [Wikitech-l] Developer Relations Weekly Summary

On Thu, Jan 28, 2016 at 2:57 PM, Pine W wrote: > Is there, or will there be, a page somewhere that describes the outcomes of > the Developer Summit? > I would love for the working group chairs to make the outcomes available from the main WikiDev16 page:

Re: [Wikitech-l] Close test2wiki?

On Wed, Jan 27, 2016 at 10:51 PM, Ori Livneh wrote: > Ok, understood. Keeping it around costs little. Dan, in case you were > volunteering, please go ahead and document the purpose of test2 on its main > page and/or wikitech -- I think it is a good idea. > > If it is cheap to

Re: [Wikitech-l] Scope of ArchCom

Thanks for articulating this very clearly Faidon! More inline... On Thu, Jan 28, 2016 at 3:11 AM, Faidon Liambotis <fai...@wikimedia.org> wrote: > On Fri, Jan 22, 2016 at 02:30:22PM -0800, Rob Lanphier wrote: > > Ultimately, WMF TechOps has correctly blocked a lot of

Re: [Wikitech-l] Scope of ArchCom

On Thu, Jan 28, 2016 at 11:21 AM, Greg Grossmeier <g...@wikimedia.org> wrote: > > > On 28 January 2016 at 18:53, Rob Lanphier <ro...@wikimedia.org> wrote: > > > > > This is especially true given that ArchComm really has absolutely no > say > > >

Re: [Wikitech-l] Scope of ArchCom

On Mon, Jan 25, 2016 at 9:59 AM, Matthew Flaschen <mflasc...@wikimedia.org> wrote: > On 01/22/2016 05:03 PM, Rob Lanphier wrote: >> >> The reason I want the rename [in T124255 >> <https://phabricator.wikimedia.org/T124255>]: ArchCom is the mechanism >> we

[Wikitech-l] Scope of ArchCom

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

Re: [Wikitech-l] Scope of ArchCom

On Fri, Jan 22, 2016 at 2:08 PM, Alex Monk wrote: > To clarify - are you saying this ([deploying increasingly excellent > software on the Wikimedia production cluster in a consensus-oriented > manner]) is the actual current scope of ArchCom, or are you advocating for > a

Re: [Wikitech-l] Last call on RFC: drop PHP 5.3/5.4 support

On Thu, Jan 21, 2016 at 8:12 PM, Tim Starling wrote: > This is a last call for new arguments and facts related to the > proposal to drop PHP 5.3 and PHP 5.4 support in MediaWiki core git master. > > If you have anything new to say about this issue, please comment on > the

Re: [Wikitech-l] Scope of ArchCom

On Fri, Jan 22, 2016 at 2:58 PM, C. Scott Ananian wrote: > Perhaps you could elaborate on the "WMF TechOps" aspect a bit, either here > in email or on the Phab ticket. It seems that some of the tasks currently > tagged as "RfCs" are actually not ArchCom RfCs (they are >

[Wikitech-l] Meeting scribes for WMF meetings

Hi folks, One thing we'd love to get better at is taking and publishing useful notes from our meetings. An example of that is ArchCom meetings, for which we have been taking notes for a while, but I haven't gotten around to publishing. Another example is our weekly tech Engineering Tech

[Wikitech-l] Governance model for Wikimedia software development (e.g. MediaWiki)

Hi folks, Over the past few weeks (including WikiDev '16) we've had several conversations the Wikimedia software development governance model. For a lot of people, the most important aspect of this is MediaWiki. More generally, though, the scope is about we deploy to Wikimedia sites that we

[Wikitech-l] WikiDev '16 summary

Hi everyone, As many of you know (because you were here), we had the Wikimedia Developer Summit 2016 last week. It was wonderful to see so many of you! Rachel Farrand and Quim Gil ensured we had an excellent venue and had a wonderful opportunity to work together, and the people here had some

[Wikitech-l] WikiDev '16 summary

Hi everyone, As many of you know (because you were here), we had the Wikimedia Developer Summit 2016 last week. It was wonderful to see so many of you! Rachel Farrand and Quim Gil ensured we had an excellent venue and had a wonderful opportunity to work together, and the people here had some

Re: [Wikitech-l] [Wikimedia-l] Community Wishlist Survey: Top 10 wishes!

On Fri, Jan 8, 2016 at 11:07 AM, Bill Morrisson wrote: > I wish to ask if volunteer developers can participate in one of the top 10 > wishes of the community wishlist or can only start working on those wishes > that are at the rest of the list or if volunteer developers

[Wikitech-l] Making our software simple and effective

Hi folks, One thing we're trying to do as we schedule WikiDev '16 is make sure that sessions are solving for one of five problems. One of the problems I've been trying to figure out how to articulate I think I've finally got some wording around, and I'd like your thoughts. The question: "how do

[Wikitech-l] Agenda bashing on Wednesday AND something to bash!

Hi everyone, Quim and I met earlier, and we agreed to a main room schedule for WikiDev '16: That maybe is overstating it a bit; we mainly

Re: [Wikitech-l] Appreciation thread, 2015

On Thu, Dec 10, 2015 at 8:33 AM, Vituzzu wrote: > *Wikidata developers which turned into solid reality one of the most > dreamlike ideas of our universe > +thousands to this. If I started on the full list of stuff I should say "thanks" for, I might never get around to

Re: [Wikitech-l] Who owns (or should own) OOjs UI?

On Thu, Dec 10, 2015 at 5:40 PM, Jon Robson wrote: > [OOjs UI ownership] might be a good discussion for the dev summit? Perhaps. I'd say the idea in Phab. It's obviously way past the scheduled date for submissions[1], but the schedule isn't etched in stone, and it might

Re: [Wikitech-l] Ideas for tech-related IdeaLab Campaigns?

Hi Chris, I wonder if we can use Phabricator as an incubator for IdeaLab proposals? We already have the #possible-tech-projects tag in Phabricator [1], which seems like a sensible place to discuss the ideas amongst the people who have ideas in this area. I know there is some cynicism about the

[Wikitech-l] Procedural updates to the RFC process (Re: Objections to PHP 5.5 version requirement)

On Wed, Dec 2, 2015 at 6:32 PM, Tim Starling wrote: > On [T118932], I proposed a process whereby the RFC will be reopened > for review if any existing Phabricator user will second the motion. If > you do object, please register your objection on Phabricator. > > In the

[Wikitech-l] RFC Meeting on #wikimedia-office IRC channel (T118517)

Hi folks, RFC meeting this week - usual time and place: - Location: #wikimedia-office IRC channel - Time: 2015-12-02, Wednesday 22:00 UTC (2pm PST ) - Agenda: - T118517: [RFC] Use for media

Re: [Wikitech-l] RFC meeting: Minimum PHP version

On Sat, Nov 28, 2015 at 1:35 PM, Marcin Cieslak <sa...@saper.info> wrote: > On 2015-11-24, Rob Lanphier <ro...@wikimedia.org> wrote: > > [regarding discussion about <https://phabricator.wikimedia.org/T118932>] > > The main task this week is to plan out what w

[Wikitech-l] Ending RFC review meetings a little early

Hi folks, One idea that achieved consensus here at WMF, but was never discussed publicly (that I'm aware of) is the idea that meetings should use the Google Calendar speedy meeting option.[1] Since we didn't have a public discussion of this, it's technically not the standard for RFC review

[Wikitech-l] RFC meeting: Minimum PHP version

Hi folks, This week's RFC review meeting is scheduled for Wednesday, November 25 at 2pm PST (22:00 UTC). Event particulars can be found at The main task this week is to plan out what we will define the minimum PHP version to be for MediaWiki 1.27 (the

[Wikitech-l] WikiDev '16 working areas

Hi everyone, I mopped up a bunch of Brion's time and expertise earlier this week, did some futzing, discussed it a little with ArchCom, and and came up with a set of working areas that are reflected on Phab[1] and on mediawiki.org[2] Here's the list that's posted in Phab: - Content format

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

Hi Gilles, Thanks for leading this! My reading of your agenda leads me to believe that this is intended as a "problem solving" meeting, as described in User:RobLa-WMF/Meetings#Taxonomy. To quote that article: *Problem-solving* - Discuss a problem that we don’t know how to solve. >

[Wikitech-l] RFC meeting tomorrow about EventBus

Hi folks, I wanted to let everyone know about the ArchCom RFC discussions we're having on IRC in the #wikimedia-office channel. We're having both a special one tomorrow, and the regularly scheduled one Wednesday UTC. Tomorrow, we have Phab event E86 scheduled to discuss Task T88459

[Wikitech-l] RfC reviews meetings(!) this week:

Hi everyone, We have our usually scheduled RfC review meeting on IRC coming up tomorrow. At this meeting, we plan to discuss the following RfCs: * T112553: Integrate the Virtual Rest Service (VRS) into core * T90914: Provide semantic wiki-configurable styles for media display We anticipate the

[Wikitech-l] WikiDev16: Problem-solving, field narrowing and consensus

Hi folks, As you saw, the initial call for participation for WikiDev16[1] calls for session proposals to be in fairly early (due October 2). Many people have already submitted proposals.[2] It's encouraging to see this early activity for this. Let's make sure we plan to talk about what needs

[Wikitech-l] Development policy around database/SQL use

Hi folks, Executive summary: T108255 is the default option for our Wednesday RfC review (E66)[0]. As part of improving our database use, we need to start gating our code review on better shared norms of SQL correctness. We need to enable strict mode, cleanup/enforce primary keys (T17441), and

  1   2   3   4   5   6   >