Also a shared understanding of who the users/stakeholders are? Ie, should the WMF target MediaWiki the product for other WMF developers? For all developers within the Wikimedia movement? For all MediaWiki developers, period? And if the WMF does not do that, should someone else? (Admittedly that's a large enough topic for a separate discussion.)

@Tgr yea, that ties in with the MediaWiki Foundation topic. You are right that there should be some room here to talk about who the users of the platform are. To me, the simplistic answer is: extension authors and other developers of "vertical" features.

They are users in the general sense, sure. The question is, are they part of the target audience of whatever management structure would hopefully result from the discussion? In the end, that is a movement strategy question: should the Wikimedia movement spend resources on supporting MediaWiki users who are not part of of the movement? Historically, the answer was no (or at least, spending very little - the WMF does pay for some stuff which is not really useful for Wikimedians, such as MW release management). If you want to initiate a discussion about changing that, the timing seems right (with the movement strategy discussion ongoing), but it's worth to be explicit about it.

I think this session has more to do with TechCom and the Technology and Product departments than with Developer Relations.

@Tgr my intention is mainly to start considering ourselves (payed WMF and WM* staff) users of the mediawiki plattform. 3rd party developers should also be considered users, but I agree that support for that group is a larger strategic discussion.

At the ArchCom office hour on December 21, we discussed some questions that may be relevant to this sessions. See the meeting log: https://tools.wmflabs.org/meetbot/wikimedia-office/2016/wikimedia-office.2016-12-21-22.00.log.html

To the owner of this session: Here is the link to the session guidelines page: https://www.mediawiki.org/wiki/Wikimedia_Developer_Summit/2017/Session_Guidelines. We encourage you to recruit Note-taker(s) 2(min) and 3(max), Remote Moderator, and Advocate (optional) on the spot before the beginning of your session. Instructions about each role player's task are outlined in the guidelines. The physical version of the role cards will be made available in all the session rooms. Good luck prepping, see you at the summit! :)

Note-taker(s) of this session: Follow the instructions here: https://www.mediawiki.org/wiki/Wikimedia_Developer_Summit/2017/Session_Guidelines#NOTE-TAKER.28S.29 After the session, DO NOT FORGET to copy the relevant notes and summary into a new wiki page following the template here: https://www.mediawiki.org/wiki/Wikimedia_Developer_Summit/2017/Your_Session and also link this from the All Session Notes page: https://www.mediawiki.org/wiki/Wikimedia_Developer_Summit/2017/All_Session_Notes. The EtherPad links are also now linked from the Schedule page (https://www.mediawiki.org/wiki/Wikimedia_Developer_Summit/2017/Schedule) for you!

Notes from this session: https://etherpad.wikimedia.org/p/devsummit17-platforms-are-products

In T149533#2956629, @greg wrote:

• Charter for the Arch Committee
  • Session happened on Wednesday, https://etherpad.wikimedia.org/p/devsummit17-role-of-archcom

That summary is at https://www.mediawiki.org/wiki/Wikimedia_Developer_Summit/2017/Role-of-ArchCom