Many of the usual IRC participants are traveling to Jerusalem for the Wikimedia Hackathon 2016 and will be unavailable at this time.
See the Architecture meetings page for more general information about this meeting (also: Phab query: list of upcoming RFC meetings, Phab query: list of all RFC meetings).
My understanding is that TechCom decided to temporarily suspend these meetings at the 2016-03-23 ArchCom meeting. Since I'm not traveling to the Hackathon this year, I think this timeslot might be a good opportunity to have a working session on the RFCs that are assigned to me to shepherd:
It won't be a time to declare "this has ArchCom consensus" on any of these, but I think it'll be a good opportunity to discuss these, and maybe move one or more of them closer to resolution. Thoughts?
T126605 Create Wikimedia equivalent of Rust's Moderation subteam
See my comment there. Also, people who would be interested in this will be at or travelling to the Hackathon in that timeslot.
Fair enough. I'll remove that from the list so as to not bifurcate the conversation. My intention is to ensure we keep momentum going on TechCom-RFC s generally, and I quickly offered up the list of the RFCs I'm shepherding.
Here's what remains:
It looks like @Ckoerner booked and announced something on #wikimedia-office that possibly overlaps with our normal RFC meetings (unless it's only 30 minutes), and I haven't resolved that conflict yet.
This was a general open discussion, where we ended up spending most of the hour on T119908: [RfC]: Migrate code review / management from Gerrit to Phabricator, and in particular, on the timeline. Here's what we figured out, based on the plan:
We then spent the last 15 minutes or so discussing T123753: Establish retrospective reports for #security and #performance incidents. For that, I said the Security-Team and Performance-Team should make recommendations for what should have a retrospective, and then the parties responsible for the root cause would hopefully often do them.
I mentioned that @GWicke would like to put T129435: RFC: drop support for running without mbstring into last call, which seems reasonable to me. @GWicke will explain that further.