Talk:Wikimedia Platform Engineering

Collapsable section for the backburner projects
Hi Guillaume...this is a wonderfully useful page now! One suggestion: make the section for backburner projects collapsable, defaulting to collapsed. I thought about moving it to a subpage, but that seems like just a little too much friction. Hopefully the template voodoo involved in making it collapse nicely doesn't involve the lives of too many small animals ;-)  -- RobLa-WMF 02:32, 10 November 2011 (UTC)
 * Good idea; I've simply created an alternate header with the appropriate classes. I've also added it to "recently completed projects". guillom 07:05, 10 November 2011 (UTC)

TODO: add indiv "what is PE" blog posts, open positions
A note for whoever wants to do it, or for me when I return from illness: it would be nice to add links to the individual "what is platform eng" posts, and to open job positions. Sumana Harihareswara, Wikimedia Foundation Volunteer Development Coordinator 16:43, 4 January 2012 (UTC)

Engineering Community Team/Group/Support/Leaders/Shepherds/Gardeners/Mentors....
Guillaume renamed our team for consistency; since people at Wikimedia Foundation are accustomed to calling the team "Engineering Community Team" (when they don't remember it as "TLDR") I think it's better to keep the inconsistency instead of relabeling again, and I think "support" is not quite the right word for a new label. So I'm switching it back to Team for now and am happy to chat about what the right term should be. Sumana Harihareswara, Engineering Community Manager (talk) 06:35, 1 September 2012 (UTC)

Re: [Wikitech-l] Org changes in WMF's Platform Engineering group
Will the "Availability" team be responsible with providing "uptime" metrics and similar for the Wikimedia projects? --Nemo 06:51, 25 March 2015 (UTC)

Phabricator budgeting
Hello, this situation with Phabricator is not sustainable: https://phabricator.wikimedia.org/project/sprint/board/6/query/open/ As I said multiple times in teampractices and elsewhere, we need some budget to be set for Phabricator development. A possibility is to assign/hire a developer to work upstream, but it's probably both cheaper and faster to hire Phacility to fix the bugs we upstreamed as well as to triage/upstream/fix our local reports. --Nemo 10:59, 20 April 2015 (UTC)
 * With the reorg, this is getting even more confusing. The Phabricator team is now split across "Engineering Community" and "Release Engineering" (+ops => Infrastructure) which are in two different departments. Who is responsible for Phabricator budgeting now? Lila directly? --Nemo 15:01, 31 May 2015 (UTC)