I'm resolving this request: The MediaWiki Engineering Group will take on stewardship for CentralAuth, supported by Security-Team (cc @acooper). @MNadrofsky is going to update the developers/maintainers list. You can use MediaWiki-Platform-Team as tag if you'd like to get things surfaced to the team.

Thanks for taking the time to speak with me! - This is helpful input and was also a good test run to check if these types of questions work well for people. I’m closing this ticket now since it was a Hackathon project. Next step on the research side of things is to create a research plan + related umbrella/epic ticket in July - once the actual work kicks off. The input documented here in the ticket is a starting point and will be enhanced by yet-to-come interviews, review of existing material, and other explorations (which ultimately will end up in a first report).

Talked to 6 people specifically about this set of questions at the Hackathon to gather some initial input. Here are the notes copied over from the Etherpad:

@Aklapper third person should be someone from Dev Advocacy as well, not me. maybe @TBurmeister can help finding a third person - thanks.

My apologies for the delayed update. As a next step, we'd like to document how we use the policy in practice—e.g., looking at stalled cases—to inform potential policy updates before getting this to the CTPO for review and approval. If folks have thoughts on that, input is welcome!

Thanks for your work here! I’m declining this ticket since we’re not proceeding with this specific research approach. A note on Gerrit data as a source: This data gives insights into who contributes via Gerrit in a given timeframe, but unfortunately can’t tell us who is a new developer at Wikimedia or who has stopped contributing to Wikimedia as a developer. The experimental Gerrit newcomer retention dashboard should be viewed with that in mind.

@bd808 and I discussed this a bit. Technical Engagement can offer to help with simplifying the ingestion pipeline of APIFeatureUsage, and work on it likely early in the next quarter.

@Aklapper this is now a task for July-Sept, as discussed during quarterly planning. Apologies for the delay in following up here on the ticket. Melinda will be the assignee of this ticket.

Hey @TJones @Gehel, as you're doing this session as a team, do you have a need for an extra facilitator? If so, we'd try to get you one, or I'd join!

Hey @Legoktm Not all of TechCom’s former responsibilities - or perceived responsibilities - are routed through the new Tech Decision Forum. One of these is the Gerrit Privilege Policy. Those types of decisions are listed in the technical decision type matrix, along side with new responsible parties. “Ownership” means that the team is responsible for ensuring process continuity for Gerrit Privilege requests in the post TechCom world, and to step into TechCom’s former role where required. Handling privilege requests is in most of the cases a self-running system supported by many - Gerrit Privilege policy applies. This ticket explores what needs to be done to make sure the process always works - I.e. in cases where there is not enough input, or not a clear outcome, or when no one acts on a positive decision (which I’d assume, is seldom the case, but we should plan for it regardless). The other aspect that needs discussion is which process we should establish for making changes to the Gerrit Privilege Policy in the future.

approved, thanks!

approved, thanks!

From the sync with @jwang today:

OK from my side!

For the record, https://www.mediawiki.org/wiki/Communication#Blog is updated.

In T243401#6010189, @Aklapper wrote:

@Bmueller: I apologize that contacting me via Phab or email works quite well, unfortunately. ;)

ähm -- I meant "after the email to Wikitech etc. is out" ;) - but should be ok - Sarah planned to send the announcements out in PST morning (= in 3-4 hours).

@Aklapper: "Update sidebar link on mw.org to point to new tech blog at https://www.mediawiki.org/wiki/MediaWiki:Blog-url" &
"Add an item to https://www.mediawiki.org/wiki/Template:MediaWiki_News" requires admin rights. Could you take over those 2 items? Will work on the rest today.

Hi @CCicalese_WMF, no, @eprodromou has not discussed this with Technical Engagement yet. My understanding was that the plan was not to duplicate documentation or replacing wikitech or MediaWiki.org, but providing a static/simple dynamic site that directs people into existing documentation, and also focuses on APIs only. Could you provide more context?

Hey @faidon yes, you're right and that's the plan :-) @srodlund will create a task, probably today/tomorrow.

Notes from the session:

In T234661#5588306, @Tgr wrote:

In T234661#5584790, @Bmueller wrote:

@Tgr, would you be interested in helping to run the breakout group?

Sure!

@Amire80, yes. Ideally, we'd use a part of the first 20 min ("Intro") to provide an overview on known issues to get everyone on the same page. We should also add links to the outcome of sessions that cover aspects of this topic to the pre-reading list, so that we can build upon previous discussions in the breakout groups. Let's talk about this in more detail next week, when the session plan is finalised and session leaders can start to work on their sessions :-)

@hashar, looks like Fisch will be back in time, will add both of you as session leaders to the task description. :-)

Thanks @Tgr! @Amire80, the goal of this session here would be to discuss a variety of questions, and come up with a list of recommendations and concrete ideas to improve developer productivity in the area of templates, modules, and gadgets. (See also Tgr’s list) Brainstorming technical solutions for global modules and gadgets only/specifically would make an awesome follow up session in the unconference part of the conference though, if you are mainly interested in that. Also - @Tgr, would you be interested in helping to run the breakout group?